WORKED DEMONSTRATION

Try a supplier price update with known results

Start with a small example whose answer you can check. Then decide whether your own Shopify export and supplier file fit the same workflow.

Updated 5 min read By BLZN Works

Use this when the two files already exist

You sell existing Shopify variants, have a fresh complete Shopify product CSV export, and receive a supplier CSV containing the same unique SKUs plus costs or suggested selling prices. The tool calculates selling prices; it does not update Shopify's Cost per item.

A supplier PDF, an XLSX workbook, a price in another currency or a list without matching SKUs needs separate preparation. Do not buy this tool expecting it to extract a PDF, guess matches, convert currencies, sync stock or create products.

1. Download the two practice files

These are BLZN Works synthetic examples, not files from a real store. The links use example.com placeholders. Use them only to practice; never import these examples into your store.

Your own store file must be a fresh complete export, including all sibling variants of each product. Preserve the untouched export as a backup. Shopify's official CSV guide explains the handle, option-column dependencies and overwrite behavior.

2. Make the calculation explicit

  1. Open the free Supplier Update Guard demo. Choose both practice CSVs, leave both separators as Comma, then select Confirm formats and parse.
  2. Map Supplier SKU column to supplier_item_code, Price / unit cost column to new_unit_cost, and optional notes to notes.
  3. Choose Markup, USD, decimal point and 40 percent. Leave case-insensitive matching off and the default thresholds at 20% warning, 35% individual approval and 20% price drop.
  4. Select Calculate price review. The demo reviews all four practice rows because they fit within its first-10-row limit.

The same files and settings are available through Try the sample in the tool. Loading a sample alone does not perform the review; calculate after inspecting the mapping.

3. Check the answer before approving anything

Expected results: 40% markup means cost × 1.40, rounded to cents.
SKUCurrent priceSupplier costProposed priceExpected review
001-A$19.00$10.00$14.00Proposed; 26.32% drop, individual approval
001-B$21.00$12.00$16.80Proposed; 20% drop, individual approval
MUG-01$12.00$7.50$10.50Proposed; 12.5% drop
UNKNOWN-01Not present$8.00No proposalUnmatched supplier SKU; never creates a product

You should see 3 valid matched, 3 proposed, 0 unchanged, 1 unmatched supplier, and 0 approved before any decisions. A markup calculation can lower your current selling price: that is why both shirt variants need individual approval. Approval is your decision, not a recommendation from the tool.

For a harmless practice decision, approve only MUG-01; the approved count becomes 1. The demo creates no download files. In the full edition, generating files for that same decision changes only the mug's price; the untouched shirt product is omitted. Review the actual files and test one real product before a real import.

4. Decide whether the paid workflow helps you

For a handful of known prices, Shopify's included bulk editor may be enough. A spreadsheet can also calculate markup; check duplicates and preserve SKU text, including leading zeros. Use the free markup and margin calculator for a single price.

Supplier Update Guard is useful when you want repeated exact-SKU comparison, visible exceptions, explicit risky-price decisions and candidate/rollback files in one local workflow. It still requires your export, source review and manual import. Unit-priced products, stock syncing, ambiguous SKUs and multi-currency pricing need another workflow. See the formats, backup steps and limits before buying.