Two aggregators, 78 stores, reconciled to the order
Weekly exports from two third-party aggregators became order-level reporting for every store, and a check on whether the payout matched the sales the aggregator claimed.
Client work is anonymised. One client, a 78-store QSR group in South Africa.
Illustrative. Figures inside the visual are not client figures.
The problem
Two third-party aggregators sent weekly report exports. Nobody could say, per order, what was late, missed or misreported. Nobody could say whether the money that arrived matched the sales the aggregator said it had made. The exports were complete enough to file and too coarse to question.
What we built
An ingestion pipeline that collects both aggregators' exports each week, validates that they are complete, hashes and stages them, and loads order-level data into a portal in the client's own Google Cloud project. Reconciliation compares aggregator-reported sales against what was actually paid, and flags the gaps.
What changed
Order-level visibility for every store, every week, and a recoverable number where the payout fell short of the claim. Recoverable is the accurate word: the system finds and evidences the gap, and recovery is a conversation with the aggregator.
How it is governed
The pipeline reads and reports. It does not raise a claim, contact an aggregator, or adjust a figure. Every ingest is hashed and logged, so a number in the portal can be traced back to the export it came from and the week it arrived.
What this takes
Scoped per system. What sets the length is how the aggregators export and how far back the history goes.