Short answer: treat a pre-order as a paid order with a clearly pending deliverable. Confirm what the customer ordered, record the expected preparation point, create the file when the underlying work is ready, review it against the order, and deliver it through the order-specific path. Do not send a generic product download or a premature placeholder just because the order exists.
This workflow fits stores selling made-to-order reports, future-dated certificates, custom plans, property documents, readings, audits, and other files that cannot exist at checkout. The customer may pay today, but the correct document may depend on a later event, a completed service, or information that is still being processed.
Why pre-orders create a file-delivery risk.
A normal digital download assumes the file already exists and is the same for every buyer. A pre-order for a custom deliverable breaks both assumptions. The file may be created weeks later, and every customer may receive a different result.
Manual email makes the timing problem worse. A message in an inbox can be marked complete even when the file is still pending, while a shared folder may contain several customers waiting for similar documents. Sending too early, forgetting the order, or attaching a file to the wrong customer are all easy mistakes when the order and deliverable live in separate systems.
Use a pending-to-ready workflow.
- Confirm the order context. Check the Shopify order number, customer, line item, requested deliverable, and any date or event that controls preparation.
- Mark the file as pending. Keep the paid order visible in the work queue. A pending status is more useful than pretending fulfillment is complete.
- Set a preparation checkpoint. Add the next action to the team's workflow: a service date, source document, approval, or other input needed before the file can be created.
- Prepare the customer-specific file. When the required information is available, create the report, certificate, proof, or PDF for that order—not from a generic product folder.
- Review before delivery. Match the customer name, order details, requested scope, dates, and file contents. For sensitive documents, use a second-person check where practical.
- Attach it to the order item. Upload the file or add the secure link to the matching Shopify order and line item. Avoid starting a disconnected email thread.
- Deliver when ready. Send a clear branded download email that says what is ready and gives the customer one obvious next action.
Worked example: a future-dated property report.
Imagine a store selling a property monitoring report that is prepared after a scheduled inspection. Taylor places a pre-order in June for a report due after the July inspection. The merchant records the order as pending, keeps the promised timing visible, and does not send an empty PDF or a generic guide.
After the inspection, the team prepares Taylor's report, checks the property details and order number, then attaches the finished PDF to that order item. Taylor receives a delivery email when the report is actually ready. If support receives a question later, the team starts with the order rather than searching an inbox for a June promise.
What to tell the customer while the file is pending.
Set expectations at purchase and repeat them in any status message. Explain that the file is prepared specifically for the order, give the expected timing or trigger, and say that the customer will receive a download message when it is ready. Do not call an order fulfilled merely because payment was received if the custom deliverable is still being prepared.
If the timing changes, update the customer with the new expectation and keep the order in the pending workflow. For a broader approach, read how to tell a customer their custom file is still pending.
Why a generic digital download app is not enough.
Product-level download apps are useful when every buyer receives the same asset immediately. They are a poor fit when the file is created later and differs by order. Manual email can deliver the finished document, but it leaves the pending state, order match, and delivery record dependent on team discipline.
QuickAttach is built for order-specific file delivery: attach a different file or secure link to the relevant Shopify order item, deliver it through a branded email when fulfillment is ready, and keep the customer download path associated with that order.
For orders with several deliverables, see how to handle partial file delivery. For the general model, read how to deliver a file created after checkout.
Keep pre-order files tied to the order.
QuickAttach helps merchants prepare customer-specific files after checkout and deliver each one when it is genuinely ready.
Install on Shopify