Monitor MAP prices and unknown sellers, and keep every decision with a person
Updated · By Ecomsellertool editorial team
To automate MAP price and unauthorized seller monitoring, collect the offers on your listings from each marketplace, match every seller to your authorized-reseller list and every advertised price to your MAP sheet, and save evidence for each mismatch: a screenshot, the time, the price and the seller ID. The automation records and queues. A person decides every contact, report or change to a reseller agreement, under your own policy.
- MAP is a brand's own policy. The FTC says a manufacturer may stop dealing with a retailer that does not follow its price policy, while dealers cannot agree on retail prices (checked October 20, 2026).
- Amazon's ANY_OFFER_CHANGED notification fires on a change to any of the top 20 offers by condition, or to the Buy Box winner or price, but only for items where you have an active offer.
- Amazon's getItemOffers returns the lowest priced offers for one ASIN, with each offer's seller ID, at a default rate of 0.5 requests per second.
- eBay says its VeRO program applies only to intellectual property rights, not distribution or pricing agreements; Walmart's Brand Portal takes copyright, trademark, patent and counterfeit claims.
- In this recipe rules match prices and sellers and save evidence; a person decides every contact, report and reseller-agreement change.
The step map: who runs each step
Trigger: A change to the offers on one of your listings (an Amazon offer-change notification where you sell the item), plus scheduled checks of every monitored listing on Amazon, Walmart and eBay.
| Step | What happens | Who runs it |
|---|---|---|
| 1 | Offers on each monitored listing are collected: Amazon offer-change notifications where you have an active offer, scheduled getItemOffers calls for the ASINs where you do not, and scheduled checks of your Walmart and eBay listings. | Rule |
| 2 | Each offer is matched to the authorized-reseller list by marketplace seller ID, and its advertised price is compared with the MAP sheet row for that SKU and date, after any approved promotion window. | Rule |
| 3 | Each mismatch is classed with the rule table: below MAP by an authorized reseller, unknown seller, possible counterfeit, Buy Box lost to an unknown seller, or listing content changed. | Rule |
| 4 | Evidence is captured at once: a full-page screenshot with the URL, the time in UTC, the seller name and ID, the price and shipping, the condition and the fulfillment method, stored where nobody can edit it. | Rule |
| 5 | Repeat sightings are grouped into one case per seller and SKU, and the case is re-checked on the next run so a person sees whether it is still live. | Rule |
| 6 | A person reviews each case against the brand's written policy and decides the next step: no action, a reminder under the reseller's own agreement, a test buy, an intellectual-property report, or a referral to counsel. | Person |
| 7 | The decision, who made it and the date are logged on the case, and the case closes only when a later check shows the offer has changed or gone. | Rule |
6 rule steps · 0 AI model steps · 1 person step. A rule follows fixed logic you approve; an AI model handles messy input and its output is checked by rules; a person makes the calls listed below.
What stays with a person
- Whether a price below MAP is a policy breach at all: promotions, open-box items, different conditions and approved exceptions
- Any message to a reseller, and what it says
- Any report to a marketplace, which must rest on a real intellectual-property issue, never on price alone
- Any change to, or end of, a reseller agreement, decided with the brand's counsel
- Changes to the MAP sheet, the authorized-reseller list and the rule table
Which tools can run it
- A spreadsheet and a weekly manual check, for a few ASINs and two or three resellers
- A third-party MAP or brand monitoring service that captures offers and screenshots, with your own review queue on top
- A workflow tool such as Zapier, Make or n8n receiving Amazon notifications and writing cases to a sheet or ticket queue
- Custom code on your accounts, for offers on several marketplaces, seller-ID matching, evidence storage and one case queue
Systems it connects
- Amazon Selling Partner API (Notifications, Product Pricing)
- Walmart and eBay listing pages or a monitoring service
- MAP sheet (SKU, MAP, effective dates, promotion windows)
- Authorized-reseller list with marketplace seller IDs
- Evidence store for screenshots and offer records
- Ticket queue, Slack or email for cases
Build size: Medium
Matching is simple; the work is collecting offers from several marketplaces, keeping seller IDs current and saving evidence a person can rely on later.
Picture a typical week (an illustrative example). A new seller appears on your best ASIN overnight, priced under your minimum advertised price. One of your own resellers runs a "price in cart" deal on Walmart. An eBay listing uses your photos for an item you never sold to anyone. Each of these needs a different response, and most brands find out days later, from a customer or a sales rep. This recipe watches the offers on your listings, matches each one to your reseller list and your MAP sheet, saves the evidence, and puts a case in front of a person. It never contacts or reports anyone by itself. It is one page of our automation library.
What should the monitor do with each kind of offer it sees?
Write the rule table before you connect anything. Each row names what the monitor sees, what it records, who acts and the next steps your policy allows. The automation owns the first two columns. People own the last two. The rows are a starting point: your counsel and your policy decide what belongs in the last column.
| # | What the monitor sees | What it records | Who acts | Allowed next steps |
|---|---|---|---|---|
| 1 | An authorized reseller advertises below the MAP for that SKU and date | Screenshot, time, price and shipping, seller ID, the MAP row that applied | Channel or sales manager | Check for an approved promotion or exception; if none, follow the steps your policy and that reseller's agreement set out. No message goes out without a person |
| 2 | An unknown seller (an ID not on your reseller list) offers your product | Seller ID and storefront, price, condition, fulfillment method, first-seen time | Brand protection owner | Check whether the seller bought from one of your distributors; log it; consider a test buy. Being unknown is not by itself grounds for a marketplace report |
| 3 | A buyer review, a test buy or a seller's own listing suggests the item is counterfeit | The evidence behind the suspicion, order details from any test buy, photos | Brand protection owner, with counsel | An intellectual-property report through the marketplace's own program, only when the evidence supports it |
| 4 | The price is above MAP on the page but lower once the item is in the cart | The page screenshot and a cart screenshot, both timed | Channel manager | Your policy decides whether a cart price counts as advertised; act only on what the policy says |
| 5 | The Buy Box moves to an unknown seller | The new winner's seller ID, price and fulfillment method, your own offer's price at that moment | Brand protection owner and the Amazon account manager | Treat as row 2; check your own offer's stock and price, since a lost Buy Box is often an operations problem |
| 6 | Listing content changes: title, images, bullets or brand field | Before-and-after copy and images, time, and which seller is on the listing | Catalog owner | Restore your content through your own Brand Registry access; report only real IP misuse |
| 7 | An item sold as used, open-box or refurbished below MAP | Condition, condition notes, price | Channel manager | Usually no action; your policy says whether MAP covers non-new conditions |
| 8 | An offer that was flagged is gone or back above MAP on the next check | The new state and time | Nobody (rule) | Close the case automatically, keeping its evidence |
Three choices make the table safe. The automation records; it never contacts a reseller, files a report or changes an agreement. "Unknown" and "below MAP" are different problems with different owners, so they stay in different rows. And every case carries the exact MAP row that applied on that date, because a price is only a breach against the right number.
What evidence should each case keep?
Evidence decides whether a person can act on a case a week later. The capture runs the moment a mismatch is found, because offers change by the hour. Store each record where nobody can edit it, and add every later check and decision to the same case.
- A full-page screenshot with the URL and a visible capture time
- The capture time in UTC, plus your local time
- The marketplace, the listing ID (ASIN, Walmart item ID or eBay item number) and your SKU
- The seller name, the marketplace seller ID and a link to the storefront
- The advertised price, the shipping price and any coupon or promotion shown
- The condition, the condition notes and the fulfillment method
- Whether the seller is on your authorized-reseller list, and which agreement applies
- The MAP sheet row that applied on that date, including any promotion window
- Every later check of the same offer, with its time and result
- Every decision: who made it, when, and what was done
Where do the offers come from on each marketplace?
On Amazon, the Selling Partner API does most of the work. Amazon's notification type values say ANY_OFFER_CHANGED is sent whenever any of the top 20 offers changes, by condition, or the Buy Box winner or Buy Box price changes, but only for items where you have active offers (checked October 20, 2026). Each offer in it carries a SellerId, ListingPrice, Shipping, IsFulfilledByAmazon and IsBuyBoxWinner, which is what rows 1, 2 and 5 need.
For ASINs where you have no active offer, use a scheduled check instead. Amazon's getItemOffers returns the lowest priced offers for a single item by ASIN, at a default rate of 0.5 requests per second (checked October 20, 2026), and its offer list holds up to 20 offers. At that rate, for example, a brand watching 2,000 ASINs needs a little over an hour for one full pass, so check top sellers more often than the long tail.
For Walmart and eBay we do not rely on a seller-side API for other sellers' offers. Most brands use scheduled checks of their own listing pages or a monitoring service that captures offers and screenshots. Either way, the records land in the same case queue and go through the same rule table. Our Buy Box glossary entry explains how Amazon picks the featured offer, which helps a person read row 5.
Can a marketplace remove a seller for breaking your MAP policy?
Plan as if it cannot. The marketplaces' brand programs are built for intellectual property, not for pricing. Amazon describes Brand Registry's Report a Violation tool as a place to report suspected IP infringement, store policy violations and regulatory concerns (checked October 20, 2026); pricing is not among them.
eBay is explicit. Its VeRO program page says the program only applies to intellectual property rights, not distribution or pricing agreements, and lists preventing the sale of items below a price point as a reason not to report (checked October 20, 2026). Walmart's Brand Portal overview says approved brand owners can submit claims of copyright, trademark, patent and counterfeit, and requires a trademark registered with the USPTO (checked October 20, 2026).
So a report belongs only in row 3 or row 6, when there is a real IP issue and evidence for it. That is why every report in this recipe is a person's decision, made on the evidence the automation saved.
What does the law say about MAP policies?
We are not lawyers, and this is not legal advice. The FTC's guide to manufacturer-imposed requirements says a manufacturer may deal only with retailers who agree to its pricing policy, and may stop dealing with a retailer that does not follow it (checked October 20, 2026). The same page says competitors at each level must set prices independently, so dealers cannot agree on retail prices.
The page also says the FTC once challenged MAP policies of large music distributors as unreasonable, and that some state laws and international authorities treat minimum price rules as illegal per se. That is why the policy, the reseller agreements and any step that touches a reseller belong to your counsel, not to software. The monitor's job is narrower: show a person, accurately and quickly, what is happening on your listings.
Who builds MAP and seller monitoring for brands?
Ecomsellertool builds workflow automation on your own marketplace accounts. We have built software on Amazon's seller APIs since 2017 and shipped 50+ tools for 100+ teams. For seller monitoring we start with your MAP sheet, your reseller list and your policy, then connect the offer data, the evidence capture and one case queue. Send a project brief below, or read how our workflow automation service works.
The building blocks are work we have shipped:
- Seller alerts for Amazon accounts. For AccountDr we built rule-based alerting software that sends push and email notifications for hijackers, ASIN changes, suppressed Buy Box, listing faults and other account events, the same signals behind rows 2, 5 and 6.
- Offer-change data, read by rules. For the repricer we built, rule-based automation, offer-change notifications feed rules that compare each offer with the Buy Box or the lowest price on the same ASIN, with logs of every change.
A full account-level view, with health metrics and drafted case responses, is our account health agent; listing errors on Walmart, eBay and TikTok Shop are covered by our listing error alerts recipe. Custom builds can run on Ecomsellertool Growth OS, beside your listings and orders. You keep your accounts, your data and the custom code we build; the Growth OS base is licensed to you.
Get your seller monitoring built
Send us your listings, your reseller list and what you need to see
Describe the workflow you want automated. We reply with a written plan: scope, timeline and a fixed price.
Frequently asked questions
Does Amazon enforce my MAP policy?
Do not plan on it. MAP is your own policy, and you apply it through your own reseller relationships. Amazon describes its Brand Registry Report a Violation tool as a place to report suspected intellectual-property infringement and store policy violations, and pricing is not one of the listed uses. Reports should rest on a real IP issue, such as a counterfeit or a misused trademark.
Can I report a seller on eBay or Walmart for selling below MAP?
Not as a pricing matter. eBay says VeRO applies only to intellectual property rights, not distribution or pricing agreements, and lists preventing sales below a price point as a reason not to report. Walmart's Brand Portal accepts copyright, trademark, patent and counterfeit claims. A below-MAP price is something you raise with your own reseller, under your own agreement.
How do I find out who an unknown seller on my Amazon listing is?
Start with the seller ID. Amazon's offer data includes a SellerId for each offer. Match the ID against your authorized-reseller list, then check whether the seller bought from one of your distributors. A person decides whether a test buy or an IP report is justified.
Is a MAP policy legal?
The FTC says a manufacturer may deal only with retailers who agree to its pricing policy and may stop dealing with a retailer that does not follow it, while competitors must set prices independently. It also notes that some state laws treat minimum price rules more strictly. This is not legal advice: your counsel writes the policy and decides how it is applied.
Should the monitoring tool email resellers automatically?
No. An automatic warning can read as pressure on resale prices or reach a seller who was never in breach, such as one selling a used item. The automation should gather the evidence and queue the case; a person checks it against the policy and decides whether anyone is contacted, and what they are told.
What evidence should I keep for a MAP or unauthorized seller case?
A full-page screenshot with the URL and a visible timestamp, the time in UTC, the seller name and marketplace seller ID, the advertised price, shipping, condition and fulfillment method, the ASIN or item ID, and the MAP row that applied that day. Store it unchanged and log every later check and decision on the same case.
