Skip to main content
This is the live shop window for everything the radar finds: listings appear the second they are born on Vinted, and a BUY button sits on each one. Everything else in REGA serves this screen.
The REGA dashboard, with the settings panel on the left and the stream of listings in the middle

The dashboard on a populated account: settings on the left, the stream in the middle.

The radar sweeps around 150 listings per second for all customers together. A complete card reaches the screen ~950 ms after the listing is born; its details follow at ~734 ms and its photo at ~1026 ms. You will never watch those numbers go by — what you see is the result.

​
What you are looking at

The dashboard with numbered badges on its twelve main controls

The twelve controls of the screen, numbered.

The Table button (12) is greyed out but still there, and it tells you why it refuses. That is the rule for this whole screen: an unavailable control does not disappear, it explains itself. Always hover before concluding something is broken — on this screen, nearly everything that looks broken carries its reason in a tooltip.
Top left of the capture, the radar’s state: “RADAR ACTIVE”, “RADAR PAUSED” (that is the case here), “RADAR UNREACHABLE”, or simply “RADAR” while it is not known yet.

​
Your first half hour

Check who pays, and with what

In the BUYING ACCOUNT panel, the sub-line must read “connected · ready to pay”. If it reads “not connected — the purchase would fail”, nothing will go through. Unfold the account card (badge 7) and check both blocks, ADDRESS and PAYMENT. Without an address and a card a purchase cannot go through — and the screen says so in plain words.

Set a cap on every filter, not here

Filters screen → open each filter → the € max field. Left empty, the screen warns you once: “No cap: this filter will buy whatever the price.” That is the only cap automatic buying actually reads.

Arm the filter, THEN the AUTOBUY badge

Arming the badge is not enough: each filter is armed separately, in the Filters screen. The list of armed filters is re-read every 20 seconds — after arming somewhere else, give it 20 s before concluding that “it is not buying”.

Buy by hand once

Click BUY on a listing, then follow the line that appears in RECENT PURCHASES (the ⋮ button). That line carries the truth: the account actually committed, and the total debited.

Trigger a detection and check that a line appears

The ARMED badge on its own proves nothing. The only check that counts is a purchase line appearing by itself on the first matching item — with its AUTO badge, “Triggered by autobuy”.

Prepare your carriers (optional)

PICKUP POINT panel → MANAGE ▸, or the Accounts screen. Vinted only remembers a collection point after a first purchase actually paid via that carrier. Once per account and per carrier, a few euros — and after that the purchase goes straight out.

​
The left column — who pays, and with what

It is a column on a large screen. Below that it becomes a SETTINGS sheet called up with ☰ (“Account, autobuy and feed settings”).

​
BUYING ACCOUNT

MAIN ACCOUNT is the only editable setting in this panel: it names who pays. Going back to “Every account · rotation” puts rotation back to work. The members are listed underneath, read-only, with their state:
  • “compte_demo will pay for the next purchase”
  • “compte_demo is not connected — it will be skipped”
  • “compte_demo is excluded from this scope — it will never pay” — an excluded member stays visible and struck through, otherwise the blacklist would be invisible from the very screen where it prevents buying.
Refusals on this setting, quoted as they appear:
  • “Main account unreadable — the server is not answering. Nothing changed.”
  • “Setting out of date — who pays changed elsewhere. The screen shows the current state.”
  • “Main account not saved — nothing changed.”
  • “No account available to pay. Connect a Vinted account in Accounts.”
A feed opened on a group can carry its own buying scope: “A feed group can carry its own scope: it then takes precedence over this one.” If your purchases go out from the wrong account, look at the group first, not at this panel.

​
PICKUP POINT

On our test account the panel shows “state unknown for this account” and a MANAGE ▸ button. Three states are possible, per carrier: The screen explains it without dodging: “Vinted remembers a pickup point for each carrier. When it does, the purchase goes straight out: about 1.3 s saved. Otherwise the point has to be chosen during the purchase — and the purchase is that much slower.”
Preparing a carrier is a real purchase of a few euros, once per account and per carrier: “Vinted only saves a pickup point after a first purchase actually paid via this carrier. This happens once only.” The screen warns first: “This money is really spent.”It is optional — without it the purchase still goes through, simply ~1.3 s slower. And the gain is not additive: the seller is the one who picks the carrier. Preparing several carriers widens the share of your purchases that save those 1.3 s, never the gain itself.
Another setting has a similar name and does something entirely different: Automatic pick-up point, in Settings → BUYING, is on by default and must stay that way. “rega chooses the collection point during the purchase. Turned off, the purchase fails for want of a pick-up point — leave it on.” Turned off, the purchase fails: nobody will be asked anything.

