Selling digital products creates a filing problem that service businesses don't have: every product exists in three simultaneous versions, and mixing them up has customer-facing consequences.
There's the source file you edit. There's the delivery file the customer downloads. And there are the listing assets — mockups, thumbnails, descriptions — that sell it. Confusing these is how the wrong file ends up in a download link, and how you discover eight months later that you can't update a product because the editable original is gone.
The three-layer structure
04 Products/
[Product Name]/
01 Source/
02 Delivery/
03 Listing/
04 Docs/01 Source — the editable originals. Design files, spreadsheets, scripts, fonts used, linked images. Everything needed to rebuild the product from scratch.
02 Delivery — exactly what the customer receives. The final PDF, the zip, the template link. Nothing else in this folder, ever.
03 Listing — mockups, thumbnails, gallery images, video previews, and the written listing copy.
04 Docs — the product's own paperwork: license terms, the changelog, notes on what fonts and assets were used and under what license.
The discipline that makes this work is that 02 Delivery contains only shippable files. When you're updating a link at 11pm, you should be able to open that folder and have exactly one candidate. Any folder that contains both planner-v3-WORKING.pdf and planner-v3.pdf will eventually deliver the wrong one.
Version delivery files, and keep the old ones
02 Delivery/
Current/
Wedding-Planner-v4.pdf
Previous/
Wedding-Planner-v3.pdf
Wedding-Planner-v2.pdfTwo reasons to keep old delivery versions rather than overwriting.
Support. A customer emails about page 82 of a file they bought last year. If v3 is gone, you can't see what they're looking at.
Rollback. You upload v4, and within a day someone reports that a link is broken or a page is blank. Being able to restore the previous file in thirty seconds while you fix it is worth the storage.
Version the filename itself, not just the folder. Customers download files into their own downloads folders where your folder structure means nothing, and a file called planner.pdf is indistinguishable from any other.
The changelog is not optional
04 Docs/CHANGELOG.md, one entry per release:
## v4 — 2025-04-08
- Added 12 new pages (budget tracker section)
- Fixed typo p.34
- Rebuilt cover for higher print resolution
## v3 — 2024-11-02
- Fixed broken internal links in ToC
- Corrected page numbering after chapter 6This is the file that saves you when a customer says the file they downloaded is different from what's advertised, or when you're deciding whether to notify past buyers of an update. It's also what lets you write "Updated April 2025" in a listing with confidence about what actually changed.
Thirty seconds per release. It will be the most-consulted file in the product folder.
Fonts, images, and licenses go in the folder
The single most expensive mistake in digital product filing is losing track of what you licensed.
04 Docs/ASSETS-USED.md:
Fonts:
Playfair Display — Google Fonts, OFL, commercial use OK
Sofia Pro — Adobe Fonts, subscription — CANNOT embed in sold PDF
Images:
Cover photo — [source], license type, license ID, date purchased
Icons — [source], extended license purchased 2024-03-11, receipt in 02 FinanceTwo things this prevents. First, opening a source file in two years and finding a substituted font because your subscription lapsed. Second, and far worse, discovering that a font or image in a product you've sold 4,000 copies of was never licensed for that use. Font licensing in particular is full of distinctions — desktop versus web versus embedding versus sale — and the terms are not intuitive.
Where a license permits it, put a copy of the actual font or asset file in 01 Source alongside the design file. Cloud-synced font libraries are convenient and they disappear.
Bundles and variants
Digital sellers accumulate combinations fast: a product, a printable version, an editable version, a bundle of five, a seasonal variant. Trying to store these as separate full products duplicates everything and guarantees drift.
Keep one folder per product, with variants inside delivery:
04 Products/
Wedding Planner/
02 Delivery/
Current/
Wedding-Planner-A4-v4.pdf
Wedding-Planner-Letter-v4.pdf
Wedding-Planner-Editable-v4.link.txtAnd handle bundles as a manifest rather than a copy:
04 Products/
_Bundles/
Complete-Wedding-Suite/
MANIFEST.md ← lists which products and which versions
03 Listing/The manifest lists what's in the bundle and what version each component is at. When you update a component, you check the manifest to see which bundles are affected. Copying files into bundle folders means updating a product requires you to remember every bundle it appears in, which you won't.
Listing assets, per platform
If you sell on more than one platform, each has different image dimensions and different rules:
03 Listing/
Copy/
title-and-tags.md
description.md
Images/
Master/ ← the high-res mockups
Etsy/ ← sized and cropped for Etsy
Shopify/
Pinterest/Keep the master mockups separate from the platform crops. When a platform changes its image dimensions — which they do — you re-crop from masters instead of rebuilding.
Store listing copy as text files, not only in the platform's editor. Descriptions and tag sets are real work, they're reused across platforms, and having them locally means you can search and edit them without logging into anything. It also means you still have them if a shop is ever suspended.
The delivery-link register
Wherever your files are actually hosted for customer download — a shop platform, a file host, an email delivery service — keep a register:
Product | Version | Platform | Link | Last updated | Verified
Wedding Planner | v4 | Etsy | [listing] | 2025-04-08 | 2025-04-08
Wedding Planner | v4 | Shopify | [link] | 2025-04-08 | 2025-04-08
Wedding Planner | v3 | Gumroad | [link] | 2024-11-02 | ← STALEMulti-platform sellers update one platform and forget another constantly. The register makes the gap visible. Verify the links quarterly by actually clicking one and downloading the file — link rot in digital product delivery is common and silent, and the person who discovers it is otherwise a customer.
The rebuild test
Once a product is done, ask: if my computer vanished tonight and I only had the cloud copy of this folder, could I rebuild and re-deliver this product?
Missing fonts, linked images stored elsewhere, a design file that references a template on a platform account, a script with a dependency you didn't record — these are the usual gaps, and they're all invisible until the day they matter.
Run the test on your top three products. Those are the ones where the answer needs to be yes.
Next in this series: How to Manage File Access and Permissions for Contractors