I keep seeing the same fragile handoff in custom-product stores:
A proof is sent by email.
The customer replies with something like “looks good”.
Someone has to work out which attachment they meant.
Production is told separately that the job can start.
It works — until revisions, busy inboxes, or several team members are involved.
I built a free two-minute workflow check for Shopify merchants who sell personalised products, printing, signage, embroidery, packaging, or anything else that needs customer approval before production:
It asks six practical questions and gives you a risk score plus one recommended next step. There is no signup and the answers are not saved.
Full disclosure: I am also the developer of ClearToMake, a recently launched Shopify app that connects proof versions, customer decisions, and production holds to the order. The check is useful without installing the app.
I would genuinely like to learn from merchants doing this every day:
Where does final approval live in your current workflow?
How does production know which version is safe to make?
What is the most expensive or frustrating failure you have seen?
I’d be genuinely interested to hear how custom-product merchants handle this handoff today.
One useful follow-up: I turned the workflow above into a practical, step-by-step guide for Shopify custom-product teams:
It covers the five handoff steps, the warning phrases that should pause production, and the minimum evidence an approval record should contain. Full disclosure: this is published by ClearToMake, but the workflow is usable without installing the app.
If you run proofs after checkout, I would be interested to know which part does not match the way your shop actually works.
The above is definitely possible with regular Shopify without Plus, by combining several purpose-built apps rather than relying on Shopify B2B, which is Plus-only.
Some pieces to investigate:
Wholesale/B2B Ordering Apps — There are a few non-Plus apps for handling wholesale, dealer or wholesaler applications, and custom checkout fields like PO numbers.
Custom checkout fields (PO number, delivery date, delivery method) most wholesale apps have these built in, but if you need more flexibility, a simple form app that writes to order notes/metafields works well too.
Quoting - this is usually bundled into the same wholesale apps rather than needing a separate solution.
Order approval — worth thinking about whether you’ll need any orders held for review before they’re processed, e.g. high-value POs or new accounts. If so, there are lightweight approval apps (SampleGuard is one I’ve used) that sit on top of your existing setup and pause specific orders for sign-off without needing Plus.
Packing slips with signature proof of delivery — this is more of a fulfillment/shipping app feature, worth checking your shipping app or a standalone packing slip app for signature capture.
Invoicing (PO number, discount terms, multi-recipient sending) — the hardest piece to match outside Plus. Dedicated B2B/wholesale invoicing apps tend to handle discount terms and multi-email sending better than Shopify’s native invoicing.
Realistically you’re looking at combining a couple of apps here rather than one all-in-one solution, but it’s very doable.
Thanks, Yuta — this is exactly the distinction I was trying to get at.
ClearToMake already records the proof version, a SHA-256 file hash, customer email, timestamp, and written note in an immutable receipt. Uploading a new proof also blocks Shopify fulfillment again. Your point about order changes is right, though: approved quantities and options need to be part of that record, and any relevant edit should invalidate the release. I’m implementing that now.
The multi-route question is the harder one. A Shopify fulfillment hold can enforce the state inside Shopify, but a CSV export or external production board can still bypass it. My current direction is to make the approval state easy to verify and integrate at the production handoff rather than pretend one Shopify hold controls every external path.
I’ll also change the validation questions to focus on the last real failure: remake cost, shipping delay, and staff time. That is a much stronger pricing signal than a general risk score.