How to Create a Marketplace Seller Map
Store names displayed on a marketplace do not always reveal the underlying seller structure. The same business may operate under several store names, or a seller may use different identities…
What’s in this article?
Store names displayed on a marketplace do not always reveal the underlying seller structure. The same business may operate under several store names, or a seller may use different identities across channels.
A seller map treats stores as entities whose relationships can be analysed, rather than as isolated records.
Create seller entities
For each store, record the platform, store name, seller ID, registered business name if available, and profile details in structured fields.
Compare Product Portfolio
Stores selling the same combinations of products may be connected. Portfolio similarity alone is not conclusive evidence, but it is a strong signal for further investigation.
Examine pricing behaviour
Simultaneous price changes or prices consistently moving within the same range can be analysed to identify seller clusters.
Digital footprints
- Website
- Social media account
- Contact information
- Domain
- Store description
- Brand portfolio
Identity Resolution
Name similarity alone is not enough to match identities. Asserting a definite relationship without several supporting signals for the same entity can lead to false positives.
Graph model
Entities such as sellers, products, brands, domains and social media accounts can be modelled as nodes, with their relationships represented as edges.
Risk score
Multiple stores, recurring infringements, unusual prices or shared digital footprints can contribute to the risk score.
How do you turn data into intelligence?
Individual screenshots or daily snapshots are not enough. Link seller entities, product portfolio comparisons and pricing behaviour over time within the same data model. Wherever possible, store each observation in structured fields for platform, seller, product, listing, price, stock status and observation time. This makes it possible to trace which entity a change started with and to analyse behaviour and trends rather than just checking a moment in time.
Data quality is a critical part of an intelligence system. Incorrect product matches, changing store names, promotional prices recorded as regular prices or missing seller details can produce misleading results. Record confidence levels for product matching and seller identity resolution, and send low-confidence matches to a review queue rather than treating them as definitive automatic conclusions. Feeding expert-confirmed or rejected records back into the system can improve subsequent matches.
Operational monitoring should focus on the verified risk rate, false positives, new and recurring sellers, the duration of price deviations, stock anomalies and resolution times for open cases, rather than raw alert counts. A single signal may not seem critical, but a price anomaly, multiple stores and recurring brand risk associated with the same seller can justify higher priority. This turns marketplace monitoring from data collection into decision support that explains seller, channel and brand behaviour.
Marketplace intelligence checklist
- Are sellers and listings stored as separate entities?
- Does product matching include a confidence score?
- Are different price types distinguished?
- Are stock changes recorded as a time series?
- Are new and recurring sellers monitored separately?
- Is feedback on false positives fed back into the system?
- Does the system identify risks and priorities for action rather than just issue alerts?
The seller–listing–product relationship model
Reliable analysis requires separate seller, listing and product records. A seller may publish several listings, different sellers may list the same product, and a store name may change over time. Link seller entities, product portfolio comparisons and pricing behaviour using stable keys such as seller IDs, listing IDs, barcodes or model codes wherever possible, rather than relying on displayed text alone. This reduces analytical errors caused by incorrect product or seller matches.
Evidence trail and time dimension
Marketplace data is valuable not just because it shows the current situation, but because it can explain when and how a change occurred. For each critical observation, store its time, platform, seller, listing, product, displayed price and stock status, plus a source URL or technical record where possible. A price anomaly, a new seller’s arrival or a stock change can then be checked retrospectively. Time series, rather than single-day snapshots, help distinguish short promotions from recurring seller behaviour or lasting channel changes.
From risk to action
An intelligence system should not automatically classify every anomaly as an infringement or a critical case. Assess data confidence, recurrence, commercial impact, seller history and other independent signals together. Low-confidence records can go to data verification, medium-risk records to expert review, and high-confidence, high-impact cases to the relevant brand, e-commerce or channel management team. This distinction reduces alert fatigue and helps teams focus on events that require action.
- Keep seller IDs separate from store names
- Do not confuse listing IDs with product identities
- Record a confidence level for product matching
- Make observation time a required field
- Preserve the evidence URL or source record
- Measure recurrence and commercial impact, not just individual alerts
- Feed expert verification back into risk scoring
The B10 Digital Agency approach to marketplace intelligence
B10 Digital Agency treats marketplace data as more than price tracking: it forms a measurable channel intelligence system linking sellers, listings, products, stock, reviews and brand risks.
- Marketplace Intelligence & E-Commerce Monitoring
- Brand Protection & Monitoring
- Data Analytics & Social Listening
- E-Commerce Management & Operations
Frequently Asked Questions
Are two stores that sell the same products the same seller?
No. Portfolio similarity is only a signal for further investigation.
What is a seller map used for?
It reveals seller networks and recurring behaviour, rather than treating stores in isolation.
Is a graph database required?
No. A relational data model may also be sufficient for small datasets.
How can false positives in seller matching be reduced?
Use several independent signals and, where necessary, expert verification.
Turn marketplace data into decision signals
Explore the B10 Digital Agency approach to marketplace intelligence to turn seller, price, stock, review and brand-risk data into measurable channel insights.
Sources and related documents
These documents provide references for the methods and rules discussed in this article.
