PriceTool.io Request a demo
MAP & Compliance

Stay in compliance without having to remember.

MAP audits don't care that it was the marketplace repricer. PriceTool enforces every supplier's MAP floor and MSRP ceiling on every run — before any file leaves the engine.

Request a demo See all safeguards
What's at stake

A MAP violation isn't a fine. It's a relationship.

Marine suppliers audit aggressively, and the consequences aren't financial — they're whether you keep selling the brand at all.

$0
Cost of one MAP slip
Some marine suppliers will pull your dealer status on a single audited violation. The line goes away. The margin goes with it.
14d
Typical MAP audit cycle
Suppliers run automated MAP audits every two weeks across Amazon, eBay, and your storefront. They don't email first.
∞
Times humans miss it
If MAP enforcement lives in someone's head, it eventually slips. The only safe place for the floor is in the engine.
The guard

Your markup wants $2,580. MAP says $2,725. The engine knows which one ships.

Every price the engine produces is checked against the supplier's MAP floor and MSRP ceiling before it is written to a channel file. Below is a real run, on a real Lewmar SKU.

Workflow diagram · One SKU through the guard LW-V4-WCH · Lewmar V4 Windlass · Cost $2,180 · MAP $2,725
Stage 1 — your markup formula
cost × 1.34
$2,921.20
Formula priced above MAP — fine on its own. But on the discounted tier (cost × 1.18), the same formula yields:
cost × 1.18
$2,572.40
⚠ Below MAP — would violate
Stage 2 — guard fires
max(formula, MAP)
$2,725.00
Held at MAP floor. Logged on the run report. Surfaced in the exception list for your records — so you can show the supplier what fired, when, on which SKU.
✓ MAP enforced — shipped

The same logic applies in reverse for MSRP — when a sale-tier markup would exceed MSRP, the engine caps it. Both directions, every channel, every run.

What runs on every file

Six checks. One run. Zero things to remember.

Compliance enforcement isn't a separate step you can forget — it's wired into the run alongside parsing, transformation, and export.

Guard

MAP floor enforcement

Every channel price is compared against the supplier's MAP for that SKU. If the formula would fall below, the price is held at MAP and flagged on the run report.

  • Per-supplier MAP tables (Harken, Lewmar, Garmin, B&G, Raymarine)
  • SKU-level overrides for short-term supplier promos
  • Floor applied per-channel — Amazon, eBay, web, POS
Guard

MSRP ceiling cap

If a markup tier — pro account, marketplace fee buffer — would push price above MSRP, the engine caps it at MSRP. The compare-at price stays accurate.

  • compare_at_price = MSRP for storefront feeds
  • Cap applied before rounding so the .95 ending doesn't break it
  • Per-supplier MSRP tables refreshed on every supplier file
Guard

Promo / sale window

Some suppliers permit MAP relaxation during named promos. The engine accepts a date-bounded promo window and re-tightens the floor automatically when it ends.

  • Start / end dates per promo, per supplier
  • Auto-revert to standard MAP at midnight on end date
  • Promo tag carried into channel file for marketing alignment
Guard

Marketplace repricer floor

If you run an Amazon or eBay repricer, the engine writes a min-price column equal to MAP — so the repricer cannot dip below the floor while chasing the Buy Box.

  • min_price column auto-populated to MAP
  • Buy Box buffer added on top, never below
  • Configurable per-channel (Amazon vs. eBay differ)
Guard

Dealer-tier carve-outs

Pro and contractor accounts have their own permitted floors that aren't public MAP. The engine applies the right floor to the right tier — never publishes the dealer price to the storefront.

  • Tier-aware MAP for trade and contractor accounts
  • Tier price exported to a separate, gated file
  • Public storefront file always uses public MAP
Guard

Audit-ready exception log

Every guard fire is recorded. When a supplier audit asks why a SKU was priced at MAP and not below, you have the timestamped log of the formula, the floor, and the decision.

  • Per-run exception CSV — held SKUs, capped SKUs, the math
  • Versioned, queryable across runs and channels
  • Exportable for supplier review on request
Audit-ready

When the audit email arrives, you already have the answer.

The exception log is a row-level record of every guard fire across every run. You can answer a Lewmar audit ticket the same morning it lands, with the math, the timestamp, and the SKU.

Request a demo
Exception ledger · workflow diagram #R-2026-04-25-LWM
SKUDescriptionFormulaShippedAction
LW-V4-WCH V4 Windlass $2,572.40 $2,725.00 Held MAP
LW-VX2-GR VX2 Gypsy Rope $418.10 $445.00 Held MAP
LW-CHN-12M Chain pipe 12mm $1,985.00 $1,985.00 Capped MSRP
LW-RV-700 Rocna 700 anchor $1,210.40 $1,295.00 Held MAP
LW-SR-12V Solenoid relay 12V $182.30 $199.00 Held MAP
Compliance shouldn't depend on memory

The floor belongs in the engine — not in your head.

Every supplier policy, every channel, every run. The audit comes when it comes. Your file already passed.

Request a demo