Skip to content

Praesenz / L1 Context: ecosystem

C4 level 1. Macro view: Praesenz in its world, its external actors. This diagram evolves slowly (changes a few times per year).

Macro diagram

graph TB subgraph Sources["📦 Product data sources"] OFF[Open Food Facts
free public API] Salsify[Salsify SupplierXM
~60% FR grocery PDM covered] Akeneo[Akeneo PIM
open source FR] Equadis[Equadis
food/cosmetics] GDSN[GS1 GDSN
normalized fiches] end subgraph Standards["🌐 Standards & regulation"] GS1DL[GS1 Digital Link
QR EAN+URL
EU mandate 2027] EPCIS[GS1 EPCIS
traceability] GDPR[GDPR / DSA
opt-in, anonymous] EUDR[EU regulation
digital labeling 2027] end subgraph Retailers["🏪 Host retailers"] Leclerc[E.Leclerc ⭐ lead
Infomil / Abaco] SystemeU[Système U
UTech] ITM[Intermarché
STIME] Centrakor[Centrakor
non-food discount] GrandFrais[Grand Frais
Prosol] Picard[Picard
SAP S/4HANA] Carrefour[Carrefour
Smart PoS] Auchan[Auchan
Oracle Retail] Monoprix[Monoprix
Casino group] Biocoop[Biocoop
ECO-SI] end subgraph InStore["🛒 Real-time in-store truth"] ESL[ESL broadcast
VusionGroup / Hanshow
real-time pricing] BORetailer[Retailer BO
nightly CSV export] end subgraph Praesenz["🌸 Praesenz"] Kiosk[Léa kiosk
state machine
4 QR per moment] Cloud[Praesenz Cloud
knowledge layer
orchestrator] end subgraph Customer["📱 End customer"] Smartphone[Customer smartphone
WhatsApp Business
scans QR] end subgraph Brands["🥫 Brands"] Brands1[Danone, Coca,
Lactalis, L'Oréal,
etc.] end Brands1 -->|fiche syndication| Salsify Brands1 -->|syndication| Equadis Brands1 -->|fiches via GDSN| GDSN GDSN -->|GDSN partners| Salsify GDSN -->|GDSN partners| Equadis OFF -->|REST API · MVP| Cloud Salsify -->|REST API · V2| Cloud Akeneo -->|REST API · V2| Cloud Equadis -->|GS1 GDSN · V3| Cloud ESL -->|radio broadcast
RF/BLE/NFC| Kiosk BORetailer -.->|nightly CSV
Abaco/SAP/Oracle path| Cloud Leclerc -.-> Kiosk SystemeU -.-> Kiosk ITM -.-> Kiosk Centrakor -.-> Kiosk GrandFrais -.-> Kiosk Picard -.-> Kiosk Carrefour -.-> Kiosk Auchan -.-> Kiosk Monoprix -.-> Kiosk Biocoop -.-> Kiosk Kiosk <-->|triggers| Smartphone Smartphone -->|QR scan| Kiosk Smartphone <-->|conversation| Cloud Kiosk <-->|orchestration| Cloud GS1DL -.->|encodes EAN+URL| Kiosk EPCIS -.->|traceability| Cloud GDPR -.->|constrains| Praesenz EUDR -.->|2027 opportunity| Praesenz classDef hero fill:#166534,stroke:#22c55e,stroke-width:3px,color:#fff classDef key fill:#0f766e,stroke:#5eead4,stroke-width:2px,color:#fff classDef accent fill:#a16207,stroke:#fbbf24,stroke-width:2px,color:#fff class Kiosk,Cloud hero class Salsify,GS1DL key class Leclerc accent

Reading the diagram

Main flows

  1. Brands → PIM → Praesenz: the preferred path for product data. A single Salsify integration = ~60% French grocery PDM covered, no retailer SI integration needed.
  2. Open Food Facts → Praesenz: MVP foundation, free, independent.
  3. ESL broadcast → Kiosk: real-time in-store price truth, no retailer BO integration.
  4. Kiosk ↔ Smartphone: QR scan → WhatsApp draft → persisted conversation.
  5. Retailer BO → Praesenz (dashed): optional integration path, V2/V3 once the pilot allows.

Why Praesenz is agnostic of the retailer SI by design

The solid arrows do not depend on any retailer BO integration. The dashed arrows to retailer SIs (Abaco, Picard SAP, Auchan Oracle) are optional and come in V2/V3.

This design comes from ADR 005 (PIM-native architecture).

Go-to-market note — because the kiosk is SI-agnostic, it can be proposed across a portfolio of enseignes (ADR-012): E.Leclerc via Infomil is the lead partnership channel, alongside Système U (UTech), Intermarché (STIME), Centrakor and Grand Frais, with Picard kept as the clean SAP track.

The end customer never sees the retailer SI

From the customer's point of view: 1. They walk by → the kiosk wakes up 2. They see 4 QR codes → they scan one 3. WhatsApp opens with a draft → they send 4. Léa replies with the daily menu

At no point does the customer depend on the availability of the Abaco/SAP/Oracle SI. Maximum robustness.

Diagram source

The diagram above is edited in this same markdown file (mermaid block). Any change is: - Diffable in git - Re-rendable by Gitea, MkDocs, native GitHub - Versioned like code

To clarify

  • Salsify connector: exact protocol and access level (read-only, brand scope vs distributor scope). To validate via Salsify France commercial call.
  • ESL VusionGroup connector: status of the "VusionLink" API for third parties, partner access TBC.
  • GS1 France: Praesenz membership conditions as a Digital Link ecosystem player. To investigate.