Your Shopify CSV Downloaded. Can You Actually Use It?

Imagine opening a supplier file and seeing SKU 00042 displayed as 42. The sheet looks tidy. The identifier has changed.

Now imagine matching that row to another system. The repair work starts after the export reported success.

That small example captures why I care about export quality while building Catalog Prep. The useful question is what survives the handoff from the public storefront to the file you will work with.

Keep an untouched file before opening a working copy

Save the original download. Use Catalog Prep's text-typed catalog.xlsx for spreadsheet inspection, or import its CSV with identifier columns explicitly set to text.

Long product IDs can be rounded. Date-like strings can be reinterpreted. Leading zeros can disappear. Source values that resemble formulas should be inspected as text rather than executed.

The exact CSV preserves source text. The workbook helps you view it without turning an identifier into a guessed number. Keep your analysis and corrections in a separate copy.

Use identity before SKU

In a retained 28 October 2026 audit of Silver Paw's public feed, there were 89 unique products, 267 variants, and 264 distinct nonempty SKUs.

Those counts are enough to show why SKU alone is a poor deduplication key. A missing or reused SKU does not cancel a valid variant identity.

For a simple illustrative product:

That is one product and three variants. Keep the third row, preserve its identity, and mark the missing value for review. Inventing a SKU would hide what the source actually supplied.

Catalog Prep retains product and variant identities and flags reused SKUs. Check returned option sets against a few source products before you use the file downstream.

Follow an image back to the right product

A product gallery and a variant-specific image are different relationships. A default product photo should not become evidence that a particular size or color has a distinct image.

Use images.csv and normalized JSON to inspect product associations, gallery order, and variant references where exposed. Catalog Prep exports the links and available metadata; it does not download image binaries.

Open a few references while reviewing the capture. Source-hosted URLs can change, so retain observation time and confirm permitted reuse before moving assets into another system.

Keep the price beside its currency evidence

The same dated Silver Paw audit recorded a CAD page-currency hint and USD in public shop metadata. A visible currency symbol alone was insufficient to explain the cookie-free feed's price context.

Catalog Prep keeps page hints separate from detected store metadata and does not convert prices. When source metadata is unavailable, currency stays unknown.

For a comparison sheet, retain source amount, currency status, locale or scope, and capture time. Add any conversion in your own analysis with an explicit rate and date. Public availability belongs in a separate field; it is not an inventory quantity.

Make a count explain itself

That audit also found 89 products in the whole-store feed and 85 in the all-products-xx collection. The collection name did not establish whole-store scope.

Before calling a file incomplete, check its URL, selected scope, product count, variant count, and stopping condition. Before calling it complete, inspect the same evidence.

Catalog Prep's manifest keeps capture context beside the rows. Pro has no fixed product or variant cap per run; Free captures use the remaining monthly allowance. Browser resources and source access still affect coverage. A qualified partial file can be useful for a clearly defined review.

The audit figures are dated source observations, not current store totals or a competing tool's benchmark.

Use a repeatable acceptance check

The 15-row worksheet gives you space for the check, evidence, result, and next action. Start with one multi-variant product, one literal SKU, one gallery association, one currency record, and the capture scope.

The result should tell a colleague what they can trust and what still needs review. Mapping into a destination system remains a separate step; Catalog Prep does not automatically write a native Shopify import.

Try a small collection in Catalog Prep, then open the workbook beside the storefront. The download is the beginning of that check.