Supplier price-list updates

Supplier Price List Updates: A Safer Review Process

Supplier price lists look simple until a below-cost price, an unexpected increase, or a missing product reaches a customer-facing catalog. A repeatable review process keeps the file, the decision, and the approved version connected.

Why this matters

Teams often compare files by hand, overwrite a master spreadsheet, and discover the expensive change after a quote, order, or website update.

A safer process

Turn the update into a clear decision.

  1. 1Keep the current approved catalog as the baseline.
  2. 2Map the new supplier file to the same product fields.
  3. 3Flag price, cost, margin, removal, and missing-data changes.
  4. 4Require a person to approve, reject, or hold each important change.
  5. 5Publish exports only from the approved version.

Review checklist

Before you publish.

  • The supplier file is dated and retained.
  • Each product has a stable SKU or identifier.
  • Cost and sell-price changes are compared with the approved version.
  • Below-cost and margin-rule exceptions are held for review.
  • The prior approved version can be restored.

Frequently asked questions

How often should supplier price lists be reviewed?

Review every received update before it changes a customer-facing catalog, price list, feed, or export.

What is the biggest risk?

A price, cost, or product removal can be accepted silently when a new file replaces the approved catalog without review.

Check your own supplier file before anything changes.

Start with one CSV or Excel file. ProductCatalogs.ai shows the risky changes and keeps the current catalog protected until you approve.

Get my free report