Recover Shopify product content from a genuine product export before rebuilding it from archives. A CSV can preserve structured product and variant fields; a public capture can help verify visible wording and images. Neither should be treated as a complete store backup. Review collections, image availability, importer behavior and current owner decisions separately.
Do not import an unreviewed recovery spreadsheet into a working catalog. An update intended to restore one description can overwrite other values or alter variant relationships if the file is prepared incorrectly.
Read the source file before repairing it
Retain the original export unchanged. Record its date, originating store and the set of products it was meant to include. Check whether it is a complete export or a selected subset. An absent row may reflect the export scope rather than a lost product.
Compare identifiers and handle relationships with the current catalog if one exists. Product titles are not reliable enough for automatic matching. Separate deliberate renaming from a recovery mismatch, and preserve established handles where the agreed URL plan requires them.
A file with many columns can still be incomplete for the specific recovery. Identify which required fields survive, which are blank and which rely on information elsewhere. Do not fill gaps with values from a superficially similar product.
Use public evidence to verify, not invent structured records
Match each capture to the correct product and capture date. Extract only readable descriptions, specifications and public images that are actually supported. Keep historical prices and stock statements as dated evidence pending current business approval.
Separate a confirmed option from an inferred variation. A captured selection control does not demonstrate all combinations or their private IDs. Missing internal relationships need a native source or an explicit new reconstruction decision.
Do not treat storefront evidence as a source for customer records, orders, supplier costs, private app data or confidential integration settings. The recovery file should disclose those boundaries without hiding them behind a general claim of complete restoration.
Review Shopify’s import dependencies
The current Shopify CSV guidance distinguishes new-product requirements from updates. It warns that dependent option columns matter and that changing option values can replace variant IDs, affecting integrations. Variant metafields are not supported by the product CSV.
Review the exact current file schema, not a remembered template. Do not remove columns solely to simplify the spreadsheet without checking what remaining fields depend on them. A narrow content repair should avoid unnecessary changes to working variants and connected systems.
Have the owner approve which products may be purchasable after reconstruction. Explicitly review publication status and current prices instead of relying on importer defaults. Technical import success is not business approval to sell.
Collections require a separate relationship review
Shopify’s documentation says its optional Collection import column is not included in product CSV exports and assigns only one collection through that column. A product export therefore should not be assumed to preserve every collection membership.
Record missing collection relationships independently. Review surviving admin information, owner-held lists and public collection captures. For conditional collections, identify the actual rule rather than manually assigning products until the page happens to resemble a screenshot.
Preserve each collection’s purpose and historical URL where possible. Do not create an empty collection for every captured navigation label or collapse unrelated categories into a single general shop page.
Image URLs are references, not proof that files survive
Inspect the image sources associated with each product. Verify that the intended files are accessible, authorized for reuse and correctly matched to the item or variation. A spreadsheet cell can contain a valid-looking address whose image no longer exists.
Keep a media-acceptance note: source reference, verified file, intended product relationship and reviewed display. Replacements supplied by the business should be identified as replacements in the private recovery record, not claimed as the original recovered photographs.
Review descriptive image text and displayed order after preparation. A missing secondary image may matter if it shows a specification, included accessory or different product state. Do not substitute an unrelated file simply to fill a gallery slot.
A controlled product-content handoff
- Preserved source: unchanged export and scope/date record.
- Identity map: original handles and confirmed product/variant references.
- Working file: documented recovered fields and owner-approved replacements.
- Relationship exceptions: unresolved collections, options, images and external dependencies.
- Review result: representative authorized import or preview evidence, with affected values compared before and after.
Use a small representative review before wider application. Verify the affected description, existing variants, handle, collection result, image order and publication state. Keep errors and skipped items visible instead of reporting the file’s row count as a recovered product count.
For an archive-led reconstruction request, the recovery review can assess native exports and public evidence within an agreed Shopify scope. If several sources need reconciliation, use the source-mapping approach to identify what each one can actually supply.
Shopify catalog questions
Is a product CSV a complete store backup?
No. Inspect its specific fields and export scope, then review collections, assets, private commerce records and integrations independently.
Can descriptions be repaired without changing variants?
That should be the intended scope of a description repair, but verify the current schema and update behavior carefully. Do not remove dependent columns or alter option values without reviewing the consequences.
