The subtitle says it before anything else:
Prices as of the last check, never live — last checked {quand}. A price shown here is at most 15 minutes old. That line never folds away, on purpose: a watch screen that hides the date of its last check makes you believe its prices are from right now.
The watchlist in List layout: one price drop, one item on sale, one under review, one sold.
What you are looking at
The screen's twelve controls, numbered.
The life of a watched item
This is the heart of the screen: what REGA allows itself to say about an item, and on what proof.
Every status chip carries that sentence as its tooltip: hover it rather than guess.
Under review and Hidden by the seller look alike and are opposites. Two witness items, compared field by field on 27/07, carried exactly the same hiding markers and differed on one point only: Vinted allowed the transaction for one, not for the other. A Hidden by the seller can be bought right away through its link; an Under review gets queued.Reading a row in three seconds
The listing title is a direct link to Vinted (
↗). Clicking the title opens Vinted; clicking the card opens the details inside REGA.
The Checks and favourites drawer
The button (marker 6) opens two panels, folded by default.
The CHECK banner
It carries, in order: the state (Running…, No check yet, or Last checked {quand}), the load (every item is up to date or {n} items waiting), the rhythm (one check every {duree}), and the Check now button — help: Check the price and availability of the watched items.
What can refuse “Check now”
What can refuse “Check now”
- A check is already running:
Check skipped — a check is already running - Everything was checked less than a minute ago:
Check skipped — everything was checked less than a minute ago
What it answers when it works
What it answers when it works
Checked — {n} items{suffixe}, where the suffix adds up what changed: {n} price drops, {n} listings vanished, {n} with no answer.If you read “checks slowed ×N”
If you read “checks slowed ×N”
The banner shows
checks slowed ×{facteur} and {n} behind, with this explanation: The watch can serve {capacite} checks per hour; these items ask for {demande}. None is lost, they are served more slowly: the real interval is about {reel}.In plain terms: your prices are N × 15 min behind, nothing is lost, and the slowdown is uniform. Simulated over 24 h at 2.8× saturation: 0 item left unchecked, 2 checks of spread between the best and least served.The VINTED FAVOURITES panel
1
Open the drawer
The
Checks and favourites button, to the right of the title.2
Pick the account
The selector only lists connected accounts, and shows their username — never the email address. With no connected account:
Connect an account to import its Vinted favourites into the watchlist.3
Click “Sync”
The button switches to
Syncing…. Note shown: Items already watched are not duplicated.4
Read the report
{n} favourites imported, or No new favourite — they were already being watched, or No favourite to import. On failure: Import failed — {raison} (fallback: the server did not answer).The import goes up to 10,000 favourites and reproduces Vinted’s order: the most recently liked comes first under the
Recent sort.The toolbar
It stays stuck to the top while you scroll.- Sort
- Status
- Filter and price
- Tidy up and search
A single menu, titled
Sort by, ten entries. The trigger shows Sort : {label}.Buying from the watchlist
1
Click BUY on the row
The confirmation button becomes
Queue it instead of Buy if the item is being reviewed by Vinted — and the window title changes from Confirm the purchase to Schedule the purchase.2
Read the confirmation window
Direct purchase:
The purchase goes out immediately. It is real money, with no safety cap.Queued: This item is being reviewed by Vinted. The purchase will be queued and will start automatically as soon as it is reviewed.3
Check the payer
Direct purchase:
Next payer announced: {pseudo} — the account actually used is the one the server assigns at the moment of firing. Queued: With the account {pseudo} — that one really is the account that will pay, hours later if need be.4
Confirm
The outcome is read in the Orders screen, and for a queued purchase in Orders → Under review.
Where automatic buying runs: on our servers — closing the tab does not stop it. The
AUTOBUY pill (marker 4) arms the server; it survives closing the tab, closing the browser, shutting the machine down. The only gesture that stops it is disarming it.The three ceilings, from widest to narrowest
The three ceilings, from widest to narrowest
Purchase ceiling— Settings → BUYING. Applies to every purchase, manual and automatic, on every machine. Empty by default. Once set, it also refuses an item whose price is unreadable.Cap per item— the AUTOBUY panel on the dashboard. Worth 120 € out of the box, and remembered in this browser only.- A filter’s cap — bounds only the automatic buying of that one filter.
The pick-up point — check it once and for all
The pick-up point — check it once and for all
Automatic pick-up point, in Settings, is on out of the box. Switched off, the purchase fails: No pick-up point could be selected for this order. Nothing asks you anything at the moment of paying.Not to be confused with PREPARE THIS CARRIER, in the Accounts screen: that is a real purchase of a few euros, once per account and per carrier, and it is optional — without it the purchase still goes through, about 1.3 s slower. The gain does not add up: it is the seller who picks the carrier, so preparing several widens the share of your purchases that gain that time, never the time gained.If the connection drops while paying
If the connection drops while paying
The payment is never replayed: its outcome is unknown, and replaying it would risk a double charge. You find the real state in Orders.
Making an offer
The window opens at the floor, at −40% of the current price, slider included.- Permanent summary:
{montant} will be offered for {article} with the account {pseudo}. The seller receives the offer immediately, and accepting it closes the sale at that price. - The floor line:
Minimum offer {montant} — Vinted refuses below −40%. - The account is announced as
account set by the buying scope — changeable for this offer, with aChangebutton:Change the account that will send this offer. - The
Send {montant}button sends on the first click: there is no second confirmation.
What blocks the offer, before sending
What blocks the offer, before sending
This item's price has not been checked yet — the offer floor cannot be worked out.Seller unknown for now: it arrives at the next enriched check, and the offer needs it.No account can make an offer — set this in Accounts.
What Vinted can refuse, after sending
What Vinted can refuse, after sending
Offer too low — minimum {plancher} €.— the window then raises your entry to the floor it returned.Listed price missing — reopen the item then try again.Too many offers in a row — wait a moment before trying again.Item not open to offers yet — try again in a few seconds.
A batch of offers
Tick several items: the selection bar appears inside the toolbar, withSelect all, Deselect all, Offer on {n} and Delete the selection.
The confirmation is explicit: Each offer goes out at the floor Vinted accepts (−40%) of the item's current price, one every 5 seconds — that is about {durée}. Beyond twenty items: Your selection contains {n}: only the first 20 will receive an offer.
While sending, the button counts (Offers… {fait}/{total}) and Stop interrupts the batch.
Three shop routines
- Hunting price drops
- Knowing what sells fast
- A wave of offers without being rate-limited
- The weekly tidy-up
1
Filter on the “Drop” chip
It is the only coloured chip in the bar: it carries the number of active drops.
2
Sort by “Drop”
The biggest price drop first — the top of the list is your margin.3
Set your budget in PRICE max
The field applies to the current price. Commit with Enter: the list is re-read.
4
Decide row by row
BUY if the price suits you as it is, Make an offer otherwise. A drop shown here is at most 15 minutes old: that is what makes it usable.Buy, offer, or wait?
The screen’s states
The six restrictions the empty state can name:
status “X”, brand “X”, category “X”, price between {min} and {max} €, price above {min} €, price below {max} €, search “X”.
Our advice
Judge selling speed on “Sold”, never on “Withdrawn”
On our production data, 31 items carried the sold status, only 11 carried the sale marker. REGA steps down a notch on the other twenty. To know whether a model sells fast: sort by
Recently sold and count only the Sold chips.Buy the ambers, do not discard them
Measured on 26/07 on 42
Under review items re-probed: 0 withdrawn, 31 still buyable, 9 fully back on sale. Click BUY anyway: the window becomes Schedule the purchase, and the purchase fires on its own at approval, with a 96 h horizon.A “Hidden by the seller” can be bought right away
It has left the Vinted catalogue, but the transaction is still allowed: it is buyable through its link. On a check of 233 items, 8 were hidden and 7 perfectly buyable. Do not wait for it to “come back”.
A drop shown here is at most 15 minutes old
The rhythm is flat: 15 minutes for every item, whatever its age. That is what makes a drop usable for arbitrage. No point re-clicking
Check now: a 60 s floor per item applies to the manual button too.Change account for a batch of offers
20 offers at most, one every 5 seconds, quota per account — and it is the purchases’ quota. In the offer window,
Change picks the account for this offer only: split your waves, and keep one account at rest to buy with.Import your favourites instead of re-clicking 200 hearts
Sync goes up to 10,000 favourites and respects Vinted’s order. Then set the periodic sync in Accounts → Favourites: 15 min, 30 min, 1 h, 3 h, 6 h, 24 h. It is off out of the box.Tidy up — the list never empties itself
The sidebar counter and the
All chip include finished items. The three TIDY UP buttons are the only way out. Remember that removal takes the price history with it and cannot be undone.Before “Select all”, read the grey line
Select all only takes what the current filter lets you see. The screen warns you: {n} watched items outside this view — not affected. To treat everything at once, clear the filters first.Do not tidy up “to speed things up”
At 253 items, the watch serves 1,012 checks per hour out of 14,400 possible. Saturation only arrives around 3,600 items, and when it does, it is uniform: nothing is abandoned. Look at the
×N factor instead, it will be more useful.Hover: the tooltips carry the facts
Checked {quand} gives the full date, the rhythm and Next check in {duree}. The ♥ gives Peak observed: {n} favourites. The price of a gone item warns: Last price seen before the listing left the market — this is not a confirmed sale amount.A “Price only” row is repaired row by row
With no seller read, the
Make an offer entry does not even exist. Open that row’s ⋯ menu and click Check now: the next check brings back category, favourites and seller.Decide WHO pays before clicking
On an immediate purchase, the account shown is only an announcement — the server assigns at the moment of firing. If a specific item must go out from a specific account, set the buying scope in Accounts first, then check the account actually used in Orders.
Find an item, and check what it really is
The
Filter by brand or title… field also accepts the item’s identifier: that is the fastest route when you have the Vinted link in front of you. And before committing money, Search the image (Google Lens) opens the listing’s photo on Google Lens — to identify the model, or to compare.What surprises people
The feed heart stays lit after a removal made here
The feed heart stays lit after a removal made here
Removing an item from the watchlist does not switch off the heart on its feed card. Symmetrically, an imported favourite lights no heart in the feed. The watchlist is the one that counts.
After a reload, a queued item shows BUY again
After a reload, a queued item shows BUY again
The queuing is properly recorded on the server — it is only this page’s button that does not remember it after a reload. The durable truth is in Orders → Under review.
A network incident never writes “gone”
A network incident never writes “gone”
A check that does not succeed leaves the status as it is — it does not even count as an absence. It takes two checks with no answer to conclude a departure. One is enough on an item already
Under review or Hidden by the seller, where the absence is a second independent signal.An item gone during its review is never called sold
An item gone during its review is never called sold
It was not buyable: a sale is excluded by the measurement. It therefore leaves the watch without that word, and the Orders screen files it under
Check failed.A sold item keeps its page for a long time, a withdrawn one vanishes at once
A sold item keeps its page for a long time, a withdrawn one vanishes at once
Measured: four items sold 39 to 51 minutes earlier, and five others 11.9 hours earlier, still answered with their sale marker. A withdrawn listing, on the other hand, stops answering. That is why a sudden disappearance reads
Withdrawn and not Sold.The search is local, the filters are on the server
The search is local, the filters are on the server
Emptying the list with the search field depends on no toolbar setting. It is the most confusing of the six cases: if the list looks empty for no reason, clear the search field first.
The screen only refreshes if the tab is visible
The screen only refreshes if the tab is visible
The list reloads on its own every 20 seconds, but only when the tab is in the foreground. A machine left open overnight asks for nothing — it is the watch on our servers that keeps checking, not your browser.
The Grid or Table layout is forgotten at sign-out
The Grid or Table layout is forgotten at sign-out
The choice is remembered in this browser only, and it is cleared when you sign out. On another machine you start again in
List.An old item's thumbnail can disappear
An old item's thumbnail can disappear
Vinted’s image addresses expire. Rather than a broken icon, REGA shows a grey frame. A photo arrives about 1 second after the card anyway, and measured coverage tops out around 83 to 88%: a card with no photo is a normal case, not a failure.
Re-clicking the heart on an already watched item resets nothing
Re-clicking the heart on an already watched item resets nothing
Neither the reference price, nor the date it was put under watch. The drop keeps being counted from day one — which is what you want.
“Watched for” is not the listing date
“Watched for” is not the listing date
The date Vinted publishes is reset every time an item is relisted — up to 40 days of difference on a single page. REGA dates from the first day it saw the item, and announces it with a
≈. In the same way, Sold in under {duree} is a maximum, and Stayed on sale at least {duree} a minimum.On a phone
The watchlist on a phone: the toolbar folds behind “Refine”.
What changes
- The
List/Grid/Tableselector is not shown: the grid needs 760 px, the table 1100 px. We do not offer a dead button. - Brand, category, price bounds and the
TIDY UPbuttons move behindRefine. - The status chips scroll horizontally.
- The card reorganises into three rows: identity, then price and purchase, then the times.
- Navigation moves to the bottom:
Feed,Filters,Orders,Tracked,More.
What does not change
- Sorting, the
Allchip and the search stay directly accessible. BUY, the⋯menu and the details view work identically.- The subtitle keeps announcing the date of the last check.
- Touch targets are at least 44 px: the sort menu is usable without zooming.
The limits, said plainly
Going further
The dashboard
The live feed: it is the heart on a card that fills the watchlist.
Orders
Where a purchase launched from here lands, queued ones included.
Accounts
The buying scope, and the periodic favourites sync.
Settings
The
Purchase ceiling, the automatic pick-up point and the notifications.