Use PricePatch to review proposed retail prices against a catalog export. It matches SKU values, flags ambiguous input, and produces review files. It does not connect to a live store, convert currencies, or update inventory.
Start with synthetic data
Open PricePatch and load its example. Download the catalog CSV and price CSV to inspect the original rows. “Supplier” is a column role in this test fixture, not a real vendor, endorsement, or commercial relationship.
Rows that deserve a decision
0001and0002: preserve leading zeros. Opening and re-saving in a spreadsheet can turn them into numbers and break matching.VASE-01: the price input contains 23.00 and 24.00 for the same SKU. Resolve the conflicting source rows rather than guessing which price wins.MUG-01: a leading space distinguishes this value fromMUG-01. The example intentionally does not silently trim it.NEW-01: a price row without a catalog match needs review; it is not authorization to create a new product.DUP-01: an ambiguous SKU cannot safely identify one catalog target.
Safe review sequence
- Keep an untouched current catalog export and record its date.
- Map the SKU and retail-price columns, confirming that the source uses the same currency and price meaning.
- Resolve duplicates, unmatched rows, and unusually large changes before export.
- Review the resulting file and change log. An old catalog can overwrite newer non-price fields during an import.
Completion boundary
Live Shopify import and rollback remain unverified. This workflow ends at CSV review. A successful preview is not proof that a store import is safe. Verify import behavior and restoration in an appropriate test store before any production operation. No store access or paid plan is needed to try these synthetic examples.