How to send custom proofs to the correct Shopify customer.

A custom proof is usually made for one customer: a design approval, artwork mock-up, personalised preview, or production-ready document. Because the proof is created after the order is placed, it does not exist when the customer checks out. The practical solution is to treat the Shopify order as the delivery record, then attach the finished proof to that order before sending it.

This is different from a standard digital download. A product-level file sends the same asset to every buyer. A proof workflow needs a different file for each order, with enough context for the team and customer to know exactly what it represents.

Why custom proofs get lost.

Many merchants start with an inbox and a folder. The order arrives, a designer creates a file, and someone emails it manually. That can work for a handful of orders, but the connection between the proof and the purchase becomes fragile as volume grows.

• A filename may not make the customer or order obvious.
• The latest revision can be confused with an earlier proof.
• Support has to search email to confirm what was sent.
• A customer may not know where to find the proof again.

A reliable Shopify proof workflow.

1. Capture the brief with the order. Keep the customer instructions, selected product, and any reference details associated with the Shopify order. The order is the anchor for the work that follows.

2. Create and check the proof. Prepare the file after payment, then check the customer name, order details, revision, and intended output before delivery. A short filename that includes the order number can make the human review easier.

3. Attach the proof to the matching order item. Upload the finished file or add its secure link to the order and line item it belongs to. This is the step that prevents a custom deliverable from becoming an orphaned attachment in a shared folder.

4. Tell the customer what is ready. The delivery message should identify the order, describe the proof, and explain what the customer should do next. If approval or feedback is required, say so clearly rather than treating the file as a final production asset.

5. Keep the path available. Customers may lose an email or return later from another device. An order-linked download path gives them a sensible place to find the proof again, while support can start with the order when answering questions.

Example: a personalised packaging proof.

Imagine a store selling custom packaging artwork. A customer orders a design package and provides their business details at checkout. The merchant creates a PDF proof the next day, checks that the logo and wording match the order, and attaches that file to the relevant order item. The customer receives a branded delivery email with the proof and can return to the order-linked path when they need another copy.

If the customer orders two different design packages, each proof should remain identifiable as its own deliverable. That is why an order-and-line-item workflow is more useful than a single product download attached to the catalogue item.

Where QuickAttach fits.

QuickAttach is being built for Shopify merchants who create a different file or secure link for each order after checkout. It connects the deliverable to the relevant order item, supports a branded download email when fulfillment is ready, and keeps a customer download path associated with the order.

For the broader setup, read how to deliver a file created after checkout. To reduce mix-ups, see how to prevent sending the wrong PDF. For multiple proofs in one purchase, read how to manage made-to-order PDFs for multiple line items.