Fifty-Four Left, Fifty-Two Arrived
A transfer that arrives short is usually recorded as a smaller receipt and forgotten. The missing stock left one shelf and reached no other, so it is not on either. What it takes to make every unit that left a warehouse end up somewhere on the record: picking before dispatch, a case for every shortfall, and a ledger that checks the road.
Sixty cartons were requested. Fifty-four were on the shelf, so fifty-four went on the truck. Fifty-two arrived. The receiving clerk typed fifty-two, the branch had fifty-two more than it did yesterday, the main store had fifty-four fewer, and the two cartons in between were on no shelf at all. Nobody had stolen anything yet, as far as anyone knew. The records simply had a hole the size of two cartons in them, and it would stay there until a count found it months later and nobody could say which week it happened.
Transfers are where stock goes missing without anyone deciding anything. A sale has a customer and a receipt has a supplier, and both have someone who cares about the number. A transfer has two storekeepers in two places, each of whom is right about their own shelf. We covered the long-haul version of this in stock in transit on an inland corridor. The fix is not a better receiving screen. It is a rule: every unit that leaves has to end up somewhere on the record, and the system refuses to let a shortfall be saved as a smaller number.
Count it before it leaves
The first two cartons of the story — the sixty requested against fifty-four on the shelf — are not a loss at all, and should never look like one. Picking records what actually came off the shelf, and that becomes the quantity dispatched. A short pick is on the record before the truck leaves, so the branch is expecting fifty-four, not sixty. Packing then seals the line into a counted number of packages, and once a line is packed it cannot be picked again, because that would change what is inside a sealed package. Photos can be taken at pack, dispatch, receipt and discrepancy.
| Step | What it fixes | Where it happens |
|---|---|---|
| Pick | Request versus what was on the shelf | Source warehouse |
| Pack | What was sealed and in how many packages | Source warehouse |
| Dispatch | What left, signed | Source warehouse |
| Receive | What arrived, signed, with a reason for any shortfall | Destination |
| Discrepancy | Where every missing unit went | Destination |
A shortfall is a question, not an answer
When fifty-two arrive against fifty-four dispatched, the receiver has to say why — damaged in transit, lost or stolen, less sent than recorded, a counting error — and a discrepancy opens in the same step. A short receipt cannot be saved without one. Investigating adds notes and moves nothing. Resolving says where every missing unit is, in three numbers that must add up to the shortfall.
The two cartons, resolved
The write-off is the moment the inventory account shrinks. Until then the two cartons were still owned, just not on a shelf; a transfer moves stock between warehouses, not between accounts.
The receiver is right about their shelf and the sender is right about theirs. The discrepancy is where somebody has to be right about the road.
A ledger for the road
Cases close one at a time. The In-Transit Ledger checks all of them at once. For every dispatched line it asks three things: does it balance — dispatched equals received plus returned plus still in transit plus short; does the movement trace written at each end agree with the transfer; and is every short unit covered by a resolved discrepancy. Lines older than the trace are marked untraced rather than wrong. A line that fails the second check points at a record changed outside the transfer screens, which is a different conversation from a carton on a truck. It belongs beside the item-total reconciliation in the stock figure the auditor rebuilds.
The right end does each step
Pick and pack happen at the source and a discrepancy is worked at the destination. A scanner phone assigned to a different warehouse is refused for those steps, with a message naming both, and so is an account restricted to another branch. Steps taken offline in the app are queued, never applied twice, and come back as a conflict if the transfer has moved on in the meantime.
Our position
Count stock before it leaves, so the request and the shelf stop being confused with a loss. Refuse to save a short receipt without a case, and refuse to close the case until every missing unit is found, returned or written off. Then check the road as a whole, every month, because the hole you are looking for is the one nobody opened a case for.
What AWRA OpsHub does today
- Pick and pack before dispatch, with the picked quantity becoming the dispatched quantity and a packed line sealed against re-picking.
- Photos at pack, dispatch, receipt and discrepancy, up to 24 per transfer.
- A discrepancy opened by every short receipt, resolved only when found, returned and written-off quantities equal the shortfall, with serials named for serial-tracked items.
- A write-off that posts once, to the count-shortage loss account, at the cost fixed at receipt.
- An In-Transit Ledger checking balance, movement trace and unexplained shortfalls on every dispatched line, with a CSV export.
- All of it in the mobile app, offline included, with phones assigned to a warehouse refused at the wrong end.
More we can add to your workspace
- A carrier or driver signature at a hand-off to a third party, so the leg between your two warehouses has its own signed record.
- An ageing alert on an open discrepancy, so a case nobody resolves reaches a manager after a set number of days.
- A claim against a carrier raised from a write-off, carrying the photos and the case notes.
Where we point you to a specialist
- We will not let a short receipt be saved as a smaller number with nothing behind it. The shortfall is either explained or it is a case.
The ageing alert is the smallest of the three and the one that stops open cases accumulating quietly.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsThree questions about your transfers
When a transfer arrives short, what happens to the missing units?
What you will probably hear
The receiver types what arrived.
How to read it
Then the missing units are on no shelf and no record. They will surface as a count variance with no date attached.
Can you tell a short pick from a loss on the road?
What you will probably hear
Not really.
How to read it
Without a pick step, the request and the shelf are compared at the far end, and every shortage looks like theft.
Who checks that every dispatched unit ended up somewhere?
What you will probably hear
The year-end count.
How to read it
A monthly ledger of the road finds the hole in the week it happened, while someone still remembers the truck.
See stock transfers
Requests, approvals, two signatures, picking and packing, and a discrepancy for every short delivery, on the web and in the app.
Explore stock transfersFrequently asked questions
What happens when a stock transfer arrives short?
The receiver records what arrived and must give a reason for the shortfall, and a discrepancy opens in the same step. It is resolved by saying how many units were found at the destination, sent back to the source or written off, and those must add up to the shortfall.
Is picking a transfer required before dispatch?
No. Picking and packing are optional steps. When they are used, the quantity picked becomes the quantity dispatched, so a short pick is recorded before the stock leaves.
When does a transfer shortfall reduce the inventory value?
Only when units are written off on the discrepancy. The write-off posts once to the same loss account a count shortage uses, at the cost fixed when the units were received.
What does the In-Transit Ledger check?
For every dispatched transfer line: that dispatched equals received plus returned plus in transit plus short, that the movement records at both ends agree with the transfer, and that every short unit has a resolved discrepancy.
Do these steps work offline?
Yes. In the mobile app, pick, pack, discrepancy steps and photos are queued offline and sent on reconnection. A step is never applied twice, and one overtaken by a change made elsewhere comes back as a conflict.
