Warehouse reconciliation: close the gap with a document, not a keystroke

What it looks like on the floor

Month end. A spreadsheet with two columns, system and counted, and a third column of differences that someone will type into the system one by one. Next month the same rows are back with new differences, because the corrections fixed the numbers and not the reasons.

Why it happens

Reconciliation fails when correcting is easier than explaining. If the product page has a quantity field and anyone with access can type in it, the gap between shelf and record closes in one keystroke and reopens the moment the cause repeats. The system is now wrong in a way nobody can trace, because the correction overwrote the only evidence.

The second failure is that reconciliation is treated as something people do to the system, rather than something the system does to itself.

What DockingWare does

The system reconciles itself every night. It replays every movement row for every product and compares the replayed balance with the stored snapshot, bucket by bucket. A difference becomes a discrepancy with a severity, on a reconciliation run that is kept on record. The ledger is the authority; the snapshot is a cache of it, and the run proves the cache is honest.

People reconcile through documents. A cycle count records what was found at a location. Each line that differs from the record is a variance, and a variance cannot be approved without a reason code or a note. Approval writes an adjustment movement that carries the count number, the reason and the approver. The product page has no quantity field to type over. If a number changed, there is a document that changed it and a name on the document.

Channel quantities are reconciled too. A pass compares what each connected channel currently holds against what the warehouse computed and names the difference, so a stale marketplace number is a finding on a list, not a customer complaint.

Movement types carry their meaning. A marketplace removal that comes back to the dock is booked as a channel inbound, not as a customer return, because the two have different accounting and different reasons, and a ledger that merges them cannot be reconciled against the books.

Every screen that shows a movement history shows the physical rows first. Reservations and pipeline rows sit behind a toggle, so a reconciler reads one row per physical event instead of three.

What it does not do

It does not let you skip the count. There is no “trust me” button that sets a quantity without a document behind it. That is deliberate. The purpose of reconciliation is not to make the numbers match today. It is to be able to show, later, why they matched.

What you can verify

Every rule above is enforced in code and covered by a test that fails first, then passes. The changelog names the version each one shipped in.