Mapping a vending estate to its legal establishments
A French vending operator had to tie every machine in the field to the establishment that legally hosts it, because tax reporting and client invoicing are both done per site rather than per company. The mapping existed only in the memory of the people who installed the machines.
Industry: Retail & Consumer
The challenge
Site names in the operator's own records rarely matched the official register: the same client appeared under a trading name in one row, a building name in another, and an old address in a third. Matching them by hand was slow enough that new installs went unmapped for weeks.
An unmapped machine is revenue that cannot be invoiced to the site that earned it. It is also a reporting gap, because the filing is written per establishment, so a single unmapped machine turns a routine submission into an investigation of which sites are missing and why.
The register itself moves. Establishments close, merge, and change address without telling anyone downstream, so a mapping that was correct when it was made quietly becomes wrong. Nothing in the operator's process would have detected that, because the link had been treated as a fact rather than as a claim with a date on it.
What we built
- 01Establishment resolution service
- 02Review queue for weak matches
- 03Change tracking against the register
- 04Invoicing and reporting exports
That is the outline. The PDF walks the same build through in detail: the screens, the data moving between them, and how each piece was put together.
