An order-wide label can hide useful detail
A customer who bought three custom items needs to know which of the three can be used now. A broad “in progress” label can hide a finished file; a broad “complete” label can imply unfinished work is ready. Per-item language makes the delivery scope easier to understand.
QuickAttach documents partial delivery, and its walkthrough describes an order-status download path. Those statements do not establish every possible pending-state label or customization control. Inspect your configured customer page before writing instructions about it.
A state-copy specification
| Business state | Useful customer wording | Action |
|---|---|---|
| Work not yet released | Still being prepared | Explain next update if needed |
| Reviewed and delivered | Ready to download | Offer the matching download |
| Previously delivered but unavailable | Download currently unavailable | Provide a support route |
| New revision delivered | Revised version available | Identify the intended revision |
This is a content specification, not a screenshot of QuickAttach or a promise that each label is configurable. Apply it through the controls your store actually supports. If the page cannot show necessary context, use accurate delivery-email wording and a verified help route.
Fictional example: a two-part planning order
Order 4503 contains a room diagram and a shopping list. The diagram is delivered first. A customer-facing explanation says the diagram is ready and the list is still being prepared. The buyer can begin reviewing the room arrangement without assuming the list was omitted accidentally.
When the list is released, the merchant checks the return page again. Both files should remain distinguishable by item and intended revision in the observed workflow. The test should inspect the actual result, not just the text of the second email.
Review the page in three moments
- Before any item is delivered, record what the customer sees.
- After a partial release, check both the ready item and the remaining work.
- After the final release, check that the page and messages no longer imply unfinished production.
Use synthetic files and record any mismatch between the page, email, and production record. These are planned checks, not completed results.
Do not rely on color alone to distinguish states. If a limitation prevents a clear customer experience, describe the exact issue to support and keep customer promises aligned with the verified behavior.
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