MAP monitoring
MAP monitoring is checking that resellers advertise your products at or above the minimum advertised price, and recording proof when they do not. Zenrows fetches marketplace and reseller listings, extracts the advertised price and seller, and captures a timestamped screenshot of each violation, so your channel team acts on evidence.
Updated
{
"violation_id": "map-2026-10-17-0193",
"sku": "KX-500-BLK",
"map_price": 499.0,
"advertised_price": 449.0,
"gap": -50.0,
"gap_pct": -10.0,
"currency": "USD",
"channel": "marketplace",
"listing_url": "https://www.example-marketplace.com/item/kx-500-black",
"seller": {
"name": "Example Deals Store",
"seller_id": "A1EXAMPLE42",
"authorized": false
},
"price_location": "product_page",
"evidence": {
"screenshot": "evidence/map-2026-10-17-0193.png",
"captured_at": "2026-10-17T14:32:07Z",
"proxy_country": "us"
},
"first_seen": "2026-10-18T09:05:00Z",
"times_seen": 3
}
What MAP enforcement teams collect
A MAP program needs every place your product is advertised, and proof of what each listing showed at a given moment.
| Job | Data you collect | Typical sources |
|---|---|---|
| Authorized reseller sweep | Advertised price per SKU per authorized dealer | Reseller product pages, |
| Marketplace seller scan | Every seller of the SKU, price, seller ID | |
| Unknown seller discovery | Stores selling your products off your dealer list | |
| Evidence capture | Full-page screenshot, URL, price, seller, timestamp, country | The violating listing, at check time |
| Cart and email-for-price checks | Price only after "add to cart" or "see price in cart" | Reseller cart pages |
| Repeat offender history | Violations per seller over time, notice dates, time to fix | Your violation log |
Why MAP violation monitoring breaks
Checks must be accurate per seller and defensible later.
A miss costs margin; a false hit sends a notice to an innocent dealer.
"The price was never that", with nothing on file
A screenshot per violation from a Browser session in the market's country, with URL and timestamp
CAPTCHAs or empty offer pages after a few checks
Zenrows' stealth gets through AWS WAF, PerimeterX (HUMAN) and Akamai
Featured seller and price change intraday; a daily check misses them
Batch runs the SKU and seller list several times a day
MAP on the product page, a discount in the cart
Browser runs Playwright or Puppeteer to read the cart price
A lower price in one country only
Geotargeting checks from each policy country
One scraper per dealer, breaking on redesign
Extract returns price and product fields without selectors
How to set up MAP monitoring with Zenrows
- Load your MAP list: SKU, MAP price, start date, authorized sellers.
- Find every listing on Google Shopping and marketplaces; add new seller URLs to the watch list.
- Check advertised prices with Adaptive Stealth Mode and CSS selectors (Extract for varied dealer layouts), against MAP.
- Capture evidence on violations only: screenshot the URL, or use a Browser session from the same country, and store it with the record.
- Check cart prices where needed: add to cart in Browser and read the total.
# pip install requests
import json
from datetime import datetime, timezone
import requests
API = "https://api.zenrows.com/v1/"
LISTING_URL = "LISTING_URL" # one seller's listing for the SKU
SKU, MAP_PRICE = "KX-500-BLK", 499.0
base = {"apikey": "YOUR_ZENROWS_API_KEY", "url": LISTING_URL}
# Example selectors: match them to the marketplace or dealer site
fields = {"price": ".offer-price", "seller": ".seller-name"}
offer = requests.get(API, params={**base, "mode": "auto", "proxy_country": "us",
"css_extractor": json.dumps(fields)}).json()
price = float(offer["price"].replace("$", "").replace(",", ""))
if price < MAP_PRICE:
# Evidence capture. For a screenshot pinned to one country, use the
# Browser example below with proxy_country in the connection URL.
# Screenshots need a full browser render.
shot = requests.get(API, params={**base, "js_render": "true",
"premium_proxy": "true",
"screenshot": "true",
"screenshot_fullpage": "true"})
stamp = datetime.now(timezone.utc).strftime("%Y%m%dT%H%M%SZ")
with open(f"evidence/{SKU}-{stamp}.png", "wb") as f:
f.write(shot.content)
print("violation", offer["seller"], price, stamp)// npm install playwright (save as check-cart.mjs)
import { chromium } from "playwright";
const browser = await chromium.connectOverCDP(
"wss://browser.zenrows.com?apikey=YOUR_ZENROWS_API_KEY&proxy_country=us"
);
const page = await browser.newPage();
// Example URLs and selectors: match them to the reseller's store
await page.goto("RESELLER_PRODUCT_URL");
await page.click("button.add-to-cart");
await page.goto("RESELLER_CART_URL");
const cartPrice = await page.textContent(".cart-line-price");
await page.screenshot({ path: "evidence/cart-price.png", fullPage: true });
console.log({ cartPrice, checkedAt: new Date().toISOString() });
await browser.close();npx -y @zenrows/cli init
zenrows extract LISTING_URL --css '{"price":".offer-price","seller":".seller-name"}'
zenrows fetch LISTING_URL --proxy-country us --screenshot --out evidence/KX-500-BLK.png
# listings.jsonl: one {"url": "LISTING_URL"} per seller and SKU
zenrows batch create listings.jsonl --wait# Connect once
claude mcp add zenrows -e ZENROWS_API_KEY=YOUR_ZENROWS_API_KEY -- npx -y @zenrows/mcp
# Then ask:
Use Zenrows to open each Amazon and Walmart listing in listings.txt for SKU KX-500-BLK,
return the seller name and advertised price for each, and take a full-page screenshot
of any listing priced below our $499 MAP.Which Zenrows product fits
- Check one listing and capture a screenshot FetchCSS selectors read price and seller; a screenshot records the page
- Read prices across many dealer site layouts ExtractPrice and product fields without per-site selectors
- Check all SKUs and sellers several times daily BatchOne job, a result per URL
- Read prices hidden behind "add to cart" BrowserA real browser in your chosen country clicks to the cart and screenshots it
What success looks like
| Measure | What good looks like | How to check it |
|---|---|---|
| Detection lag | New violations flagged within one cycle | first_seen against change time, on test listings you control |
| Evidence completeness | URL, price, seller, timestamp, country and screenshot on every violation | Share of records with all six |
| False positives | Almost no notices to compliant sellers | Review and log the cause of every dispute |
| Seller coverage | Every seller of your top SKUs watched | Weekly seller counts per SKU against your list |
| Repeat offender tracking | Each seller's history one query away | Violations per seller per month |
| Cycle run time | A full check done before the next cycle | Start and end time per Batch job |
MAP monitoring FAQ
-
Tracking the prices retailers and marketplace sellers advertise for your products against your minimum advertised price policy. It covers authorized dealers, marketplace sellers and unknown stores, recording each listing below MAP with evidence to follow up.
-
Monitoring finds and documents violations. Enforcement follows your policy: a notice, a warning, then its steps for repeat violations. Good monitoring speeds it up: each notice already has URL, price, seller, time and screenshot.
-
Search each SKU on Google Shopping and every marketplace in your category, and compare sellers with your authorized list. Repeat on a schedule: unauthorized sellers often appear for a few days. Store seller IDs to tell returning sellers from new ones.
-
Start daily. Check top SKUs several times a day where the featured seller rotates; weekly suits slow dealer sites.
-
At least the URL, advertised price, seller name or ID, date and time, and a screenshot of the price. Record the check's country too: some sellers price by region.
-
Each violation with SKU, MAP price, advertised price, gap, seller, marketplace, country, first and last seen, and a screenshot link. Add a seller view of violations per month, so repeat offenders stand out, and a SKU view of the most discounted products. Export as CSV or feed your BI tool.
-
Advertised prices are public by design, and brands commonly monitor them. MAP policies fall under competition law, which varies by country, so ask your legal team about each market. Collect listing data only, not personal data about sellers' customers.