Shopify operations · 8 minute read
How to stop an unapproved custom order reaching production
A proof approval process is safe only when the exact version, customer decision, and production release are connected. Here is a practical workflow for Shopify stores selling made-to-order products.
The short answer
Email can carry a proof. It cannot protect production.
Most approval failures are not caused by a difficult customer. They happen because the proof, the decision, and the production status live in different places. One person sees an approval email, another downloads an older attachment, and production starts from the wrong file.
- Which exact proof did the customer approve?
- Where is that decision recorded?
- What prevents production from starting before it?
The recommended workflow
Five controls from paid order to clear-to-make.
You do not need a complicated creative-review system. You need a small number of operational controls that remain clear when revisions, staff changes, or busy inboxes are involved.
Start from the Shopify order
Keep the customer, line item, requested customisation, and proof status together. A separate project name or email subject should never be the only link back to the order.
Give every proof a version
Treat each revision as a new version. Do not overwrite the old file. Production should be able to see exactly which version is current and which versions were rejected.
Ask for an explicit decision
Use two unambiguous actions: approve this version or request changes. A reply such as “looks good” is risky when several attachments or conversations exist.
Hold production while approval is open
The order should remain visibly blocked until the required decision exists. A message to production is not the same as a gate that everyone can verify.
Release with a durable receipt
Record the approved version, decision, customer, and timestamp. The production release and the evidence for it should be part of the same handoff.
Where the process breaks
Four phrases that should make production pause.
Looks good!
The decision sounds positive, but the version is unclear.
Use the latest one.
“Latest” depends on which inbox or folder someone opens.
I told the workshop.
The release exists as a conversation, not an order status.
We can find it later.
The evidence is already fragmented before a dispute occurs.
Minimum viable evidence
What the approval record should contain.
The goal is not paperwork. It is one durable source of truth that a merchant, production teammate, or support agent can understand without reconstructing a conversation.
- Order
- The Shopify order and relevant line item.
- Version
- The exact proof file and its version number.
- Decision
- Approved or revision requested — never inferred.
- Identity
- The customer or authorised approver.
- Time
- A reliable timestamp for the decision.
- Release
- The resulting production status and receipt.
Choose the right level
Manual, connected, or gated?
| Approach | Works when | Main risk |
|---|---|---|
| Email + checklist | Volume is low and one person owns every order | The approved version still has to be reconciled |
| Shared status board | Several teammates need visibility | Status and proof can drift apart |
| Order-linked approval | Approval is a repeatable part of production | Requires a clear setup and owner |
| Production gate | A wrong release creates expensive remakes | The gate must match the real fulfilment flow |
Free two-minute check
How exposed is your current workflow?
Answer six practical questions. No signup, and your answers are not saved.
Questions merchants ask
Before changing the workflow.
Is a customer email enough proof of approval?
It can document intent, but it often leaves the approved attachment or version unclear. A safer record connects the decision directly to one proof version and one Shopify order.
Should production begin before the customer approves?
Only when the product and your terms genuinely do not require approval. If approval is part of the sale, keep the production status blocked until the decision is recorded.
What should an approval record contain?
At minimum: Shopify order, proof version, decision, customer identity, timestamp, and the person or system that released production.
Does the customer need another account?
Not necessarily. A secure, order-specific link can give the customer a clear approve-or-revise step without asking them to create an account.
Built for this handoff
Connect the proof, decision, and production release.
ClearToMake adds a versioned approval workflow to Shopify orders. Customers review without an account, while your team gets a clear production gate and approval receipt.
View ClearToMake on Shopify 14-day trial · $19/month · billed by Shopify