Catalog RelayOpen the workbench

Keep each size.

Your supplier sends new prices for two SKUs. Your Shopify product has six variants. Review the two changes and carry the other four sizes and colors into the update CSV.

Try the six-variant example
Juniper Outfitters · fictional supplier update
Navy / M · JN-NV-M68.00 → 72.00
Update
Moss / S · JN-MS-S68.00 → 74.00
Update
Four other size/color combinationsAbsent from this delivery · stay 68.00
Preserve
Two incoming rows. One approved product. Six output variants.

1. Start with every variant of the product

A supplier delivery can be incomplete. It may contain only the sizes whose prices changed. Use a fresh Shopify product export containing every variant of each product you intend to update as the baseline. Catalog Relay can preserve only the variants present in that file.

Download these practice files. Juniper Outfitters and every product row here are fictional. Use them in Catalog Relay only; don’t import these sample products into a live store.

Incoming supplier fileTwo SKUs with new prices for the Trail overshirt.

Download CSV

Complete Shopify baselineOne product: three sizes in Navy and three in Moss.

Download CSV

Expected reviewed outputThe six-row CSV produced by this exact example.

Download CSV

Open Catalog Relay. If you already have work there, choose Project → Download project backup first. Choose Start a fresh project, then confirm Start fresh. Under Source files, load the two-row file as the incoming supplier catalog and the six-row file as the current Shopify product export.

2. Match SKUs and keep the baseline’s options

Choose Map columns. Name the mapping “Juniper variant update,” use decimal-point numbers and check these three assignments:

Supplier-file mapping
Catalog Relay fieldSupplier column
SKUSupplier SKU
Product titleProduct
Selling priceRetail

Leave every other field Not mapped, including Product group, Shopify handle and all three option values. Choose Save mapping. For these matching SKUs, the baseline supplies the existing handle and the Size/Color option names and values.

The title is mapped and included in the output, so check that “Trail overshirt” is the title you want across the product. Vendor and other unmapped optional fields are omitted from this update file. An omitted column differs from a mapped column containing blank cells; inspect the actual output before an import.

Keep variant identity intact. Shopify warns that missing required option columns can remove existing variants, and changing option values creates new variant identities. See Shopify’s CSV dependencies and option guidance. This exercise retains the baseline’s handle, SKUs and options; it does not rename sizes or add variants.

3. Approve one product and inspect six rows

Choose Review changes. Trail overshirt should appear as one updated existing product. Its two supplied variants have new prices. The review also lists JN-NV-S, JN-NV-L, JN-MS-M and JN-MS-L as missing from the supplier file and preserved in the update.

Expected six-variant output · fictional data
SKUSize / colorPriceAction
JN-NV-SS / Navy68.00Preserve baseline
JN-NV-MM / Navy72.00Update from 68.00
JN-NV-LL / Navy68.00Preserve baseline
JN-MS-SS / Moss74.00Update from 68.00
JN-MS-MM / Moss68.00Preserve baseline
JN-MS-LL / Moss68.00Preserve baseline

Select Approve this product, then Review export. Open Preview exact Shopify output. Expect six output variant rows with the existing trail-overshirt handle, both option dimensions and the prices above. Download shopify-reviewed-updates.csv and compare it with the expected file. The review report accounts for the two incoming supplier rows; the update CSV carries all six variants.

Stop if an intended update appears as a new product. Check the SKU text and the baseline first. A renamed SKU is not automatically the same variant. Duplicate SKUs, ambiguous matches and changed existing option values can block approval. This workflow does not add a new size to an existing product.

Missing is not a deletion request. Missing variants of this approved product retain their baseline values. Products absent from the supplier delivery are not exported at all. Catalog Relay does not generate deletions or infer that a supplier has discontinued an item.

4. Check Shopify’s preview before changing the store

For your own real files, keep the fresh Shopify export and a Catalog Relay project backup. Inspect the update CSV’s handles, SKUs, options, titles, prices and any included blank cells. In Shopify, choose the matching-handle overwrite setting deliberately and read the import preview. Cancel if any variant or field change is unexpected.

Catalog Relay prepares files; it never connects to your store or submits an import. Local undo and project backups cannot reverse a Shopify import. Image changes, inventory synchronization, metafields, option restructuring and adding variants to existing products are outside this version. The example changes ordinary Price values, not market-specific prices.

Up to 50 incoming supplier data rows per file export free. Larger files use a $29 USD one-time individual license for your work on your devices. No subscription. Import, review and project backups remain available without purchase.

For more price-mapping detail, see update Shopify prices by SKU. The supplier CSV walkthrough also covers new draft products and a missing-price correction.

Check all six variants in your own download.

This two-row supplier example fits the free allowance. Compare the actual CSV with the expected output before trying your own files.

Open Catalog Relay