What counts as a pricing error?
Any published price that is wrong, below cost, stale, in the wrong unit, or changed without the required review.
Prevent catalog pricing errors
How to Prevent Catalog Pricing Errors Before They Reach Customers
A catalog pricing error is usually not a math problem. It is a process problem: a new supplier file changed a price, nobody noticed the business impact, and the file became live too quickly.
Why this matters
Teams can publish below-cost prices, stale prices, or unreviewed large increases when price updates are treated as a simple import.
A safer process
Turn the update into a clear decision.
- 1Keep approved cost and sell-price values together.
- 2Set a minimum margin or exception rule.
- 3Flag proposed sell prices below cost.
- 4Flag price changes outside an expected range.
- 5Require approval before a changed price enters an export or catalog.
Review checklist
Before you publish.
- Cost and sell price are both present where required.
- Currency and units are consistent.
- Below-cost proposals are blocked.
- Large increases are reviewed.
- Price changes can be traced to a source row and approver.
Frequently asked questions
Should every price change be blocked?
No. The right approach is to automatically surface changes and let the business approve routine changes while holding unusual or dangerous ones.
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