The Transfer That Approves Itself
Our stock transfer has an action named Approve. Out of the box it is a synonym for Dispatch, in both the web application and the API, and the stock leaves the source warehouse in the same instant. Switch on transfer approval and it becomes a real state — approved and waiting, by somebody other than the person who asked.
A branch in Kandy asks the Colombo warehouse for forty units. Somebody in Colombo opens the request and presses Approve. The forty units are now gone from Colombo, in transit, and on their way — before anybody has picked them, packed them, or put them on a lorry.
That is not a description of a bug. It is a description of what the word means in our product by default. With transfer approval switched off, the approve action returns the dispatch action — the same code, reached by two different names, in the web application and in the API alike. The setting that changes this is the subject of the second half of this page.
The three states, and the one the setting adds
A transfer here moves through pending, then in transit, then either completed or returned. That is a sound and honest little state machine, and each transition does real work: dispatch reduces the source, receipt increases the destination, and a short receipt is recorded as a shortfall rather than silently absorbed.
What is not in that list, by default, is a state between asked for and gone. With approval off there is nowhere for a transfer to sit having been authorised and not yet physically moved, so whoever authorises is also, necessarily, the person deciding the stock leaves right now. Turn on Transfers need approval in Inventory Settings and that state exists: approving records who said yes and when, moves no stock, and dispatch is refused until it has happened.
With approval off, Approve and Dispatch are two words for one function. That default is a choice, and it is worth making on purpose.
It is worth saying what is not wrong here. There is a reject action, so a transfer is not unstoppable. The movement is recorded with a full history. The receiving end has its own confirmation and its own shortfall handling. Nothing is lost or untraceable. The gap, where the setting is off, is narrower and more specific than "no approval": it is that the accept path has no stop on it.
Why an island operation feels this first
Because a Sri Lankan distribution network is usually one central store and a scatter of outstations, connected by roads where a journey is measured in hours and a mistake is measured in days. Colombo to Jaffna is not a decision you unwind by driving back.
Three consequences follow, and they compound.
-
The source is short before the goods have moved
Between the press of the button and the pallet actually leaving, the stock is out of the source warehouse in the system and not in the destination. If a walk-in customer wants those units in that window, the system says there are none — and there are, on the floor, twenty metres away.
-
The authoriser and the picker become the same decision
In most operations these are deliberately different people at different times. A manager says yes on Monday; a storeman picks on Tuesday. Here the yes IS the pick, in record terms, so the record says something happened on Monday that happened on Tuesday.
-
A transfer that never physically leaves is invisible
Approved, dispatched, and then the lorry is full or the road is closed. The system believes those units are in transit. Nothing ages an in-transit transfer, nothing asks why it has been travelling for eleven days, and the source cannot see them.
The third one is the expensive one, and it is the reason this post exists. Stock in transit is stock nobody is looking at. The longer the corridor, the more of it there is, and the less anybody notices.
What to do about it
Four controls that work with the states that exist
- Switch on transfer approval, and press Dispatch at the loading bay. With the setting on, the yes is its own recorded step, by somebody other than the person who raised the transfer; dispatch then happens when the goods are physically on the vehicle, so the record says Monday for the decision and Tuesday for the pick.
- Put a maximum age on in-transit. Agree a number — two days, four days, whatever your longest route is plus one — and review the transfer list against it every week. Nothing in the product will do this for you, so make it somebody's named job rather than a good intention.
- Use the shortfall properly at the receiving end. A short receipt has to carry a reason, can name who answers for it, and records the value of the missing units — the best evidence you will get that something went wrong in the corridor. Insist that receipts are entered on arrival, not on Friday afternoon in a batch.
- Separate the people, and let the system hold you to it. With approval on, the raiser cannot approve their own transfer and the dispatcher cannot receive it, whatever their permissions. With it off, the same person can raise, dispatch and receive, and keeping them apart is a staffing decision.
A note on the word itself
A control named for something it does not do is worse than no control, because it recruits the reader’s trust for free. With approval off, the honest label for this action is Dispatch, and that is the label the interface renders — the approve name survives in the routes and the API, where an integrator will meet it and reasonably assume it means what it says. With approval on, it does.
Four questions to ask about transfers, in any system
Show me a transfer that has been approved and not yet dispatched.
A good answer sounds like
A record in that state, on screen, with a timestamp for the approval and none for the dispatch.
What it actually means
If the answer is that no such state exists, the authorisation and the movement are the same event — as they are here until transfer approval is switched on.
Where is stock that has left the source and not arrived?
A good answer sounds like
A named in-transit position, visible in a report, with an age.
What it actually means
In-transit stock that cannot be aged is stock nobody will look at until a count finds it missing.
Can one person raise, send and receive the same transfer?
A good answer sounds like
A clear yes or no, and a demonstration.
What it actually means
A no is a real control, and ours is a no once transfer approval is on. A yes is manageable, but only if you know about it before you write your role design rather than after.
What happens to a transfer that is dispatched and never received?
A good answer sounds like
A shortfall, an alert, an ageing report — something.
What it actually means
Ours records the shortfall at receipt, with a reason and its value, and does not chase the receipt. That difference is where losses hide.
What AWRA OpsHub does today
- A four-state transfer — pending, in transit, completed or returned — with dispatch reducing the source and receipt increasing the destination, each recorded with who and when.
- Partial and line-by-line dispatch and receipt, plus return-to-source with a stored reason.
- A recorded shortfall when less is received than was sent, held against the transfer.
- A reject action, on both the web application and the API, so an unwanted transfer can be refused.
- Signature capture on the transfer, and a PDF of the document.
- An approved state, when Transfers need approval is on: approving moves no stock, dispatch refuses an unapproved transfer, the raiser cannot approve their own and the dispatcher cannot receive — the same rules on the web, the API and the mobile app.
- A reason on every shortfall, an optional named party who answers for it, and the value of the missing units recorded at receipt.
More we can add to your workspace
- A hold on the source stock between approval and dispatch, so goods agreed for a transfer stop counting as available to sell at the source. Commission it
- Ageing of in-transit transfers, flagging a movement that has been travelling too long. Commission it
Where we point you to a specialist
- Approval is off by default, and off means exactly the old behaviour: the approve route dispatches. That is the organisation’s choice to make, so we leave it as a setting rather than switching it on for everyone.
- With approval on, separation of duties is enforced in code and no permission buys past it. With it off, assume you must enforce it with people.
- This is market-neutral. It applies to any hub-and-spoke network; the longer your corridor, the more that state is worth.
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 a tax authority pipeline, 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.
Tax authority pipelines and reporting
Electronic invoicing or invoice registration against your authority's published interface, with retries, a failure queue and a daily report of sales that carry no reference. The regimes across this region differ enough that this is one build per country rather than one build for the region, and the local bench is deep in most of them — so the honest question is usually whether you need this from us at all, or whether you need the operations layer that feeds whatever you already file with.
Local payment rails and bank feeds
Real-time payment collection matched to the invoice, bulk payment files in your bank's format, and statement feeds wired into the Payments Register.
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
Statutory payroll and social security schedules computed on live records and produced in the layout each filing body expects. Per-state and per-province variation is the norm rather than the exception here, and it is what makes this a country build rather than a regional one.
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 integratedDesign the transfer process around what exists
Most of the risk in this page is closed by switching on transfer approval and deciding who presses Dispatch and where they are standing when they press it. We will walk your network and write that down with you.
Talk it throughFrequently asked questions
If I never use the approve route, does anything change?
Not with approval off: the interface shows Dispatch, so a normal user is already using the honestly named action, and the alias matters only if you are integrating against the API. With approval on, the approve route becomes a real authorisation step and dispatch waits for it.
Can I stop a transfer after it has been dispatched?
You can return it to source, which is a real action with a stored reason, and you can reject a transfer before dispatch. What you cannot do is undo the dispatch as though it never happened — the movement is history, and returning it is a second movement.
Is there an approval step?
Yes — switch on Transfers need approval in Inventory Settings. Approving then needs its own permission, cannot be done by the person who raised the transfer, and moves no stock. A hold on the source stock between approval and dispatch is the next layer, because the availability calculation moves with it; if it is decisive for your network, describe it and we will come back with a written scope, timeline and cost before you commit.