Data Quality & Safety

A bad price file shouldn't be able to break your catalog.

Pricing mistakes are expensive. Some are catastrophic. PriceTool builds the safeguards into every run — so the worst-case file your supplier sends doesn't become the worst-case Monday morning for you.

Safeguard

Customizations are saved

The custom work you've done — renamed parts, pricing groups, assortment choices, the way variants are set up — stays put. Every time a supplier update comes in, your customizations come along with it. You don't redo them.

Scenario You renamed 200 SKUs for your storefront last quarter. Next supplier update keeps the renames intact.
Safeguard

MAP & MSRP enforcement

Your supplier's MAP floors and MSRP ceilings are built into every run — not something you have to remember to check. The file we send back won't price anything below MAP or above MSRP, and the change report shows you every time a guard caught one.

Scenario Your 28% markup would have priced a Harken winch under MAP. Held at floor. Logged on the report.
Safeguard

Duplicate file detection

Every supplier file gets a unique fingerprint when it lands. If the same file shows up twice, we catch it before anything goes out — so you don't accidentally re-run last quarter's prices.

Scenario Same Ronstan price list forwarded twice. We catch it. No double-import, no surprise overwrites.
Safeguard

Old-file protection

If a file you forward is older than the one we already have for that supplier, we don't just overwrite. We stop, ask once, and only run it if you say so — so an old email can't roll back your live prices.

Scenario Last September's Harken file accidentally re-forwarded. Held. Your current prices stay current.
Safeguard

Version tracking & rollback

We keep every file we've ever run for you. If a price update goes out wrong, we can roll it back — wait for the corrected file from your supplier, then re-run it. Nothing is lost.

Scenario Supplier sent a file with a column-shift error. Roll back, wait for the corrected file, re-run.
Safeguard

Mass-discontinuation guard

If a new supplier file looks like half their parts vanished, we don't trust it. We block the import until you give the OK. Nine times out of ten it's a broken export on their end, not your supplier dropping half their line.

Scenario Supplier's export script broke and only sent half their SKUs. We block. You don't end up with 4,000 unbuyable parts.
What it looks like

Every run includes a paper trail.

Each delivery package includes a run summary that tells you exactly what fired and what was held — so the file we return is something you can sign off on, not something you have to spot-check by eye.

Request a demo
Run report · workflow diagram #R-2026-04-25-RNS
SHA-256 fresh — not a duplicateok
File newer than last acceptedok
1,284 lines parsed by Ronstan transformer100%
i312 price changes · 8 new · 14 discontinueddelta
Mass-discontinuation guard — under threshold1.1%
!3 lines held at MAP floorguard
!2 unmapped SKUs flagged for reviewexcept
Customizations preserved (54 overrides)persist
Channel exports written: web, amazon, in-house3 files
Status: ready to uploaddelivered
Sleep at night

Pricing at this scale should not depend on whether you remembered.

The safeguards run on every file, every time. You don't have to be the one who catches the bad import.

Request a demo