MAP (Minimum Advertised Price)
MAP (Minimum Advertised Price) is the lowest price a brand allows a reseller to display publicly — in an ad, on a product page, or in a search result. It governs the advertised number, not the price a buyer actually pays at checkout. Brands publish a MAP policy plus a per-SKU price list, monitor the digital shelf for violations, and enforce commercially by pulling rebates, co-op funds, or supply.
What MAP actually governs
MAP puts a floor under the advertised number. It does not set the transaction price. A distributor can sell a 20V cordless impact driver below MAP all day. They just can't publish that number where the public can see it before the cart.
That one distinction explains most of what you see on the digital shelf: "Add to cart to see price," "Call for pricing," "See price in cart," "Log in for your price." A cart is not an advertisement. A category grid is.
| Term | What it is | Who sets it | Shown publicly? |
|---|---|---|---|
| MAP | Floor on the advertised price | Brand / manufacturer | Indirectly — it constrains what's shown |
| MSRP | Suggested retail price | Brand / manufacturer | Often, as a strike-through |
| List price | Reseller's own posted price | Reseller | Yes |
| Dealer / net cost | What the reseller pays | Negotiated | Never |
| Street price | What the buyer actually pays | Reseller, per deal | Sometimes, post-login |
MAP exists because a brand selling through 400 resellers has no other lever on price presentation. Once a UL listed 600V wire connector is advertised at 40% off on one marketplace, every other reseller's margin gets repriced against that number, and the brand's own direct channel looks overpriced.
How MAP is enforced
MAP enforcement is commercial, not judicial. In the US, a brand can generally announce a unilateral policy and refuse to sell to resellers who don't follow it — that's the Colgate doctrine. A negotiated agreement to fix resale prices is a different animal, evaluated under the rule of reason since Leegin (2007). Structure matters, so this is counsel's call, not marketing's.
The operating loop looks like this:
- Publish the policy. A unilateral MAP policy document, dated, sent to every authorized reseller.
- Publish the prices. A per-SKU MAP list with effective and expiration dates, distributed with the product feed.
- Monitor. Crawl authorized reseller PDPs, marketplaces, and shopping feeds. Match each listing back to your SKU, then compare the displayed price to the MAP in force on that date.
- Notice. Screenshot, timestamp, URL, the SKU it matched to, the price observed.
- Consequence. Warning, then loss of co-op dollars or rebate, then suspension of shipments.
The hard part is almost never the policy. It's step three. Monitoring only works if the listing you found can be matched with confidence to the SKU whose MAP you're checking.
MAP is a data field, not a memo
Here's the usual failure. The policy lives in a PDF, the prices live in a quarterly spreadsheet, and the spreadsheet drifts from the feed. A reseller advertises against last quarter's number, and the enforcement letter goes out wrong.
MAP is a governed attribute on the SKU record, with the same lineage requirements as a GTIN or a torque rating:
| Field | Example value | Why it exists |
|---|---|---|
map_price | 149.00 | The floor itself |
map_currency | USD | A CAD listing isn't a USD violation |
map_effective_date | 2026-07-01 | Which number was in force when observed |
map_expiration_date | 2026-09-30 | Prevents enforcing a dead price |
map_policy_id | NA-2026-R3 | Ties the SKU to the governing document |
map_promo_window | 2026-08-15/2026-08-31 | Sanctioned exception (holiday, closeout) |
map_display_rule | add_to_cart | What the reseller may show instead |
map_exempt_channel (multi-select) | punchout | Negotiated B2B pricing isn't advertising |
Every one of those fields travels with the product content, in the same feed, on the same cadence. Which means MAP inherits every defect your catalog already has.
Where MAP breaks on the digital shelf
MAP failures are usually identity failures, not pricing failures:
- The listing won't match. A reseller lists your part with their own internal number and a mangled MPN. Your monitoring can't tie it to a SKU, so it doesn't get checked.
- Variants collapse. A 3/8-16 Grade 8 hex bolt has a MAP per length and per box quantity. If parent-child structure is flat, one MAP gets applied across ten prices.
- Kits and bundles. A reseller bundles the driver, two batteries, and a charger. There's no MAP on a bundle that only exists on their site, so the bundle becomes the loophole.
- Stale windows. The promo ended June 30. The feed still carries the promo price. The reseller is compliant with what you sent them.
- UOM mismatch. MAP is per 100-count box. The marketplace lists each. Now every listing looks like a violation.
None of these are enforcement problems. They're gaps in SKU identity, variant structure, and unit of measure — the same gaps that tank conversion on the PDP.
Where Anglera fits
The PIM stores your MAP field. It has a column for map_price, it versions it, it syndicates it. What it doesn't do is the work of making sure 60,000 SKUs each carry a MAP tied to a live policy, a correct UOM, a clean MPN, and a variant structure that survives contact with a marketplace.
That's the work Anglera does, alongside Akeneo, Salsify, Syndigo, inriver, or Pimberly. We complete and normalize the SKU record so identifiers resolve, variants split correctly, and units are consistent — so a crawl that finds your part can tie it to the SKU whose MAP it's checking. Pricing strategy stays yours. The data underneath it stops being the reason enforcement doesn't work.
Frequently asked questions
Is MAP pricing legal in the United States?
It depends on how you build it. Announcing terms and declining to sell to resellers who ignore them is generally permitted under the Colgate doctrine — you are refusing business, not fixing a price. Bargain over resale prices instead and you're in rule-of-reason territory post-Leegin (2007), with state law adding variation. Get antitrust counsel on the wording before a template does it for you.
What's the difference between MAP and MSRP?
MSRP is a suggestion about the selling price and is usually shown publicly as a strike-through. MAP is a floor on what may be advertised, and it's a condition of doing business. A reseller can ignore MSRP without consequence. Ignoring MAP typically costs them co-op funds, rebates, or supply. They're often the same number, but they do different jobs.
Why do sites say "add to cart to see price"?
Because MAP restricts the advertised price, not the transaction price. Moving the number behind the cart means it isn't being advertised, so the reseller can sell below MAP while staying compliant. It's a common workaround. Some brands close it by writing cart-price rules into the policy itself, which is why `map_display_rule` belongs on the SKU record.
What does a MAP violation notice need to contain?
It has to survive the reseller replying "that wasn't us, and that wasn't the price." So it carries a screenshot, a timestamp, the URL, the internal SKU the listing was matched to, and the MAP in force on the date observed — not today's MAP. Miss those last two and you've sent an assertion rather than evidence, which is how enforcement stalls.
Should MAP live in the PIM or the ERP?
Pricing usually originates in the ERP or a pricing system. But MAP has to travel with product content to every channel, so it needs to exist as a governed attribute on the SKU record in the PIM too, with effective and expiration dates. The failure mode is a MAP list maintained separately from the feed. It drifts, and enforcement letters start going out against prices you no longer publish.