A Shortfall That Carries a Name
Send a hundred, receive ninety-seven, and our system used to record the three and nothing else — not why, not who, not what they were worth — while returning goods deliberately to the source always required a reason. A short receipt now has to explain itself too.
Every long-haul transfer eventually arrives short. It is not always theft and it is rarely dramatic: a miscount at the origin, a carton left on a dock, a pallet split across two vehicles, breakage. What separates a controlled operation from a leaking one is whether anybody can say which.
For a long time our system told you that three units did not arrive and nothing else about them. It now asks the receiver why, takes a name for who owns the gap, and puts a money figure on it the moment the receipt is saved.
What is recorded, exactly
Receive a transfer for fewer units than were dispatched and the difference is computed and stored on the transfer as a shrinkage quantity. It is a real field, it persists, and it appears in the transfers report, which totals it across whatever period you ask for.
Three things are now stored alongside it.
- A reason. A short receipt in the browser is refused until the receiver picks one — damaged in transit, lost or stolen, less sent than recorded, a counting error, or other with a note — so miscounted, stolen and never-loaded stop being indistinguishable.
- A responsible party. The receipt takes the name of whoever owns the difference — the carrier, the dispatching site, a driver — which is a different statement from who dispatched and who received.
- A value. The missing units are valued at the item’s cost when the receipt is saved, and the transfers report totals that money figure beside the units, so three high-value units and three washers no longer weigh the same.
Returning goods on purpose always required a written reason. Losing them did not, until now.
That asymmetry was not a design decision anybody made. It is what happens when two paths are built at different times: the return path was written as a deliberate act, so it asked why. The shortfall was computed as a side effect of a receipt, so it asked nothing — and closing that gap meant making the receipt ask.
Why a long, thin country makes this expensive
Chilean distribution is a geometry problem before it is anything else. A network running from the north to the south is a series of very long single legs, often with a single carrier, and often with days between dispatch and receipt.
Three consequences follow from the length of the leg, and they are why these fields are worth more here than they would be in a compact market.
| What the length does | What the field is for |
|---|---|
| More handovers between dispatch and receipt | A responsible party is somebody who can be asked. Each handover is a place the goods could have gone, and the receipt is where one of them gets named. |
| Days rather than hours in transit | By the time a shortfall is noticed, the origin has moved on. A reason recorded at receipt is the last moment anybody remembers anything. |
| Higher freight per unit, so denser loads | A units-only shortfall total is least informative exactly when the mix is widest, which is why the value is fixed at receipt rather than worked out later. |
| Fewer, larger movements | A pattern needs repetitions to become visible. With fewer transfers, the only way to see a pattern is a reason code, recorded every time. |
How to use it
-
Treat the reason list as a commitment, not a formality
The receipt offers five reasons and other-with-a-note. Agree on the wall what each one means — when a carton is crushed it is damaged, when it never left it is less sent than recorded — so the same event is coded the same way at every site.
-
Keep other rare
Other is there for the genuinely unusual, and it insists on a note. If it becomes the commonest reason, the list your team is working from is wrong, not the event.
-
Read the money, monthly
The transfers report totals the shortfall in units and in value, each loss priced at the cost on the day it was received. Pesos get attention that units never do.
-
Decide whose name goes in the responsible field
Decide whether a shortfall belongs to the dispatching site, the receiving one or the carrier, and write it the same way every time. Both answers are defensible; having no answer means the difference is charged to nobody and therefore examined by nobody.
-
Chase what is still on the road
A transfer in transit for more than seven days is flagged on the transfers list and counted in the report, because stock in that state sits in neither warehouse and on no count.
The number that changes the conversation
Run the transfers report for a full year and take the value line to whoever owns your logistics contract. Shortfalls expressed in units are a warehouse matter that nobody escalates. The same shortfalls expressed in money, over twelve months, against a freight bill and read by the reason recorded at receipt, are a commercial conversation with a carrier.
Our position
Recording the shortfall at all always put this product ahead of anything that silently absorbs the difference into a stock count later. But a quantity with no reason, no owner and no value was an observation rather than a control, so a short receipt now carries all three. What turns them into a control is yours: a shared meaning for each reason, a monthly read of the value, and a written rule about whose loss it is.
What AWRA OpsHub does today
- A shortfall computed at receipt as dispatched minus received, stored on the transfer and persisted.
- The shortfall totalled in the transfers report over any period, alongside transfer counts and in-transit counts.
- A stored reason on a deliberate return to source, which is a different and better-served path.
- Who dispatched and who received, with timestamps, on every transfer.
- Partial and line-by-line receipt, so a split delivery is not forced into an all-or-nothing decision.
- Signature capture on the transfer document, and a PDF of it.
- A required reason on a short receipt in the browser, from a fixed list, with a note insisted on when the reason is other.
- A responsible party recorded on the shortfall, naming who owns the difference.
- A value on every shortfall, fixed at the item’s cost when the receipt is saved and totalled in the transfers report beside the units.
- A flag on transfers in transit for more than seven days, on the transfers list and in the report.
More we can add to your workspace
- The shortfall reason asked on the mobile app as well. A short receipt from the phone is recorded today with its reason marked not stated, so it stands out in the report; the same prompt the browser shows is being built into the app. Commission it
- Pattern detection, flagging a route, a carrier, a site or a person whose shortfalls run unusual. Commission it
- A responsible party chosen from your own list of carriers and sites rather than typed, so it groups as cleanly as the reason does. Commission it
Where we point you to a specialist
- Recording the shortfall at all is the right design and the important half. Systems that reconcile transfers only at the next stocktake lose the event entirely.
- The free-text vocabulary workaround is real and used. It is weaker than a coded reason because nothing can group it, and it is far stronger than nothing.
- This is market-neutral. It is the arithmetic of long legs; Chile is where the legs are longest.
What we can build for your market on top of the standard product
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point for your market, not a limit on what AWRA OpsHub can do there. Kenya's eTIMS integration and its maintained payroll engine are in the product because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If the seam to a clearance provider, a supplier invoice that can be read, a limit that is not an amount, a bank or mobile money feed, a statutory return format, a rule specific to how your operation runs, or a link to a system you already have is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
Which end of the document you stand at, and what the limit is written in
Three builds cover most of what this region exposes, and the first is a seam rather than a system. Document exchange with the authority runs through a role somebody is accredited for, so what we build is the two-way join to the provider you pick — our document handed over in the shape they expect, and the reference, status and any acknowledgement written straight back onto our record, which is what turns "which of ours are not yet cleared" into a report rather than a reconstruction. Second, reading a supplier's electronic invoice into lines that carry tax, so the purchase side holds a rate and not only an amount. Third, a limit expressed as a multiple of an index unit rather than as a sum of money, with something that actually reads the unit when it is revalued. All three are data-model changes rather than settings, and we would quote them as such.
Local payment rails, and obligations that fall on the buyer
Statement feeds and local payment rails wired into the Payments Register, alongside the buyer-side obligations this region is unusual for — an acknowledgement generated from a receiving event and transmitted, and a report of purchases received but not yet acknowledged. Receiving against the order already runs; the outbound half is the buildable part on top of it.
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.
Payroll and statutory returns
A local payroll engine with income tax tables and social security contributions computed on live employee records, producing returns in the layout your authority expects rather than rebuilt each month.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
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. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedFour questions about transfer losses
Receive a transfer short, in front of me. Show me every field that gets written.
A good answer sounds like
A quantity, a reason, an owner and a value.
What it actually means
Ours writes all four from the browser. Watching the save happen is faster than reading a feature list.
What is my shortfall worth this year?
A good answer sounds like
A currency figure from a report.
What it actually means
A units figure means somebody has to do arithmetic before anybody will act, and that person does not exist in most organisations.
Which route loses the most?
A good answer sounds like
A breakdown by origin and destination.
What it actually means
Without it, a bad leg is averaged into a national number and stays invisible for years.
Who is charged for a shortfall?
A good answer sounds like
A stated rule, in the system or in the process.
What it actually means
If neither the vendor nor you can answer, the loss belongs to nobody, which is the same as belonging to the business.
Turn units into money
Every short receipt now carries its reason, its owner and its value. Talk to us about reading a year of them by route and carrier — it is usually the number that starts the conversation nobody has been having.
Value the lossFrequently asked questions
Is the shortfall the same thing as shrinkage found in a stocktake?
No, and keeping them separate matters. A transfer shortfall is a difference between two known figures on one movement, which makes it attributable in principle. Stocktake shrinkage is a difference between a book figure and a count, with an unknown number of causes across an unknown period. Any loss you can pin to a single movement is worth far more than one you cannot.
Can I add a reason as a custom field?
There is no need to. A short receipt in the browser already asks for a reason from a fixed list, with a note when the reason is other, and the transfers report shows the reason beside each shortfall. What makes it useful is everybody meaning the same thing by each reason.
Does the shortfall adjust stock at both ends?
The dispatch reduces the source by what was sent and the receipt increases the destination by what arrived, so the difference is not sitting anywhere at the end of the process — it has left the business. That is the correct treatment, and the reason, owner and value recorded at receipt are what say why it left and what it cost.