Editable Source Files Versus Viewing Exports: An Honest Deliverable Inventory for a Download Shop

Buyers of digital downloads often misunderstand what is inside the package. One buyer expects a file they can modify; another only wants something to print or view. If the page is vague, both are disappointed. This article proposes a product-page workflow that separates an editable source file from a viewing export and shows an honest inventory of deliverables. It is an example process, not an observed client result, and it deliberately avoids naming file formats or software.

Plain definitions

Editable source file: a file intended to be opened in suitable software so the buyer can change its contents, such as text, layout or parts.

Viewing export: a fixed copy meant for looking at, printing or sharing. It is not designed for changing the content, even if some changes might technically be possible.

Write these two definitions on the page in your own words, once, and link to them from each product.

Inputs

Use a hypothetical sample. A fictional seller offers a "Weekly meal planner sheet". Gather for each file in the package:

1. Display name as the buyer will see it.
2. Role: editable source, viewing export, or supporting extra such as a short guide.
3. What the buyer can do with it, in one sentence.
4. What the buyer cannot do with it, in one sentence.
5. What software category is needed, described generally, such as "a program that can open layout files", only if you are sure.

Decision branches

Step 1: Does the package include an editable source? If yes, list it first and describe what can be changed. If no, state plainly: "This product contains viewing exports only. You cannot edit the layout." Do not leave it to inference.

Step 2: Does the package include a viewing export? If yes, state its intended use, such as printing at home.

Step 3: Are any parts of the editable file locked or dependent on items not included, like a typeface? If you know of a dependency, say so. If you are unsure, say "Check the included guide before editing" only if the guide really covers it. Never claim compatibility you have not verified.

Step 4: Do the two files represent the same design? State whether the export is generated from the source and whether they are the same version.

Stop conditions

Stop and fix the listing if any file lacks a stated role. Stop if the source and export differ in content and the page does not say so. Stop if you cannot verify what a file contains; open every deliverable before writing its line.

Sample deliverable inventory

File 1: Meal planner, editable. Role: editable source. You can change headings, days and notes. You cannot recover the original if you overwrite it, so keep a copy.

File 2: Meal planner, print version. Role: viewing export. You can print or view it. You cannot change the text.

File 3: Quick start guide. Role: supporting extra. Explains which file to choose.

A short line beneath the table says: "Both files show the same design, version 1."

Choosing guidance for the buyer

Add two lines: "Want to change wording or days? Choose the editable file. Only want to print as is? The print version is enough." This avoids pushing every buyer toward the larger file.

Acceptance test

Open the finished product page and give it to someone who has not seen the product. Ask them three questions: Which file can I edit? Which file should I use just to print? Is there anything I cannot do? They should answer correctly from the page alone. Then download the real package and compare it against the inventory item by item: names, roles and count must match exactly, and the export must show the same content as the source. The test passes only if the inventory matches the package, no file is unexplained, and a product with no editable source says so openly.

Conclusion

An honest inventory sets expectations before purchase. Define the two terms once, label every file with a role and a limit, verify contents yourself, and let buyers choose the file that suits their need.

Sources