Dispatched is not the same as received at the outlet
For Inventory managers and supply-chain heads · Plan implementation
TL;DR — what you’ll learn
- Record dispatch and outlet receipt as separate events with stock visible in transit.
- Keep short receipts open until the missing quantity has an explained outcome.
- Distinguish physically received food from stock approved for service.
- Use stable transfer references so late or duplicate mobile submissions cannot create extra stock.
At 6 a.m. the kitchen sends 120 meal trays. The outlet signs for 116. The kitchen's application has already increased outlet stock by 120, so the outlet starts the day with four trays it cannot sell. A nightly integration will make the same mistake faster unless the transfer model changes.
How do you reconcile central kitchen transfers when an outlet receives less than dispatched?
Use a dispatch event and a separate receiving confirmation, with stock visible in transit between them. Record shortages and condition exceptions against the original transfer. Close the discrepancy only when its agreed resolution has been recorded.
- 01Create the transferSource, destination and units
- 02Dispatch the stockActual quantities and lots
- 03Record the receiptAccepted and disputed quantitiesDo dispatch and receipt agree?YesReconcile the transferNoAssign the discrepancy; do not manufacture a matching receipt.
- 04Reconcile the transferResolve the in-transit balance
Illustrative information flow. The article explains the evidence, exceptions and responsible decisions. Diagram: NextEdge Labs.
Keep the unconfirmed quantity visible
For this illustrative transfer, dispatch reduces the sending location by 120 and places 120 in transit. Receiving confirms 116 at the destination. Four remain unresolved until the team records whether they are still with the vehicle, received elsewhere, damaged or missing. Do not label all four as waste simply to close the transfer.
ERPNext documents a transit option for stock transfers. Whatever product you use, check that the receiving step can report an actual quantity and retain the original dispatch quantity. Replacing one number with the other destroys the comparison.
Source: Frappe / ERPNext · Material transfer and add-to-transit handling. Reference details
Give the receiver a practical screen
Show the expected items and units, but allow an exception with a reason and supporting evidence. Identify the receiving person and time. A tray, tub and kilogram are not interchangeable quantities; use the agreed unit for each product and make conversions explicit.
Condition decisions require their own status. An outlet may physically receive a tray that is not available for service. A signed delivery record should not automatically make all received food unrestricted stock.
Handle a late receipt without changing yesterday silently
An outlet may receive food before opening and enter the confirmation hours later. Store both the receiving event time and the submission time. The stock view should make pending transfers visible so staff do not interpret an unconfirmed delivery as either definite stock or definite loss. Define how a late confirmation affects the outlet's daily reconciliation.
If the outlet has already closed the day's count, the correction needs a controlled path. Preserve the original count and the late transfer evidence rather than silently recalculating the old record. This is especially important when the same daily figures feed food-cost reporting or responsibility discussions. A date field alone does not establish when the business knew about the receipt.
Split a delivery across destinations explicitly
Consider a vehicle carrying an illustrative 120 trays for Outlet A and 80 for Outlet B. A route change sends twenty of A's trays to B. The transfer record needs an authorised redirection of those twenty trays, including their lot and the two affected destination balances. If the driver simply edits A's dispatched quantity to 100, the original kitchen handover becomes difficult to reconcile.
Record what each outlet actually receives. The route change may alter selling windows or customer commitments, so the relevant operational checks still apply. A transport note is helpful evidence, but it should connect to the stock movement. The vehicle's total quantity can balance while both outlet records are wrong if destination changes are not represented.
Give busy outlets an exception-first confirmation
A receiver should be able to confirm the expected delivery quickly and enter a difference without navigating a full ERP transaction. Show product, unit, expected quantity and lot or handling-unit identity where required. Offer clear options for short quantity, extra quantity, damaged or restricted goods, and an item that was not expected. Keep free text available for circumstances the reason list misses.
Separate a receiver's observation from the eventual resolution. The person opening the outlet may be able to report four missing trays but may not know whether they remained in the kitchen or went to another stop. Route the investigation to the accountable team. Closing the form should confirm that the observation was saved, not imply that the difference has been settled.
Use a dashboard that shows unfinished handovers
Group unresolved transfers by route, outlet, age and reason. Distinguish a missing confirmation from a confirmed shortage so the supervisor knows which conversation is needed. Review repeated patterns, such as one route regularly arriving after the receiving window. The integration has succeeded when teams can settle those handovers with evidence and use the corrected stock for the next replenishment decision.
Build the pilot around unresolved transfers
Connect one kitchen and a small set of outlets. Preserve a stable transfer ID across dispatch, driver handover, receipt and correction so retries cannot create a second receipt. Assign overdue confirmations to an owner, with a sensible escalation based on the operating schedule.
Measure outstanding quantities, the age of unresolved transfers and correction time. Reconstruct a partial receipt and a duplicate mobile submission during acceptance testing. An assessment can begin with a dispatch sheet, the receiving format and the current stock export; customer names and sensitive commercial details can be removed before sharing.
Summary
A transfer is complete when the receiving record and any discrepancy explain the dispatch. Automatic stock updates should preserve that handover. In-transit visibility, practical outlet confirmation and an owned exception queue provide a reliable base for central-kitchen replenishment.
What to do next
- Reconcile yesterday's dispatch quantities against each outlet's actual receipt.
- Identify who owns unconfirmed quantities at every stage of the route.
- Test a short receipt, a damaged receipt and a duplicate submission before connecting more outlets.
Scope this automation around your operation
Tell us your current systems, transaction volume and the exception you need to resolve. We can discuss a bounded first release, its review controls and how to measure the result.
Sources and further reading
Sources checked 15 October 2026. The worked examples and software evaluation suggestions are NextEdge Labs’ editorial analysis.
- Stock EntryFrappe / ERPNext · Online product documentation, accessed October 2026
Examples of distinct material receipt, issue, transfer and manufacturing transactions, including transit handling.
Visual credits
AI-generated illustration created for NextEdge Labs; it does not depict a client facility. Workflow diagram by NextEdge Labs. Icons from Lucide (ISC licence).
