“Customer account” is not a complete configuration description
A help procedure that simply says “log in and open downloads” can fail if the store does not expose that route. Record the account setup, enabled extensions, and pages used in your actual customer journey before writing instructions.
Shopify’s documentation explains that app blocks are added to supported pages in the checkout and accounts editor. Available pages and settings depend on the app and configuration. The QuickAttach walkthrough describes an order-status return path, not a universal guarantee for every account mode.
Keep a configuration record
- Store account experience in use.
- Page where the download block is enabled.
- Relevant app and block settings.
- Customer route used to reach the order.
- Whether the tested route requires sign-in.
- Date and devices used for verification.
This short record helps support distinguish a configuration change from a customer mistake. It also avoids treating an old screenshot as evidence of the current store experience.
A fictional acceptance scenario
A merchant creates two controlled customer identities and two synthetic orders. Each receives a different test PDF. The tester signs in as the first customer through the store’s normal route, opens the corresponding order, and checks the available file. They then repeat with the second identity in a separate browser context.
The test should record which order is visible and which file opens. Merely reaching an account homepage is not enough. Avoid probing with real customer data or assuming that one successful guest path proves the signed-in path works.
A focused test matrix
| Case | Question |
|---|---|
| Delivered order | Can the intended customer retrieve the correct file? |
| Undelivered order | Is the lack of a ready file understandable? |
| Return visit | Can the customer find the order again? |
| Different customer context | Does each tested identity see its appropriate order and file? |
| Phone | Does sign-in and retrieval remain usable? |
These are proposed checks, not completed results or a security certification. Record unsupported cases explicitly and do not advertise them as available.
When an extension fails to appear, confirm page support and saved configuration before changing customer records. Ask QuickAttach support with sanitized details about the account mode, page, and observed behavior. Once verified, publish instructions that match the exact route customers will use.
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