Evidence
Why Screenshot-Only MAP Evidence Is Weak
A screenshot is persuasive and easy, and it answers almost none of the questions a challenged MAP finding has to answer. What it leaves out, how it can be obtained badly, and what to keep beside it.
Most MAP programs start with screenshots, because a screenshot is the obvious thing to take when you see a price you do not like. It is fast, it is visual, and in a conversation with a seller it is persuasive: here is your listing, here is the price, here is the date. For a first conversation with a partner that is often enough.
It is not enough for the conversations after that, and a program that relies on screenshots alone finds this out at the worst moment — when a seller, a distributor's lawyer or a marketplace asks a question the picture cannot answer.
Four questions a screenshot cannot answer
Which seller? A screenshot shows a storefront name. Storefronts rename; two storefronts can choose similar names; the name at the time of the screenshot may not be the name the seller trades under when the notice arrives. The identity that persists is the marketplace's seller identifier, and it is not on the screenshot.
Against which policy? A screenshot shows a price. It does not show the floor that applied on that date, the tolerance, whether shipping was included in the comparison, whether a promotion was in force, or whether the seller had an exception. A price of $129.99 is a violation of a $149.00 floor and compliant under a $125.00 promotional floor, and the picture looks identical in both cases.
How much of the listing did you see? A screenshot captures a viewport. It does not record that the offer list was complete, that the seller in question was the one holding the Buy Box, or that the price shown was the advertised price rather than a cart-revealed one. Coverage — what a capture did and did not see — is what decides whether an absence means anything, and a screenshot has no concept of it.
Has it been changed? An image file can be edited. Its metadata can be edited. A seller who wants to dispute a finding does not need to prove the screenshot was altered; they only need to observe that it could have been, and that the brand cannot prove otherwise. A record with no fingerprint, no sealing time and no verification is exactly as trustworthy as the person presenting it.
The provenance problem
There is a further problem specific to screenshots taken by automation.
A person opening a product page in a browser and taking a screenshot is doing what any customer does. A system that takes screenshots at scale is doing something else, and the question is how. If it solves challenges, rotates through proxies to avoid rate limits, farms accounts, or disguises its browser to evade detection, then every screenshot it produces is also a record of the presenting party working around the marketplace's access controls. That is worse than no evidence: it hands the other side an argument, and it exposes the brand to the marketplace's own remedies.
This is why MapProtector does not take screenshots of Amazon. It reads offers through the Selling Partner API authorization the brand grants from Seller Central, and every evidence package is labeled with what it is — derived from MapProtector's own records of what the source reported; not a picture of the listing page. The label is inside the sealed record, not just on the screen, so the distinction cannot be lost in forwarding. Screenshots and captured files says the same thing from the product's side.
What a defensible record has instead
The alternative to a picture of the listing is a record of the observation: the facts the source reported, assembled from records that were written once and never edited, and sealed.
| The screenshot shows | The record establishes |
|---|---|
| A storefront name | The seller's marketplace id and the name it was seen under at the time |
| A price | The advertised price and currency, condition, fulfillment and Buy Box state, at an instant in UTC |
| — | The coverage of the scan that saw it |
| — | The policy version, tolerance and treatment rules it was measured against, and the effective floor after any promotion |
| — | The seller's authorization standing at the time of capture |
| — | Who confirmed the finding and when |
| — | A SHA-256 fingerprint, the sealing time and person, and a verification that still passes |
The last row is the one that changes the conversation. "This record was sealed on the 3rd at 09:31 by our compliance administrator and has verified on every read since" is a sentence a screenshot cannot produce. What Evidence Should You Capture for a MAP Violation? sets out each part.
Where screenshots still belong
None of this makes a screenshot useless. In a first conversation with an authorized partner — "your listing showed this on Tuesday" — a picture is more persuasive than a table of fields, and there is nothing wrong with a person taking one. Two rules keep it honest.
Keep it beside the sealed record, not instead of it. The screenshot illustrates; the record proves.
Keep it with its provenance: the URL, the date and time, who took it, and how. A screenshot with those four facts written down is a reasonable illustration. A folder of undated images named "violation1.png" is a liability.
The test to apply
Before relying on any piece of evidence, ask what it would take for the other side to say "prove it". If the answer is "nothing — they would just have to ask", the evidence is weak. A sealed observation record answers the question before it is asked; a screenshot invites it. The MAP Evidence Checklist lists what to look for on a record before you treat a finding as proven.