The reconciliation tax
When two systems each hold their own view of stock, price or balance, somebody has to make them agree. That somebody is a permanent cost, and their work produces nothing a customer values.
Every one of these costs is paid in salary, in margin, or in the confidence of the person answering a customer. None of them appear as a line item, which is exactly why they persist.
When two systems each hold their own view of stock, price or balance, somebody has to make them agree. That somebody is a permanent cost, and their work produces nothing a customer values.
A customer is told one thing online and another at the counter. Both staff are reading a screen. Both screens are wrong in different directions.
The money in a multi-site business is increasingly made after the sale — service, protection, trade-in, refurbishment, the second purchase. Systems that model only the transaction cannot show you that margin, so it is managed by instinct.
When evidence lives in six systems with six permission models, proving what happened stops being a query and becomes a quarter of somebody’s year.
Every integration you buy to fix this is a bridge across a gap you were not meant to have.
Service, protection, trade-in, refurbishment and the repeat purchase are where multi-site operators now make their margin. A system that treats the sale as the event and everything after it as an exception will always report the least interesting part of the business most accurately.
If the price a customer sees online can differ from the price at the counter, the business is not slightly inconsistent — it is wrong, and someone will absorb the cost of being wrong. Treating that as a synchronisation setting accepts permanent error as a normal operating condition.
Identity, permission, evidence and the shape of the data are not plumbing to be revisited later. They are the constraints every capability inherits, so they are built first and they are published, not discovered by a customer two years in.
Every channel reads the same record, so the counter and the website cannot disagree.
Designed to retire eight or more systems and the integrations holding them together.
Service, protection and trade-in modelled as first-class events, not exceptions.
Tamper-evident records written as work happens, so proving it later is a query.
Bounded by the authority of the person it acts for. It proposes; a person disposes.
WCAG 2.2 AA is a build condition, so the software does not exclude your own staff.
Retail chains, distributors, service and repair networks, franchised operators and clinics. What they have in common is not an industry — it is a shape.
Absolute isolation between customers, by design rather than by configuration.
Tamper-evident records of what happened, who did it, and when.
Bounded by human authority. Nothing irreversible happens without confirmation.
WCAG 2.2 AA as a build condition, not a remediation project.
Orbit is in active development. If you run a multi-site operation and this describes a problem you recognise, we would like to hear about it.
Get in touch