REWE Digital is putting a process layer around work that no single German merchandising or logistics application owns end to end. Orders, invoices and logistics handoffs still start in one system, wait on another, involve suppliers or partners, and finish in a warehouse, store or accounting step. According to Retail Optimiser, Camunda is being expanded as the orchestration layer that coordinates those crossings of microservices, internal applications and external parties.
The immediate problem is operational visibility. When a flow stalls, the gap is often a missing shared view of process state rather than a missing model. BPMN is used so business and IT can look at the same production process. REWE Digital has described Camunda’s open, modular architecture as a way to attach existing microservices and change workflows without stopping operations.
That choice predates the current wave of agent talk. The group started with Camunda in 2024 on warehouse-location evaluation. The present move is into broader supplier-facing and logistics processes, where traceability and compliance weigh more heavily. Parts of REWE’s infrastructure sit under strict regulatory and operational rules; a defined process with an event history is easier to govern than an opaque chain of API calls.
Camunda positions the same platform to run conventional systems, automated steps, people and AI agents in one workflow. REWE Digital plans to use that layer later for AI applications, including model choice, governance and audit trails. Sequencing matters: a model can stay probabilistic while permissions, escalations, system-of-record updates and human approval stay explicit. An agent may classify an exception or suggest a next step; it is not asked to invent the retailer’s state machine on the fly.
The trade-off is concentration. Process models, connectors and the teams that maintain them become operational dependencies once more cross-system state sits in one layer. That is not the same as replacing every backend with a single suite, but it can still affect many workflows at once.
REWE has not published before-and-after figures for cycle time, exception recovery or cost. The decision on the table is architectural: a visible, auditable process layer that can say what stage the business is in before any model is allowed to decide what happens next.