Guide · The queue · 4 min read · updated 4 September 2026
A production queue for a made-to-order Shopify shop, without a spreadsheet
Open the Orders page and you see orders: number, customer, total, fulfilment status. Open one and the engraving text is three clicks down. Nobody at the bench works from that page, which is why the bench works from a spreadsheet, a whiteboard, or a printout with pen marks.
The spreadsheet drifts the day the second person edits it. This guide covers what a queue must show for the work to run from it, why the one status that matters is derived rather than typed, and how it stays honest with Shopify.
An order is not a job
The unit of work is the line item, not the order. One order with a cutting board and a tote is two jobs on two machines with two lead times, and the tote may ship before the board is approved. A queue of orders makes someone open each one to find out what is inside. A queue of jobs puts the product, the quantity, the personalisation as typed, the due date and the stage on one row.
Quantity matters too. A tote ordered four times is one job with four pieces on the run sheet, each with its own tick box.
#1041 · P.N. Monogram: P.N. · Thread colour: Navy 19 Sep Ready to produce Approved
#1041 · P.N. Engraving: The Nakamura Family · Est. 2019 · Font: Serif 111 Sep Awaiting approval Sent, viewedv2 · sent 2 Sep
#1035 · A.R. Engraving: Cheers to 40 · Font: Script 21 day late
due 3 Sep In production None needed
#1041 · P.N. Engraving: The Nakamura Family · Est. 2019 111 Sep Awaiting approval Changes requested
#1035 · A.R. Engraving: Cheers to 40 · Font: Script 21 day late
due 3 Sep In production None needed
#1047 · D.K. Gift box: Yes · Monogram: D.K. 114 Sep Artwork To send
sent 2 Sep · viewed 2 Sep · auto-approves 5 Sep
Run sheet —
Assignee Sam
Scans none
Monogram: P.N. · Navy
Ready to produce
Derived, never typed: artwork present and the proof approved or not needed. Tick the identical work and it prints as one run sheet.
Every stuck job says what is wrong in a sentence and offers the one action that unsticks it — an unmapped property, a change the customer asked for, a date that has passed.
The screen behind a row, in two columns as the page has it. The work on the left: what is stuck and the one action for it, the personalisation as typed with the unmapped property called out, the proof at its version, and a line saying what the customer is reading right now. The job's context on the right: whether it is batched and printed, the order's other items, and every event that touched it.
What blocks a job: artwork, approval, stock
Ask a maker what they want to see first thing and the answer is what can be made right now. That is a derived fact: the artwork is there, and the proof is approved or none was needed. When the status is typed by hand it goes stale the moment anyone forgets to update it; when it is derived from the work it cannot.
The rest of the queue is what is stuck and why. Five counts cover a morning:
- Needs attention: a property the shop has not mapped, a customer asking for changes, a job past its date.
- Awaiting customer: proofs sent and not yet answered.
- Ready to produce: derived, never typed.
- In production: on a bench, on a run sheet, assigned to someone.
- Overdue: a day past the expected date, with the day count and the customer to tell.
Due dates you can stand behind
A due date typed into a note is a guess. A due date computed from a per-product lead time in working days is a fact you can show the customer. It counts from the proof approval, or from the order where no proof is needed, and it takes your closed days out. Two refinements make it honest:
- A closure calendar: the craft fair, the winter break. Every expected date crossing the closure moves, and the shop sees how many jobs it moved before customers are told.
- A needed-by date from the order itself, when the occasion date is a line-item property, as a soft deadline next to the computed date.
Batching identical work
Six journals in gold foil are one setup, not six. A queue that batches earns its keep three times over. It groups ready jobs by a property value or a process. It prints them as one run sheet — a tick box per piece, and the text to make set large enough to read at the bench. And it puts a QR code on each piece, so a phone can advance the stage or mark it done. The queue becomes the shop's paperwork instead of a second thing to keep up to date.
Sign off ____________________ Date ________
Est. 2019
- New, done
- Artwork, done
- Awaiting approval, done
- Ready to produce, done
- In production, now
- Done, to come
In production · since 3 Sep · next: Done
marked done by SAM
- New, done
- Artwork, done
- Awaiting approval, done
- Ready to produce, done
- In production, now
- Done, to come
In production · 3 of 4 pieces here
- #1041 · The Nakamura FamilyIn production
- #1035 · Cheers to 40In production
- #1044 · For Grandaddone
Printed once for the batch: a row per piece, the words to cut set large, a tick box, and a code on each piece with one for the whole batch in the header.
No login — the link in the code is the credential. The rail says where the piece is; the buttons are the only things that move it.
What happened leads the screen, and a mis-scan on a busy morning can be undone for a minute.
The header code moves every piece at once, after showing which ones it is about to move.
Keeping Shopify the source of truth
A queue that lives beside Shopify has to agree with it in both directions. Every stage change should write a tag and an order metafield, so Flow, saved views and the packing app see the same state. A line fulfilled in Shopify should mark its job done on its own, and a cancelled line should leave the queue, so nobody counts finished work as work in flight. POS sales and draft orders are not jobs and should never appear.
Doing it with StatusClerk
StatusClerk syncs open orders into one job per line item. It derives ready to produce from the artwork and the proof, and computes expected dates in working days against your closure calendar. Identical work batches into run sheets, with a QR per piece and a scan page for the floor. Every change goes back to Shopify as a tag and a metafield. Free for up to 25 active jobs; Pro is $19 a month.