Multiple Vinted accounts
What is isolated and what is not
This is the part nobody reads until they hit the problem. Spending five minutes on it now will save you from wondering why a setting "does not apply to the right account".
General rule
What goes to the dashboard is isolated per account. What stays in the browser is shared per Chrome profile.
Isolated per Vinted account
Everything stored on the Vintedge side carries the account it came from:
- sales, purchases, wardrobe items, promotions;
- conversations and messages;
- listings published through the Poster, and their account templates;
- agent statuses and activity logs;
- analytics, invoices, accounting, expenses.
On the dashboard, the account selector filters all of it. So you can compare two shops, or look at only one, with no risk of mixing them up.
Shared within the same Chrome profile
These items live in your browser, not on our servers. They are therefore common to every Vinted account used in that Chrome profile:
| Item | Concrete consequence |
|---|---|
| Repost settings | Your price, image and title rules apply to every account in the profile |
| Auto-Repost settings | The repost and price-drop intervals are shared |
| Favorites message templates (local) | The same message goes out from any account |
| Message quick replies | Shared |
| Shipping label settings | Text source, size, position: shared |
| Purchase confirmation rating and comment | Shared |
| Index of favoriters already contacted | Someone contacted from one account is treated as contacted for the other accounts in the profile |
| Today's repost counter | Shared across the profile |
| Language, theme, date format | Shared |
The two traps to know about
1. The panel lists after switching account
The Wardrobe, Purchases, Sales and Messages tabs keep the previous account's data in cache. You think you are seeing a mix: it is just a display that has not been refreshed yet. Click Refresh.
2. Favoriters already contacted
The Favorites agent never contacts someone it has already contacted. Since that
index is local to the Chrome profile, a person contacted from maison-lila will
not get a message from atelier-nord if both accounts share the same Chrome
profile.
Depending on your point of view, that is a protection (the buyer does not get two near-identical messages from two shops) or a limitation. If you want each shop to have its own contact memory, give it its own Chrome profile.
What follows from all this
This is the real reason behind the "one browser profile per account" recommendation. It is not only about running the agents in parallel: it is what gives each shop its own settings and its own memory.
| Setup | Data | Settings | Contact memory | Agents in parallel |
|---|---|---|---|---|
| One profile, alternating sessions (discouraged) | Isolated | Shared | Shared | No |
| One profile per account | Isolated | Specific to each account | Specific to each account | Yes |
What about the dashboard?
Some dashboard settings are deliberately per account: the Poster's account templates, for instance, define a distinct listing style for each shop.
Others are global to your Vintedge account: tax regime, invoice templates, monthly revenue target, SKU settings. They concern your business, not one particular shop.