Datum accelerator

Datum for retail.

Datum accelerates the deployment of the data operating model in retail — with a customer Golden Record, a product model aligned with GS1/GTIN and multi-brand federated governance ready for distributed operations.

Key capabilities
Golden Record del cliente
Modelo de producto GS1/GTIN
KPIs de ventas certificados
Gobierno federado multi-marca
Databricks · Snowflake · Confluent
The problem

Retail data is abundant. The problem is that it is not connected or coherent.

01
Omnichannel
The customer exists in five different systems

Physical store, ecommerce, app, loyalty programme, call centre — every channel produces its own version of the customer. Without a common data model, a single customer view is a goal that is never achieved.

02
Product
Product catalogue misaligned across channels and brands

Each channel keeps its own product sheet, with slightly different attributes, images and descriptions. Without a common product model aligned with sector standards (GS1/GTIN), cross-channel reconciliation is a permanent manual effort.

03
Reporting
Sales KPIs that don't match across areas

Operations, finance and marketing produce different versions of the same sales metrics. The committee debate is about which number is right, not which decision to make.

04
Operations
Stock, demand and supply chain disconnected

Stockouts, excess inventory and forecasting errors originate from demand, stock and supplier data that is neither integrated nor governed. The cost hits margin directly.

05
Expansion
Scale by brand or geography without rebuilding the platform

Every new brand or market multiplies complexity if there is no federated data governance model. The platform grows in silos and operating cost rises out of control.

Retail data architecture

Four layers. One source of truth on customer, product and channel.

DATUM in retail isn't a BI project nor an ERP refactor. It's a data model that separates operational sources, governed data and consumption, with the sector's Common Data — Customer, GS1 Product, Order, Assortment — modeled from day one.

CATALOGSBusiness cataloguesBrand · Category · Channel · Market · Point of saleCDMRetail Common DataCustomer (Golden Record) · Product (GS1/GTIN) · Order · Stock · Promotion · PricingGOVERNANCEGovernance and qualityDomain ownership · Golden Record quality · KPI to source lineage · GDPR/LSSI rulesPRODUCTSData productsCustomer 360 view · Store-level assortment · Margin per product · Demand forecast · Activatable audience

Notes on the architecture

01
Retail Common Data — GS1 as a first-class citizen

The core retail entities (customer, product, order, assortment, promotion) are modeled from day one aligned with GS1/GTIN. There's no intermediate translation between a generic CDM and retail semantics. Integration with marketplaces, ECR/EDI and data pools is direct.

02
Federated Golden Record, not forcibly centralized

Customer data lives in e-commerce, ERP, loyalty, CRM and POS. DATUM builds the Golden Record without migrating anything: it identifies, links and certifies the reference version while respecting operational sources. Marketing, loyalty and customer service work on the same data without forcing artificial syncs.

03
Multi-brand and multi-market by design

Governance is federated by brand, country or commercial format. Each unit keeps its operational autonomy but shares the common model. Corporate consolidation stops depending on reconciliation spreadsheets.

Regulatory framework

What DATUM covers, what it partially aligns with and what stays out of scope.

An honest table. Retail handles sensitive personal data (GDPR/LSSI), regulated product information (labelling, traceability), financial reporting (IFRS 15) and emerging sustainability obligations (EUDR). We say it in green, amber and grey.

Full coverage

DATUM provides governed data and the necessary traceability without external components.

GDPR
Customer data processing
Ownership and traceability of personal data in the Golden Record. Catalogue with legal bases, consents, purposes and retention periods by domain. Lineage to source system.
GS1/GTIN
Product identification and modeling
Product modeled from origin aligned with GS1/GTIN. Certified attributes, hierarchy and lifecycle. Native integration with data pools and marketplaces.
IFRS 15
Revenue recognition
Order-to-invoice traceability, returns and promotions control, separation of performance obligations. Certified, reconcilable revenue KPI.

Partial coverage

DATUM provides the governed data foundation; operational compliance depends on client's systems and processes.

LSSI-CE
E-commerce and commercial communications
We cover marketing consent traceability and the customer base. Commercial conduct (emails, banners, call centre) is the responsibility of the marketing automation system.
EUDR
EU Deforestation Regulation
We provide governed product and supplier data with traceability. Due diligence declaration in EUDR-IS and physical supply chain control remain the client's responsibility.
PSD2
Payments and strong customer authentication
We cover customer and transaction data. SCA authentication and payment rails depend on the integrated PSP.

Out of scope

