Why cutting your price is the wrong answer to a MAP violation
A MAP violation is a contract problem, not a pricing problem. How to measure its size, why matching the price backfires, and what the correct response looks like.
One morning the dashboard tells you that one of your resellers has listed your product below the minimum advertised price they agreed to. Same product, lower number, and theirs is the listing buyers see first.
The first instinct is almost always the same: match it.
That is the most expensive move available. A MAP violation is not a pricing problem, it is a contract problem — and answering a contract problem with price rewards the violation.
What MAP is, and what it is not
MAP (Minimum Advertised Price) is the floor a brand sets for its resellers: you may not advertise below this number.
The load-bearing word is advertised. MAP is not a floor on the selling price. A reseller may go lower in the cart, in a negotiation, or inside a closed promotion; what is constrained is the price at which the product is shown. The distinction also matters legally — in many jurisdictions, setting a reseller's resale price and setting a floor on advertised price are treated very differently.
In practice MAP protects price perception. When one product appears at three prices in three places, buyers anchor on the lowest one and that number becomes the product's "real" price. MAP exists to stop that anchor from drifting down.
How to measure the size of a violation
A violation is not a binary state. It has a magnitude, and the magnitude is simple:
A negative result means a violation. The difference between −3% and −25% is the difference between two completely different situations described by the same word: the first is usually a side effect of how a promotion was built, the second is deliberate positioning.
Dividing by MAP rather than by the advertised price is a deliberate choice. "14% below MAP" matches the language of the contract, because MAP is the committed reference. Divide the same two numbers by the listing price and you get a different percentage that corresponds to no clause anywhere.
The currency trap
The comparison has to happen in a single currency. If listings in different currencies land in the same pool, the arithmetic above stays correct and the result becomes meaningless. This is a place where correctness lives in the data selection, not in the formula — and when it goes wrong it raises no error at all. It just produces a wrong percentage.
Why matching the price is the wrong answer
Say your MAP is €1,000 and a reseller advertises at €850. You go to €850, or €840 to be safe. What happens?
- The violating reseller pays no cost — and their move worked.
- Other resellers see the new floor and follow it down.
- The buyer's reference price moves from €1,000 to €850 and does not move back.
- You have spent margin not to stop the violation but to join it.
Answering with price does not punish a violation. It makes it the new normal.
There is a quieter cost too. Every listing below MAP drags down the reference for every future pricing decision on that product. Six months later, when you ask why there is no margin left on this SKU, the answer is the single listing you matched six months ago.
One word, two different jobs
In practice "MAP" is used for two entirely different situations, and the confusion puts the wrong decision on the wrong screen:
| Situation | What it means | Whose job |
|---|---|---|
| A competitor listing is below MAP | A reseller is breaking the agreement | Channel management / legal — collect evidence, notify |
| A calculated price falls below MAP | You have hit your own floor | Pricing — suppress the recommendation, hold the floor |
The first is a commercial and enforcement matter; the second is a pricing constraint. Same word, two jobs, two people, two screens. Collapsing them into one list is the fastest way to do both badly.
The right move is evidence, not price
The answer to a MAP violation is enforcement. For enforcement to work you need exactly one thing: a document you can send.
- A timestamp. When the violation was observed. "I saw it last week" is a claim; a date and time is a record.
- The price and the gap. What MAP is, what was advertised, and the percentage between them.
- Visual evidence. The page as it looked at the moment of observation, so the proof survives the reseller quietly fixing the listing.
- Persistence. One-off, or running for three weeks. Those two call for different responses.
With those four in hand, the conversation does not start with "I think there may be an issue." It starts with "you have been 14% below MAP since 17 August, records attached." The second sentence gets results.
How to build this into the system
If you run an automated pricing engine, this distinction has to exist in the code. In Nudge, when a product's competitive position is classified, MAP comes before everything else: if a competing listing sits below MAP, the product is flagged as a violation before it is ever labelled "we are cheaper" or "we are more expensive" — and no price recommendation is produced for it at all.
That silence is deliberate, not a gap. The engine will not propose going under a violating listing, because price is not the correct answer and manufacturing an answer that does not exist is an invitation to the wrong move.
The violation does not disappear. It sits on its own screen, in its own record, in its own workflow. Telling one fact on two screens does not make it twice as important; it only blurs which screen belongs to which job.
Three decisions to make when you set up violation tracking
1. Threshold: which gap counts as an incident
Not every negative gap is equal. A −0.5% deviation is usually rounding, currency movement, or the side effect of how a promotion was constructed. Alerting on it buries the team in noise, and two weeks later nobody reads the notifications. Pick a threshold; record what falls below it, but do not alert on it.
2. Persistence: how many observations make an incident
A single observation can be wrong. Requiring the same violation to appear in two or three consecutive updates prevents you from sending a reseller a false accusation because of a temporary campaign page. It costs a little sensitivity and buys you the guarantee that every notice you send is correct — and a wrong notice is far more expensive than a missed violation.
3. Ownership: who actually receives this
MAP violations are not the pricing team's work. They belong to channel management, sales, or legal. If the alerts pile up on a pricing screen nobody acts, because the person looking at that screen has no authority to call the reseller. The violation has to sit on its own screen, with its own owner.
Summary
- MAP is a floor on the advertised price, not the selling price.
- Measure the violation as a percentage of MAP, in a single currency.
- Matching the price moves the floor down permanently.
- The correct response is enforcement backed by timestamped evidence.
- A pricing engine should stay silent on a product where it sees a violation.
Frequently asked questions
What is MAP?
MAP (Minimum Advertised Price) is the floor a brand sets for its resellers: they may not advertise below it. It is not a floor on the selling price — what is constrained is the price at which the product is shown, not the price at which it is sold.
How do you calculate the size of a MAP violation?
Gap % = (advertised price − MAP) ÷ MAP × 100. A negative result means a violation. MAP is the denominator because MAP is the reference committed to in the contract, and the comparison must be made in a single currency.
Why is cutting your price the wrong response to a MAP violation?
Because the violating reseller pays no cost, other resellers see the new floor and follow it down, and the buyer's reference price moves down permanently. You spend margin not to stop the violation but to join it.
What is the correct response to a MAP violation?
Enforcement rather than price: a timestamp, the gap percentage between MAP and the advertised price, visual evidence from the moment of observation, and how long the violation has persisted. With those four, the conversation with the reseller starts from a record rather than a claim.