Updating Shopify prices and costs by SKU

Feedstead reconciles a supplier file against a Shopify product export and prepares an update for review. It uses exact SKU text as the match key.

Worked example

Client export:

Supplier file:

Map Product code to supplier SKU and Net cost to supplier cost. With a 50% markup and nearest-cent rounding, 0002 proposes a cost of 11.00 and a price of 16.50 because 11.00 × 1.50 = 16.50; its old price is 18.00. NEW-007 is an exception because no exact client SKU exists.

The review shows the old and proposed values before export. The complete change report includes both matching rows and NEW-007, and the workflow never creates a near match for it.

Shopify columns and dependencies

Shopify’s current product CSV documentation says that updates require URL handle and Title. It also says variant-related columns such as SKU and Weight value (grams) depend on the relevant option-name and option-value columns. Missing dependent option fields can create a default variant and delete existing variants. Feedstead’s export must preserve the current format and needed dependencies rather than emitting a two-column “SKU, price” file that Shopify cannot safely interpret.

Source: Shopify Help Center — Using CSV files to import and export products.

What the output records

The update CSV contains the approved exact-SKU changes plus every sibling variant of each affected product. Unchanged siblings retain their current price and cost. The complete change report retains every supplier row with its match status, old values, proposed values, and any reason that prevented an update.