Batch the day by setup, not by order number.
Running jobs in the order they were opened means re-setting the machine for every piece. MakeFlow groups approved work by the keys you choose — material, method, colour, finish — so a day of small orders becomes a handful of setups.
- Groups by material, method and colour
- Release a batch in one action
- Print the whole batch at once
- Recall a batch if plans change
Three steps from paid order to released batch.
Running jobs in the order they were opened means re-setting the machine for every piece. MakeFlow groups approved work by the keys you choose — material, method, colour, finish — so a day of small orders becomes a handful of setups.
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
Can I change the grouping?
Yes. Batching keys are editable per template in Settings, and any job's keys can be overridden.
What stops a bad batch?
Only approved or no-proof jobs are eligible. A revision sits out of the batch until it is settled.
Can I undo a release?
Yes. Recall returns every job in the batch to the queue without losing its packet.