12 sellers, three weeks, one recommended price. That combination, not the depth of the discount, decides how a price gap should be read, and most brand teams never collect the two fields that separate the two cases. As of November 15, 2026, the practical question for European brands is narrower than it used to be — not whether to monitor price, but which fields to collect so a gap can be attributed instead of merely reported.
A price gap is not yet a violation
A listing below the recommended price may be a permitted promotion, a clearance of old stock, a pricing exception agreed with the brand, or an unauthorised seller. Monitoring can only tell you that a number is different. Attribution needs three more fields: seller identity, offer duration, and whether the discount is a coupon or a shelf price. Without them, every alert turns into an email thread rather than a decision.
Duration matters more than depth. A 30% gap that lasts four hours during a campaign and a 12% gap that persists for a month are different problems with different owners. The first is usually a campaign mechanics issue; the second is usually a distribution issue, and it compounds because other retailers start matching it.
| Field | What it adds | Why it changes the decision |
|---|---|---|
| Seller identity | Who is advertising | Authorised or not |
| Offer duration | How long the gap lasts | Campaign noise or structural |
| Coupon vs shelf price | How the discount is applied | Whether the RRP was actually breached |
| Total price with shipping | Landed cost | Cheapest headline is not cheapest total |
Collect the offer, not the page
Product pages change layout, add modules, and rotate recommendations. Offer-level records survive that. What you want is one row per offer per day: product identifier, seller, price, shipping cost, availability, delivery window, and the URL of the offer. Match on EAN or GTIN first, model number second, title last — title matching produces false positives that quietly erode trust in the whole dashboard.
Frequency should follow commercial exposure rather than habit. Key SKUs daily, the long tail weekly, and everything more often in the two weeks around a major promotional date. Collecting public offer data at a higher rate than you can review is a common failure mode: the dashboard fills up, nobody reads it, and the team concludes that monitoring does not work.
Separate detection from enforcement
Detection is a data job; enforcement is a commercial and legal one. Keeping them in one workflow is how brands end up sending blunt warnings that damage retailer relationships. The practical split is a weekly gap report that commercial teams act on, and a small escalation list of persistent, deep gaps that legal reviews before anyone contacts a seller.
Content drift triggers price drift
Price arguments often start as content arguments. When a listing shows an old pack size, an outdated specification, or a variant that was discontinued, the price comparison behind it is wrong, and the brand looks like the one discounting. Auditing product facts across channels is therefore part of price governance, not a separate project.
The cheapest reliable routine is a comparison sheet keyed by SKU, with columns for the fields that must match across channels: name, key specifications, pack size, image set, price, and stock. Rows that differ from the master record get flagged, and the flag becomes a task with an owner. Spreadsheets are enough for a modest range; the discipline matters more than the tooling.
Use customer signals as the trigger
Reviews, questions and return reasons surface drift before a dashboard does. A cluster of questions about whether a product includes a certain accessory usually means the listing and the product disagree, and the same discrepancy will distort any price comparison built on that page. Treat these signals as audit triggers rather than as a separate customer-service metric.
None of this makes discounting disappear, and it is not supposed to. What it changes is the quality of the conversation: a team that can say which seller, for how long, at what landed price, and against which pack size is arguing about facts, and facts are the only thing a retailer will accept.
FAQ
Is a listing below the recommended price automatically a violation?
No. It may be a permitted promotion, a clearance, an agreed exception or an unauthorised seller. Attribution requires seller identity, duration and the way the discount is applied.
Why track total price including shipping?
Because the cheapest headline price is often not the cheapest landed cost. Comparing shelf prices alone produces gaps that do not exist for shoppers.
How often should offers be collected?
Daily for key SKUs, weekly for the long tail, and more frequently around major promotional dates. Collecting faster than you can review is wasted effort.
What does product content have to do with price?
Wrong pack sizes or outdated specifications make the price comparison itself wrong, so content audits belong inside price governance.
