Manage orders
Find any order in seconds, read it without opening it, and move it from incoming to handed over — from the Orders screen in your Kitchen.
Published
Orders is the record of everything your storefront has ever sold. Every order from every drop, every custom order, every cancellation — one searchable list, described on the screen itself as Every order, searchable.
It is not the screen you run a pickup day from. Pickup Day does that: one day, one location, five verbs. Orders answers the other question — where is this one order, and what is true about it?
Find an order
The search field sits at the top of the list: Search name or #reference. It looks at
the buyer’s name and the order reference, and it folds accents, so typing soderberg
finds Söderberg.
A search spans the whole book, not the chip you happen to be standing on. A completed order from March is findable while Active is on screen — and while a search is running no chip is pressed, because a segment is not what you are looking at. Press a chip again and the search clears; the two are one control in two dresses.
The five chips
Above the list, five chips split the book by state:
- Active — the orders waiting on your kitchen.
- Ready — packed and waiting for the buyer.
- Completed — the buyer has the order.
- Cancelled & no-show — kept as a record. Pressing it reveals a second pair, Cancelled and No-show, so you can read one at a time.
- Awaiting payment — checkouts still inside their 15-minute payment hold. Nothing here needs you; it either becomes an order or it lapses.
What a row already tells you
The list is built so most questions never need the order opened:
| Column | What it carries |
|---|---|
| Order | the order reference, #9012 |
| Buyer | the name, and a mark when they are a regular |
| Items | a short summary of what was ordered (on wide screens) |
| Pickup promise | the day, the window and the place — or an amber No day yet |
| Status | Incoming, Ready, Completed, Cancelled, No-show, Awaiting payment |
| Payment | Unpaid, Partly paid, Paid, Partly refunded or Refunded, with the amount still due beneath it |
Payment is the one column you can sort on — its header reads Sort by amount due, which is what it does. The sort menu beside the chips does the other axis: Newest or Oldest, by when the order was placed.
A custom order carries a Custom chip on its row. An order from an extras sale carries an
Extras chip, and its tooltip says what that means: a pre-packed hand-over, no bake work
left.
Open one
Click a row. On a wide screen the order opens as a panel docked beside the list, so the list stays visible and you can move between records without losing your place; Open full page gives it the whole screen. On a phone it opens full page straight away.
The record holds, in order: the progress stepper (Placed, the payment step, Ready, Handed over), the pickup or delivery block, the items with their subtotal, delivery fee and total, the Payment ledger, an Internal note box — Only your kitchen sees this — and the Activity feed.
Move an order along
One verb sits at the foot of the record, and it is whichever one the order is waiting for:
- Mark ready on an incoming order. It emails the buyer their tracking link.
- Mark collected on a ready order — or Mark delivered when the order is a delivery. Either way the state word becomes Completed.
Everything else lives behind More actions: Refund…, Message, Print ticket, Move pickup… or Set pickup day…, Mark no-show… and Cancel order…. Each destructive one opens a ceremony that states what happens before you commit, and the safe answer holds the first keystroke.
Print a batch of tickets
Tick the checkbox on each row you want and a bar appears above the list with one verb: Print tickets. The selection is scoped to the page and to the current search, so changing either clears it — you are never holding a selection you cannot see. A single ticket also prints from a row’s own menu.
When you are looking at a subset
Arriving from a drop, or from a link that scopes the book, puts a band above the list naming the scope. It has no dismiss, only Clear — a silently narrowed list is exactly what it exists to prevent. While a scope is on, the chip counts are hidden rather than quietly counting something else.
While you work
Payment and cancellation truth change without you doing anything. When you are idle the rows update in place. When you are mid-task — an order open, a page past the first, rows selected — nothing moves under your hands: the update waits behind a small pill above the list reading 3 orders updated, with a Refresh button beside it.
If the screen says you cannot see this
Orders is gated on the orders permission, and marking, cancelling or recording payment needs the update grade on top of it. If you land on You do not have permission to view orders, ask a storefront admin to widen your role.