Retail and consumer goods

One designed process. 294 ways of running it.

In a consumer goods order to invoice engagement, RE-ViVE reconstructed 2.47 million order lines and found the process running 294 distinct ways. None of those variants had been designed. All of them were being executed, every day, at volume.

294execution variants in one process
9.69Mdays of rework
2.47Morder lines reconstructed
Read-onlyno changes to source systems

Figures from a consumer goods order to invoice engagement. Read the case study.

1Why

Retail runs on volume, and volume hides variation.

At a few thousand orders a month you can feel the exceptions. At two and a half million order lines they disappear into the average, and the average looks fine.

The exception quietly becomes the process

A workaround invented once for a difficult customer gets reused, taught to the next hire, and within two years is standard practice in one region. Nothing was ever decided. The process simply drifted, and no document records it.

SAPOracleSalesforceServiceNowQADJD EdwardsAS400

Every channel and region adds paths

Wholesale, retail, e-commerce and marketplace all run the same order to invoice on paper. In execution each has its own credit rules, pricing exceptions, delivery patterns and billing corrections, multiplying the number of live paths.

Manual change loops never appear as cost

An order edited three times before it invoices is still one order in every report. The three edits are the cost, and they are only visible when the order is reconstructed as a sequence rather than a row.

One process. 294 ways of running it.

Execution variants by volume

294 distinct paths, of which one was designed

294 variants across 2.47M order lines, carrying 9.69M days of rework. Every one of them was being executed; none of them was designed.

Headline figures are from a consumer goods order to invoice engagement. The distribution shape is illustrative; your own variant curve is measured from your data.

2Where

Where it shows up in retail and consumer goods

Order to invoice is usually where the variants are densest. The same reconstruction applies right through the supply and trade cycle.

Trade and order operations

Where margin, working capital and the customer promise are decided.

  • Order to invoice
  • Order to cash
  • Customer returns and refunds
  • Promotion campaign execution
  • Inventory replenishment
  • Shelf replenishment and planogram compliance
  • Warehouse management, inbound and outbound
  • Product quality control and recall

Supply and enterprise processes

Where cost, supply reliability and compliance are decided.

  • Supplier procurement and vendor management
  • Procure to pay
  • Supply chain and logistics management
  • Risk and compliance
  • Customer service and support
  • Human resources management
  • IT operations and ontology mapping

3How

How RE-ViVE gets there

No new instrumentation, no data warehouse programme and no curation layer to build first. Four steps, from access to a live view.

Point at data you already keep

Status histories, workflow logs and audit trails in the systems you already run. If a record carries a case identifier, an activity and a timestamp, it is enough.

Reconstruct the case, not the table

Records from separate systems are linked back into one case — a single order followed across everything that touched it, in the order it happened.

Compare designed against actual

The process as it was intended, set against every path it really ran. Variants, rework loops, waiting time and team differences are counted rather than estimated.

Keep watching

The view refreshes as the data does, so drift shows up as it happens instead of surfacing in the next review cycle.

4What

What becomes visible

Not a score or a maturity rating. The actual behaviour of your order process, in units your commercial and supply chain teams already argue about.

Variant sprawl

How many distinct paths one designed process actually runs, and which handful of them carry most of the delay and cost.

Manual change loops

Orders edited, re-priced, re-approved or re-issued before they invoiced — separated from orders that ran once.

Delayed and rejected value

The revenue sitting in orders that stalled, were rejected downstream, or invoiced later than they should have.

Collection gap

Where the distance between shipping the goods and collecting the cash is created, step by step.

Channel and region variation

The same order type compared across channels and markets, rather than averaged into one number that describes none of them.

Promotion execution drift

How campaigns actually ran against how they were planned — pricing exceptions, late activations and manual corrections.

Evidence · Consumer goods · Order to invoice

Why does one designed process run 294 different ways?

Variant sprawl · manual change loops · delayed and rejected value · collection gap

Read the case study
294execution variants
9.69Mrework days
2.47Morder lines

Start with one process and one channel

Pick the flow where variants cost you the most in margin or in cash. We will tell you, before any commitment, whether the data you already hold can reconstruct it.