Favourites boost
Get favourites on your items through a member exchange — how the queue works and what it asks in return.
Why boost?
The platform promotes what people like: an item with favourites climbs the results and shows up in recommendations. Boosting brings those favourites.
But read on before enabling: this isn't a counter you inflate, it is an exchange between members. Your browser also leaves favourites on other people's items, and that is what gives you access to the queue.
The principle, plainly
While the automation runs, it adds favourites to other members' items from your platform account. That contribution is what gives you access to the queue: your own requests enter it once you have contributed for about twenty minutes. The favourites balance — given minus received — decides your priority: a positive balance is served first, a negative one after everyone else.
Those twenty minutes count as contribution time, not wall-clock time: the wait only advances while the automation runs. Never start it, and your request never leaves. One exception: if there is nothing left to boost for anyone else, your request is released straight away — holding you back would serve no one.
If that exchange doesn't suit you, don't enable this automation. The other two don't depend on it.

How to do it
In the Configuration tab, select the items to push and set how many favourites you want per item — your plan caps that number. Only items with the On sale status are listed: sold, reserved, hidden items and drafts don't appear. Sending the request starts the automation: your browser begins contributing, and your items enter the queue.
Following a request
The My boosts tab lists your requests and their status.
| Status | What it says |
|---|---|
| Queued — 0/10 favourites | Active: it waits for other members' automations to serve it; the count shows the favourites received out of those requested |
| Held until 2:30 PM | Not eligible yet — it is released 20 minutes after the request, at your boost automation's next cycle |
| Leaves at your automation's next cycle | The time has passed: the request leaves with your boost automation's next cycle |
| Will leave when one of your boost automations runs | The time has passed: the request only leaves during a cycle of one of your boost automations, on any of your accounts, and this account's is stopped |
| In progress | Favourites are coming in |
| Done | The requested count is reached |
| Item not found | The platform says the item no longer exists — the request leaves the queue |
Two counters accompany the automation: the favourites balance and the completion rate.
What it changes on the platform
The favourites you give are visible from your account, like any favourite. And since each item you favourite can trigger a notification for its seller, the automation mutes your favourite notifications while it works.
The message "the platform's favourite notifications could not be turned off" flags exactly that case: the boost carries on, but you will get one notification per contributed item.
What the queue guarantees — and what it doesn't
The queue is bounded on the Vintex side: a request is not served instantly, it waits its turn. The number of favourites you can ask for per item is capped — the dialog shows "Subscription limit: N favourites per item" once you hit yours.
Cancelling a request only stops the remaining deliveries. Favourites already received stay on your item, and the favourites you gave to others are not returned — your balance does not go back up.
If it doesn't work
| Symptom | Likely cause | Fix |
|---|---|---|
| "No item on sale" | No eligible item on that account | Put at least one item on sale |
| The request stays on Leaves at your automation's next cycle | The automation has not run since the release time | Let the automation run; the request leaves at its next cycle |
| The request stays on Will leave when one of your boost automations runs | None of your boost automations has run since the release time | Start one, on this account or another: the request leaves during its cycle |
| Item not found status | The platform says the item no longer exists (sold, deleted…) | If it's still on sale, request it again: the request goes back into the queue |
| No favourites coming in | Negative favourites balance | Let it run longer to bring the balance back up |
| A flood of platform notifications | Muting the notifications failed | Mute them manually in your platform settings |
