Know where every custom order stands.
A personalized order passes through proof, release, production and completion. MakeFlow keeps that state explicit, so the answer to 'where is order 1049?' is one glance rather than a search through mail and memory.
- Proof, release and production states
- Overdue and rush flags
- Audit log per job
- Search across orders and instructions
Three steps from paid order to released batch.
A personalized order passes through proof, release, production and completion. MakeFlow keeps that state explicit, so the answer to 'where is order 1049?' is one glance rather than a search through mail and memory.
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
Does it sync status back to Shopify?
Order tagging and fulfillment sync are part of the connected app; the desk works fully without them.
Can I see what changed and when?
Every job carries an activity log: proof sends, decisions, status changes and batch releases.
Is there a customer portal?
No. Customers see a proof when you send one; the desk is for your team.