The Orders table

What this tab is for

This is your list of sales, with what's left to do on each. You come here in the morning to see what's waiting to ship, and after delivery to rate the buyers — without opening one Vinted conversation after another.

Three tasks start from it: the shipping label, the rating and the shipped marker.

Vinted decides what is offered

For each order on the page, Vintex asks Vinted what it actually allows instead of guessing from the displayed status. An action missing from the menu isn't an oversight: Vinted doesn't offer it on that order.

Filtering

A search and a status filter: Action required, Waiting, Completed, Cancelled, Failed. The list is paginated; sorting is done on the column headers.

Cancelling an order, extending the shipping deadline

Neither gesture is in the dashboard: both are done on Vinted, from the order's conversation. The extension in particular is a request subject to the buyer's acceptance — not an immediate action.

Why the list isn't always to the second

Vintex keeps Vinted reads in memory for 5 minutes for the list, 15 for each order’s detail: without that, every tab switch would hammer Vinted's API — exactly the kind of burst that gets an account noticed.

So you needn't fear acting on stale data: every write refreshes what it invalidated. What the cache covers is change coming from elsewhere — a buyer paying, a sale landing. The Refresh button, at the top of the page, forces an immediate re-read.

If it doesn't work