Proof approval with a real audit trail.
Approval by email and screenshot has no version history and no record of what was agreed. MakeFlow sends a calm, branded proof page, records the decision with a timestamp, and keeps every round so 'what did they approve?' has an answer.
- Branded, mobile-friendly proof page
- Approve or request a change
- Version history kept forever
- Waive proofs for simple items
Three steps from paid order to released batch.
Approval by email and screenshot has no version history and no record of what was agreed. MakeFlow sends a calm, branded proof page, records the decision with a timestamp, and keeps every round so 'what did they approve?' has an answer.
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 customers see the artwork?
Yes. Captured image and PDF links are shown on the proof page next to the written details.
What happens on a change request?
The job moves to a revision state with the customer's note attached. Sending again creates the next version.
Can I approve on the customer's behalf?
Yes, for phone approvals. The decision is still recorded with a timestamp and note.