Mixed personalization, one calm queue.
A gift shop rarely does one craft. Engraved boxes, printed totes and monogrammed tags all land in the same morning. MakeFlow detects the right template per line, keeps every property, and batches approved work by what the bench actually needs.
- Automatic template per line
- Every property kept, nothing dropped
- Proofs for the ambiguous items only
- One queue across crafts
Three steps from paid order to released batch.
A gift shop rarely does one craft. Engraved boxes, printed totes and monogrammed tags all land in the same morning. MakeFlow detects the right template per line, keeps every property, and batches approved work by what the bench actually needs.
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
How does it pick a template?
It scores each template against the properties on the line and uses the best match, falling back to a generic packet that keeps everything.
Will unusual properties be lost?
No. Anything the template does not map is appended to the packet verbatim.
Can I run proofs only for some items?
Yes. Proofs are required per template, and any individual job can be waived or required from its drawer.