Choose the scope of the change first
A catalog record describes what you sell. An existing order records what a particular customer bought. A new personalized PDF belongs to that customer’s delivery work, even when hundreds of people purchase the same catalog item.
Before uploading, ask a simple question: should every buyer receive this document, or only this order? If the answer is one order, choose a workflow that stores that association explicitly. QuickAttach documents file and link delivery per order item, which supports that distinction.
A scope review before you change anything
| Proposed change | Correct scope to investigate | Check before release |
|---|---|---|
| New personalized report | Existing order item | Customer and approved revision |
| Corrected public product description | Catalog | Effect on future buyers |
| New generic handbook for all purchasers | Shared digital-product workflow | Which purchases receive the update |
The table is an operational decision aid, not a claim that every app handles updates identically. Product-associated digital apps can have different rules for existing purchases. Verify those rules rather than using a shared attachment as a shortcut for one customer.
Fictional example: a finished portrait guide
Order 4107 and order 4108 both contain “custom framing guide.” Only 4107’s guide is finished. The merchant opens 4107, matches the current line item, and associates its final PDF through the order delivery workflow. The product page continues to describe the service; it does not gain a link to that customer’s document.
Before sending, the merchant checks whether the order was edited or canceled while the guide was being prepared. A correct file can still be attached to an outdated delivery plan if that check is skipped.
Test that the change stays with the order
- Use two harmless test orders for the same product.
- Record the product’s current public content and each order’s expected file state.
- Attach a synthetic document only to the first order item.
- Inspect the first customer’s delivery path.
- Inspect the second customer’s path and the shared product again.
- Record whether only the intended order changed, including any unexpected behavior.
This is a regression protocol to run in your store, not a completed result. Repeat the relevant checks when changing delivery apps or workflow settings. Never use a real customer’s private document to test whether an unintended audience can see it.
Deliver the right file with the right order
See how QuickAttach connects a customer-specific file or link to a Shopify order item.
See the QuickAttach order-to-download walkthrough