A Shortfall With No Name on It
Send a hundred, receive ninety-seven, and our system records the three. It does not record why, who, or what they were worth. Meanwhile returning goods deliberately to the source does require a reason — so the intentional act must explain itself and the unexplained one does not.
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.
Our system will tell you that three units did not arrive. It will not tell you anything else about them, ever.
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 not stored alongside it.
- A reason. There is no reason code and no note attached to the shortfall. Miscounted, stolen, damaged and never-loaded are indistinguishable.
- A responsible party. Nobody owns the difference. Not the dispatcher, not the carrier, not the receiver — the transfer knows who dispatched and who received, and neither of those is a statement about who is answerable for the gap.
- A value. The report sums the shortfall in units. There is no cost join, so three high-value units and three washers contribute equally to the total.
Returning goods on purpose requires a written reason. Losing them does not.
That asymmetry is 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 asks why. The shortfall is computed as a side effect of a receipt, so it asks nothing.
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 the missing fields cost more here than they would in a compact market.
| What the length does | What the missing field costs |
|---|---|
| More handovers between dispatch and receipt | With no responsible party, nobody can be asked. Each handover is a place the goods could have gone and none of them is 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 what a consolidated long-haul load is. |
| Fewer, larger movements | A pattern needs repetitions to become visible. With fewer transfers, the only way to see a pattern is a reason code, and there is not one. |
What to do instead
-
Put the reason where the system does have a field: the receipt
The receiving side of a transfer can carry a note. It is free text and nothing groups or reports on it, but it is the difference between a number and a fact — and a free-text reason you can read is worth more than a coded one you never captured.
-
Use a fixed vocabulary in that free text, from day one
Four or five words, agreed and written on the wall: MISCOUNT, DAMAGE, SHORT-LOADED, NOT-DELIVERED, UNKNOWN. Free text is only unsearchable if everybody writes something different. This is the single cheapest control on this page.
-
Value the shortfall yourself, monthly
The transfers report gives you the units. Your item costs are in the system. One multiplication turns a number of units into a number of pesos, and only the second one will get anybody's attention.
-
Name the owner in your process, since the record will not
Decide whether a shortfall belongs to the dispatching site or the receiving one, and apply it consistently. Both answers are defensible; having no answer means the difference is charged to nobody and therefore examined by nobody.
The number that changes the conversation
Do the multiplication once, for a full year, and take it 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, are a commercial conversation with a carrier — and that conversation is available to you today with no feature at all.
Our position
The shortfall is recorded, which puts 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 is an observation rather than a control. Fix it with a four-word vocabulary in the receipt note, a monthly multiplication, and a written rule about whose loss it is — none of which need us.
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.
What it does not do
- A reason on a shortfall. There is no code, no list and no required note.
- A responsible party on a shortfall. Nobody owns the difference in the record.
- A value on a shortfall. The report sums units with no cost join, so mix is invisible.
- Any pattern detection — nothing flags a route, a carrier, a site or a person whose shortfalls are unusual.
- Ageing of transfers in transit, so a movement that never arrives is never chased.
Not ours, by choice
- 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.
- Nothing here is Chilean. It is the arithmetic of long legs; Chile is where the legs are longest.
What is not built for your market today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in your market. Kenya's eTIMS integration and its maintained payroll engine exist 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 your own operation needs that the standard one does not have, or a link to a system you already run 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 the first only. 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 once
Send us a year of transfer shortfalls and your item costs and we will do the multiplication with you. 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?
Custom fields capture information on the records that support them, and that would give you somewhere consistent to write the reason — but nothing would group or report on it any more than the note does today. The vocabulary discipline is what makes either option useful.
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; the gap is that nothing says why it left.
