Shopify Digital File Not Received: A Troubleshooting Checklist

Ask for the symptom before resending

Use a neutral question: “Did the delivery email arrive, and what happens after you select the download button?” Record the order reference and the visible error, without requesting the customer’s document. Confirm the requester through your normal support process before changing a recipient address.

A payment receipt is not evidence that a made-to-order file has been prepared. Likewise, an uploaded file does not prove a delivery email was sent. Check each transition independently. QuickAttach documents delivery and download tracking; use the available record as a clue, not proof that a person read the content.

A decision tree for the support desk

1. No finished file against the item: route the case to production and provide a realistic update. Do not resend an empty delivery.
2. File attached, no send recorded: verify the recipient and approved version, then perform the intended delivery action.
3. Send recorded, no email found: check the address, message time, spam folder, and any visible delivery error.
4. Email found, link fails: record whether the destination is app-hosted or external. Investigate expiry, deletion, and external permissions separately.
5. File downloads but cannot open: inspect format, completeness, and required software. A successful transfer does not validate the file.

A fictional case

Order DEMO-461 contains a custom analysis. The buyer says the PDF never arrived. Support discovers that the email arrived and its button opens Google Drive, which requests permission. The useful correction is to check the intended Google identity and sharing settings. Sending the same email again would leave the permission problem unchanged.

After a correction, test with a permitted identity that does not own the file. Ask the buyer to try the latest message, then record what worked. Avoid deleting the delivery record simply to make the order look clean.

Close with an actionable handoff

Keep a short internal note: order, affected item, last working step, observed error, action taken, next owner, and next update time. If escalating to QuickAttach support, include the store domain and relevant error while excluding passwords and unrelated customer information. The case is ready to close when the customer has a usable route to the intended file, not merely when a second message has been sent.