MAP monitoring, evidence capture and enforcement

A MAP program lives or dies on proof. Detecting a low price is the easy part; what decides whether a seller comes back into line is whether you can show them a dated picture of their own page next to your policy. This module checks every monitored listing against the MAP you set, captures the offending page the moment it is found, names the seller behind it, follows the violation through notice and cure, and hands you a packet you can attach to an email.

How MAP monitoring detects a violation

Import a MAP price per SKU by CSV or through the API, with effective dates if your policy changes seasonally. Every collected observation on that SKU is compared against its MAP, and a violation opens when the observed price falls below it beyond your tolerance.

The arithmetic is deliberately simple, because it has to be defensible in a conversation with a seller. A $199.00 MAP listed at $159.00 is $40.00 below MAP, which is 20.1 percent, because (199.00 - 159.00) / 199.00 = 0.201. That depth is stored on the violation and drives how it is prioritized.

The three settings that decide what counts

• Tolerance. A cent or two of rounding is usually not worth a letter. Set a floor in percent or dollars so a $198.99 listing against a $199.00 MAP logs quietly instead of firing a notice, while a real cut opens a case.
• Effective price versus advertised price. Some policies govern only the advertised number; others reach the price after an on-page coupon. Both are captured, and you choose which one opens a violation. Example: a $199.00 listing with a 15 percent checkout coupon has an effective price of $169.15, which is 15.0 percent below a $199.00 MAP even though the advertised figure complies. The MAP policy template covers how to write that distinction down before you need it.
• Stock requirement. An out-of-stock listing still advertises its price, so it can still be a violation. It is captured either way and you decide whether it opens a case, since a permanently out-of-stock low price is often a stale listing rather than an active seller.

The evidence chain, capture by capture

The moment a violation opens, the offending page is captured. Not a row in a report saying a price was low, but the page itself. A screenshot is something a seller can look at; a spreadsheet cell is something they argue about.

Seller identification

A violation is only actionable if it has a name on it. For a storefront that is the domain. For a marketplace it is the seller behind the offer at the time of capture, which matters because the offer on a marketplace listing can change hands several times a day and the low price may not belong to whoever holds it now.

• Violations are keyed to the seller, not to the URL, so one seller undercutting on nine SKUs is one offender with nine cases rather than nine unrelated rows.
• You maintain an authorized seller list. Anyone outside it is flagged as unauthorized, which usually changes the response from a policy reminder to a supply investigation. The unauthorized sellers guide covers how those two paths differ.
• Marketplace seller names are recorded as displayed, so an alias operating across several marketplaces can be linked manually into a single offender record once you spot the pattern.
• Where a seller cannot be identified from the page, the violation still opens and still holds its evidence. It is marked unidentified rather than dropped.

The enforcement workflow

Every violation moves through states, and each state records who moved it and when. That log is the second half of the evidence, because a pattern of notices matters more than any single screenshot.

Repeat-offender tracking

One violation is an incident. The same seller, three times in a quarter across four SKUs, is a program problem. Each offender carries a record that answers that without rebuilding a spreadsheet.

• Total violations, and how many distinct SKUs they touched.
• Cumulative days below MAP, which is the number that shows scale better than a violation count.
• Average and deepest cut below MAP, in percent and dollars.
• Median time to cure after a notice, which separates sellers who respond from sellers who wait you out.
• Notices sent, with the date of each and the evidence packet attached to it.

Patterns worth reading in the history

• Test and retreat. A seller drops below MAP for a day, comes back up, and repeats a fortnight later. They are measuring your response time.
• Weekend runs. Violations that open Friday evening and cure Monday morning are invisible to a daily check that lands at 9am.
• Follow-the-leader. Two sellers go below MAP within hours of each other, repeatedly. Usually one is repricing automatically against the other, so the notice that matters goes to whoever moves first.
• Channel leakage. The same unauthorized seller appearing across several marketplaces with matching inventory points at a supply question rather than a pricing one.

The exportable evidence packet

The packet is what you attach to an email. It assembles for one violation, one seller, or a whole date range, and it contains the page captures with their times, the source URLs, the observed prices against your MAP with the depth calculated, the seller identity, the full observation series showing how long each listing stayed low, and the notice log for that seller. The underlying observations export as CSV alongside it, so anyone reviewing it can check the numbers rather than take them on trust.

Most brands send the first packet themselves; some hand it to counsel or a channel agency. Either way it reads without access to this account. To see what detection looks like on a few of your own SKUs first, the MAP violation checker does that without a signup.