Define success as using the file
A mobile screenshot can show that a button fits the screen. It cannot establish that the button leads to the intended document or that the customer can open it. Follow the journey far enough to inspect the contents and understand where the file goes on the device.
The QuickAttach delivery flow includes an email download action and a supported order-status return path. Test the paths your store actually offers, with a harmless file in the same format and approximate complexity as the products you sell.
A phone test record
| Record | Example of useful detail |
|---|---|
| Device context | Phone model, operating system, browser, email client |
| Entry point | Delivery email or verified order page |
| File | Synthetic PDF, archive, or supported output type |
| Account context | Signed in or the supported guest route |
| Observed result | Opened, saved, blocked, or unclear |
Do not label a test “mobile passed” without this context. Different entry points can behave differently even on the same phone.
Run the journey
- Receive the synthetic delivery email through the normal send process.
- Identify the store and ready item without zooming repeatedly.
- Select the download action and observe any sign-in or redirect.
- Confirm that the resulting file contains the expected test marker.
- Try the save or open action appropriate to that device and format.
- Leave the page, then return through the supported customer route.
- Repeat the relevant case for an external destination if your store uses one.
Fictional example: an archive adds a step
A studio delivers a PDF and source artwork together for order 4507. Its phone test reaches the archive successfully, but the tester does not know how to access the files inside. The issue is not necessarily a failed download. The merchant may need clearer package instructions or a different supported delivery format.
The scenario is illustrative; no device result is claimed. Record what actually occurs in your test and avoid inventing a universal tap sequence for every phone.
Turn findings into specific fixes
Classify each problem as message clarity, page layout, account access, provider permissions, file format, or saving instructions. This makes the next action concrete. Send support sanitized details for app issues, including the visible error and tested route. Never include passwords or working private access links in a public report.
Retest the affected step after changing it, then confirm the full journey still reaches the correct file.
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