Functions DATUM doesn't perform that should be explicitly stated to avoid scope misunderstandings.

Physical labelling
In-store product labelling
DATUM provides the governed product information; printing, shelf labelling and physical compliance with obligations (allergens, origin, CE marking) is executed by labelling systems and store processes.
Dynamic pricing
Pricing and promotions engine
DATUM provides historical data, elasticity and context. The pricing engine and promotional execution live in specialized tools (Revionics, Pricer, in-house solutions).
Retail regulatory pyramid — what each layer covers
Financial reportingIFRS 15 · IFRS 16 · Annual accountsDatumCertified revenue and lease datasets on CDM · order→invoice reconciliationPersonal data and commerceGDPR · LSSI-CE · PSD2DatumGolden Record with legal bases · purposes catalogue · consent traceabilityProduct and traceabilityGS1/GTIN · EUDR · LabellingDatumGS1 product model · certified attributes · origin→shelf lineageStore operationsECR · EDI · Store systemsDatumGoverned stock · demand forecast · point-of-sale assortment
Semantic standard — GS1

GS1 as the common vocabulary of global retail.

Retail is global by nature: the same product crosses countries, brands, channels and marketplaces. GS1 (with GTIN, GLN, GPC) is the standard that allows unequivocal identification of product, location and category. DATUM activates it from day one.

Why GS1 is the foundation, not an annex

01
Common sector vocabulary

Defines standardized entities — Product, Location, Category, Lot, Asset, Document — recognized by any supplier, marketplace or regulator. No translations, no parallel glossaries.

02
Unequivocal end-to-end identification

GTIN for product, GLN for location, SSCC for shipment, GPC for category. Manufacturer → distributor → store → end customer traceability is native and verifiable.

03
Native integration with data pools and marketplaces

AECOC Data, GS1 GDSN, Amazon, Carrefour Marketplace, Mirakl. Catalogue synchronization and attribute quality require no intermediate translation.

04
Accelerated regulatory compliance

European frameworks (EUDR, Digital Product Passport, origin labelling) are built on GS1. Starting with GS1 is starting ready for what's coming.

Functional areas covered by the model

The core areas of the retail model that DATUM activates from day one. Each with its canonical model, certified attributes and connection to operational systems.

GS1 / GTINCommon DataRetail ModelPRODUCTProductPARTYPartyLOCATIONLocationORDEROrderINVENTORYInventoryPROMOTIONPromotion
PRODUCT
Product
GTIN, commercial hierarchy, GPC attributes, lifecycle, assortment.
PARTY
Party
Customer (Golden Record), supplier, distributor, carrier.
LOCATION
Location
Store GLN, warehouse, logistics centre, delivery point.
ORDER
Order
Customer order, supplier order, return, invoice, credit note.
INVENTORY
Inventory
Stock by GLN, lot, expiry date, valuation, movements.
PROMOTION
Promotion
Promotion, discount, coupon, loyalty, commercial mechanism.
DATUM doesn't force migration to GS1 overnight. The Retail Common Data progressively maps existing sources against GS1, keeping the operation alive. Adoption is by domain, not big-bang.
What Datum activates

Data capabilities designed for the retail context.

01
Single customer model (Golden Record)

Customer identity architecture that unifies every touchpoint into a governed canonical entity, with merge rules, quality and change traceability.

02
Product model aligned with GS1

Canonical product entity with full lifecycle (launch, variant, promotion, end of life) and attributes aligned with GS1/GTIN to enable interoperability with suppliers, marketplaces and logistics partners.

03
Certified business KPIs

Definition, ownership and lineage of critical retail indicators: sales, average ticket, conversion, stock rotation, margin per channel — with one single version for the whole organisation.

04
Multi-brand federated governance

Corporate data model with autonomy per brand or domain. Each unit operates its own data but shares semantics, policies and corporate standards.

05
DataOps for commercial operations

Automation of ingestion, quality and publication circuits for sales, stock and demand data to reduce operational latency and eliminate critical manual processes.

Retail experience

Federated governance and DATUM in a restaurant group.

Over 60% operational savings by modernising the data platform of an international restaurant group
Federated governance and Databricks + Confluent Cloud + Snowflake architecture across multiple brands and geographies
Results with Datum · unattributed ranges
reduction in data teams while maintaining coverage
performance improvement in governed pipelines
for the first data capability in production
Another sector?
Every sector has its own regulatory and semantic context. Explore the other industry solutions.
Next step

Accelerate Datum in your retail group.

An initial assessment identifies the starting point, pilot domain and deployment model that fit best.