Multiple Vinted accounts
Switch between your accounts
With one browser per account: change window
If each account has its own browser (see Add a Vinted account), there is nothing to switch. You move from one shop to another by changing window, device or profile.
All accounts stay active, and their agents run at the same time. The dashboard brings everything together; the account selector filters the display.
In the same browser: only one account runs
You can also log out of Vinted and log back in with another account, in the same browser. The extension detects it and switches to the new account.
But a browser holds only one Vinted session. The account you leave goes offline:
- its agents stop: reposts, offers, favorites, message sync;
- dashboard actions aimed at it (publication, message, price change…) wait;
- everything resumes as soon as a browser is logged into that account again.
What Revendor reconfigures itself
When the Vinted session changes, the extension updates, without asking you anything:
| Item | What happens |
|---|---|
| Vinted domain | If you move from .fr to .it, calls switch domain |
| Real-time stream | The messages connection is closed and reopened |
| Account link | The new account is attached to your subscription, if it was not already |
| Purchase history | An account never seen before triggers a full import of its purchases |
| Data labelling | Everything sent to the dashboard carries the new account |
| Dashboard actions | Those meant for the previous account are refused here and wait |
What you need to do yourself
Refresh the panel lists. The Wardrobe, Purchases, Sales and Messages tabs still show the previous account's data until the next refresh. Click Refresh in each tab.
Nothing is mixed up: only the display is not up to date yet.
Check before a bulk action. Before a batch repost, look at Settings → Account in the panel to confirm the active account.
The safeguard
An action sent from the dashboard always carries the target account. If the browser is logged into another account, the extension refuses to run it rather than send it from the wrong shop. The action waits for a browser logged into the right account.
That is why a publication can stay "Queued" in the Poster.