​
AUTOBUY

The panel carries four controls, and only one of the four acts on what really buys.
The “Cap per item” field at 120 € does not bound your purchases. This is the most expensive trap in the product: the only cap visible on the buying screen is not the one that decides. It is 120 € out of the box and it is remembered in this browser only — another machine, a private window, and it is back to 120.
There are three distinct caps, from the widest to the narrowest:
REGA sets no price cap out of the box. That is an explicit decision by the owner of the tool: visibility replaces constraint. If you want a bound, it is set filter by filter.

​
FEED SETTINGS

Two switches, both on in our test account:
  • Auto message on purchase — “sent to the seller as soon as payment goes through”
  • Auto message on cancellation — “sent if the order is cancelled”
If they show “Setting unreadable — the server did not answer”, do not flip them back and forth: it is the reading that failed, not the setting.

​
The toolbar — it governs the whole screen

It acts on the entire screen, never on a single band of listings.

​
The three layouts

“Many listings at a glance, photo first”. One photo is loaded per tile; the others are one click away in the viewer. Four columns are guaranteed as soon as the room exists, and a tile never drops below 224 px. This is the spotting view.
Table refuses on the width actually left for the listings, not on the size of your screen. Measured: at a 1920 px window only 1004 px are left for the listings (panels and margins take the rest) while the table needs 1138 — so it only appears from roughly 2054 px of window.
Widening the window can SHRINK the room available. Measured: at a 1279 px window, 1183 px are left for the listings; at 1280 px only 712 are left, because the left panel comes back. To get Table: fold the side panels away (☰ and ⋮), or move to the detached window ⧉, which docks none of them.
On a phone the selector does not exist at all: “On a phone there is only one layout.” Your choice stays remembered and comes back untouched on a large screen.

​
The rate and the backlog

The figure followed by /min counts the listings the radar found, not the ones painted on screen. Its tooltip says so: “This figure depends neither on the display being paused nor on how many cards are kept on screen.” Four states:
Always read the rate AND the backlog button together. A backlog growing under “radar stopped” does not tell the same story as a backlog growing under a lively stream: the first is a leftover, the second is a stream you paused without meaning to. The backlog button shows “42 NEW”, and caps at “99+”.

​
LIVE — the only pause button

The button switches between LIVE and PAUSED, with a badge counting what is waiting (“12 listings waiting — resume the live stream”, or “No listing waiting — resume the live stream”). There were once three different pause commands on this screen; only one is left. Learn that one and only that one. What freezes the display, besides the button:
  • scrolling more than 40 pixels inside a band — silently, and deliberately: a card slotting in under your cursor as you take aim is a real unwanted purchase;
  • opening a ⋯ menu or the full-screen photo viewer.
Freezing stops the painting, never the detection. Nothing is lost during a pause: listings keep arriving, keep filling in, and automatic buying keeps firing. The band’s badge turns grey and says so: “Display frozen — detection itself carries on”.

​
⧉ The detached window

Opens the general stream in a 560 × 980 window, with no chrome and no side panels. It is the monitoring tool for when you are working on something else — and it is also the shortest path to the Table layout, since it docks no panel at all.

​
Three ways to work this screen

The hunt

Wall layout to spot (four guaranteed columns), then Folder to decide. You stay LIVE and you do not scroll: you let cards come to the top and you take aim. This is the mode where the 40 px of scrolling matter most.

The permanent desk

Two or three bands opened with + Feed, pinned, with the buying scope checked band by band. The layout is remembered: you find the same desk tomorrow morning. Feeds that no longer fit move to tabs and carry on detecting.

Monitoring

The ⧉ window (560 × 980) in a corner of the screen while you work elsewhere, plus automatic buying armed. You stop watching the screen: you watch the notifications and the RECENT PURCHASES lines.

​
Feeds: ”+ Feed”, tabs, groups

