Skip to main content
RetailData
Intermarché

Before data can drive every aisle, warehouse and recommendation, someone has to build the foundations

Before

15+ initiatives

with no shared architecture or governance: a risk of widespread technical debt

After

15+

data initiatives delivered

15+

data initiatives delivered

3

domains: ML/AI, BI, streaming

Multi-year

continuous engagement

Intermarché, France's third-largest food retail network, launches an ambitious data program: reduce product stockouts, tailor store assortments, know each customer better and accelerate its e-commerce. A dedicated Data Factory is set up to run the initiatives in parallel: ML, BI reporting, real-time streaming. But building fast without a solid architecture means piling up invisible debt that will eventually bring production to a halt.

SITUATION BEFORE

Operational baseline
A fledgling Data Factory running more than 15 initiatives in parallel (ML/AI, BI, e-commerce streaming) with no shared reference architecture, each team inventing its own foundations.
Teams affected
All the Data Factory teams and the business teams consuming their output (supply chain, stores, e-commerce): a risk of widespread technical debt eventually blocking production.
Hidden costs
Without a reference architecture, technical debt builds up silently across 15+ simultaneous initiatives. What was meant to speed things up would have ended up slowing them down.
Why it was not solved earlier.
The Data Factory was created to move fast: the pressure to deliver ML and BI use cases left little room for cross-cutting architecture work upfront.

THE STORY

Intermarché, France’s third-largest food retail network, has long known that the retail battle is won in the details: the right product, in the right place, at the right time. But running thousands of stores, anticipating stockouts, personalizing recommendations and accelerating e-commerce within the same strategic sequence takes far more than Excel spreadsheets and gut feeling from the field. It takes data: structured, governed, put to work.

To deliver on this ambition, Intermarché creates a Data Factory: a unit dedicated to industrializing the value extracted from data, able to run several initiatives in parallel. But a Data Factory without a reference architecture is a construction site where every team invents its own foundations. Technical debt builds up silently, and what was meant to speed things up ends up slowing them down.

Nobori Partners joins the program as its first data architect, to get things back on course and enable the real-time use cases.

The work starts upstream of the code, in business workshops. For each initiative, the task is to understand the business process involved, identify the available data, assess its maturity and choose the right patterns: how to ingest, how to transform, how to deliver. This initial scoping avoids bad surprises during development and aligns the data and business teams before the first pipeline is written.

On the ML and AI front, three structural use cases are covered: a product recommendation engine, a tool comparing performance across stores, and customer insight models. For each one, the architecture covers the feature pipelines, the training pipelines on Databricks and Spark, and the delivery interfaces to the consuming applications through Azure Functions.

BI reporting is the second major domain. Supply chain teams need to see stock levels, stockout risks and logistics flows in real time. Store managers want their own dashboards: clean, consistent, actionable. Nobori Partners scopes the reporting needs with the business teams and defines the architecture of the data flows feeding the Power BI dashboards.

The third domain is real-time streaming for e-commerce. Here, latency matters: an online order, an updated stock level, a recommendation displayed within seconds. The architecture relies on Kafka, Solace and Boomi iPaaS to orchestrate event streams and make sure data moves at the speed customers expect.

Across all of this, Nobori Partners structures the data architect function itself within the Data Factory: architecture review templates, a pattern library by type of project, a standardized onboarding process. When a new use case comes in, the team no longer improvises; it follows a proven path.

Over the years, more than fifteen initiatives have gone from idea to production within this framework. Recommendations, logistics management, customer insight, e-commerce streaming: each one benefits from a well-designed architecture, documented governance and a consistent technical foundation that makes evolution and maintenance easier.

OUR APPROACH

5 steps to get there

1

Architecture scoping and business study

For each initiative: analysis of the business processes involved, mapping of the data objects, assessment of the maturity of the available sources, and selection of the ingestion, integration and delivery patterns suited to the use case. The outcome: an architecture sheet shared between the Data Factory and the business teams before any development starts.

Azure DatalakeDatabricks
2

Modeling and governance for each project

Working with project teams on data modeling (schemas, relationships, granularity), writing the data dictionary, tracing data lineage and defining quality patterns. Every domain (ML/AI, BI, streaming) follows the same conventions, which keeps pipelines readable and maintainable over time.

SparkPower BIBoomi iPaaS
3

ML & AI initiatives

Architecture and governance of the machine learning use cases: product recommendation engine, performance comparison across stores, and deeper customer insight. For each model put into production: definition of the features, the training data flows and the delivery interfaces to the business applications.

DatabricksSparkAzure DatalakeAzure Functions
4

Reporting & operational management

Design of supply chain dashboards to monitor stockouts and logistics flows, and of store dashboards for store managers. Scoping of reporting needs with the business teams to ensure a consistent reading of performance at every level of the organization.

Power BIAzure DatalakeDatabricks
5

Industrializing the data architect function

Structuring the data architect role within the Data Factory: architecture review templates, a pattern library by type of initiative, an onboarding process for new projects. The goal: enable the Data Factory to take on new use cases without starting from scratch every time.

SolaceKafkaBoomi iPaaSAzure Functions

RESULTS

The measurable impact

15+data initiatives delivered
3domains: ML/AI, BI, streaming
Multi-yearcontinuous engagement

More than 15 initiatives delivered to production across three complementary domains: ML recommendations and customer insight, supply chain monitoring and store dashboards, real-time streaming for e-commerce, all built on a shared architecture and lasting governance.

Book a discovery call