Skip to main content

Orders

Open in TWICE Admin

orders
There is no “today” screen in TWICE. What there is instead is one Orders table flexible enough to become one, and the point of this guide is that you build it once and save it rather than reconstructing it every morning. Three questions run a counter: what goes out today, what comes back today, and what should already have come back. Each is a filter, and each is worth its own saved view. Dates are not the only axis, either. State — Open, In progress, Closed — slices the same table by where an order has got to rather than when it is due, and the two combine: state plus date is what makes the overdue view possible at all.

​
Prerequisites

Required permissions: orders:order in view to read the table, and manage to mark items as they move. Marking items also needs orders:order_stock_items. All four system roles hold these. See Users & Roles.
Before you start:
  • Check your selected locations. The table is scoped to them, so a counter at one site should have only that site selected — otherwise the day’s list includes other people’s work.
  • Know your timezone is the merchant’s. Date filters resolve against your account’s timezone, not the browser’s, so “today” means the same thing for everyone on the team.

​
The Walkthrough

1

Build today's pickups

Filter Start date to today. The date filter’s relative-day operators need no date picker, so this is a couple of clicks rather than a calendar visit — and it keeps meaning “today” tomorrow, which a hard date would not.Add Fulfillment state to see what is prepared. Sort or group by it and the list splits into what still needs picking and what is bagged and waiting.Useful columns for this view: Reference, Customer, Start date, Fulfillment state, Payment, and Listings so you can see what to fetch without opening each order.
2

Build today's returns

The same move on End date. This is the list you work the other half of the day from, and it wants slightly different columns — Stock items and Fulfillment state matter more than Listings, because the question is which units are coming back rather than what was ordered.
3

Build views by state, not only by date

State answers a different question from the dates: not “when is this due” but “how far has it got”. Filter it to:Group by State instead of filtering and the whole table splits three ways at once, which is the fastest read of the week’s shape.Other columns worth a view of their own: Payment filtered to Unpaid (money to chase), Has conflicts to Yes (stock that needs reassigning), and Fulfillment state to find what is prepared but not handed over.
4

Build the overdue list — nothing else will

Nothing flags a late return. There is no overdue badge, no notification and no automatic fee, so an order whose end date passed last week looks exactly like any other. But the filters find them, which is why this view exists.Combine the two axes: State is Open or In progress, and End date is before today. An order that has not been closed while its return date has passed is one nobody has brought back.Narrow it further with Fulfillment state if you want only the items still recorded as out rather than Returned.This is the single highest-value view on the page, precisely because nothing surfaces it for you.
5

Save each one, and put them in order

Save each filter as a view so tomorrow is one click. Views appear as tabs on the table’s tab row, and the three-dot button at the right of that row opens a panel to search, reorder and hide them.Two things about that panel worth knowing before you rely on it:
  • Reordering and hiding are per-user and per-browser. Dragging a shared view does not move it for a colleague, and a different device starts from the default row.
  • A view saved now, or shared with you since you last dragged anything, lands at the end of the row rather than in place.
Put the three in the order the day runs — pickups, returns, overdue — and hide the tabs you never use. See Tables for the full set of view and column controls.
6

Switch to the calendar when the shape of the day matters

The Layout control to the left of the search box swaps the grid for a calendar of pickups and returns. It is the better view when you need to see when rather than what — a morning rush against a quiet afternoon.It opens on Grid Week; Grid Day and List Day are the ones for a single day’s work, and Today with the arrows beside it moves the range. Pickups carry a purple up arrow, returns a blue down arrow, and clicking an event lists one row per order with its reference, time and item count, each row a link into the order.Two limits to plan around: the calendar plots only the orders currently loaded in the table, so your filters and page decide what appears on it, and it is disabled while the table is grouped — clear the grouping to switch.
7

Work the list

Open an order from the view and act on it in place:
  • Going out: select the items and Mark as → Ready when picked, then Fulfilled at handover. For a whole order leaving at once, moving the status chip to In progress does both — it sets the status and marks every eligible item Fulfilled.
  • Coming back: Mark as → Returned, per item. Anything not clean is a return case.
  • A single order’s own timeline is on its Fulfillment & Return tab, which is the same calendar scoped to that order.
Then re-open the view. The order drops off it as its state changes, which is what makes the list a worklist rather than a report.

​
How do I know it worked?

  • Three saved views — pickups, returns, overdue — sitting on the tab row in the order you work them.
  • Each empties as the day goes on, because the filters key off state rather than a date you typed.
  • The overdue view is empty, or every row on it is one you know about and are chasing.
  • No order on today’s list is still Unassigned by the time the customer arrives.

​
Troubleshooting / Common Pitfalls

Cause: more than one location is selected. The table is scoped to your selection, not to where you are standing.What to do: select only the location you are working. This also scopes the conflicts banner and count, so it makes the whole page truthful for your site at once.
Cause: you filtered on a specific date rather than a relative one. The view faithfully shows the day you saved.What to do: rebuild it with the relative-day operators — “today”, “before today” — which re-resolve every time the view is opened. This is the difference between a saved view that works forever and one that works once.
Correct — there is no overdue detection at all. No flag, no badge, no notification, no late fee.What to do: build the overdue view in step three and open it daily. It is the only thing standing between you and a unit nobody has noticed is missing.
Cause: the calendar plots only what the table has currently loaded. Your filters and the page you are on decide its contents.What to do: widen the filter or move through the pages. If the calendar is empty of a day you know has work, check you have not filtered that day out of the grid first.
Cause: the table is grouped. Layouts and grouping are mutually exclusive.What to do: clear the grouping, then switch layout. Grouping by Fulfillment state is genuinely useful on a pickup list, so this is a real trade rather than an oversight — keep two views if you want both.
Expected. Hiding and reordering view tabs is stored per user and per browser. Sharing a view shares the view, not your arrangement of the row.What to do: share the views and let each person arrange their own tabs. Tell them the tabs will be at the end of their row until they drag them.

​
Next Steps

Handle a return

The late, damaged and partial cases the overdue view finds.

Tables

Filters, saved views, column and tab controls in full.

Take an order in admin

Where the orders on today’s list came from.

Orders overview

Every column and layout the table offers.