Washing station records: what to capture at receiving

A washing station creates one record for every delivery, and that record is the origin of almost everything the business later reports: what was bought, from whom, at what price, and what it became. Get it right and the rest follows. Get it wrong and every downstream number inherits the error.

The problem is that receiving is also the moment of maximum time pressure. Trucks arrive together, queues form, and the person recording the delivery is being asked to be fast. Records designed for the office do not survive that.

A delivery record needs enough to support purchasing, quality, traceability and payment. In practice that means:

A sequentially generated receipt number does three things a hand-written one cannot. It cannot be duplicated. It cannot be skipped without being noticed. And it makes the record citable in conversation, in a ledger and in a dispute.

Per-station sequences matter here. A business running several stations wants each to number its own deliveries, so a receipt number identifies where the coffee was received as well as when.

Quality data captured at receiving is more valuable than quality data captured later, because it describes what actually arrived rather than what survived the queue. Even simple observations — ripeness, visible defects, moisture impression — give the processing team something to work with.

Captured against the lot, this becomes part of what can be said about the coffee later. Captured in a notebook, it is lost by the time anyone asks.

Recording payment status at receiving is what makes it possible to answer, without a reconciliation exercise, what is owed to whom. It also links the purchasing record to the finance side of the business, so cost per kilogram is real rather than estimated.

Most of this is straightforward until the network drops, which at a rural station it will. A records system for receiving has to work offline, store the record on the device, and synchronise when connectivity returns — because the alternative is a paper fallback, and paper fallback is where data quality goes to die.

Receiving data is operationally sensitive, so it should not be uniformly visible. Station staff should see their own station; management should see everything. That distinction is worth enforcing in the system rather than relying on discretion, because a station-level restriction that only hides menu items is not a restriction.