Catalog Relay Open the workbench

From supplier CSV to a reviewed Shopify file.

A changed price, a missing color, a new product. Give each one the right outcome before anything reaches your store.

Follow along with five fictional supplier rows
One supplier delivery. Three decisions.
Camp mug · Cream & InkPrice changes from 22.00 to 24.00
Review update
Camp mug · MossAbsent from the supplier file
Preserve
Oak serving boardSelling price has not been supplied
Hold for data
Illustration of the fictional practice files below.

1. Get the practice files

Catalog Relay compares an incoming supplier catalog with a Shopify product export. It matches existing variants by SKU, lets you review product groups, and produces separate CSVs for existing-product updates and new unpublished drafts.

These small CSVs use an entirely fictional supplier, Harbor Table. They are for practicing in Catalog Relay; do not import them into a live store.

Incoming supplier catalogFive rows: two mugs, two napkin colors and one incomplete board.

Download CSV

Shopify baseline exampleFour existing variants, including a mug color absent from the delivery.

Download CSV

Next supplier revisionThe mugs change price again; the board receives a price.

Download CSV

Supplier files with up to 50 data rows per file are free to export. Larger files require a $29 USD one-time individual license for your own work on your own devices. There is no subscription or automatic renewal. Import, review and project backups remain available without a purchase. The row allowance counts the supplier file, not just the rows you approve.

2. Bring in a current baseline

Open Catalog Relay. If you already have work to keep, use Project → Download project backup before changing files. For this practice run, choose Project → Start a fresh project, then confirm Start fresh.

  1. In Source files, use Incoming supplier catalog → Choose file to load harbor-table-supplier.csv.
  2. Return to Source files and load harbor-table-shopify-baseline.csv under Current Shopify product export.
  3. For real work, use a fresh product export from your store covering the products and variants you intend to update. Keep the original export as a backup.

The baseline decides what already exists. Without it, Catalog Relay prepares new drafts. It cannot know that a supplier SKU already belongs to your store. A missing SKU match deserves investigation before you approve it as a new product.

CSV and .xlsx are supported, with limits of 10 MB per file, 10,000 data rows and 100 columns per sheet. Choose the relevant worksheet when prompted. For Excel formulas, export calculated values first; formula-containing, encrypted, macro-enabled and externally linked workbooks are unsupported. Keep identifiers as text so leading zeros and long SKUs survive.

3. Map columns to meaning

Choose Map columns in the workflow navigation to open Supplier mapping. Suggested matches are a starting point; check each one. Name this mapping “Harbor Table” and choose the decimal point number format for these practice files.

Mapping for the fictional Harbor Table files
Shopify fieldSupplier columnPurpose
SKUSupplier SKUMatch the exact existing variant.
Product titleProductUse one title across a product’s variants.
Product groupStyleKeep the two napkin colors together.
Selling priceRetailThe price customers pay.
Cost per itemCostYour per-item cost.
VendorBrandThe fictional supplier name.
Option 1 valueColorCream, Ink, Natural or Blue.

Set Option 2 value and Option 3 value to Not mapped. The column suggestions may initially place Color in Option 2; move it to Option 1 for this example. Leave Shopify handle, Description and Tags unmapped.

Set New product option 1 name to Color and clear the unused option names. Existing variants retain their baseline option names and values. For new products, the group and option values determine which rows belong together.

Under Columns kept in the project only, check Warehouse note. This explicitly retains it in the source data and backup while excluding it from Shopify output. Then choose Save mapping.

A blank value and an absent column are different. Included blank fields can clear existing values on import. Unmapped optional fields are omitted from the update. Review the exact export, especially if you map descriptions, vendors or tags.

4. Review whole products

Choose Review changes. With the mappings above, the five supplier rows form three product groups:

  • Camp mug — Updated. Cream and Ink move from 22.00 to 24.00, with cost moving from 8.00 to 8.50. Open the product and inspect both variants.
  • Linen napkins — New product. Natural and Blue belong to one new product with two Color options. Check its title, handle, prices and costs.
  • Oak serving board — Check data. Selling price is blank, so the product cannot be approved. Leave it excluded until you have the correct price.

The missing color is still part of the product

The baseline includes HT-MUG-MOS, the Moss mug. It is absent from this supplier delivery. When you approve Camp mug, the export carries that variant through with its existing 22.00 price, 8.00 cost and Color option.

Approvals apply to whole product groups, not isolated supplier rows. Product-level fields such as title, description, vendor and tags apply across the group, including preserved variants. Missing products are not deleted, and no deletion file is generated.

After inspecting the results, select Approve this product for Camp mug and Linen napkins. Keep the board unapproved. The workspace should show two approved products and one that needs attention.

If a product cannot be approved

For a complete blocked-file and repair example, see review duplicate supplier SKUs before an import.

Read the highlighted issue before editing. Duplicate SKUs, an ambiguous baseline match, inconsistent product-level values, invalid prices or changed existing options can block a group. Use Correct this source row when available, or repair and reload the source. Corrections retain the original source data; changes clear approvals so you can review again.

This workflow does not add variants to existing products, rename existing handles or restructure options. It also does not change images, sync inventory or edit metafields.

5. Choose the right export

Select Review export and expand Preview exact Shopify output. With only the mug and napkins approved, expect two separate files:

Existing-product updates

Three Camp mug variants: Cream and Ink updated, Moss preserved.

shopify-reviewed-updates.csv

New unpublished drafts

Two Linen napkins variants, with draft status and online publication set to false.

shopify-new-drafts.csv

Download the review report too. It accounts for all five supplier rows: the four approved rows and the excluded board, with its blocking issue. The report is for your records, not a Shopify product import.

Before using your real files in Shopify

  • Keep a fresh Shopify product export and a Catalog Relay project backup.
  • Inspect the exact output for handles, option identities, prices and any included blank fields.
  • Upload the appropriate updates or new-drafts CSV and inspect Shopify’s import preview.
  • For existing-product updates, deliberately choose Shopify’s matching-handle overwrite option. Cancel if the preview contains unexpected changes.

Your final review happens in Shopify. Catalog Relay prepares files and never connects to your store or submits an import. Workspace undo and project backups cannot reverse a Shopify import.

6. Repeat the routine next delivery

Only updating prices? Follow the worked SKU price-update guide with three incoming rows, preserved variants and a downloadable expected output.

Use Source files → Replace file under the supplier panel when a new delivery arrives. The current mapping is retained. Check every mapped header again; a renamed or missing column needs repair. You can also choose a template under Saved mapping.

For a second practice pass, load harbor-table-next-revision.csv. It raises Cream and Ink to 25.00 and supplies the board’s 44.00 selling price. The fictional baseline can stay in place because this exercise made no store changes.

For a real second delivery, replace the baseline with a fresh export of the store’s current state. A previous supplier file is not a substitute for the Shopify baseline. Review and approve the product groups again before exporting.

Keep the project as well as the output

Project → Download project backup saves the source data, mappings and corrections in a portable JSON file. Restore project backup brings that workspace back and requires fresh approvals. A saved mapping lives inside the project; the backup carries it to another device.

Your catalog contents are processed in this browser and are not sent to Catalog Relay’s servers. The current project is saved on this device, so clearing browser data or losing browser storage can remove it. Purchase, license and support services use an online connection; your license is stored separately from project backups.

Updating only a few sizes or colors? Follow the six-variant preservation walkthrough to inspect the other variants carried into the output.

Give the five-row workflow a try.

Download the fictional files, check the mapping and review a real CSV export. All five supplier rows fit within the free allowance.

Open Catalog Relay