One source of truth: what it means when you take it literally

Ask three people in a transport office where a pallet is and you can get three answers, all given in good faith. The planner reads the run sheet. The warehouse reads the stock system. Whoever is on the phone to the customer reads the last email anybody sent. Nobody is lying and nobody is careless. Each is reading a different record of the same fact.

“A single source of truth” is the phrase for fixing that, and it has been said so often that it has stopped carrying meaning. It appears on every vendor’s site, ours included. So it is worth writing down what it actually claims, in a form you could check on a Tuesday.

The claim, stated so it can be tested

For any fact your operation depends on — where a consignment is, what it weighs, what it will be billed at, whether a truck is legal to dispatch — there is exactly one place where that fact is written, and every screen showing it derives from that place instead of keeping its own copy.

That is the whole of it. It is not a technology, and it is not “everything in one database”: you can have one database and still hold the same weight in four columns that nobody keeps in step.

The test that follows is short. Can two screens in your operation disagree about the same fact? If they can, you do not have a source of truth. You have copies, plus a convention about which one people trust — and a convention is not enforced by anything.

Where the copies come from

Nobody sets out to keep four versions of a delivery address. They arrive in ordinary ways.

• The export. Somebody needed a list, exported it, and the list became a working document. It was accurate for one afternoon.
• The integration that pushes and never pulls. Bookings flow out to the accounting system. Corrections flow back by phone.
• The re-typing. The quote lives in one place, the booking in another. Someone reads the first and types the second. The two agree until something changes.
• The field with two owners. Sales edits the customer’s payment terms. The office edits them too. Both are right, in turn.
• The spreadsheet that started as a workaround. It solved a real gap. Then it grew columns the system does not have, and now it is a source — unversioned, on one laptop.

Every one of those is a rational local decision. Together they are why your Monday morning has a reconciliation step in it.

Some copies are correct, and this is the part that gets skipped

A single source of truth is not a rule that nothing may ever be copied. Several things in freight must be frozen, and freezing is copying on purpose.

An issued invoice is what you asked to be paid, on the day you asked. If it re-derived itself from today’s price list it would quietly restate history, and the customer’s copy would stop matching yours. A signed consignment note records the parties and the goods as they were at signature; the consignee changes company name a year later and the note does not. The address a delivery was actually made to is not the address that customer has now.

So the distinction is not copy versus no copy. It is declared versus undeclared. A snapshot with a reason, a moment and a direction — this was true then, it is frozen, nothing writes to it again — is a record. A value that keeps drifting because two screens both write to it is a defect. Most operations have plenty of the second and file them mentally under the first.

What it buys you

• The status the customer reads and the status the dispatcher reads are the same status, so a status call becomes a lookup rather than an investigation.
• An invoice line traces back to the work that earned it, so a dispute is answered from the record instead of from memory.
• A vehicle that may not legally be dispatched is one fact, which the planning screen, the fleet board and the confirm button all know. It is not a note somebody keeps.
• Nothing is typed twice, which removes the whole class of error where two people typed the same thing differently and both were certain.

What it does not buy you

Being honest about this matters more than the pitch does.

• It does not make the data right. One record means one place to be wrong, consistently and everywhere. That is better — a wrong figure you can find beats four you cannot compare — but it is not correctness, and a system that agrees with itself is very convincing while it is wrong.
• It does not mean one screen. Warehouse and dispatch need different views of the same load. Having one record is precisely what lets those views differ without disagreeing.
• It does not remove integrations. You will still exchange data with customers, accountants and partners. What changes is direction: each fact has one owner, and everything else is a subscriber to it.
• Getting there is visible work. The hard part is never the software. It is deciding who owns a field that two departments both edit today, and then living with the decision when it is inconvenient.

The exercise that tells you where you stand

Take five facts your operation runs on. A delivery address. The price for a lane. A shipment’s status. A vehicle’s next inspection date. What a customer owes you.

For each one, ask three questions: where is it written, who may change it, and what else holds a copy? Do not answer from an architecture diagram. Answer by finding the people who look those things up and asking what they actually open.

Most operations get one or two clean answers and three uncomfortable ones. The uncomfortable ones are your list. You will not fix them all, and you probably should not try at once — but you should know which of your facts have an owner and which are a consensus that holds until the day it does not.

Where navichain stands

navichain is built as one system rather than three that talk to each other: transport, warehouse and intelligence on a single source of truth, three modules over one set of data, so the booking, the run that carries it, the stock it draws on and the invoice that follows all read the same record. The day-to-day version of that is as boring as it should be — one set of numbers the whole office reads from, updated as the day happens, and a customer portal where the customer sees the same status the dispatcher sees rather than a report about it. The platform page sets out what sits inside.

Where two systems are kept apart instead, the gap between them is exactly where custody, billing and trust leak — the same argument as this one, approached from the other end.