MAP monitoring software built around the enforcement chain

MAP monitoring software watches every place your products are advertised, compares each listed price against the Minimum Advertised Price you set, and records a violation the moment one appears. Detection is the easy half. What decides whether a MAP program works is the quality of the evidence behind each violation and the record of what you did about it.

What MAP monitoring software does, and where MAP programs fail

A MAP violation is a display fact: on a given day, at a given URL, a specific seller advertised your product below the number your policy allows. The notice, the marketplace complaint and the decision to stop shipping all rest on that fact, and on your ability to show it later to someone who was not there and has no reason to take your word for it.

Detection on its own is therefore a weak product. Almost any tool can tell you a price was below MAP an hour ago. Fewer can show the page as the shopper saw it, name the seller, prove the record has not been edited since capture, and show that the same seller did this twice already this quarter. Those are the parts that change behavior.

• Checks every tracked listing on your refresh schedule against the MAP in force that day. Refresh runs daily on Starter, twice daily on Growth, four times daily on Scale, hourly on Enterprise.
• Captures a full-page screenshot at detection time, stored with the URL, the timestamp in UTC, the price read, the MAP in force and the gap.
• Identifies the seller: storefront name and domain, or seller name and marketplace seller ID.
• Scores severity from the gap and the seller history, so a first-time three percent slip is not treated like a repeat twenty-four percent cut.
• Tracks status: open, notice sent, resolved, reopened, with the date of each transition.
• Exports an evidence packet for a notice, a distributor conversation or a marketplace complaint.
• Alerts by email or Slack when a violation appears, with a weekly digest for the program.

The enforcement chain: detect, prove, notify, verify

A MAP program is a chain, only as strong as its weakest link. Most programs are strong at step one and weak at steps two, six and seven, which is why they produce plenty of alerts and very little compliance. Here is the chain, with what usually goes wrong at each step.

1. 1

   Detect the violation

   Compare the advertised price on each tracked listing against the MAP for that product. Detection frequency is the ceiling on the program: a daily check cannot see a nine-hour flash sale that began and ended between two checks.

2. 2

   Capture the evidence

   The screenshot has to be taken at detection time, automatically. By the time an analyst opens the link next morning the price is usually back at MAP, and the only record left is a number in a spreadsheet. One capture stores the image, URL, timestamp, price read and MAP in force together.

3. 3

   Identify the seller

   A URL is not a defendant. On a marketplace the same listing can be held by different sellers on different days, so the record must name the seller who held the offer at capture time, with the seller ID. On a storefront, record the name, the domain and the checkout entity.

4. 4

   Classify the severity

   Decide the response from the size of the gap and the seller history, using a written rule rather than a judgement call. Writing it down is what makes the same violation get the same response in a quiet week and in a peak-season scramble.

5. 5

   Notify the seller

   Most violations are corrected by the first clear notice. One naming the product, the URL, the price displayed and the capture time, with the image attached, is far harder to argue with than an email saying you appear to be below MAP. Policy language is in the MAP policy template guide.

6. 6

   Escalate when the deadline passes

   Escalate where you can actually apply pressure: the marketplace policy team, the distributor who supplied the inventory, or your own decision to stop shipping. The evidence packet earns its keep here, because you are talking to a party with no reason to accept an assertion.

7. 7

   Verify the fix and count repeats

   Recheck on the next cycle and record the result. A violation is resolved when the page shows a compliant price, not when the seller says it is fixed. Then keep the count: the pattern across SKUs shows whether you have a careless repricer or an unauthorized seller moving diverted inventory.

Why a spreadsheet of prices is not evidence

A spreadsheet row reading Ironside 20V Drill Kit, DealVault, 149.00, March 3 is a claim, not a record. It is a number typed by your own team, in a file anyone can edit without leaving a trace, describing a page that no longer looks that way. It does nothing when the seller replies that the price was never that low.

What makes a capture usable

• The full page, not a crop. A cropped price proves nothing about which product or seller it belonged to. The image needs title, seller and price together.
• The exact URL, including variant parameters. A size or color variant often carries a different price, and a bare product URL loads whichever variant it likes.
• Capture time stored in UTC. The seller is in another timezone and the page has changed twice since. A timestamp with no timezone is an argument waiting to happen.
• Seller identity as displayed at capture time. Not who holds the listing today. Who held it then.
• The MAP in force on that date. Schedules change, so a March violation is judged against the March number rather than today's.
• Page context: currency, availability, shipping shown, and any promotion or coupon text.
• An immutable store. A capture is written once and never edited. A correction is a new capture. Every export is logged.

