Merchant operations

How to name customer-specific files before Shopify delivery.

A consistent filename makes the final delivery check faster: identify the order, the deliverable, and its revision before attaching anything to Shopify.

Merchant workspace preparing customer-specific files for delivery

When every customer receives a different report, certificate, proof, or PDF, the filename is part of your fulfillment workflow. “Final.pdf” and “new-version-2.pdf” may make sense to the person who created them, but they are dangerous when a team is preparing several Shopify orders at once.

The practical answer is to use a predictable filename built from the Shopify order number, the deliverable type, and the revision. Then check that name against the order before attaching the file or sending the customer’s download email.

Use an order-first filename.

A useful pattern is:

order-number_deliverable_customer-or-project_revision.extension

For example: 10482_property-report_lee-family_v2.pdf. The order number should be the primary identifier because names and project descriptions can be similar. Keep the customer or project label short, and use a revision marker whenever a file can be replaced.

Keep the naming rules boring.

Do not make your team remember a different naming style for every product. Use lowercase, hyphens or underscores, and avoid special characters that behave differently across operating systems. Do not put passwords, full addresses, payment details, or other unnecessary personal information in a filename.

Also decide whether the order number includes a prefix. If Shopify shows an order as #10482, your internal filename can use 10482 consistently. The important rule is not the exact punctuation; it is that every person follows the same rule.

Add a delivery check before sending.

Filename discipline does not replace an order-linked delivery record. It gives your team a fast first check. Before sending a custom file, confirm:

If the file is still being prepared, leave it pending rather than attaching a draft. For multi-file orders, name and check each file separately. One correct filename does not prove that the other deliverables belong to the same order.

Worked example: a property document store.

Imagine a store that prepares a different property document pack for every buyer. Three orders arrive while the team is working: 10482 for Lee, 10483 for Patel, and 10484 for Nguyen. A folder full of final.pdf, final-2.pdf, and title.pdf creates a manual matching problem.

With an order-first convention, the files become 10482_property-pack_lee_v1.pdf, 10483_property-pack_patel_v1.pdf, and 10484_property-pack_nguyen_v1.pdf. The operator can compare each file with the Shopify order, attach it to the matching order item, and record the revision if the customer later requests a correction.

Email folders alone do not provide that structure. Generic product-level download apps also do not solve the identity problem when each buyer needs a different file. The filename helps, but the order must remain the source of truth for delivery.

Where QuickAttach fits.

QuickAttach is designed for the step after the file exists: attach the customer-specific file or secure link to the relevant Shopify order or line item, then deliver it through a branded customer download path when fulfillment is ready. That keeps the file, order context, and customer delivery connected instead of relying on an inbox search.

For the wider process, see how to prevent the wrong PDF from reaching a Shopify customer and how to replace a custom Shopify file. If your team is still using email and folders, read how to stop tracking customer files in email and folders.

Make the filename the first delivery check.

QuickAttach helps Shopify merchants connect the finished file to the order that produced it and give the customer a clear download path.

Install on Shopify