Retail & E-commerce

Personalise. Convert. Retain.

Margins under pressure, channels that do not talk to each other, and a catalogue too large to maintain by hand. We industrialise demand forecasting, catalogue enrichment and personalisation, with retailers, marketplaces and connected commerce players.

Sell right, stock right, hold the catalogue.

Three subjects come up in every conversation with a commerce or supply executive. They drive everything else: what gets promoted, what is actually in stock, and what you are able to describe.

01

Forecasting demand, not the average

Models built on history, seasonality, weather and trade activity, at store and SKU level. A stockout and an overstock share one cause: a forecast computed too high in the product hierarchy.

02

Holding a catalogue too large for manual work

Generating and translating descriptions, extracting attributes from supplier sheets, spotting duplicates. The rule that matters is the review rule: anything published unread eventually shows.

03

Personalising without becoming intrusive

Recommendations built on in-session behaviour rather than an accumulated profile. It works better on anonymous traffic, and it reduces the volume of personal data you have to justify.

Solutions

In-session personalisation

(01)

Journeys fragmented across channels, and recommendations so generic they no longer engage anyone.

Recommendations built on in-session behaviour rather than an accumulated profile, which also works on anonymous traffic.

Conversational commerce

(02)

Scripted assistants that frustrate, customer service disconnected from the purchase, and drop-off at checkout.

An assistant wired into your catalogue and CRM, stating what it is, citing the product page it refers to, and handing over to an adviser.

Forecasting and replenishment

(03)

Frequent stockouts, costly overstock, and a forecast computed too high in the product hierarchy.

Forecasting at store and SKU level, factoring in seasonality and trade activity, with replenishment proposed warehouse by warehouse.

Catalogue enrichment

(04)

Incomplete descriptions, expensive translation, and missing attributes across a large share of the range.

Content generation and translation, attribute extraction from supplier sheets, with a human review rate that you set.

Price steering

(05)

Competition moving daily, margins under pressure, and elasticity poorly understood by category.

A pricing engine that respects your margin floors and trade commitments, and measures the real effect before generalising.

Fraud and chargebacks

(06)

Payment and promotion abuse, and a hard trade-off between security and a fluid journey.

Multi-signal scoring and step-up authentication triggered only where it is warranted, with false positives measured.

Compliance & standards

DSA

Digital Services Act, EU 2022/2065

AI Act

Conversational & recommendation agents

GDPR

Cookies, consent, profiling

CSRD

Value chain sustainability reporting

PCI-DSS

Payment security

RGAA

Digital accessibility

Eco-design

AGEC & Climate law

Stack & partners

Mistral AI

Sovereign European LLM

Anthropic Claude

Modèles frontière via gateway

Vector DB

Pinecone · Weaviate · pgvector

Commerce platforms

Shopify · commercetools · Magento · Salesforce

Data platform

Snowflake · Databricks · BigQuery

CDP & marketing

Segment · Braze · Klaviyo

Our ideas

From data to smart data: actionable insights at the point of collection

Smart data delivers actionable insights right at the point of collection: definition, benefits, edge computing and embedded AI, use cases and adoption in 2026.

Read the article
Shoppers in store, seen from the mezzanine
TALK TO AN EXPERT

Let's talk about your retail roadmap

An hour to test your forecasting, catalogue and personalisation challenges against what we have already put into production elsewhere.

By submitting this form, you agree to our privacy policy.

Frequently asked questions

Through the interfaces your platform already exposes, with no migration and without replacing your product management, your CRM or your customer data tool. The analysis layer sits alongside and reads what it needs. What takes time is almost never the connection: it is the state of the catalogue. Missing attributes, duplicates, reference data that diverges between the site and the store, that work determines the quality of everything downstream, and it is worth looking at before picking a model.

Three things. Saying it is a machine, which the European AI regulation has required since 2 August 2025 for systems interacting with people. Letting customers reach a human without an obstacle course. And keeping a record of what was told to the customer, because an assistant that describes a product badly commits the seller exactly as an adviser would. A conversational agent falls under limited risk, not high risk: the obligations are about transparency, not certification.

It depends on your starting point, and we would rather say so than publish a conversion range that supposedly holds for everyone. The method matters more than the promise: measure on a share of traffic against a control group, over a period covering at least one full purchase cycle, and look at margin rather than conversion alone. Personalisation that lifts conversion by pushing the lowest-margin items improves a dashboard and degrades a P&L.

Framing takes 2 to 6 weeks depending on scope and the number of systems to connect. A first version tested on one category or funnel follows in 4 to 10 weeks, depending on the state of your catalogue, which is almost always the deciding factor. Extending across the whole catalogue, including team training, runs to 3 to 6 months. These ranges are the ones we apply everywhere, and each comes with what makes it vary.

In batches, with validation rules written before the first generation: length, tone, prohibited vocabulary, mandatory statements by category. Generated content is checked automatically against those rules, then a sample goes to human review, at a proportion you set. Throughput depends on your volumes and your inference budget, and we measure it on a pilot batch before quoting a rate, a figure published without your catalogue behind it means nothing.

Wherever you decide, and that sorting comes before the hosting choice. An open-weights model operated in sovereign cloud handles the majority of cases, from product copy to recommendation. An external call remains possible for uses that warrant it, under a processing agreement with guaranteed data residency. The simple rule: anything that identifies a customer does not leave your perimeter by default, and each exception is decided rather than discovered.