Violation severity tiers and the response each warrants

Do the arithmetic precisely, because the tier decides the response. A product with a MAP of $199.00 advertised at $159.00 is $40.00 below, and 40.00 divided by 199.00 is 0.201, so the listing is 20.1 percent below MAP. That is a tenth of a point over the critical line. Decide the boundary rule once, in writing.

The hard cases in MAP violation detection

Below-MAP is trivial to detect when a page shows one price. Real channels are messier. These five cases are where MAP violation detection gets difficult, and what each one requires.

Coupon at cart

The product page shows $199.00, exactly at MAP. A site-wide code takes 15 percent off at checkout, so the shopper pays $169.15. Nothing displayed is below MAP. Whether this is a violation depends entirely on your policy: one governing the advertised price and one governing the net price after generally available discounts give opposite answers here. Monitoring records what was displayed, including the promotion text and any code on the page, and flags the listing as promotion-present so a human applies your policy. We do not complete checkouts to compute a net price.

Bundle pricing

A MAP-protected $429 speaker ships with a $79 stand at $429 for the pair. No advertised number is below MAP and real value has still been given away. This is a matching problem before it is a pricing problem: the listing has to be recognized as containing your product. Matching joins on GTIN first, then on title and attribute similarity, and a bundle usually surfaces as a lower-confidence match against the base product. Review that queue rather than filtering it out, and write your bundle rule before you need it.

Strikethrough and compare-at prices

A page shows $249.00 struck through and $179.00 in red. Both numbers exist in the HTML, and a naive scraper returns whichever one its selector points at. Read the compare-at price and you never see the violation. Read a strike price on a page with no active discount and you send a notice you have to withdraw, which costs you credibility with that seller for a year. We read schema.org Product structured data where a site publishes it, because it separates offer price from list price explicitly, and fall back to a per-domain recipe tested against both states of the page.

Marketplace buy-box rotation

On a marketplace the featured offer rotates through the day as sellers compete, and a daily check samples one moment of that rotation. If a compliant seller holds the box at 6 a.m. and a violator holds it at 8 p.m., that check reports a clean channel all week. Two things fix it: check more often, four times a day on Scale and hourly on Enterprise, and read the full offer list rather than the featured offer alone.

Price shown only after add to cart

Some sellers hide the number behind an add-to-cart action or a click-for-price link precisely because a hidden price is harder to call an advertised price. We record what the page displayed, which here is the absence of an advertised price, with the seller identity and the capture. We do not add items to carts or place orders. Treat it as a policy signal rather than a detected violation: many brands address price-hiding mechanics in the policy text, and a documented pattern is useful with a marketplace.

Repeat offenders and the patterns worth reading

One violation is an incident. The same seller three times in a quarter is a program problem, and the two need different work. After a few months of history, the shape of the violations tells you more than the count.

• One seller, many unrelated SKUs. A supply question, not a pricing question. Someone is selling inventory they were not meant to have. Trace the lot.
• Many sellers, one SKU, all at the same number. A price leaked through a feed or a distributor sheet. Fix the source and most listings correct themselves.
• Violations hours after a competitor price move. An automated repricer with no MAP floor. The most fixable case: the seller is not hostile, their rule is missing a floor.
• A seller who corrects after every notice, then reoffends. They are testing enforcement consistency. The counter is a documented ladder applied identically.
• Violations concentrated on new SKUs. Check that the MAP schedule reached the channel before the product did. Many first-week violations are administrative.

The habit that makes this work is boring: review the whole violation log monthly, not just the open items. The how to monitor MAP violations guide sets out that review, and MAP protection covers the module.

What MAP price monitoring costs here

MAP monitoring with screenshot evidence is included on every plan, Starter upward. You pay for scale, meaning how many products you track and how often they refresh, never for the capability. Users are unlimited too, because a program only the pricing analyst can see stops when they take a week off. Detail is on pricing, and you can spot-check a few listings with the free MAP violation checker.