Consolidating reporting across coffee stations
Running more than one station multiplies the reporting problem. The figures only reconcile if every station defines intake, yield and cost the same way — and that is a systems question before it is an accounting one.
- Published
- 6 October 2026
- Reading time
- 6 min
Why consolidated figures disagree
When each station keeps its own records, the totals rarely reconcile — and the reason is almost never arithmetic. It is definitional. One station counts cherry at the gate, another after sorting. One includes transport in cost per kilogram, another does not. One records yield against parchment, another against green.
Consolidation fails at the definition, not at the sum. No amount of spreadsheet care fixes it, because the problem is upstream of the spreadsheet.
The cure is a shared definition, not a shared spreadsheet
The figures reconcile when every station records the same quantities in the same way, from the same system, with the same rules. Then consolidation is aggregation rather than negotiation.
| Measure | Definition that has to be shared |
|---|---|
| Cherry in | Weighed at intake, before any sorting adjustment |
| Green output | Saleable green after processing, on the same moisture basis |
| Yield | Derived from those two figures, per batch |
| Cost per kg | Which costs are included, and where they are attributed |
| Expenses | Captured per station, by category, so they roll up cleanly |
What management actually needs to see
With shared definitions, a consolidated view becomes possible and useful. The questions a manager asks are consistent across stations:
- Cherry intake per station, and how it is tracking against expectation
- Green output and yield per station, and per process
- Purchase cost and cost per kilogram of green
- Expenses by category, per station
- Margin, and where the operation is strongest
Scoping and permission are part of the design
A consolidated view for management and a restricted view for stations are two different things, and both are legitimate. Getting this wrong in either direction causes problems: over-expose and station staff see commercially sensitive figures from other stations; under-expose and management cannot see the operation as a whole.
The workable arrangement is that every record belongs to a station, reports can be scoped to one station or rolled up across all of them, and the scoping is enforced where the data is served rather than where it is displayed.
A restriction that only hides menu items is not a restriction. Station-level scoping should be enforced on the server, on reads, reports and writes.
The period question
Consolidated reporting is only comparable if the period is consistent. A flexible period selector — today, a month, a quarter, a year, all time — combined with a station filter gives the same numbers a manager would otherwise assemble by hand, without the assembly risk.
Why this is a systems problem
Multi-station reporting is often treated as a finance problem, to be solved with a consolidated spreadsheet. It is more accurately a systems problem: the figures reconcile when the stations share a system and a definition, and they do not when they share a template.
Common questions
Yes, and it is enforced server-side. Station roles are restricted to their assigned stations for reads, reports and writes.
See it against your own operation.
Tell us how your stations, paperwork and reporting work today.