One made-to-order item, from the order landing in the queue to the finished piece. The screens are the app's own, on a sample
shop. Press the highlighted action on each to move the work along; nothing leaves this browser.
Merchant seesA new order becomes a jobFri 4 Sep 10:30
Jonas P. ordered a cutting board with an engraving. The line item is a job in the queue, carrying the text as typed. The rule asks for a proof, so the proof column reads To send.
Up to date · last synced 10:30 · Friday, 4 September 2026
Needs attention
0
Awaiting customer
0
Ready to produce
0
In production
0
Overdue
0
Search item, order, name…
Item · orderPersonalisation, as typedQtyDueStageProofBatch · who
Engraving text: Happy 60th, Dad · Font: Script1exp. 11 SepNewTo sendnot sent yetunbatched
1 active job · 0 done today · 1 of 150 active on Pro (trial, 9 days left)Rows 1–1 of 1
Meanwhile · the same moment, three screens
Merchantin the Shopify adminon screen
New · proof To send
No proof yet.
Can do now
Upload proof
Render text proof
Waive
Move stage (not past the gate without a proof)
Customeron their order page
Order received · expected 11 September
Can do now
Request a change to the spelling
Makerat the bench
Nothing at the bench yet
A piece reaches the bench on a run sheet, once it is Ready to produce and batched.
That was the whole loop
Nobody typed a status.
The merchant sent a proof, the customer approved it, the maker scanned a code. Each of those is one fact, and the queue, the
order page and the bench all read the same one. The sample shop, its makers and its customers are made up; the screens are not.