One work order per personalized item.
A work order is the bridge between a paid order and a machine. MakeFlow builds it from the captured properties, keeps every unmapped value, and prints it in the order an operator reads: what to make, how, for whom, and what was approved.
- Printed and CSV work orders
- Every property preserved
- Artwork listed and linked
- Proof state on the sheet
Three steps from paid order to released batch.
A work order is the bridge between a paid order and a machine. MakeFlow builds it from the captured properties, keeps every unmapped value, and prints it in the order an operator reads: what to make, how, for whom, and what was approved.
MakeFlow reads the line-item properties your store already captures and maps them through a template into a single work packet. Any property the template does not recognise is kept verbatim, so nothing a customer typed is ever dropped.
Jobs that need approval go to a calm, branded proof page. The customer approves or asks for a change, and every version is kept with a timestamp. Approved jobs then group by material, method and colour, so the shop floor runs setups instead of order numbers.
Related: production desk · pricing · support
Common questions
What format is the work order?
A printable sheet per job, plus a wide CSV table and a long one-row-per-field CSV for spreadsheets.
Can I add operator notes?
Yes. Each job takes notes that appear on the packet and the print sheet.
Does it replace my spreadsheet?
For the handoff it does; the CSV export still lets you keep one if you like.