Use a small, stable pattern
A practical convention is order-item-purpose-vNN.extension. The order reference anchors the file to a purchase, the item distinguishes outputs within that purchase, and the revision separates corrections. Decide whether your team includes the Shopify display prefix and follow that decision consistently.
Use readable separators and keep the real extension. Do not rename a format to evade an upload restriction. Avoid customer email addresses, full addresses, dates of birth, passwords, and other unnecessary sensitive data. A filename often appears in emails, support notes, and download interfaces.
Ten synthetic examples
5166-poster-proof-v01.pdf
5166-poster-proof-v02.pdf
5166-poster-print-v03.pdf
5167-logo-screen-v01.png
5167-logo-package-v02.zip
5168-song-main-v01.mp3
5168-song-instrumental-v01.wav
5169-guide-setup-v02.pdf
5170-report-2030-04-v01.pdf
5170-report-2030-04-v02.pdf
These examples demonstrate naming only. They do not establish that every extension is accepted in your store or suitable for every customer device. Notice that revisions remain distinct from reporting periods: an April report can have both v01 and v02 without becoming a May report.
A fictional matching problem
Two demonstration orders contain a poster proof. One file is named final.pdf; the other follows the convention. Staff can identify the second candidate faster, but must still open it and compare the personalized wording with the order. Renaming the first file without inspecting it would simply give uncertain contents a convincing label.
Define exceptions before they spread
- For two similar items, add a stable item reference rather than a person's name.
- For a package, give the archive and manifest the same package revision.
- For a corrected period report, preserve the period and increment the revision.
- For drafts, use a clear draft label and keep them outside the release folder.
- For imported files, preserve any required supplier reference in the internal record.
Make the convention part of the final delivery check: order, item, intended output, revision, and actual contents must agree. Use the QuickAttach order workflow to retain the delivery context, rather than relying on filename discipline alone.
If an old name is already in customer circulation, record the mapping when you rename the replacement. Support needs to recognize both references without guessing which one the customer means.
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