Your lookout on Vestiaire Collective: arm the radar, set your filters, connect your accounts, and make an offer or prepare a purchase on a listing nobody has seen yet.
This screen watches Vestiaire Collective from the second a listing goes live — while the site’s “New in” page still takes 5 to 10 minutes to show it — and lets you, on every line it finds, make an offer or prepare the purchase from one of your Vestiaire accounts.
How to get here. This screen is not in the left-hand menu yet: you open it by typing its address, /app/vestiaire. Bookmark it in your browser — that is what everyone who uses it daily does.
The Vestiaire Collective screen, radar disarmed: two filters ready, no account connected, no detection — and a red banner left over from an interrupted read.
Starts the watch. Once armed, the button becomes “Disarm the radar” and loses its accent colour: that is deliberate — the accent always marks the gesture that is missing.
2
“Detections” tab with its count
What the radar has found. It is the tab open by default, because it is what you came to see.
3
“Filters” tab with its count
What the radar should keep. Here: 2.
4
“Accounts” tab with its count
Your Vestiaire accounts — the ones offers and purchases go out from. Here: 0.
Under the title, a status line sums it all up at a glance: “Radar disarmed · 2 active filters · 0 usable accounts”. When armed, it starts with “Radar armed” and the dot turns green.
The red banner on the capture — “Request cancelled.” — is not a radar fault. It is what the screen shows when a read it had started did not finish, typically because the page was reloaded or the language switched while it was reading. The next automatic refresh, five seconds later, clears it. A genuine radar outage says something else entirely, and names the radar: see the “The states of this screen” table further down.
On the capture, the three numbers tell a complete story: the radar is not running, two filters are waiting, and no account is connected. In that state, even armed, the radar would detect — but nothing could be bought or negotiated. The Accounts tab says so: “No account: the radar detects, but nothing can be bought or negotiated.”
The arming button is greyed out until the screen has read the radar’s state, and shows … while it switches. Nothing else can refuse arming: if a red message appears instead, the screen could not reach our servers, and the sentence shown says so.Once the state is read, six measurement tiles appear under the title. Hover them: each carries its own explanation.
Tile
What it counts
Tooltip
watch rounds
How many full rounds have been done
“One round = one full read of what is new on Vestiaire.”
listings seen
Everything the radar looked at, kept or not
—
detections
What your filters kept
—
usual delay
The median delay between going live and our discovery
“Time between the listing going live on Vestiaire and the moment we saw it. Fixed at discovery.”
longest delay
The delay nine detections out of ten stay under
“Nine times out of ten, we see the listing in less than this.”
refusals from Vestiaire
The times the marketplace asked us to slow down
“Vestiaire asked us to slow down, or did not answer. A rising figure means listings are getting past us.”
The one tile to keep an eye on is “refusals from Vestiaire”. It turns red from 1 onwards. At zero, all is well. If it climbs, the “usual delay” will climb behind it: listings are getting through.
A seventh tile, in italics, appears for the first five rounds: “starting up: the first listings are the backlog already online”. It exists to save you a false alarm — see tip nº 2.
On Vestiaire, a listing is validated by hand by the marketplace’s staff, roughly an hour after it is submitted. That validation is what makes it publicly exist — and that exact moment is when the race starts.On our test bench, the median delay between validation and our discovery is 6 seconds (nine times out of ten under 13 s, never above 21 s across 108 measured detections). On the armed production path we measured a median of 3.0 seconds over 112 detections, without a single refusal from the marketplace. That gap against the 5 to 10 minutes of the “New in” page is the whole point of this screen.
Two controls appear as soon as the list is not empty:
“Filter” — a dropdown, with “All filters” at the top.
“Search” — a text field, example brand or model.
Search only reads the brand and the title — not the description, not the seller’s name — and it is accent-sensitive. The “Filter” dropdown, for its part, lists all your filters, active or not.
Past 80 visible lines, a banner warns you: {n} detections kept — the {plafond} most recent are shown. Nothing is lost, only the display is capped — drawing 300 thumbnails every 5 seconds would make the screen unusable.
Each line carries, left to right: the thumbnail (a link to the listing), the brand in bold then the title, the price rounded to the euro, and the latency.
Latency is the figure that is worth money. It is written seen in {n} s and turns red past 12 seconds. Its tooltip: “Time between validation by the Vestiaire team and our discovery”. It is fixed at discovery: it will never move again, even if you come back to the line tomorrow.
Below it, a note line: “seller” + their username (and their country), their number of sales if known, the name of the filter that kept the listing, and item in {pays}. When the brand was not recognised, the screen writes “Unknown brand” — never an identifier. When the filter has since been deleted, it writes “deleted filter”.Finally, the “Buy or make an offer” button, which opens the buying panel.
Opening the panel fires four reads in parallel — offer terms, position in the market, seller card, your account list. While they come back, the screen shows “Querying the marketplace…”.
Cheaper than {pct} of the {n} comparable listings. If the comparison rests on fewer than 30 listings, the screen adds “— thin sample”. If it cannot decide, it writes “Position in the market undetermined” rather than invent a figure.
Price and floor
Price {prix} · minimum offer {min}, followed by the gap as a percentage. The floor is served by Vestiaire, never computed here: it sits around 70 % of the price, but we measured 70.690 % and 70.352 % on real items.
Seller card
Username, badges, and three figures — “sold”, “shipped”, “cancelled” — plus “{taux} % of their sales went out on time”, or “Not enough sales yet to judge their dispatch”.
Which account
A “From” dropdown if you have several accounts, otherwise From {compte}. It governs all three gestures: favourite, offer and preparation all go out from the account shown there.
The “What do these figures mean?” button opens the explanations written by Vestiaire itself — we do not rewrite them. When the marketplace says nothing about the seller, the screen admits it: “Vestiaire has said nothing about this seller for now.”
The dropdown resets to the first usable account every time the panel opens, not to your last choice. With more than one account, this is the step you must never skip.
2
“Prepare the purchase (no payment)” — everything but the charge
A confirmation stands in the way first: “Preparing this purchase from {compte} first removes everything sitting in its Vestiaire basket. No payment is triggered.” Then “Empty the basket and prepare” or “Cancel”.
3
Or “Offer” the amount proposed — red button
Confirmation as well: “This offer goes out from {compte} and becomes the floor: you will not be able to offer less, and if the seller accepts, the purchase is committed.” The confirm button repeats the amount.
4
Read the result in full
A successful preparation shows “Purchase prepared from {compte}” — and, always, underneath: “No payment took place.” followed by the sentence saying everything is ready up to the moment of paying, and that payment itself finishes on Vestiaire, because rega does not yet present your card for you.
The yellow line you must not miss. If the screen shows {detail}: their price is part of the amount prepared., emptying the basket failed: the amount prepared contains something other than your item. Go and check your basket on Vestiaire before going any further.
“No Vestiaire account is usable. Connect one to carry on.”
The chosen account has signed out
“This account is not connected. Reconnect it to carry on.”
The account has no slot allocated yet
“This account holds no dedicated address. It cannot be connected until one has been allocated to it.”
The listing has gone from the marketplace
“This item was not found on Vestiaire.”
Vestiaire refuses the offer
Vestiaire says: {texte} — the marketplace’s reason, quoted as it stands
The offer did not go out
“This offer could not be sent.”
A refusal from Vestiaire does not sign you out of REGA. It is the Vestiaire connection being refused, not yours: you stay on the screen, the message is red, nothing else moves.
A header card “New filter” with the “Create the filter” button, then one card per filter.Each card sums its filter up in a line: the number of hits (the listings it kept), last {quand} — or “never” —, the number of brands, the price bounds, and the searched text in quotes.
The hit counter is the only thing that tells you whether a filter works. No description of criteria will ever say it for you. One hour after creating it: 0 hits · last never means the filter is too narrow.
Two switches and three buttons per card:
Control
Effect
active
Unticked, the filter is kept but the radar ignores it.
notify
An alert on every kept listing. Handle with care — see tip nº 10.
Edit
Opens the criteria window.
Rename
A “Filter name” field inside the card. Enter confirms, Esc cancels. An empty name is refused: “Give this filter a name so you can find it again.”
Delete
Confirmation inside the card: “Delete “{nom}”? The radar will stop looking for these listings; detections already found stay available.”
With no filter at all, the list shows “No filter.” — and a yellow banner appears at the top of the screen: “No active filter: nothing will be kept. Create one in the Filters tab.”
The preview banner, stuck to the top of the window
“On Vestiaire right now” followed by the number of listings that would match your criteria at this instant. It updates on its own while you tick (“updating…”).
With no criteria: “No criteria: every listing would be kept.”
At zero: “No listing matches these criteria. Most often, two category levels contradict each other.”
Past 10,000: {n}+ — never a bare “10,000”, because the marketplace stops counting there.
A range shows too: Prices seen: from {de} to {a}.
It also warns that “Keywords are not counted here: they are checked at detection time, against the title and the description.”
Category — four levels, and one trap
The tree is rebuilt and the full path is shown (“Women › Clothing › Dresses”). The help text says it: “Universe, then category. Each level is a separate criterion: combining them narrows the filter.”Ticking “Women” then “Shoes (Men)” does not give you the union of the two: it gives the intersection, so zero. It is not forbidden — the preview banner says so immediately.Search shows at most 40 results and says so: {plafond} results shown out of {total}. Narrow the search.
Brands — two behaviours, depending on whether you type
Empty field: the best-stocked brands among what your other criteria already keep, with their listing counts. “The best-stocked brands here. Type to search the whole catalogue.”Filled field (from 2 characters): the search covers the whole directory — 17,530 brands, 13,679 of them active — but without the counts, which are only computed over the listings your other criteria already keep.A selected brand whose name is not known yet shows as “Selected brand”, never an identifier.
Sizes — the most expensive constraint in the form
The consequence is written above the control, before you touch anything: “Constraining size rules out bags, jewellery and watches: the field is missing from 43 % of listings.”With no category chosen, several scales coexist — the screen then offers: “Several scales coexist. Choose a category: only the one that applies will remain.” Scales have no name, only their two extremes: Scale {de} – {a}. That is deliberate: the marketplace does not name them, so we do not name them in its place.
Keywords — and the two settings that govern them
Two lists: “Keywords” (example black leather) where “Every word must be present.”, and “Words to rule out” (example replica fake) where “A single one is enough to rule the listing out.”As soon as either list has something in it, two switches appear:
“Whole word”, whose help says “bag” no longer finds “bagged”. — off by default
“Ignore accents”, whose help says “chine” finds “chiné”. — on by default
And the scope is stated in black and white: “Both settings apply to both lists, and words are searched in the title as well as in the description.”
Origin, active, alert me
Origin: “Any origin” or “Chosen countries”, with a shortcut Add the {n} best-stocked countries.“Active filter”: “An inactive filter is kept, but the radar ignores it.”“Alert me”: “An alert on every kept listing. A broad filter can produce a lot.”And, right at the bottom, the admission we prefer to write rather than let you guess: “Kept listings appear on the Vestiaire Collective screen. They do not join the main feed yet.”
The buttons at the bottom of the window: “Create the filter” or “Save”, and “Clear the criteria”. Next to them, a count — {n} values chosen — or the warning “With no constraint, this filter will keep every listing.”
An “Add an account” card, collapsed by default (“Expand”), with four fields: “Name” (example Main), “E-mail address”, “Password”, and “…or a Vestiaire sign-in code”.
The note under the fields is the most important sentence in this tab: “With a password, the account reconnects on its own. A code alone lasts 30 days, then the account stops.”An account with no password on record cannot be reconnected by our servers — its “Connect” button is greyed out.
Each connected account shows a status line concatenating its address, its ability to buy, and its expiry:
What you read
What it means
“can buy” / “cannot buy”
The account does, or does not, open Vestiaire’s buying pages
“expires in {n} days”, “expires today”, “connection expired”
The expiry of the connection, counted over 30 days
“never connected”, “expiry unknown”
The account has not been connected yet, or the marketplace did not state its expiry
“to reconnect soon”
To deal with before your next session
“no password on record”
The account will stop at expiry, with no way of resuming on its own
Three buttons: “Connect” (greyed out with no password), “Check” (greyed out with no connection, tooltip “This account is not connected — connect it first”), and “Delete”, which asks for confirmation.The verdicts, word for word:
Connection succeeded
“Connected. The connection is to be renewed in 30 days.”
Connection refused
Connection refused. {detail} — by default “Check the password, then try again.”
Check succeeded
“Connected — this account can buy.”
Check failed
This account cannot buy. {detail} — by default “Reconnect it, then try again.”
The radar runs on our servers: closing the tab, closing the browser, or shutting your machine down does not stop it. Its state, however, is not carried from one version to the next: after an update it comes back disarmed, and nothing will warn you.The move: go back to /app/vestiaire after every update announcement, and check the line does say “Radar armed”.
2 · Do not judge the speed while it is starting up
On the first arming, the radar works through the backlog already online: we measured a median of 169 s during the first minute, against 3 s once it settles. That is not a fault, it is catching up.The move: while the italic “starting up” tile is there, ignore the “usual delay”. Give it six watch rounds before judging.
3 · Empty your Vestiaire basket before preparing a purchase
“Prepare the purchase” empties the account’s real basket first — it is written in the confirmation, and it is necessary, because on Vestiaire the basket is global to the account: the amount prepared carries everything in it.The move: keep your REGA accounts with an empty basket. And if the screen shows the yellow line {detail}: their price is part of the amount prepared., stop and check the basket on Vestiaire.
4 · Aim for the floor on the first try
An offer becomes the floor: after an offer of €1,488 on an item priced €1,750, the next minimum offer is €1,488 and no longer €1,225. You can never go back down.The move: the “Offer” button already proposes the minimum amount served by Vestiaire. Do not test the water with an in-between amount: it is irreversible.
5 · Always save the password, never just a code
A Vestiaire connection lasts 30 days and does not renew itself. Our servers can only reconnect accounts that have a password on record; they take care of it on their own, every 7 days.The move: the “…or a Vestiaire sign-in code” field only exists for those who already hold one. In every other case, enter the password.
6 · Click “Check” before a hunting session
A Vestiaire connection can be half valid: on two real connections we measured the same session accepted on the browsing pages and refused on the buying pages. The “Check” button deliberately probes the buying page.The move: before hunting, click “Check” on the account you are about to use, and insist on “Connected — this account can buy.” The “can buy” label in the list is not necessarily recent.
7 · Never constrain size on bags, jewellery or watches
A field that is absent never satisfies a constraint you set. And size is missing from 43 % of listings (model from 79 %). A “Gucci bags” filter with a size ticked will find next to nothing — without saying so.The move: on a leather-goods, jewellery or watch filter, do not touch any size.
8 · Look at the preview banner BEFORE saving
“On Vestiaire right now” gives you, to the second, how many listings your filter would keep. It is the only way to catch a contradiction before it costs you a day of silence.The move: if it shows 0, one criterion contradicts another — most often two category levels. Loosen it before saving.
9 · One hour after creating a filter, read its hit counter
Nothing else will tell you whether a filter works: a description of criteria never says they are too strict together.The move: 0 hits · last never one hour after creation means widen it. Drop the size first, then the colour, then one category level.
10 · Only turn “notify” on for a filter you have already calibrated
On Vestiaire, listings are born at ~24 per minute during the day and 7.2 per minute at night. A broad filter can produce on the order of 35,000 detection lines a day.The move: let the filter run without alerts for a few hours, read its hit counter, and only turn “notify” on if that count is low and known.
11 · Take what you want to keep out the same day
Detections are wiped after 48 hours. The clean-up runs on its own, and nothing warns you beforehand.The move: on a find you want to follow, set the favourite (“Add to favourites”) or open the listing in a tab — the same day.
12 · To stop a filter, untick “active” rather than delete it
Deleting a filter does not delete its detections — it is written in the confirmation — but their note line will read “deleted filter”, and you lose the matching entry in the sort dropdown.The move: unticking “active” keeps everything, and switches back on with one click.
13 · Check the “From” dropdown before EVERY offer
The account shown under “From” governs all three gestures — favourite, offer, preparation. And it resets to the first usable account every time the panel opens, never to your last choice.The move: with more than one account, re-read the dropdown just before confirming. The offer confirmation names the account too: that is your last check.
14 · An offer we “could not record” still went out
If the screen writes Offer sent from {compte}. The floor is now set at this amount. It will not show under “Your offers”: we could not record it., the offer was sent — only our record of it is missing.The move: never replay an offer after that sentence. The floor has already risen; replaying can only cost you more.
15 · Delete the accounts you no longer use
An account left idle keeps its allocated slot; only deleting it frees the slot. If adding an account is refused with “No dedicated address is available for this account.”, that is exactly what is happening.The move: tidy up the Accounts tab before adding a new one.
Three filters keeping the same listing produce three lines. These are not duplicates: each line tells you which filter bit, and you can use the filter dropdown to separate them.
Keywords are searched in the description too
This is the difference that surprises people most in practice: a word buried in a long description brings in a listing you were not expecting. The window says it — “words are searched in the title as well as in the description” — but it is easy to forget.
“Ignore accents” is on by default, “Whole word” is not
And both apply to both lists, the one that includes and the one that rules out. That is different from the Vinted form.
The number next to a value says what you WOULD gain, not what you have
Each count is computed by relaxing its own constraint. With “Gucci” ticked, the brand list still shows Max Mara and its count: that is the count you would get if you also ticked Max Mara.
“10,000+” is not 10,000
Past that, Vestiaire stops counting and truncates. We show the + rather than the bare number, because writing “10,000” would pass a limit off as a measurement. In the same spirit, the position in the market then declines to answer.
Keywords are not counted in the preview
The preview asks the marketplace, which does not search words the way we do: we re-check them ourselves at detection time. Mixing the two would give a believable number that belongs to neither rule.
A value you ticked that is no longer offered stays on screen
And it keeps narrowing. That is deliberate: an active constraint you can no longer see is the most expensive failure mode of a form — so we keep it visible and removable.
Reopening the criteria window starts from scratch
It is torn down when closed. Practical consequence: if your filter carries no country, the origin mode shows “Any origin” again when you reopen it.
Countries are named in the form, two letters in the list
The form writes “France”; the detection line writes item in {pays} with the code Vestiaire gives us. We do not invent a name for a code the marketplace has not translated.
The radar re-sees the same listing every round, and never re-reports it
A listing already detected is not filed again. So you will never see the same line climb back to the top every ten seconds.
A filter created without a name keeps the language of that moment
The fallback name is saved as if you had typed it: created in English, it stays “New filter” even if you switch the interface to French. Renaming it is the only way out.
The same screen on a phone: the arming button moves below the status line, full width.
Nothing disappears. The arming button leaves the right-hand corner and sits under the status line, full width — easier to hit with a thumb. The three tabs stay on a single row with their counts. The measurement tiles wrap onto several rows, and detection lines stack the thumbnail above the text.
A phone is excellent for watching (reading latencies, seeing detections come in) and acceptable for offering. For setting a filter up, the criteria window — eleven sections and a sticky banner — stays more comfortable on a large screen.
We would rather write it here than let you find out halfway through.
Payment finishes on Vestiaire
“Prepare the purchase” goes all the way to the payment intent, and stops there. The screen repeats it on every preparation, including successful ones: “No payment took place.”
No automatic buying on this marketplace
Every committing gesture comes from your click, and a confirmation. The mechanisms specific to Vinted — automatic buying, groups, filter import/export — do not apply here.
Detections stay on this screen
They do not join the product’s main feed yet. The criteria window says so before you save.
“Alert me” does not ring the bell yet
The switch is in place and saved, but the alert does not reach your notification centre yet.
No removing a favourite
You set a favourite from REGA; you remove it from Vestiaire. We would rather not offer a button that would fail.
The radar outage message stays in French
The two radar outage sentences show in French even in the English interface. It is known and fixable.
It also happens that “Position in the market undetermined” or “Vestiaire has said nothing about this seller for now.” show up on a perfectly ordinary listing: both of those come from an extra read at the marketplace, which does not always succeed. Nothing is guessed — the screen would rather say so than show an invented figure, and it blocks neither the offer nor the preparation.
⌘I
Assistant
Responses are generated using AI and may contain mistakes.