Catalog RelayOpen the workbench

A worked CSV repair

Two rows. One SKU. Check before you import.

A supplier file gives the same identifier two prices. Catalog Relay blocks that product until you resolve the source. Try the mistake and its repair with these fictional files.

Download the practice files ↓
Studio tee · fictional supplier delivery
CT-TEE-SFirst supplier row · 34.00
Duplicate
CT-TEE-SSecond supplier row · 36.00
Duplicate
The file cannot tell us which identifier is wrong. Confirm it at the source.

1. Load a file with a deliberate mistake

These files describe one fictional product with three existing sizes. Two incoming prices should change; the third size should stay as it is. The first supplier file deliberately repeats the Small SKU.

Current Shopify baselineSmall, Medium and Large at 32.00.

Download baseline CSV

Supplier file with duplicateTwo rows carry CT-TEE-S.

Download duplicate CSV

Confirmed correctionThe second row is CT-TEE-M.

Download corrected CSV

Expected reviewed outputThree variants after the correction.

Download expected CSV

Open Catalog Relay. Keep any existing work with Project → Download project backup. For this exercise, choose Project → Start a fresh project → Start fresh.

  1. Under Source files, load the duplicate CSV as the Incoming supplier catalog.
  2. Load the baseline CSV as the Current Shopify product export.
  3. Open Map columns. Use decimal-point numbers. Map SKU → Supplier SKU, Product title → Product and Selling price → Retail. Leave every other field Not mapped, including Product group, Shopify handle and all option values.
  4. Choose Save mapping, then Review changes.

The matching SKUs take their existing handle and Size option from the baseline. This is an update to existing variants; it does not add a size or rename an option.

2. Inspect the block before choosing a correction

Studio tee appears as Check data. Both supplied rows show a duplicate-source-SKU issue. Approval is disabled for the whole product. You cannot export an approved update by picking one of the two prices.

In a real supplier file, pause here and check the original source. A repeated SKU could mean an accidental duplicate, two genuinely different variants sharing an identifier, or a feed with warehouse rows that needs a different preparation step. Those are different problems. Catalog Relay does not choose the right identifier or combine quantities for you.

Do not invent a new SKU to clear the warning. Matching is based on the exact SKU text, not a similar title. A changed identifier may be treated as a new product. If a SKU matches multiple variants in the baseline, repair that ambiguity too before exporting.

Keep identifiers as text. Leading zeros matter, and a spreadsheet can change long identifiers or turn them into scientific notation. The original supplier file and fresh store export are the references to preserve.

3. Replace the source with a confirmed correction

For this fictional exercise, the supplied correction confirms that the second row belongs to Medium: CT-TEE-M. Its price is 36.00. Small remains CT-TEE-S at 34.00.

Under Source files → Incoming supplier catalog, choose Replace file and load the corrected CSV. The mapping stays in the project. Check it again, then choose Review changes.

The product should now be an update with no duplicate-SKU block. Review both changed prices and the existing Large variant. Select Approve this product. Replacing a file clears earlier approvals so the new source receives a fresh review.

For your own catalog, reload a corrected source only after you have established what changed. Removing a repeated row is appropriate only if you have confirmed that it is redundant. An unsupplied variant of an approved existing product is preserved from the baseline; removing a supplier row is not an instruction to remove it from your store.

4. Check all three output rows

Choose Review export, then open Preview exact Shopify output. The existing-product update should contain these three variants:

Expected Studio tee update · fictional data
SKUSizePriceResult
CT-TEE-SS34.00Updated from 32.00
CT-TEE-MM36.00Updated from 32.00
CT-TEE-LL32.00Preserved baseline

Download shopify-reviewed-updates.csv and compare it with the expected CSV above. Check the studio-tee handle, all three SKUs, the Size option and each price. The review report accounts for the two incoming supplier rows; the update file carries the three existing variants.

For a real import, keep a fresh Shopify export and inspect Shopify’s import preview before committing. Included blank fields can clear values, while omitted optional columns leave those fields unchanged. Existing variant updates also depend on the correct option columns. Read Shopify’s CSV field guidance and its matching-handle overwrite guidance for your file.

Review the final import in Shopify. Catalog Relay prepares a CSV and never changes your store. This example verifies the local preparation and download; it is not a completed Shopify store import. Local undo and project backups cannot reverse a store import.

Up to 50 incoming supplier data rows per file export free. Larger files require a $29 USD one-time individual license for your work on your devices. No subscription. This version does not sync inventory, change images, edit metafields or restructure existing variants.

Try the blocked file, then review its repair.

The two-row example fits the free allowance. Compare your own download with the expected three-variant CSV.

Open Catalog Relay