Every open feed gets a chip in the top bar — except the general stream, which has none. Each chip carries a state (“paused”, “deleted”), a counter of new items, and a ⋯ menu: “Bring on screen”, “Pin (keep on screen)”, “Unpin”, “Rename”, “Move left”, “Move right”, “Close this feed”.
A feed that moves to a tab is not switched off. The message says it: “One more feed would fall below the readable card width. It stays as a tab and carries on detecting and counting.” Automatic buying still fires there. Do not close it because it no longer fits on screen — pin what you want to see permanently.
They are not the same screen. The sidebar opens a restricted page: a single band, no general stream, no feed bar, and a “See the whole stream” link to get out. It is not remembered — a reload brings you back to the full dashboard.+ Feed adds a band next to the general stream, and that one is remembered.For a permanent desk: + Feed. To look at a group for five minutes: the sidebar.
That is normal, it never had one — its chip repeated word for word the header of its own band a few pixels below. A message told you the moment it left: “The whole stream left the screen — “+ Feed” then “All filters” brings it back.” That is exactly the way back.
Correct. A title you write is your data: REGA never translates it. The original title is “The whole stream”.
The group behind that feed no longer exists. The band stays open so you can decide what to do with it; it does not close behind your back.

​
A card, line by line

The three layouts serve the same content: brand, title (a link to the listing), photos, facts, seller, price, BUY, ♥, ⋯.

​
The tags, in the order they appear

An item that is obviously off-topic in your stream is almost never a filter bug: it is that last tag. REGA would rather show you one card too many than hide a good one — but automatic buying holds off. If you want it, those cards are for buying by hand.

​
The two prices

In the capture, the GUCCI card shows 40 € in large type, then ≈ 44.09 € delivered underneath. These are not two versions of the same number.

40 €

The price written on the listing, in the seller’s currency. This is what all three caps compare against.

≈ 44.09 € delivered

An estimate: item + buyer protection + delivery. When the exact postage is unknown, REGA adds 3.50 € — deliberately modest.
The tooltips say it: “Estimated total price: item + delivery (about €3-4). The exact postage depends on the carrier chosen at purchase.” And when the seller covers postage: “Estimate: item + buyer protection. Delivery paid by the seller.” The amount really taken only appears afterwards: “Amount actually debited (item + delivery + buyer protection).”
Nothing is ever converted. An item listed at £10 shows £10, not an estimated euro figure. Measured on 14/08 across 217 cards, 200 of them British: showing a conversion meant publishing a figure nobody had measured.What that means in practice: set your filter caps on the item price, not on your total budget. Measured buyer protection turns 10.00 € into 11.20 €, and measured real postage is 2.89 €. Count ~4 € above the displayed price, every time.

​
BUY and its states

The button keeps exactly the same shape in every state — so the layout does not jump at the moment you are aiming at the next card.
“RETRY” disappears in four cases, and every disappearance protects your money: item under verification (the purchase restarts on its own), outcome unknown (offering a retry means offering a double charge), bank validation still in flight, and item GONE. On “TO CHECK — OUTCOME UNKNOWN” the screen is explicit: “Outcome unknown: tracking stops here. Check in Orders BEFORE retrying — a payment may still go through.”
A payment is never replayed after an interruption at the moment of paying: the outcome there is unknown, and replaying would risk a double charge. That is the whole reason those buttons are missing.

​
♥ and ⋯

♥ adds to your REGA watchlist (“Add to the watchlist” / “Remove from the watchlist”). It is local to REGA and is never greyed out, whatever the state of the listing. The ⋯ menu carries five entries: “Add to Vinted favourites”, “Search this photo on Google Lens”, “Follow the seller”, “Make an offer”, “Block the seller”. The Google Lens entry disappears when no usable photo exists.
Google Lens on the photo is your two-second authenticity check — on a luxury brand at a price that is too good, it is the cheapest move you have. And a trick along the way: opening that menu, or the full-screen viewer, freezes the display by itself. It is the simplest way to study a card without the list moving under your eyes; a menu left open releases itself after a minute.
An offer cannot go below −40 % of the price. The screen shows the floor in plain words before you confirm: “Minimum offer” … ”— that is −40 % at most.”
On a seller the stream did not identify, the entry stays clickable and answers you honestly: “Follow not possible — no account available to act”, or “Seller unknown — open the item to make an offer”.

​
The bank validation banner

When your bank asks for a validation, a banner appears at the very top of the screen: “Bank validation requested for” + the brand + ”— the purchase is not paid until it is done.”, with a VALIDATE button. It is global to the screen, not attached to a card: at the moment the bank asks, you may be looking at another feed, and the card concerned may already have left the screen.
You have 15 minutes. Past that, the purchase is lost — with no charge, but lost. Leave the bank validation notifications on, accept them on your phone, and stay reachable for a quarter of an hour after a purchase. A reminder can be sent between 1 and 15 minutes after the request.

