1. Keep an untouched original
Save the exported or supplied file once, clearly named and dated. Treat it as read-only and make changes in a separate working copy. If a formula, find-and-replace or automatic correction goes wrong, you can compare literal values with the source instead of reconstructing them.
2. Name the destination and importer
Adding products, updating them and moving a catalog are different jobs. Identify the platform and exact importer before changing columns. Start from a fresh export or current template rather than assuming an old file still represents the destination.
Shopify documents dependencies between product and variant columns. WooCommerce’s built-in importer uses its own CSV schema and UTF-8 encoding; extensions can require different fields. Check the Shopify product CSV guide and WooCommerce importer documentation for your workflow.
3. Protect identifiers as text
Spreadsheet software can remove leading zeros, display long digit strings in scientific notation or interpret values as dates. When importing the file into your editor, explicitly treat identifier columns as text before conversion occurs. Formatting a damaged value afterward does not restore it.
After export, inspect the saved CSV and compare representative SKUs and barcodes literally with the original, including leading zeros. Include the longest values and unusual characters in the check. A value looking plausible in the spreadsheet is not enough.
4. Define what may change
Write down the allowed transformations and the fields that must stay unchanged. Trimming title whitespace is a different decision from altering a price, inventory quantity, SKU or an identifier used by a connected app.
On Shopify overwrite imports, an included blank non-required field can clear an existing value; an omitted field generally retains it, subject to documented dependencies and defaults. Changing option values can recreate variant IDs. WooCommerce matches existing products by ID or SKU and provides column mapping, so confirm the match key. These platform-specific behaviors are described in the Shopify guide and WooCommerce guide.
5. Resolve exceptions deliberately
A duplicated SKU, missing price or ambiguous variant should become a question, not an invented answer. Record the row, field, issue and decision needed. Pause the affected product group until its owner resolves the uncertainty. Do not silently remove individual rows without checking parent, variant and importer dependencies.
6. Test a small batch and plan recovery
Use a representative batch in an appropriate test store or staging setup: simple products, variants and special characters. Inspect the result in both admin and storefront before the store owner runs the live import. Keep a change record and the checks performed.
A product CSV export is not a complete backup. Re-importing an older file may not reverse every change, so verify what your platform’s recovery options actually restore before relying on them.
See what a documented handoff looks like
Our Catalog Rescue synthetic sample shows proposed edits, a cell-level change log and unresolved questions. It is an illustration, not a customer file or an import-ready template.
The $199 pilot covers one CSV of up to 150 product or variant rows. It includes no store access or import. Start with a description at the studio intake form (or support@beardbytelabs.com); no attachment or payment is needed for the initial inquiry.