Refreshing is riskier than the first import, because now there is live data to damage. The task is not "import the new file" — it is "apply the differences".

The routine

  1. Diff before importing. Compare the new supplier file against the previous one and classify every row as added, removed, or changed. Supplier Change Report does this locally.
  2. Decide per class.
  • Added rows: new listings, imported as Draft.
  • Changed rows: price and stock updates only.
  • Removed rows: set to Draft or out of stock. Do not delete — you lose sales history and risk breaking old links.
  1. Match on stable keys. Match by SKU or Handle. Matching by title creates duplicates the moment a supplier renames a product.
  2. Decide what blank means. Before overwriting, state whether a blank cell means "leave the existing value" or "clear the value". Pick one and apply it consistently — the two produce opposite results.
  3. Import in batches and verify. Spot-check a few products on the storefront afterwards.

What must never change in a refresh

Handle, SKU pattern, and product identity fields. Changing any of them converts an update into a duplicate.