​
RECENT PURCHASES — the right-hand panel

Opened with ⋮, or docked on the right of the screen when the window is wide enough and there is still room for the listings. It carries the last 12 lines, most recent first, with a total in the header (“Purchases paid in this session”). Empty: “No purchase in this session — the full history is in Orders.”
The total sums only completed purchases. Adding purchases still under way would give a total that goes down when one of them fails — a counter that goes backwards is a counter nobody believes.
This, and nowhere else, is where you read which account actually paid. The name shown on the card at click time is only a forecast: the server picks and reserves the account, and the answer may name another one. To know which address a parcel leaves from, read the purchase line — and its amount slot, which first says “item price — total not confirmed yet”, then “total debited”.
Below that, the conversations. An open thread takes the whole column — at 330 px wide, a floating panel would cover exactly what you need to keep in sight.

​
The states of the screen

​
”Nothing is buying” — the decision tree

It is the most frequent question, and it almost always has one of these five answers.
“No account” and “no restriction” are not the same thing. A group you deliberately emptied refuses the purchase instead of falling back on any account at all: a loud refusal beats a purchase from the wrong account, and the opposite cannot be undone. If your automatic purchases stop for no visible reason, look at the feed’s account group first.
This is not a cap, it is freshness: an item detected several minutes ago is almost always gone. After an outage, nothing will be bought “late”.
Without that rule, arming a filter would immediately buy everything lying around in the list. Only fresh detections are bought automatically.
Look at the rate. “radar stopped” means what it says: “The radar is stopped: no listing can appear.” And a band showing “No recent detection on this source — the radar is sweeping.” is working perfectly: your filters are simply too narrow for now.

​
Our advice

Set your caps in the FILTERS, never in the AUTOBUY panel

The “Cap per item” field at 120 € on this screen does not bound the automatic buying that actually runs, and it does not follow you from one machine to another. The only portable, working cap is each filter’s € max. Sort the filter list by “Autobuy first” and check the cap column line by line: the ones showing “no cap” will buy at any price.

Set that cap on the ITEM price, not on your budget

All three caps compare the listing price, never the total. With buyer protection and postage, count ~4 € more at the charge: a 100 € cap lets through a purchase debited at ~108 €.

After arming a filter elsewhere, count 20 seconds before concluding

The list of armed filters is re-read every 20 s, and the feed catalogue every 60 s. Until the list has been read, nothing is armed — deliberately: better not to buy for one second too long than to buy what was never armed.

Do not scroll during a burst — pause, or click the backlog

Scrolling more than 40 px freezes the display without saying so, and that is a protection: a card slotting in under your cursor is an unwanted purchase. If you want to read calmly, pause on purpose: detection and automatic buying carry on. To resume, the backlog button brings everything in at once and puts the list back at the top.

Two screens beat one big one

The ⧉ window (560 × 980) sits in a corner while you work elsewhere, and it docks no panel — it is also the shortest path to the Table layout, which needs 1138 px for the listings alone.

Pin instead of closing

A feed moved to a tab carries on detecting, counting and buying. Closing it deletes it. Pinning it keeps it on screen whatever happens to the window width.

Google Lens before buying a luxury piece that is too cheap

Two seconds, in the card’s ⋯ menu. And the open menu freezes the display: you can study without the list moving.

Prepare the carriers of your recurring sellers, not all of them

Each preparation costs a real purchase of a few euros and returns ~1.3 s on purchases shipped by that carrier. Since the seller is the one who picks it, prepare first the ones you see coming back in your streams. The gain does not add up: it widens.

Stay reachable for a quarter of an hour after a purchase

Bank validation is the only moment the tool needs your hand, and it expires in 15 minutes. Leave the matching notifications on, and accept them on your phone.

On “TO CHECK — OUTCOME UNKNOWN”, go to Orders before clicking again

The missing RETRY button is not an oversight. The payment may still go through, and a second click would be a second purchase on a transaction that may already be paid.

Do not buy over an item that is “under verification”

Vinted hides a listing while it checks it, for 30 minutes to 2 hours. The purchase restarts on its own as soon as it is validated. In our measurement, 9 items out of 42 come back on sale.

Empty your verification queue before a weekend

It gives up after 96 hours: four days during which a purchase can go out on its own, with no new click. Orders screen → the verification purchase queue → remove what you no longer want. “Remove from the queue” is not a cancellation: nothing was paid.

Do not read a failure as a breakdown

