Loading

Preparing your content

Article Details
2026-11-15BXT Data Editorial

Reseller origin and discount boards

Reseller origin and discount boards article image

“Which seller is this?” is the question that decides whether a discount alert is worth acting on, and it is the field most price dashboards still do not hold. A listing at 30% below the recommended price can come from an authorised retailer clearing stock, a distributor with an agreed exception, or a reseller nobody has mapped. As of November 15, 2026, monitoring guides converge on the same point: detection is cheap, attribution is the work, and enforcement without attribution damages the relationships that make the channel work.

A discount board is not a seller register

Known factsUnverifiedTo verify
Price compliance monitoring guidance lists the core fields as price, seller name, storefront identifier, discount type, product identifier and listing URLHow seller identity is verified across marketsCoverage by marketplace
idealo aggregates offers from many German shops for the same product, while Cdiscount hosts frequent third-party price changes, so the same SKU can show a wide spread of sellersShare of offers captured per productWhether marketplace sellers are distinguishable
Guides note that an observed price discrepancy is not the same as a confirmed policy violation, because promotions and exceptions are permittedHow brands document permitted promotionsRegional legal limits

Boards are built to answer "what is the lowest price today". Registers are built to answer "who is allowed to sell this, and on what terms". The two share a product identifier and little else. A board without a register produces alerts that nobody can resolve, which is how monitoring projects lose credibility in the second quarter.

The practical fix is to hold seller identity as a first-class field, matched to an authorisation status. Once that column exists, a price gap can be classified within seconds: authorised and within promotion terms, authorised but outside terms, or unauthorised. Each class has a different owner and a different escalation path.

FieldWhy it is neededWhat breaks without it
Seller nameIdentifies the counterpartyAlerts cannot be routed
Storefront IDTracks the same seller across listingsRepeat offenders stay invisible
Authorisation statusSeparates permitted from notEvery gap looks like a violation
Discount mechanismCoupon versus shelf priceThe RRP may not be breached at all

Detect broadly, escalate narrowly

Detection should be broad and boring: collect public offers on a schedule, keep one row per offer per day, and never overwrite yesterday. Escalation should be narrow and slow: a small list of persistent gaps, reviewed against the register before anyone contacts a seller. Mixing the two produces the classic failure where a brand sends blunt warnings to its own best retailer because a coupon looked like a price cut.

Duration separates the two cases more reliably than depth. A deep gap that lasts four hours during a campaign is usually a mechanics problem; a shallow gap that persists for a month is usually a distribution problem, and it compounds because other sellers start matching it. Measuring both, side by side, is what turns a discount board into a decision tool.

Unauthorised sellers need their own queue

Unauthorised sellers behave differently from authorised ones. They rarely respond to commercial pressure, they often appear in clusters, and they frequently share fulfilment or imagery with each other. Treating them as a price problem wastes time; they belong in a separate queue with evidence attached: listing URL, seller identifier, product match, and the date the offer was first seen.

Product facts decide whether the gap is real

Half of the arguments about a price gap are actually arguments about the product. An old pack size, a discontinued variant, or a specification that differs between the marketplace listing and the brand site makes the comparison invalid. That is why a content audit belongs inside price governance: if the SKU does not match, the gap does not exist.

The routine that works is unglamorous. Export live listings from each channel, align them by SKU, and flag rows where the fields that must match actually differ: name, key specifications, pack size, image set, price and stock. Then make the flagged row a task with an owner and a date. Spreadsheets are sufficient at modest scale; the discipline is what carries.

Customer questions surface drift first

Reviews, questions and return reasons usually flag a mismatch before a dashboard does. A run of questions about whether a product includes an accessory is a signal that the listing and the product disagree, and any price comparison built on that listing is already wrong. Reading those signals weekly is cheaper than rebuilding a catalogue quarterly.

  1. Add seller name, storefront identifier and authorisation status to every offer row.
  2. Classify each gap as permitted, outside terms, or unauthorised before escalation.
  3. Keep a separate queue for unauthorised sellers with evidence attached.
  4. Audit product facts on the same SKUs so comparisons stay valid.
  5. Escalate only persistent gaps, and route them through legal before contact.
FieldExampleUse
Seller nameStorefront AIdentifies counterparty
AuthorisationAuthorised / unknownSets the escalation path
MechanismCoupon or shelf priceWhether RRP was breached
First seen12 November 2026Duration evidence

The point of all this is not to end discounting. It is to make the conversation factual: which seller, for how long, at what landed price, against which pack size. Brands that can answer those four questions get a hearing; brands that cannot get ignored.

FAQ

  • Why is seller identity more important than price depth?

    Because depth alone cannot be acted on. The same gap means different things depending on whether the seller is authorised, and the escalation path differs entirely.

  • What counts as a persistent gap?

    One that survives several collection cycles rather than a single promotional window. Duration, not size, is what separates mechanics problems from distribution problems.

  • Why audit product content as part of price monitoring?

    A wrong pack size or discontinued variant invalidates the comparison. If the SKU does not match, the apparent gap may not exist at all.

  • How should unauthorised sellers be handled?

    In a separate queue with evidence: listing URL, seller identifier, product match and first-seen date, reviewed before any contact is made.

Sources