Company control versus store responsibility
Shipped, in transit, and received
On-hand need not equal sellable
How the same units get counted twice
How shortage, loss, and cancel clear
Shipped but not received is not a stockout question
When goods have left one store and the other store has not received them, the first question is not whether someone is out of stock. Inside one company, a transfer usually leaves legal control with the company. What changes is which store is responsible, whether the units are in transit, and which of those units can still be promised to a customer. If the sending store can still sell them and the receiving store can also sell them, the company has counted one shipment twice. If both stores remove them, a customer may be blocked from goods that are already on the way and could have been promised under a written rule.
Control, in-transit status, and sellable quantity are three different ideas. Control says which entity holds the goods. In transit is a stock state. Sellable quantity says what may be promised now. A generic low-stock alert compares a balance with a minimum and cannot see that the units have left the sender without becoming sellable at the receiver. The same split applies to a retail transfer, a move between ecommerce forward warehouses, and a finished-goods warehouse feeding a store, as long as the company has not sold the goods to an outside party.
Inside one company, the goods usually stay with the company
Two stores of one legal entity are not selling to each other. The Conceptual Framework for Financial Reporting ties an asset to control: if the company can still direct the use of the goods and obtain the economic benefits, the inventory remains at company level. The IAS 2 page is the public entry for the inventories standard, which addresses recognition and measurement of inventory the entity holds. An internal transfer should not make company inventory vanish, and it should not let both stores record it. What still needs a local rule is responsibility: who carries loss on the road, and which store manager still answers for the units.
A sale to another company, or a purchase from a supplier, is where delivery terms matter. The International Trade Administration explains that Incoterms allocate tasks, costs, and risks between buyers and sellers for shipment, insurance, and paperwork. A public accounting note describes FOB shipping point as the buyer taking delivery when goods leave the supplier dock. Those are moments in a contract between two parties. They are a poor shortcut for a transfer between two stores of the same company. Internal transfers need their own states, not a borrowed external term treated as a change of ownership.
In-transit stock has to leave both on-hand balances
Keep three states: on hand at the sender, in transit, and on hand at the receiver. On dispatch, quantity leaves the sender’s on-hand balance and enters transit. On receipt, it leaves transit and enters the receiver’s on-hand balance. Company inventory is the sum of the three, and a unit is in only one of them at a time. A shortage, a transit loss, or a refusal clears the transit balance. Editing only the receiver’s balance either leaves transit hanging or creates stock the receiver never got.
Double counting usually comes from stitching two records together. Example only: store A ships 8 units, store B adds 8 when the dispatch note arrives, and store A still shows 8 until B confirms. Adding the two on-hand balances counts those 8 twice. Another example: store balances are already summed, and a separate in-transit list that is not exclusive of those balances is added again. Both cases should be tested on one transfer document to see whether quantity is conserved. This is an illustration of the mechanism, not a measured loss from a named chain. Kimball’s grain article is the relevant public reminder: say what one row represents before an on-hand row and an in-transit row can be added.
Sellable quantity does not have to move on the same day as the balance
Once the sender has loaded the truck, those units usually should not be sold to that store’s customers, even if cost stays on the sender until receipt. Sellable quantity at the sender should fall at dispatch, which may be a different moment from the cost transfer. Before the receiver has confirmed receipt and can hand the goods over, transit quantity is not ordinary sellable stock. If the business allows customers to reserve in-transit goods, mark that quantity as promised-from-transit, with an expected arrival and a cancellation rule. Do not fold it into the store’s ordinary on-hand balance.
Company sellable quantity is also not the sum of store sellable quantities plus everything on trucks. If no store can hand the goods over now, in-transit units are not immediately sellable. If an online order can be reassigned to the receiving store with a delivery promise, they may count as committable under a written rule. Committable, sellable, and on-hand need different names. When they share one label, the screen says the goods are available while the store cannot deliver them, or a replenishment buyer treats arriving goods as if the shelf were already empty.
Two operating paths, and when each one fits
Path one removes sellable quantity at dispatch, holds the units in transit, and releases ordinary sellable quantity only when the receiver confirms. It fits transfers whose travel time varies, whose loss sits with the company or the carrier, and whose receiving store must not sell early. It depends on a dispatch event that is recorded when the goods actually leave. If dispatch notes are often entered the next day, units already sold can be rewritten into transit and the sellable balance jumps. It does not fit a notice that is frequently cancelled before the vehicle leaves.
Path two assigns internal responsibility to the receiver at dispatch, while ordinary sellable quantity still waits for receipt or put-away. It fits when the receiving store carries transit loss, store-level inventory is an accountability measure, and the store cannot sell goods that are not on the shelf. It does not fit a receiver that takes customer orders from the dispatch note, because that oversells goods still on the road. Both paths keep dispatched quantity, in-transit quantity, received quantity, and a reason for any difference. A store that keeps only an ending on-hand balance cannot say who holds the goods or whether they can be sold.
A stockout alert answers a different question
Counterexample one: the receiver is below a minimum and orders more from the supplier, ignoring units about to arrive, so the company buys twice. Counterexample two: the sender’s balance falls and an alert fires, although the drop is a deliberate transfer, not a surge in demand. Counterexample three: a late truck is added to the receiver’s ordinary sellable stock, and customers buy goods that are still on the road. Counterexample four: a repeated receipt posting reduces transit twice and inflates the receiver. Counterexample five: store A ships to store B, B has not received the goods, and they are redirected to store C, but only the latest destination is stored, so responsibility in between is lost.
A lower minimum does not fix these cases. A stockout alert asks whether sellable quantity is enough. An in-transit transfer asks which state the goods are in, who is responsible, and what may be sold now. Calling a deliberate dispatch a stockout at the sender, or calling unreceived goods available at the receiver, sends replenishment and sales in the wrong direction. Unmatched dispatches and receipts should stay visible. They should not be forced to balance so the total looks calm.
Acceptance checklist
Replay a full receipt, a shortage, an overage, a transit loss, a cancelled dispatch, a duplicate receipt, and a change of destination after dispatch. At any moment a unit is in the sender, in transit, or at the receiver, not in two of them. Company quantity is conserved. The sender’s sellable quantity falls at dispatch. The receiver’s ordinary sellable quantity does not rise before confirmation. A shortage is not left both in transit and on the receiver’s shelf. In-transit goods that cross a day or a month remain visible by dispatch date and by receipt date, including across a month-end close.
A store manager and the warehouse should be able to place a difference on a store and say whether it is loss or a counting error. If the report does not match the transfer document, the carrier handover, and the store count, fix the events before talking about replenishment. The test is mutually exclusive states, conserved quantity, and sellable rules that match responsibility rules. Fewer stockout alerts are not the test. Creating the next transfer, locking stock, or ordering from a supplier is a separate decision and needs its own check.
Where BI0.AI fits, and where it does not
Pick two stores and one kind of transfer. Put dispatch, transit, receipt, and sellable quantity next to each other for one full cycle. Use that view in a replenishment discussion only after double counting is ruled out. Automatic transfer creation, automatic stock locks, and automatic supplier orders are outside this article. Whether the store system, the warehouse system, and the carrier handover share one transfer document has to be checked on the company’s own paperwork.
BI0.AI can be considered a candidate entry point for small and mid-sized firms that want operating analysis fed by the data they collect. This article does not show that the current release already performs the allocation, in-transit states, or receipt definitions discussed here. Connectors, cost definitions, and any automatic action still have to be verified for the specific project.
Public references
Take the next step with BI0.AI
Talk through a real business scenario and see how governed AI BI can fit your team.
Explore BI0.AI