Revenue Leakage: The Coffee Sales You Lose Without Noticing

QUICK ANSWER. Coffee revenue leakage is the gap between what a customer’s machines actually brew and what that customer buys from you. When cups served exceed coffee delivered, the difference is being supplied by someone else, off-contract purchasing, delivery errors or contract drift. Without comparing machine consumption to commercial deliveries, operators discover it late, or never.

Your contracted customer is drinking coffee every day.

The question is: whose coffee?

What is revenue leakage in recurring coffee sales?

The core of the OCS business model is recurring coffee revenue: the machines you place are supposed to be supplied by you. Leakage is what happens when that link quietly breaks — the site keeps brewing, but a growing share of what goes through the machine wasn’t bought from you.

It rarely announces itself. Orders don’t stop; they soften. The account still looks healthy on the revenue report. Which is exactly why it’s dangerous and this is how coffee accounts die silently.

How does the leakage start?

Usually not with a decision to leave you. It starts small: the office runs out and someone grabs supermarket beans “just this once.” A static delivery schedule doesn’t keep up with rising consumption. A delivery or invoicing error goes uncorrected. A site outgrows its contract and nobody re-baselines it.

Each event is trivial. The habit isn’t. Once a customer learns to buy around you, your recurring revenue has a competitor you never see in a tender.

Why don’t operators catch it?

Because the two numbers that would expose it live in different worlds. What the machine actually brews sits in telemetry, if the machine is connected at all. What the customer buys sits in the ERP. Almost no operator systematically compares them per site.

So the deviation is invisible until it shows up where nobody wants to find it: in declining order lines, an awkward account review, or a non-renewal that “came out of nowhere.”

How does telemetry turn sales protection proactive?

By making the comparison continuous. Put cups served next to coffee delivered, per machine, site and customer. Learn what normal looks like for each account. Flag the patterns that statistically don’t match expected baseline behavior — before they harden into habit.

That flag changes the sales conversation. Instead of waiting for orders to decline, the account manager shows up early: “Your consumption is up — your deliveries aren’t keeping pace. Let’s fix the replenishment before you have to solve it yourselves.” Data used to strengthen the customer dialogue, not to police it.

This is one of the clearest cases of why machine data alone isn’t enough — the signal only exists when telemetry meets ERP delivery and purchase data. It’s the connected view CoffeeBrain is being built to give operators, with first pilots planned for Q4 2026.

How big is the problem?

The report walks through it: how to baseline cups-served against coffee-delivered, set deviation thresholds by customer type and turn detection into recovered revenue. As one of nine steps in a full operating model for protecting and growing recurring coffee revenue. Europe’s roughly 4.5 million installed machines (EVA) run on somebody’s coffee; the operators who can see whose have a structural advantage.

Key takeaways

• Leakage = the gap between cups served and coffee purchased from you — filled by someone else’s supply.
• It starts with stockouts, static schedules and uncorrected errors — then becomes a habit.
• It’s invisible because consumption (telemetry) and purchases (ERP) are never compared per site.
• Continuous deviation detection turns sales protection from reactive to proactive — and improves the customer dialogue.
• The full method — baselines, thresholds, follow-up — is Step 4 of From Coffee Machines to Profit Machines.

Your customers are drinking coffee every day. Are they drinking yours?
Request the white paper — From Coffee Machines to Profit Machines: a step-by-step model for a more profitable OCS operation.