MAP Monitoring for Brands: How to Track Advertised Prices Online
A marketplace alert shows a product advertised at $179 against a Minimum Advertised Price of $199. Before contacting the seller, your team needs to answer a few questions. Is it the same model? Which seller displayed the price? Was it visible to everyone, or did it require a coupon? Which policy version applied when the offer was captured?
A useful MAP monitoring workflow preserves enough detail to answer those questions, even after the listing changes.
What is MAP monitoring?
MAP stands for Minimum Advertised Price. MAP monitoring compares the advertised price of a product with the threshold specified in the applicable policy. Keep the publicly displayed price, any conditional promotional price, and the checkout price in separate fields. That gives reviewers a record of what shoppers saw and where they saw it.
Review advertised prices by seller over time. A single observation may capture a short promotion, while repeated observations can show whether the same seller regularly advertises several products below the applicable threshold. For a brand and distributor perspective, see EasyBib’s article on why minimum advertised price monitoring matters.
Competitor price monitoring can help a retailer decide whether to test a different price. MAP monitoring helps a brand or distributor review how its own products are advertised across sellers. For the retailer’s perspective, see our guide to competitor price monitoring.
Set the scope before collecting prices
Start with products and channels where the team can act on the findings. A pilot might cover one product line, several retail partners, and one marketplace. Include a few similar models and bundles so you can test whether the system matches offers accurately.
For each product, record the SKU, model, variant, currency, MAP threshold, and effective dates. If the policy distinguishes between markets, channels, or promotion types, preserve those distinctions in the monitoring rules. Keep a history of thresholds so a reviewer can compare a past observation with the policy version in effect at the time.
Track the seller behind each offer
A marketplace product page may show offers from several sellers. The featured seller can change between checks, and the same product may appear in multiple listings. Store the seller name or ID alongside the listing URL so the team can tell a price change from a change in seller.
For each observation, retain:
Product identifier, variant, seller, and channel.
Advertised price, currency, and availability.
Visible coupon, membership, or promotional conditions.
Collection timestamp and the last successful check.
The applicable MAP threshold and a screenshot or other record of the offer when available.
Keep failed checks separate from out-of-stock offers. A failed check tells you that the collection system could not verify the listing. An out-of-stock flag records what the listing displayed at the time of observation.
Turn a price alert into a reviewable case
Suppose a report flags an offer at $179 against a $199 threshold. Open the captured record and confirm the seller, model, and variant. Then check where the $179 appeared and whether the listing showed any conditions. If the current page shows $199, preserve both observations with their timestamps. That allows the team to distinguish a short-lived offer from an incorrect capture.
A simple review process has four steps:
Confirm the match. Verify the seller, product, variant, and condition.
Check the context. Review availability, promotion terms, and the applicable policy version.
Record the outcome. Mark the case as confirmed observation, data error, policy exception, or pending clarification.
Assign follow-up. Give the responsible person the evidence and keep the case status visible to the team.
Prioritise recurring observations and cases affecting multiple products. Group repeated alerts for the same offer so a reviewer can see the history in one place. For examples of how promotions, changing listings, and expanding catalogues complicate manual checks, see Lemarbet’s article on seven challenges of online MAP monitoring.
Automate collection and keep a review step
Automate repeated checks, threshold comparisons, and alert grouping. Send each case to a reviewer with the evidence needed to verify it. Before configuring any seller-facing action, have the relevant team review the policy, the applicable market, and the proposed response.
Test the workflow against realistic cases. Include a bundle that resembles a standalone product, a coupon that changes the displayed price, a featured seller switch, and a page that fails to load. Check how each event appears in the report and whether a reviewer can recover the underlying observation. For an example of a workflow spanning retailer websites and marketplaces, see The Data Scientist’s guide to automating MAP monitoring.
Measure the pilot before expanding
Track how many planned offers were checked successfully, how many flagged cases contained correct product and seller matches, and how long review took. Review missed observations separately by checking a sample of listings that generated no alerts.
If too many cases lack seller IDs, timestamps, or promotion details, fix those gaps before expanding the catalogue. The pilot should leave your team with records it can verify, a manageable review queue, and a clear owner for each case.