Guide · 7 min read · updated 2026-09-30

A proof approval workflow for custom orders

A proof approval workflow is a fixed sequence that ends in one thing you can point to: a specific version of the design, for a specific order line, that the customer said yes to. The six steps are to collect the file with the order line, prepare a proof, send it as a private link, let the customer approve or request changes, retire the old version whenever anything changes, and verify the approved version against the order before you make it.

1. Collect the source file with the order line

Everything downstream depends on knowing which file belongs to which line. If the customer uploads on the product page, the file arrives already attached. If it arrives by email, the first job is to match it by hand, which is where mix-ups start. See how to collect customer artwork on Shopify.

2. Prepare the proof

A proof should show the work as it will be made, not the customer’s file as it arrived. Put on it whatever a production decision depends on:

the artwork in its final position and size;
quantity, size, material and finish for that order line;
a version number, so everyone can name the version they mean;
up to three options when the customer has a real choice to make, such as two layouts.

3. Send a private link, not an attachment

An attachment is a copy that can be forwarded, renamed and confused with the next one. A private link keeps one page as the source of truth. The customer needs no account: they open the link, review the proof and respond. Opening the link is not approval; the customer has to take an explicit action.

4. Let the customer approve or request changes in the same place

When approval and change requests happen on the same page as the proof, the answer is attached to the exact version being discussed. That removes the “looks good!” that arrives three replies later, about a file nobody can identify.

5. Version every change and retire the old approval

Any change to the design or the production details should produce a new numbered version. The previous approval must stop working at that moment, otherwise an old “yes” can be used to approve new work. In Upproof, publishing a new version retires the previous approval link.

6. Verify before production

Approval applies to a particular version, not to the order forever. Before you make anything, check the approved version against the current order and the stored files. If the order changed after approval, for example a different quantity or variant, get the updated work reviewed first. A production card that is generated from the approved version, and checked against the order, gives the person at the machine one page to follow.

Where workflows usually fail

Approval lives in a thread. The order is in Shopify, the yes is in an inbox, and the two are matched from memory.
The order changes after the approval. Nobody re-checks, and the customer receives what they approved for a different order.
Two lines, one variant. Two designs share a product variant and the files get swapped.
The old link keeps working. A revised design is approved through a stale link.

Questions

Does the customer need an account to approve a proof?

Not with Upproof. The customer opens a private link, reviews the proof and approves it or asks for changes on the same page.

Is opening the proof link the same as approving?

No. Opening a link never approves a proof. Approval needs an explicit action by the customer.

What happens to the old approval when the design changes?

Each proof is a numbered version. Publishing a new version retires the previous approval link, so an old “yes” cannot approve new work.

What if a customer loses the proof link?

Links are shown once. Publish a new version and share its link; the earlier version’s link stops working.

Keep reading

Upproof adds artwork upload and versioned proof approval to Shopify product pages. See it in the Shopify App Store or read how approval works.