Back to blog

Product photo filenames: SKUs, ZIPs and export manifests

Keep product photos traceable with SKU labels, safe ZIP filenames and JSON or CSV manifests. Learn what to verify before a catalog handoff.

By CatalogCut4 min read

AI-assisted product documentation based on CatalogCut’s implemented workflow and the linked sources. Examples are illustrative, not customer case studies. How these guides are prepared.

A product-photo handoff can fail even when every image looks good. A file called final-final-2.png does not tell an uploader which variant it belongs to, which slot it serves or whether it was approved.

Use SKU labels and an export manifest to preserve that mapping. Filenames make a folder easier to navigate; the manifest carries the information that a short filename cannot safely hold.

Agree on the product identifier first

Use the identifier your team already uses for the sold item or variant. Do not invent a second SKU system just for a photo project. Where two color variants have different SKUs, their images need distinct mappings even if the product name is the same.

In CatalogCut catalog runs, an export SKU is a run-level label. Editing it is not the same as changing a global product identifier in your store. Check it before delivery, especially if a supplier uses a different naming convention from your storefront.

For an illustrative spreadsheet, MUG-SAGE-300 and MUG-CREAM-300 distinguish the two variants. A label such as ceramic mug does not. These are organizational examples, not keyword recommendations for ranking in Google.

Expect safe filenames, not literal labels

An export service must handle slashes, reserved characters, empty labels and collisions. A seller label can contain characters that would be unsafe or confusing inside a ZIP path. Two different labels may also reduce to the same sanitized filename.

CatalogCut prepares safe, unique names for approved catalog exports. The filename therefore should not be treated as a lossless copy of the label. Use the JSON manifest when you need the exact original value and the associated output identity.

Do not rename a random image to fit a missing SKU. First prove that it depicts that item. A clean filename cannot repair a mismatched variant or unsupported product detail.

Read the manifest before uploading

An approved-output ZIP includes JSON and CSV manifests. Review the product and source references, chosen output, approval facts, final-file checks and inclusion or exclusion information. A run with twelve selected products can legitimately deliver fewer files if only some outputs were approved or available.

Use this handoff table as a review aid:

QuestionEvidence to inspect
Is this the right product?Product, SKU label and source reference
Is this the approved version?Chosen generation and review information
Did the file change?Final-byte checksum and dimensions
Is the delivery complete?Included rows and explicit exclusion reasons
What remains unresolved?Readiness findings and seller-review notes

A checksum connects a record to bytes. It does not certify that the photographed product is accurate or that Amazon will accept it.

Handle CSV as an interchange format

Spreadsheet software can interpret certain leading characters as formulas. CatalogCut neutralizes formula-like CSV cells for safer spreadsheet handling. As a result, a displayed CSV label may include protective formatting rather than being a byte-for-byte reproduction of the original text.

Use the JSON label when exact fidelity matters, and import the CSV deliberately rather than running or trusting arbitrary spreadsheet content. Neither file is a marketplace-specific bulk-upload template unless your downstream process explicitly maps it to that platform's required columns.

Archive the package with its decisions

Keep the ZIP and its manifests together. If someone optimizes, resizes or re-encodes an image afterward, the old checksum and readiness report no longer describe the transformed file. Prepare and review that new delivery rather than reusing the old evidence.

Download before the underlying images expire. Saved run history can retain decisions without retaining every photo forever. Finish with the team handoff checklist, including where the original files live and who will make the final publishing decision.

Keep a manual review sheet alongside the export

Use the free catalog review worksheet to connect your SKU, selected source, image role and approved output filename. A blank CSV and a fictional filled-in example are available without an email address. They are manual team checklists, not a replacement for the app’s actual export manifest or a marketplace import template.

Resolve two labels that sanitize to similar filenames.

Two fictional seller labels containing slashes and spaces.

  1. Keep the original label

    Retain the exact seller-entered identifier in a lossless record rather than using the filename as the database.

  2. Read the safe filename

    Expect path-safe unique archive names instead of literal slashes or reserved filename characters.

  3. Match the manifest

    Use the JSON label and output identity to match the delivered file before assigning its storefront variant.

Illustrative workflow. Review checkpoint: Formula-safe CSV formatting and filename sanitization can differ from the original JSON label.

Official sources