Out of 42 real failures classified, 25 were races lost or items already gone. The screen files every failure under a verdict — “Race lost, or the item had already gone”, “Postponed — the purchase will be retried”, “For us to fix”, “Waiting for something from you”. Only react to the last two.

Close the tab without worry — but know what that does not stop

Automatic buying runs on our servers. Closing the tab, closing the browser, shutting the machine down: none of that stops it. The only move that stops it is disarming the AUTOBUY badge.

​
What surprises people

That is the point. The state lives with us, not in your browser: it survives closing the tab, the browser and the machine. A badge found armed when reopening the app is not a bug — it is the proof that automatic buying never stopped running.
That switch states a fact, it does not set it. Its description tells the truth: “on our servers — closing the tab does not stop it”. There is nothing there to flip.
That is the cure, not the fault. Docking is decided on the room left for the listings, never on a window threshold. Without that rule, widening by 20 px could take the wall from 4 columns to 2. The panel stays reachable through ⋮.
It existed, and it was removed after measurement: it counted painted cards, capped at 200, so it stayed stuck on 200 as soon as the stream was lively. A counter that no longer moves informs nobody.
It came in as a precaution, and the truth arrived ~3 seconds later: none of your filters keeps it. It leaves the bands — but not the memory: if you had opened its detail page, it still reads.
On the card the button becomes CANCEL directly: that is the useful move at that instant. The purchase confirmation (amount, delay) stays in the tooltip. In the detail page, where there is room, both fit together.
It is capped at 96%: real measured purchases run from 5.93 s to 8.8 s and the bar is calibrated on 8 s. A full bar would not be proof of payment — the proof is the purchase line.
The account is committed at reservation, so before the outcome. That is deliberate, and it is also why “RETRY” starts again on the next account: an account that has just failed is the worst placed to try again.
It is not taken out of the rotation: it is skipped, and its tooltip says so — “compte_demo is not connected — it will be skipped”. Hiding it would suggest it no longer exists.
Deliberately: the payer rotates. Filtering on the current account would make the purchases of previous rotations disappear — that is, half of what you are looking for.
Two, not one: that is the limit. On the third, the screen answers “A purchase is already under way on this account.” With several buying accounts, the simultaneous spending window is two per account.
Elsewhere REGA prefers to refuse rather than disappear. Here the exception is owned: three chips, two of them off, cost 192 px out of 366 and pushed ☰ and ⋮ off the screen. A selector with a single option is not a selector.

​
On a phone

The REGA dashboard on a phone, with the Feed, Filters, Purchases, Watched, More navigation bar

The dashboard on a phone: a single band, Folder layout imposed.

What changes:
  • A single band, and the Folder layout is imposed. Your choice (Wall, Table) stays remembered and comes back untouched on a large screen.
  • No layout selector, and no rate figure — there is not enough room.
  • LIVE, ⧉, ☰ and ⋮ all stay within thumb reach.
  • Settings go through ☰, recent purchases through ⋮.
  • At the bottom: Feed · Filters · Purchases · Watched · More.
  • BUY takes the full width, under the photos — the one geometry where there is no risk of hitting the wrong target.
An iPad in portrait (744 to 834 px wide) gets the phone layout. That is decided on width alone, and it is owned.

​
What this screen does not do

Said plainly, so you do not go looking for it:
  • No listing publication date is shown. The time you read (“2 s ago”) is the moment REGA detected the listing. A publication date does not exist reliably anywhere in our data: relistings pollute the timestamps.
  • The detail page’s description is a 400-character extract, taken at the moment of detection. It can legitimately be missing — the page then says so: “This listing has no description, or it was not there yet at the moment of detection.” — and points to “the listing ↗”.
  • No bank card form, and there never will be: the number is encrypted by the payment provider inside Vinted’s own browser page. The address is changed in Accounts.
  • 200 cards maximum are kept on screen. Beyond that the oldest leave: the full history lives in Orders.
  • “RECENT PURCHASES” is not a history: 12 lines, current session. A line recovered from an earlier session offers no “RETRY”.
  • ~5% of listings will never have a photo. It is not slow loading: “it arrives about a second after detection, and 5% never have one.”
  • Cap per item and max purchases / hour do not follow you from one machine to another.

​
Going further

Filters

This is where automatic buying is armed, filter by filter, and where the only cap that counts is set.

Accounts

Who pays, with which address and which card — and carrier preparation.

Orders

The full history, the verification queue, and where to check an unknown outcome.

Settings

The purchase ceiling, the automatic pick-up point, and bank validation notifications.