# Mapping the retail data landscape end to end
A cotton t-shirt leaves a factory in Bangladesh with a barcode already printed. By the time it's returned by a customer six weeks later, it has generated an EDI shipping notice, a warehouse putaway record, a POS transaction, a loyalty ID match, a clickstream session, and a returns disposition code. Six data types, six systems, and at most retailers, zero people who can trace that single garment across all of them. That gap is the retail data landscape problem in miniature.
This lesson maps the terrain: where retail data actually comes from, how to judge whether it's trustworthy, and which benchmarks tell you if your measurement stack is working.
Retail data is generated at every handoff in the product journey. Group them into five clusters.
1. Supply chain and procurement data. Generated via EDI (Electronic Data Interchange, a decades-old standard for structured business-to-business messaging) documents like the 850 (purchase order), 856 (advance ship notice), and 810 (invoice). Increasingly supplemented by APIAPIApplication Programming Interface: a standardised interface that lets applications communicate and exchange data without knowing each other's internal workings.View full definition → feeds from suppliers. This data tells you what was ordered, what shipped, and when.
2. Warehouse and logistics data. Captured by the WMS (Warehouse Management System), covering putaway, pick paths, inventory location, and cycle counts. Paired with TMS (Transportation Management System) data for shipping and carrier performance.
3. Point-of-sale (POS) and transaction data. The classic retail dataset: SKU, price, quantity, timestamp, store ID, tender type. This is the most mature data source in most retailers, often 20 to 30 years deep in legacy systems.
4. Customer and loyalty data. Loyalty program IDs, CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → (Customer Relationship ManagementCustomer Relationship ManagementCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition →) records, email and app engagement, and increasingly, unified customer profiles built from a CDPCDPA Customer Data Platform unifies customer data from all sources into persistent, actionable profiles that other systems can use.View full definition → (Customer Data PlatformCustomer Data PlatformA Customer Data Platform unifies customer data from all sources into persistent, actionable profiles that other systems can use.View full definition →, software that consolidates customer data from multiple sources into a single profile).
5. Digital and clickstream data. Website and app sessions, product views, cart adds, search queries, and ad exposure. Captured via tools like Google Analytics or Adobe Analytics, and typically the least integrated with in-store data.
A sixth, cross-cutting category: inventory and merchandising master data, the product catalog, attributes, pricing, and promotions that should tie every other dataset together, but frequently doesn't, because SKUs are coded differently across systems.
Most retailers run on a patchwork built over 15 to 20 years: a legacy POS platform, a separately-sourced WMS, a bolted-on e-commerce stack, and a CRMCRMCustomer Relationship Management: software and strategy to manage and analyse customer interactions throughout their lifecycle.View full definition → acquired through M&A. Each has its own product ID scheme, customer ID scheme, and update cadence. The result is what practitioners call "identity fragmentation": the same customer, product, or store exists as different keys in different systems, and nobody owns the mapping.
This is why "omnichannelomnichannelAn integrated approach connecting all customer touchpoints (physical, digital, mobile) into a seamless experience, with shared data and consistent context across channels.View full definition →" analytics is hard in practice, not because the concept is unclear, but because the underlying joins don't exist without heavy investment in master data managementmaster data managementMaster Data Management (MDM) is the discipline of creating and maintaining a single, consistent, trusted version of an organization's core business entities like customers, products, and suppliers.View full definition → (MDMMDMMaster Data Management (MDM) is the discipline of creating and maintaining a single, consistent, trusted version of an organization's core business entities like customers, products, and suppliers.View full definition →), the discipline and tooling for maintaining a single trusted version of core entities like product, customer, and location.
Data qualityData qualityThe degree to which data is fit for purpose: accurate, complete, consistent, timely, valid and unique. Poor quality data undermines analytics, reporting and AI.View full definition → isn't binary. It's measured across dimensions, and retail has sector-specific failure points for each.
Say a mid-size apparel chain has 90% inventory accuracy across 10,000 SKUs. That means roughly 1,000 SKUs show an incorrect on-hand count at any time.
If even a quarter of those errors cause an online "in stock" promise that can't be fulfilled (a "phantom stock" scenario), that's 250 SKUs generating failed promises. If each failed promise costs one lost sale averaging $40, that's a rough $10,000 exposure per inventory snapshot, compounding daily until reconciled. This is a simplified illustrative calculation, not a benchmark, but it shows why inventory accuracy is treated as a governance-level KPIKPIKey Performance Indicator, a measurable value that shows how effectively you're achieving a specific objective, tracked over time against a target.View full definition → (Key Performance IndicatorKey Performance IndicatorKey Performance Indicator, a measurable value that shows how effectively you're achieving a specific objective, tracked over time against a target.View full definition →), not just an operations metric.
Data governanceData governanceData governance is the set of policies, roles, and processes that ensure data is accurate, secure, well-defined, and used responsibly across an organization.View full definition → in retail typically centers on:
Knowledge check
1. What does the t-shirt example (generating an EDI notice, warehouse record, POS transaction, loyalty match, clickstream session, and returns code) primarily illustrate about the retail data landscape?
2. Why is POS (point-of-sale) data typically considered the most mature retail data source?
3. What is the primary purpose of a CDP (Customer Data Platform) in the retail data landscape?
4. Select ALL correct answers about the supply chain and procurement data cluster.
Select all the correct answers.
5. Select ALL correct answers about why mapping the retail data landscape matters.
Select all the correct answers.
Once data is inventoried and reasonably trustworthy, the next question is: what should you actually measure, and against what benchmark?
Analysts often start quality diagnostics with basic completeness and duplicate checks before trusting a KPIKPIKey Performance Indicator, a measurable value that shows how effectively you're achieving a specific objective, tracked over time against a target.View full definition → dashboard:
-- Completeness check: % of SKUs missing a required attribute
SELECT
COUNT(*) AS total_skus,
SUM(CASE WHEN size IS NULL OR color IS NULL THEN 1 ELSE 0 END) AS incomplete_skus,
ROUND(100.0 * SUM(CASE WHEN size IS NULL OR color IS NULL THEN 1 ELSE 0 END) / COUNT(*), 1) AS pct_incomplete
FROM product_master;Running this before building a sell-through dashboard prevents a common failure mode: reporting a KPIKPIKey Performance Indicator, a measurable value that shows how effectively you're achieving a specific objective, tracked over time against a target.View full definition → confidently on top of a broken foundation.
Benchmarks are directional, not universal targets. A grocery chain's inventory turnover target is meaningless applied to a luxury fashion house. Always benchmark within subsector, and treat every externally-cited figure as an estimate unless it comes from your own audited systems.
🎬 [VIDEO: "How Retailers Use Data Analytics" - youtube.com/@McKinsey - a concise overview of how leading retailers connect data sources to decision-making, useful for grounding the concepts in this lesson]