MAP pricing monitoring: how it works across dealer sites
MAP pricing monitoring means checking how specific dealer listings advertise a manufacturer’s parts and comparing each price with the MAP in effect on that date. It works in five steps: agree which listings to watch, match each one to the exact part number, check prices on a schedule, compare against the right MAP and have a person review anything below it before it’s reported.
Key takeaways · if you read nothing else
- MAP monitoring is counted in listings, one part number at one dealer, so 25 priority parts across 5 dealers is 125 listings and daily checks come to about 3,750 a month.
- A price is only worth comparing once the listing is matched to the exact part number and variant on the current MAP sheet.
- Each check is compared with the MAP in effect on the date it was captured, not with whatever the sheet says today.
- A check that fails, because a page was blocked, missing or timed out, is a coverage gap to report, not a clean result.
- Software, managed services and manual checking follow the same steps; they differ in who does the matching, the checking and the review.
On this page10 sections · pipeline
- 01What does MAP monitoring actually check?
- 02What are the parts of a monitoring program?
- 03How do monitoring tools collect prices?
- 04How is a dealer listing matched to the right part?
- 05Which price counts: advertised, cart, coupon or tax?
- 06What happens to a check, step by step?
- ⌗One check, six steps
- 07What should a monitoring record contain?
- 08How often should listings be checked?
- 09Managed service or software: what’s the difference?
- 10What does a Price Axle pilot setup look like?
- —FAQ, next step, sources
What does MAP monitoring actually check?
It checks listings: the product pages where each of your part numbers appears at each dealer you monitor. A listing is one part number at one dealer.
That’s why part counts alone don’t describe the work. 25 priority MPNs across 5 dealers is 25 × 5 = 125 listings if each dealer carries all 25 parts. Not every dealer necessarily does, so setup confirms which listings actually exist before any checking starts.
The work then scales with how often each listing is checked:
| Scope (illustrative) | Listings | Checks per week, daily | Checks per week, twice a week | Checks per week, weekly |
|---|---|---|---|---|
| 25 MPNs × 5 dealers | 125 | 875 | 250 | 125 |
| 100 MPNs × 30 dealers | up to 3,000 | up to 21,000 | up to 6,000 | up to 3,000 |
At daily frequency, 125 listings is about 3,750 checks a month (125 × 30). Our dealer scope calculator does this arithmetic for your own numbers.
Try your own numbers
- Listings
- 125
- Checks per week
- 875
- Checks per month
- 3,750
25 × 100% = 25 per dealer · 25 × 5 = 125 listings · 125 × 7 = 875 checks a week · 875 × 30 ÷ 7 = 3,750 a month
What are the parts of a monitoring program?
There are three: the listings you watch, the checks you run on them and the MAP reference you compare against. Each one changes at a different pace, and each one fails in its own way.
Listings (scope)
The exact product page URL for each part at each agreed dealer
At setup, then when dealers add, drop or rename products
A listing is missed, or the wrong variant is watched
Checks (observations)
A record of what each listing displayed at a point in time
On the agreed schedule
A page is blocked, moves or shows a price that can’t be read
MAP reference
The MAP price sheet, each price with an effective date, plus the policy’s exceptions
When the manufacturer issues a new sheet or policy version
A check is compared with a stale or missing MAP
Keeping the three separate is what makes a record defensible later. A check says what the page showed. The MAP reference says what the price should be compared with on that date. The listing record says why that page is the right part.
How do monitoring tools collect prices?
Most collect prices in one of four ways: reading the page’s HTML, reading structured product data embedded in the page, loading the page in a browser so its scripts run, or receiving a feed. A fifth way is a person opening the page and recording what it shows.
Page HTML
The tool downloads the product page and finds the price in its markup.
A redesign moves the price. Some pages don’t include the price until a script runs.
Structured product data
Some product pages embed machine-readable data for search engines, such as a schema.org Offer with a price and priceCurrency.
It can be missing, or differ from the price shown to shoppers. MAP is about the displayed price, so that’s the reference.
Rendered page
The tool loads the page in a browser so scripts can run before the price is read.
Usually slower and heavier per check. Google’s own documentation describes pages whose initial HTML doesn’t contain the content until JavaScript runs.
Feeds or APIs
The dealer or a platform provides price data directly, with permission.
Only exists where someone offers it, and it reports what the feed says, not necessarily what the page displays.
Manual capture
A person opens the page, records the price as displayed and saves a screenshot.
Takes time, so it limits how many listings can be checked and how often.
Whatever the method, a check should record the price as the shopper saw it, when it was seen and whether the check worked.
At this stage, checks are recorded by hand or imported from a CSV file; we don’t run automated collection yet. Before a dealer goes in scope, we confirm its pages can be read reliably and within its site rules. We respect site rules and rate limits, and we don’t bypass logins, CAPTCHAs or access restrictions.
How is a dealer listing matched to the right part?
By the manufacturer part number and variant, not by the product title. A listing should only be compared with MAP after someone has confirmed that the page shows the exact MPN and variant on the current sheet.
Titles are the trap. Dealer catalogs often name the vehicle rather than the part, use their own SKU, or leave the finish out. Four cases cause most mismatches:
Finishes and configurations
Black and polished versions can be different MPNs with different MAPs.
Kits
A kit can carry its own MPN and MAP, separate from its components.
Superseded part numbers
An old MPN can stay listed after the price sheet moves to a new one.
Dealer SKUs
A dealer’s own stock number may not match your MPN at all.
We record match confidence for every listing as exact, probable or uncertain. Only exact matches can be marked verified, and only verified listings are ever compared with MAP or included in a report.
Illustrative example: fictional manufacturer, dealers and part numbers. Not a real MAP violation or real pricing.
| Part on the sheet | Finish | MAP (policy v2) |
|---|---|---|
| EXM-CAI-4120-BK | Black | $449.00 |
| EXM-CAI-4120-PL | Polished | $469.00 |
Dealer B’s page shows the black kit at $449.00, but its title only says “cold-air intake kit”. Matched to the polished row by mistake, it reads $449.00 − $469.00 = −$20.00, or −4.3% of MAP: a false alarm. Matched to the black row, it’s $0.00: at MAP. The price never changed; only the match did.
Which price counts: advertised, cart, coupon or tax?
The advertised price counts: what the product page displays at the time of the check, recorded exactly as shown. Cart-only prices, coupons, bundles, shipping and tax are noted separately, because the manufacturer’s policy decides whether they count.
| What the page shows | How it’s recorded | Who decides if it counts |
|---|---|---|
| A price on the product page | The advertised price, as displayed, compared with MAP | — |
| “Add to cart to see price”, or a price only in the cart | Noted separately from the advertised price | The policy |
| A coupon code beside the price | The displayed price, with the coupon noted | The policy |
| A bundle or kit with other items | Compared only with the MAP row for the exact item or kit, then flagged for policy review | The policy |
| Shipping or sales tax added at checkout | Not part of the advertised price we record | The policy, for shipping offers |
| Several prices, or a non-USD price | Sent to review instead of being guessed | A person, then the policy |
The advertised vs. cart price guide works through these cases in detail.
What happens to a check, step by step?
Every check passes through six steps: scope, match, check, compare, review and report. A check can stop early, and where it stops decides what the report says about it.
Illustrative example: fictional manufacturer, dealers and part numbers. Not a real MAP violation or real pricing.
Sample Manufacturer Co., EXM-CAI-4120-BK, MAP $449.00 under policy v2, effective Mar 1, 2026. Checks on Oct 6, 2026.
Six-step pipeline for one fictional intake-kit listing at three dealers: a valid match reported as a potential below-MAP observation, a mismatch rejected at the match step, and a blocked check reported as could not check.
- 1 Scope In the agreed list
- 2 Match Exact match, verified
- 3 Check $412.99 displayed at 9:14 a.m. CT
- 4 Compare $412.99 − $449.00 = −$36.01 (−8.0% of MAP)
- 5 Review A person classifies it as a verified potential below-MAP ad
- 6 Report Listed as a potential below-MAP observation, with its evidence
| Step | Dealer A: valid match | Dealer B: mismatch | Dealer C: failed check |
|---|---|---|---|
| 1. Scope | In the agreed list | In the agreed list | In the agreed list |
| 2. Match | Exact match, verified | The page’s part number is EXM-CAI-4120-PL, not BK: rejected | Exact match, verified |
| 3. Check | $412.99 displayed at 9:14 a.m. CT | Not compared | Blocked (HTTP 403) |
| 4. Compare | $412.99 − $449.00 = −$36.01 (−8.0% of MAP) | — | — |
| 5. Review | A person classifies it as a verified potential below-MAP ad | — | — |
| 6. Report | Listed as a potential below-MAP observation, with its evidence | Not reported; the watchlist is corrected | Listed as “could not check”, with the reason |
Two things follow from this. A mismatched listing never produces a finding, because it never reaches the compare step. And a failed check is never counted as a clean result, because nothing was seen.
What should a monitoring record contain?
Enough for someone else to check it later: which listing, what it showed, when, which MAP row it was compared with and what happened to the check. These are the fields Price Axle keeps for each check, with illustrative values.
| Field | Example (illustrative) | Why it’s there |
|---|---|---|
| Listing and dealer | Dealer A product page for EXM-CAI-4120-BK | Identifies exactly what was checked |
| Match | Exact, verified Sep 30, 2026 | Only verified listings are compared |
| Captured at | Oct 6, 2026, 9:14 a.m. CT | Decides which MAP applies |
| Price as displayed | “$412.99” | The raw text, kept alongside the number |
| Normalized price | 412.99 USD | The number used for the comparison |
| Availability | In stock | Context for the reviewer |
| Result | ok, blocked, not found, parse error, timeout or other error | A failed check is recorded, not dropped |
| Error detail | HTTP 403 | Why a check failed |
| Evidence | Private screenshot link and a note | Lets the manufacturer see what the page showed |
| MAP row used | $449.00, policy v2, effective Mar 1, 2026 | Saved with the finding, so a later sheet can’t rewrite it |
| Difference | −$36.01 (−8.0% of MAP) | Advertised − MAP; negative means below |
| Review class | Verified potential below-MAP ad, with the reviewer and date | The decision a person made, and who made it |
A person sorts every below-MAP candidate into one of seven review classes before anything reaches a report:
| Review class | What happens next |
|---|---|
| Verified potential below-MAP ad | Reported as a potential below-MAP observation |
| Price variation only | Not reported as an exception |
| Excluded under policy | A policy exception applies, and the report says which |
| Ambiguous: ask the manufacturer | Reported as a policy question |
| False match | The listing isn’t this exact part; the watchlist is fixed |
| No valid MAP reference | Reported as a policy question |
| Inaccessible | The evidence couldn’t be confirmed; treated as a coverage gap |
What the manufacturer does with a potential below-MAP observation is its own decision under its policy. The MAP pricing violations guide covers the evidence each kind of case needs.
How often should listings be checked?
As often as your policy and budget justify. Frequency multiplies the work, and anything that changes between two checks can be missed.
A short promotion that starts after one check and ends before the next appears in neither. Checking daily narrows that window; it doesn’t close it. That’s why a monitoring record should say when each check happened, and a report should say what share of scheduled checks completed. A quiet week then means the checks ran and found nothing below MAP, not that nothing was missed.
Every Price Axle pilot has a written check schedule, and every report shows the share of scheduled checks that completed and which sources couldn’t be checked. The monitoring frequency guide goes deeper on choosing a schedule.
Managed service or software: what’s the difference?
Both follow the same steps. They differ in who does the work: with self-service software your team usually runs the matching, review and follow-up, while a managed service usually does the matching, checking and review and sends you the evidence.
| Step | Manual (your team) | Self-service software (usually) | Managed service (usually) |
|---|---|---|---|
| Agree the listings | You | You, in the tool | The provider, with you |
| Match each listing | You | The tool suggests; you confirm | The provider |
| Run the checks | You | The tool | The provider |
| Review candidates | You | You | The provider |
| Decide what to do | You | You | You |
Established software tools and managed services exist, including some that focus on the automotive aftermarket. Whichever you consider, including us, these questions show how a provider works:
- What do you count: SKUs, listings, checks or domains?
- What counts as a listing, and who confirms it’s the exact part and variant?
- Which MAP do you compare against: today’s sheet, or the one in effect on the capture date?
- What happens to a failed check, and does the report show it?
- What does each record contain: timestamp, price as displayed, screenshot, MAP row?
- Who reviews a candidate before it’s reported?
- Which channels are covered: dealer sites, marketplaces or both?
- Do you contact dealers on our behalf?
Our MAP pricing software guide applies these questions to the main options.
What does a Price Axle pilot setup look like?
Six steps take a pilot from your price sheet to the first weekly report. You supply the policy and the sheet; we do the matching, checking and review; you decide what happens next.
- You share the policy and the price sheet. We load the sheet as a dated policy version, so old MAP prices are kept, not overwritten.
- We agree the dealers and the priority parts. Before a dealer goes in scope, we confirm its pages can be read reliably and within its site rules.
- We match each listing to the exact part number and variant, and mark it verified only when it’s an exact match.
- We run a baseline check of every verified listing.
- Checks run on the agreed schedule. Failed checks are recorded with a reason.
- A person reviews every candidate, and you get a weekly report with the evidence, the policy questions and the coverage gaps.
What a pilot doesn’t do, so you know before you ask:
- We monitor an agreed list of independent dealer sites, not Amazon, eBay, Walmart or other marketplaces.
- We don’t find unknown sellers beyond that list.
- We don’t contact, warn or penalize dealers.
- We don’t send real-time alerts or make legal calls.
There are two offers: a one-time paid diagnostic, and a monitoring pilot at $349 a month, cancelable, with a written listing cap and check schedule. See pilot pricing, how it works or a sample report.
FAQ
Can monitoring find sellers we don’t know about?
Some tools advertise seller discovery. Price Axle doesn’t: we monitor the dealers you agree with us, down to the exact listing.
Does MAP monitoring cover Amazon?
It can, depending on the provider. Marketplace listings raise their own questions about which seller made which offer. Price Axle’s pilot covers independent dealer sites, not marketplaces. The MAP on Amazon guide explains what public observations can and can’t show.
Is a report with no observations proof that dealers comply?
No. It shows that the checks which ran found no advertised price below MAP. Look at the share of scheduled checks that completed, and at the coverage gaps, before reading anything into a quiet week.
New to MAP? Start with what MAP pricing is and how it works across five dealer listings.