> ## Documentation Index
> Fetch the complete documentation index at: https://docs.regasolutions.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Orders
> Follow every purchase through to confirmation, know which parcel is waiting and where, answer sellers — and cancel while it is still possible.
The **Orders** screen is where a purchase becomes a parcel, and a parcel becomes a confirmed item. It answers four questions, and it has one tab for each.
The **Orders** view, as a "List" or as a "Kanban".
The **Messages** view — "All conversations".
The **Pick-up points** view, grouped by physical place.
The **Being checked** view, before the item is even buyable.
***
## What you are looking at
| № | The control | What it does |
| -- | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | The account panel, top right | The account that will **pay** for the next purchase. Tooltip: "compte\_demo will pay for the next purchase — ready to buy." It does **not** decide what the list shows. |
| 2 | The bell and its number | "3 unread notifications". |
| 3 | "Administration" | REGA staff only — this button does not appear on your account. |
| 4 | The "AUTOBUY" pill, here on "OFF" | Tooltip: "Automatic buying disarmed". |
| 5 | The "rega — home" logo | Back to the home screen. |
| 6 | The "↻" button | "Read again now" — starts a reading without waiting for the next minute. |
| 7 | "Dashboard" and the left column | Navigation between screens. |
| 8 | The "Orders" view | Your purchases, as a list or as a board. |
| 9 | The "Messages" view | "All conversations". A badge there counts unread messages. |
| 10 | The "Pick-up points" view | "Parcels waiting at a pick-up point, grouped by point". |
| 11 | The "Being checked" view | "Items being checked by Vinted — the purchase starts as soon as they are cleared". |
| 12 | "List" (and its neighbour "Kanban") | Two layouts of the same list. |
**Automatic buying runs on our servers.** The "AUTOBUY" pill arms the server: it survives closing the tab, closing the browser, shutting your machine down. The only thing that stops it is **disarming** it. Purchase ceilings are set elsewhere — see [Settings](/screens/settings).
The whole page scrolls, **header included**. Only the toolbar — ACCOUNTS, the views, then STATUS — stays pinned at the top: that is what you are looking for once you are far down the list.
***
## Three routines that make the difference
This is where the screen earns its keep. The rest of the page details the controls; these three sequences are what our most effective users actually do.
In **ACCOUNTS**, choose "All accounts". Without that, you are looking at whichever account the rotation landed on overnight — not at your activity.
Eight columns, one per stage. At a glance: what has not moved, what is waiting for you, what is dragging on.
The small "0/10" next to "read just now" counts the order pages being read. **While it is turning, the columns are not final.** It disappears once everything is resolved.
You are looking for one thing only: a line whose wait has passed "for 7 days". That is the parcel you go and collect today.
The unread badge tells you whether there is anything. Opening a thread marks it read — only open it if you intend to reply.
The list shows a **likely** status. The order page shows the **exact** one, and that reading costs you nothing.
If it says "Pick-up point not recorded for this order — the platform does not give it back after the purchase.", the address is lost for that order: carrier tracking becomes your only lead.
The "Show the tracking" button reads nothing until you click it. The steps come from the carrier, exactly as received.
"… were not examined (the reading stopped before the end)" and "The point of 2 parcels was not read …". A missing parcel is almost always in there, never in a wrong choice of account.
Its tooltip states the real shortcut: "Carrier tracking — it often names the point before the platform".
"Label created": still doable. "Dispatched": the platform will almost certainly refuse.
There is **no** cancel button on the list or on the Kanban. That is deliberate.
There are only three: "This order is already cancelled." · "The cancellation of this order has already been sent." · "No parcel is attached to this order yet: there is nothing to cancel for now."
You have no reason to type in: it is chosen automatically.
Either "Cancellation sent." or the "Answer from the platform" block carrying Vinted's own sentence. The "Cancellation sent" chip stays on the line to stop you.
***
## Which view to open
```mermaid theme={null}
flowchart TD
Q["What I want to know"] --> A{"Is it about a parcel,
a message, or a purchase
that has not left yet?"}
A -- "a purchase in progress" --> B["Orders view
List to search,
Kanban to watch"]
A -- "a parcel that is waiting" --> C["Pick-up points view
grouped by place,
all accounts together"]
A -- "a seller wrote to me" --> D["Messages view
one card per conversation"]
A -- "an item not buyable yet" --> E["Being checked view
the purchase leaves on its own
as soon as Vinted clears it"]
B --> F["The EXACT status exists
only in the conversation:
open the order"]
C --> F
```
Your purchases, as a **"List"** (one row per order, with the STATUS bar) or as a **"Kanban"** ("One column per stage"). The Kanban shows the eight stages side by side, plus a ninth "Unknown status" column **that only appears when it holds something**. An empty column shows a dash: it stays in place to give the shape of the cycle.
One card per conversation: avatar, username, last message (fallback "Preview unavailable"), item thumbnail, date, and a coloured dot "Unread message". The status chip only appears when REGA managed to match the thread to its order. While reading: "Reading conversations…", then "No conversation." if there is nothing.
Parcels that have **physically arrived**, grouped by point, all accounts together. A read-only badge shows "all accounts" — tooltip: "A pick-up point is a physical place: every account is read there together." **It is not a selector.** The ACCOUNTS selector disappears on this view.
Items Vinted has not cleared yet, so not buyable yet. REGA watches them and **starts the purchase the moment they clear**, without you.
The "Pick-up points" tab deliberately carries **no count badge**. Carrying one would force REGA to read the shipment of every live order before you have even asked for the view — that is, to pay a reading for a number you did not request.
***
## The header: freshness, and the counter that turns
To the right of the title, REGA writes how old the list is: **"read just now"**, "read 3 min ago", and **"never read"** if no reading has completed yet. The tooltip gives the exact date followed by "refreshed every minute"; if nothing has ever completed, it says "No reading completed — refreshed every minute".
Next to it, a counter such as **0/10** with a spinner. It counts the **still-live** orders whose detailed page REGA is reading in the background. Its tooltip:
> Faded cards are sorted from the list reading, without confirmation: their exact status is being read in the background.
**The counter is your green light.** While it turns, a faded card is a *likely* placement. When it disappears, every live order has been confirmed one by one. It never counts closed orders: those stay faded, on purpose.
***
## ACCOUNTS: what you are LOOKING at
The selector on the left is labelled **ACCOUNTS**, and its tooltip states exactly what it does — and above all what it does not:
> Choose which accounts you are LOOKING at — no effect on the account that pays
| Menu section | What you pick there |
| --------------- | --------------------------------------------------------------------------------------------------- |
| **SCOPE** | "Active account" (shown as "compte\_demo (active)") or "All accounts". |
| **GROUPS** | Your account groups, under their name. |
| **ONE ACCOUNT** | One specific account, by its username. |
| *(menu footer)* | "This choice only concerns **reading**: it changes neither the account that pays nor the rotation." |
A disconnected account stays **clickable**, but it is greyed out and announced: "compte\_demo — not connected: nothing can be read". Until the account states have arrived, the menu shows "The list of accounts arrives with their state."
**"Active account" is not an account: it is a moving target.** It is the account the server will make pay, and the rotation switches account **after every purchase**. If your list jumps to another account's orders on its own, that is not a fault — it is the default scope following the rotation. Choose "All accounts" or a named account explicitly: **your choice is remembered for this screen, and nothing will overwrite it again.**
Two uses, two scopes. **"All accounts"** to steer in the morning: you see everything, and every row carries the name of the account that paid. **A named account** to work one through: the list stops moving under you, and each "Load more" costs a single reading instead of one per account.
***
## STATUS: a bar that sorts, not a filter
Below the first row, the **STATUS** bar offers "All" then **eight** buttons in life-cycle order, each with its total. On narrow screens the labels shorten.
| The status, in full | On the narrow bar | What it means |
| -------------------------------- | ----------------- | ----------------------------------------------------------- |
| Purchase pending | Pending | Payment went through, the seller has done nothing. |
| Label created | Label | The seller has their label. **Still cancellable.** |
| Dispatched | Dispatched | The parcel is moving. The platform no longer cancels. |
| Delivered (to the pick-up point) | At the point | The parcel is **waiting at the point**. You do not have it. |
| To confirm (48 h) | To confirm | You collected it: 48 h to confirm. |
| Completed (confirmed) | Completed | **You** confirmed, the payment went to the seller. |
| Cancelled | Cancelled | A cancellation **or** a refund. |
| On hold | On hold | Dispute, incident. |
Hover a button: its tooltip separates **two populations** — "12 orders read on opening", or "12 read on opening, 5 matches unconfirmed". On the selected button one more sentence appears, and it is the most important information on the screen:
> Sorted here, over the 18 loaded orders. Faded rows match this status without being confirmed: open them to be sure.
On "Cancelled" only, one extra line: "‘Cancelled’ covers both a cancellation and a refund — the list does not tell them apart."
**This is not sorting done at Vinted.** Vinted silently ignores a request to sort by status: measured on 21/07, a valid request, a missing request and an invented one return **the same answer, to the byte**. The sorting is therefore done in your browser, **over the pages already loaded**. Before concluding "I have nothing to confirm", scroll down to the sweep note and click "Load more".
***
## One order row
Photo, item title (fallback "Order 12345"), then **the status label written by Vinted, shown exactly as received**, a row of chips, the price, the relative date (the tooltip gives the exact one), and "Open the conversation" — or "No conversation".
| The chip | When it appears | What it says |
| --------------------- | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Coloured marker + dot | The order is waiting for something from you | "This order is waiting for something from you" |
| The account name | Only when you are looking at several accounts | "Bought by compte\_demo — this is the account that will answer if you open the conversation." |
| The state | Always — read (exact) or inferred (likely) | "Status read when this order was opened — more precise than the list one. An open dispute or a recent closure may not show there yet." |
| "Cancellation sent" | A cancellation left from REGA | It is durable, even if the status has not moved yet. |
| "Unrecognised status" | Vinted returned an unseen value | "The platform returned a status we do not know yet. The order is shown all the same." |
| "to be confirmed" | A **live** order whose page has not been read | The counter at the top is dealing with it. |
In the list, Vinted's four coarse states are shown as they are: **"In progress"**, **"Action required"**, **"Completed"**, **"Cancelled or refunded"** — and "In progress" alone covers **six** different situations.
A click — or `Enter` / `Space` — opens the conversation. If there is none: "No conversation — this order does not have one yet".
***
## An order's life cycle
```mermaid theme={null}
flowchart LR
A["Purchase pending"] --> B["Label created
still cancellable"]
B --> C["Dispatched
the platform no longer cancels"]
C --> D["Delivered to the pick-up point
it waits there, you do not have it"]
D --> E["To confirm — 48 h
the parcel is in your hands"]
E --> F["Completed — confirmed
the payment goes to the seller"]
A -.-> X["Cancelled
a cancellation OR a refund"]
B -.-> X
C -.-> S["On hold
dispute, incident"]
```
An order only reaches its exact box **once its page has been read**. Otherwise it sits in the *likely* box inferred from the list, its card stays faded and carries the "to be confirmed" chip. That is also why the Kanban settles a few seconds after opening.
***
## What each gesture costs
REGA bills you in "readings": one reading is one request made to Vinted **for one account**. Volume is the only account-fatigue factor we have ever demonstrated — hence this table, and hence the limits on the sweep.
| The gesture | What it costs |
| --------------------------------- | -------------------------------------------------------------------------------------------------- |
| Opening the screen | Page 1, **one reading per account being looked at**, then the automatic sweep |
| "↻ Read again now" | One reading per account |
| Opening an order (its page) | **Nothing constrained**: that reading has no rate limit, and a result less than 30 s old is reused |
| "Load more" — free version | Nothing at all: it shows 50 rows already received |
| "Load more" — paid version | One reading **per account**: with 8 accounts, one click = 8 readings |
| "Show the tracking" | One reading, and **only if you click** |
| Leaving the tab in the background | Nothing: everything is suspended |
| Passing through the screen | Nothing, if the reading is less than **45 s** old |
REGA reuses a recent reading instead of asking again: **55 s** for the list, **30 s** for an order page, **60 s** for tracking, **15 s** for a conversation, **45 s** for pick-up points. Reopening a screen twice in a row therefore does not cost twice.
***
## The sweep note, and "Load more"
Below the list, one sentence says **how far REGA went**. Only one of the five is shown.
| What you read | What it means |
| ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| "Looking for orders in progress… 3 pages read" | The sweep is still running. |
| "9 in progress · every order has been swept (7 pages read)" | **Complete.** It is the only sentence that says so. |
| "9 in progress · stopped after 10 pages read — ‘Load more’ to go further back" | Stopped by the 10-page limit. |
| "9 in progress · 6 pages read, the last 2 with no order in progress — ‘Load more’ to go further back" | Stopped after 2 consecutive pages with nothing live. |
| "9 in progress · 4 pages read, the next reading failed" | Stopped by an incident. |
The shared tooltip explains the limit: "Each page costs one reading per account: the sweep is therefore bounded."
"Already loaded: showing them costs no reading." — there are rows already received but not shown yet.
"Fetches older orders — one reading per account." — and on "All accounts" with 8 accounts, that is 8 readings at once.
```mermaid theme={null}
flowchart TD
A["You open the screen"] --> B["Page 1, read on each account in scope"]
B --> C{"Any orders in progress
on this page?"}
C -- "yes" --> D["Next page:
1 reading per account"]
D --> C
C -- "2 pages in a row with nothing live" --> E["Stop: the last 2
with no order in progress"]
C -- "10 pages read" --> F["Stop: stopped after 10 pages"]
C -- "no more pages at Vinted" --> G["every order
has been swept"]
E --> H["Load more"]
F --> H
H --> I{"Are there received rows
waiting to be shown?"}
I -- "yes" --> J["Display only,
no reading"]
I -- "no" --> D
B --> K["Pages of LIVE orders read in the
background, 4 at a time, 60 per pass"]
K --> L["The statuses become exact"]
```
***
## The conversation panel
Above 1,280 px it opens as a column on the right (titled **CONVERSATION**); below that, it is a 420 px sheet sliding in from the edge. Its header carries "Close the conversation", the avatar and username (fallback "Other party"), "Reload the thread", and an "Actions on this conversation" menu offering exactly one thing: "Delete the conversation".
Name, code, carrier, address, then: "Chosen 2 d ago. A point can close: check it before you travel." While searching: "Looking for the pick-up point…".
Two refusals, not to be confused:
* **"Pick-up point not recorded — no order has a recorded pick-up point here yet."** — your register is empty, which is a normal start.
* **"Pick-up point not recorded for this order — the platform does not give it back after the purchase."** — that specific order has no point.
The section disappears as soon as the order is completed or cancelled.
They exist **only if Vinted offers them** on that order:
* **"I have received the parcel"** — "Reports receipt. The payment is not released yet."
* **"Confirm the order"** — "Releases the payment to the seller. This is final: it cannot be undone from rega."
* **"Cancel the order"**, in red — the only red we allow ourselves on this screen.
After a click, REGA is blunt: "Request sent — it is not confirmed. The real status will appear at the next reading."
It is read **on demand only**: the "Show the tracking" button, then "Reading the tracking…", then the carrier's steps exactly as received, with a "Carrier tracking ↗" link and the note "Tracking passed on as received, with no confirmation on our side." If there is nothing: "No tracking is available for this parcel."
Bubbles, offers, events. An item of an unseen kind is **never hidden**: it shows as "A message of a kind this screen cannot display yet."
Vinted sometimes offers up to **three** ready-made replies: one click drops them into the field, as they are. The composer shows "Write to the seller…" and the **"SEND"** button. On an empty field the button is not dead: it answers "Empty message — write something before sending". If Vinted closed the conversation: "Replying is not possible on this thread — the platform closed the conversation."
Three outcomes for a send: "Message sent", "Sending not confirmed — reopen the thread to check", or "Message not sent — …".
### Confirming an order
That is the exact meaning of the sentence in the dialog: "Only confirm once you have checked the item." Confirming releases the money, and **it is final**.
There is no "confirm" button on the list or on the Kanban.
The "Go back" button takes you out without doing anything.
REGA shows "Request sent — it is not confirmed. The real status will appear at the next reading." The list re-reads itself every minute.
### Cancelling an order
```mermaid theme={null}
flowchart TD
A["You click Cancel the order"] --> B{"Can REGA already
say NO, with proof?"}
B -- "already cancelled · cancellation already sent · no parcel attached" --> C["The button is not offered,
the reason is shown instead"]
B -- "no proof" --> D["The button is offered —
Vinted will decide"]
D --> E["Cancellation sent
+ Cancellation sent chip"]
D --> F["Answer from the platform:
Vinted's own sentence, untranslated"]
E --> G["The status only moves at the next
reading: do not cancel twice"]
```
The text of the **CANCEL THE ORDER** dialog says it all:
> Cancels the purchase with the seller. This is final: it cannot be undone from rega. The reason is chosen automatically — you have nothing to enter. If the parcel has already left, the platform may refuse: its answer will appear here.
Beyond two cancellations in 24 h on the same account, REGA warns you: "This account has cancelled 3 orders in the last 24 h. Too many cancellations close together can restrict the account on Vinted." **Nothing is blocked** — we inform, we do not forbid. Past that, space them out, or let another account pay.
After sending: "Cancellation sent. The state above stays the one from the last reading until the platform changes it." The **"Cancellation sent"** chip stays on the row — it is there to stop you cancelling a second time.
***
## The Pick-up points view
At the top, the summary: "3 parcels to collect" · "at 2 pick-up points", the read-only "all accounts" badge, and a "Rebuild the view" button.
Then **one row per point**, collapsed: the carrier logo, the shop name, the carrier in full, the address (or "Unknown address"), **the longest wait** at that point — "for 9 days", "arrived today", "unknown wait" —, the number of parcels, and a **"Directions ↗"** link.
Expanded ("See the items waiting here"), one row per item: photo, title, seller, and **the paying account, always shown**. The wait tooltip says where it is counted from: "Counted from the drop-off at the pick-up point." or "Counted from the Vinted notification (the real arrival is slightly earlier)."
There is a special row: **"Pick-up point not given yet"**, subtitled "Address published within a few hours", with a **"Tracking ↗"** link. On our measurement, Vinted publishes the point's name **21 to 25 h after the parcel actually arrived** (3 cases out of 3). In between, only the carrier knows where it is — which is exactly what the link's tooltip says.
The view is blunt about what it did not see, in two sentences to read **before** concluding that a parcel is missing:
"4 orders in progress were not examined (the reading stopped before the end): their parcels do not appear here."
"The point of 2 parcels was not read (the reading stopped before the end): it is known, and will appear at the next pass."
***
## The Being checked view
An item Vinted has not cleared yet cannot be bought. REGA puts it in a queue, watches it closely, and **starts the purchase the moment it clears** — you have nothing to do.
At the top, "Give up after" and its delay — tooltip: "Delay after which an item that was never checked is given up, with a notification." The delay actually applied today is **96 h**.
Four groups, decided by the server, and an empty group is not shown: **"In the purchase queue: being checked"**, **"Check failed"**, **"Successful purchases"**, **"Failed purchases"**.
A card carries the photo, the brand and title (linked to the listing), the status among nine labels, then "· followed 3 h ago", "· given up in \~72 h", "· 42.00 € charged" where they apply, the selector for the account that will start the purchase ("The purchase will come from compte\_demo.") and the price.
"Waiting to be checked" · "Purchase under way" · "Purchased" · "Purchase failed" · "Bought by another member" · "Removed or rejected at the check" · "Given up (not checked in time)" · "Could not start the purchase" · "Removed from the queue".
The **"Remove"** button exists only while the item is waiting: "Removes this item from the queue: no purchase will be started for it any more." Once the purchase has left, it is replaced by "followed in the Orders tab", whose tooltip explains why: "The purchase has left: it cannot be taken back from this queue. Its outcome — paid, refused, or a confirmation to make with your bank — appears in the list of orders." Finished entries stay visible for **7 days**, even after signing out.
**The "Confirm with your bank ↗" link has a short window.** Its tooltip: "Your bank is asking for a confirmation. Without it, the payment does not go through." It appears **during** the purchase, not after: a bank confirmation happens straight away or not at all. The same link is duplicated in the dashboard's recent purchases, on purpose.
**Past two hours, stop hoping.** Measured on 27/07 across the items followed by the queue: 16 % were genuinely being checked within their first minute, 20 % between 1 and 5 min, 36 % between 5 and 30 min, 50 % between 30 min and 2 h — and **0 % between 2 and 24 h**. That is why REGA looks at the item every second at first, then spaces out after 2 h 30. An item still "Waiting to be checked" the next day will not go: do not hold your budget for it.
***
## The screen's states
| You see | What it means |
| ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| "Reading orders…" | Nothing has been read yet. **Never** confused with "no order". |
| "No order on this scope." | The reading completed, and there really is nothing for the accounts being looked at. |
| "No order loaded with this status." | There are orders, but none with this status **among those already loaded**. Click "Load more". |
| An error sentence + "Retry" | The very first reading failed, and there is nothing in memory. |
| The list stays, but "read" gets older | A reading failed **afterwards**: nothing is wiped, you keep your rows. |
| A banner "compte\_demo could not be read — …" | One account is down, the others are up to date. With several: "3 accounts could not be read. The others are up to date." |
| Faded cards + "to be confirmed" + the counter at the top | REGA is reading the order pages. A few seconds. |
| "Reading parcels…" then "No parcel at a pick-up point. Parcels appear here as soon as they arrive — not while they are in transit." | Pick-up points view, nothing waiting. |
| "Reading failed." on pick-up points | The reading failed — **the last known view is not wiped**. |
| "Reading…" then "No item being checked." | Being checked view, empty queue. |
Failure sentences are always translated from a cause, never copied: "This account is not connected. Reconnect it from the [Accounts](/screens/accounts) tab.", "Too many requests in a row. Let a minute pass.", "Reading is momentarily unavailable on this account. Try again shortly.", "This information is unavailable for now."
There is **no alert red and no alert orange** on that banner. In REGA a failure is stated in words, not in colour — the only red on this screen is the "Cancel the order" button.
***
## Our advice
By default the scope follows the **active account**, therefore the rotation, therefore every purchase. Open ACCOUNTS and pick "All accounts" or a named account. The choice is kept **for this screen** and will never be overwritten automatically again. It is the first setting to make, and you make it once.
Vinted's list carries only **4 coarse states**; the **8 fine states** live on the order page. "In progress" alone covers **six** situations. That reading has no rate limit: open it without hesitating, as often as you like.
Only one sentence allows the word "complete": **"every order has been swept"**. On "stopped after 10 pages" or "the last 2 with no order in progress", an old on-hold order may be sleeping further back — and that is exactly the kind of order you are looking for.
"Already loaded…" = free, click as much as you want. "Fetches older orders — one reading per account." = paid, and on 8 accounts that is 8 readings at once. Ten distracted clicks are worth a hundred readings: **volume** is the only account-fatigue factor we have ever demonstrated.
Every row shows **the account that paid** — that account carries the delivery address, and it is **the recipient name on that address** the shop is expecting. Not the Vinted username on screen. Every write (replying, confirming, cancelling, deleting) also leaves from that account, never from the one shown top right.
The longest wait is carried by the **collapsed** row, on purpose: without it, a parcel forgotten for eleven days would stay invisible until someone expanded the row. Treat "for 7 days" as an alarm. Points keep a parcel for about ten days then return it to the sender, but the exact delay depends on the carrier and **Vinted publishes it nowhere**: that 7-day threshold is our convention, not a measurement.
This view reads **all accounts, always**, and shows **only** parcels that have physically arrived — never those in transit. On 01/08/2026, in production, the old version showed **12 parcels in transit** belonging to two accounts and **zero** of the **three** real collections, which were on a third account. If a parcel is missing, the answer is in the two truncation sentences at the bottom of the view.
The boundary, measured across **60 real orders**: while the parcel has not left, cancellation often goes through; once dispatched, the platform refuses. REGA can only say **no** with proof — everywhere else it offers the button and lets Vinted decide. On a refusal, the "Answer from the platform" block carries Vinted's sentence word for word: it is the only one that says why.
It shows **during** the purchase. Do not wait for the card to turn to "Purchased" — without that confirmation the payment does not go through, and the window closes. It is the only gesture on this screen that decides between bought and lost.
Our 27/07 reading: **0 %** of the items followed for 2 to 24 h were genuinely being checked, against 50 % between 30 min and 2 h. An item still waiting the next day will not go. Let the queue give up on it by itself (96 h, with a notification) rather than counting on it.
The board is the only element in REGA allowed to exceed the reading width. At the normal width (1,120 px) you only see **3 columns out of 8**; at **2,160 px** the eight fit together — a column hardly goes below **244 px** without becoming unreadable. On a laptop the Kanban watches poorly: prefer the List and its STATUS bar.
In the background, **nothing is read**: not the list (60 s), not the conversations, not the pick-up points (60 s), not the checking queue (8 s). On your return, if the period has passed, everything is re-read immediately. A list that "has not moved" while you were elsewhere is therefore normal: when you come back, look at "read … ago", not at the list.
"Confirm the order" releases the money and **it is final: it cannot be undone from rega**. The 48 h of "To confirm (48 h)" are your only window to open, check and photograph. A seller in a hurry is not a reason to give it up.
REGA preloads your orders **2.5 s** after you land on another screen, and does nothing at all if the reading is less than **45 s** old, or if an attempt — even a failed one — is less than 45 s old. Passing through Orders between two screens is therefore free; it is the paid "Load more" that costs, not the navigation.
***
## What surprises people
It adds **read** orders and **matching, unconfirmed** orders. A button showing 12 may contain no confirmed order at all. The tooltip separates them; the faded shade tells them apart at a glance.
The three labels are deliberately explicit: **"Delivered (to the pick-up point)"** = the parcel is waiting at the point; **"To confirm (48 h)"** = you collected it, 48 h to confirm; **"Completed (confirmed)"** = **you** confirmed. The word "Delivered" on its own has already misled everyone — hence the bracket.
The tooltip of the read state admits it: "An open dispute or a recent closure may not show there yet." Neither is readable from the conversation — an on-hold order has already displayed "Dispatched", in full confidence.
REGA no longer reads the pages of closed orders: they add nothing and they cost. Before that choice, **151 cards out of 160** carried "to be confirmed" — a signal carried by 94 % of the cards signals nothing at all.
The row keeps showing the status from the last reading until Vinted changes it. The "Cancellation sent" chip, however, is durable. **Do not cancel a second time** because the status has not moved: the next reading arrives within the minute.
The unread counter drops on opening, without you having replied. And a deleted thread disappears **instantly** from the list, before the next reading: deletion is irreversible at Vinted, and reopening it would lead nowhere.
An account whose unread messages could not be counted is **never** counted as zero: it stays unknown, and the total becomes partial. The tooltip then changes sentence: "At least this many unread messages — one account could not be counted". Beyond 99, the badge shows "99+".
Switching thread empties the field. That is a safety measure: it prevents accidentally sending a message into someone else's conversation.
The status label in the list, a conversation's subtitle, a cancellation refusal, a pick-up point address, the carrier's steps: all of that comes from Vinted and is shown **as received**. Translating it would create a second truth, which would become false the day Vinted changes its own.
"Unknown status" only appears when it holds something. The other eight stay in place, empty, with a dash: it is the structure of the cycle that justifies them, not their contents.
On "Pick-up points" there is none. A pick-up point is a physical place: the view reads every account together, and an account filter there would produce exactly the mistake it exists to prevent.
***
## On a phone
Nothing disappears, only the way to reach it changes:
* The toolbar goes **onto two rows** — ACCOUNTS and the views, then STATUS — and the status buttons shorten: "Pending", "Label", "At the point", "To confirm".
* Each row folds onto two lines.
* The conversation panel becomes a 380 px **side sheet** sliding in from the edge.
* The Kanban **stacks** and scrolls with the page instead of scrolling sideways.
* At the bottom, the short navigation: **Feed · Filters · Orders · Tracked · More**. Orders are under **Orders**.
This screen is one of only three we check systematically at **three sizes** (390 × 844, 768 × 1024, 1440 × 900). Measured in the browser after our last fix: the sticky bar takes **93 px, i.e. 12 % of the height** at 1280 × 800 — **6.9 orders visible** against 4.6 before — and **154 px, i.e. 21 %** at 390 × 844, i.e. **3.1 orders visible** against 0.7.
***
## What this screen cannot do
We would rather say so:
Vinted does not give one. That is the exact reason for the sentence "Request sent — it is not confirmed. The real status will appear at the next reading." Parcel tracking is in the same situation: we pass it on to you as received, without confirming it.
By construction: REGA can only prove the **no**. Everywhere else it offers and Vinted decides. The cancellation reason cannot be typed in, and a cancellation that has already left is not re-sent from a button — that is a recovery gesture, and it has no place behind a distracted click.
Vinted never gives the pick-up point back after the purchase. REGA records it **at the moment of the purchase**: an order placed before 1 August 2026 will therefore stay at the point **with no known address**, for good. Carrier tracking remains your best lead.
We have only **three** real arrival messages, all worded the same way: nothing guarantees that every carrier writes the same sentence. Our reading is therefore cautious by construction — it **never makes a parcel disappear**, it files it under "Pick-up point not given yet".
If Vinted refuses a send on an older conversation, REGA shows "Message not sent — …" and stops there. There is a second route at Vinted, but we do not take it on your behalf: switching without telling you risks sending the same message twice.
If your scope designates **no** account (an emptied group, for instance), the screen shows an off-topic sentence — "This action is not offered on this order." — instead of saying the group is empty. And the "Being checked" toolbar may briefly show "24 h" / "48 h" on the very first reading: the only delay actually applied is **96 h**.
***
Reconnect a fallen account, prepare a carrier.
The purchase ceiling and the automatic pick-up point.
Recent purchases, live.