MAP Pricing Violations: How to Detect Them and What to Do Next

Your MAP policy only works if you enforce it. Most brands write one, file it away, and discover six months later that three resellers have been advertising below MAP for weeks — and every other authorised seller has quietly matched the lower price to stay competitive.

By then, the damage is done. Here's how to stay ahead of it.

What MAP Violations Actually Cost You

The obvious cost is margin compression — resellers advertising below MAP pull your average selling price down across the channel. But the less obvious cost is brand erosion. When customers see your $149 product advertised at $89, they start anchoring to that price. Future full-price sales become harder, and your premium positioning weakens.

MAP violations also create resentment among compliant resellers. Your best retail partners — the ones investing in merchandising, customer service, and brand presentation — are being undercut by opportunistic sellers who offer none of that. Over time, compliant partners lose faith in the policy and start undercutting themselves.

How to Monitor for Violations

Manual spot-checking doesn't scale. By the time you notice a violation, it's usually been live for days. You need systematic monitoring that covers:

Search engine shopping results — run your top product searches and capture the advertised prices across all visible listings. Google Shopping is where most consumers see price comparisons, so violations here do the most damage.

Marketplace listings — Amazon, eBay, and Walmart Marketplace need separate monitoring. Prices on these platforms can change hourly, and violations often appear first here before spreading to standalone sites.

Reseller websites — your authorised seller list should be monitored directly. A crawl of their product pages two to three times per week catches most violations before they compound.

Automated price intelligence tools do this continuously and flag violations in real time, which lets you respond before the violation influences other resellers' behaviour.

Documenting a Violation

Before contacting a reseller, document the breach properly:

• Screenshot the advertised price with the full URL and timestamp visible
• Record the date, product SKU, the violating price, and your MAP threshold
• Note whether this is a first, second, or repeat violation

Good documentation protects you if the reseller disputes the notice or if you need to terminate the relationship. Keep a violation log per reseller — patterns matter when deciding how to escalate.

Responding to a Violation

First breach — a direct, professional email citing the specific violation, your MAP policy clause, the documented price, and a request to correct within 48 hours. Most first violations are resolved here, especially with smaller resellers who weren't aware they'd breached.

Second breach — escalate to a formal written warning. Make clear that a third violation will result in removal from the authorised seller programme. Copy their account manager if you have one.

Third breach or wilful violation — terminate the reseller relationship. This is the only enforcement mechanism that actually works, and other resellers are watching to see if you'll use it.

The tone throughout should be firm but not adversarial. Most resellers want to stay authorised — they just need to believe the policy is real.

Preventing Repeat Violations

The best MAP enforcement is proactive. When onboarding new resellers, require a signed MAP agreement, not just an acknowledgement email. Run a monitoring check on new resellers within their first 30 days — it establishes the precedent that you're watching.

Review your MAP thresholds annually. If your costs have shifted or the competitive landscape has changed, an outdated MAP level will drive more violations simply because compliant sellers can't make the margin work.

A MAP policy that gets enforced consistently — even for minor violations — creates a culture of compliance. One that's enforced selectively creates a culture of testing the limits.