A central kitchen can record a complete dispatch while an outlet records a smaller usable receipt. I would reconcile those records before treating the difference as a loss.
Start with the same transfer reference and unit of measure. Establish what physically arrived and what the receiving team recorded. An unexplained balance should remain visible until the evidence supports a correction.
This is a practical operating review. The example below is illustrative and does not describe a client result.
Compare the same movement
Two quantities are only comparable when they refer to the same item and delivery. If the kitchen records cartons while the outlet records packs, first confirm the conversion used for that item. A familiar product name is not enough to establish that both teams counted on the same basis.
The receiving team should check the physical delivery against the record. BCcampus describes counting or weighing incoming goods as part of receiving discipline. Foodservice inventory guidance.
I would retain dispatch and receipt as distinct records connected by one transfer reference. This makes disagreements visible without overwriting either original record. ERPNext documents separate movements through transit stock as one software example; the operating requirement applies whichever system you use. Stock entry documentation.
A worked reconciliation example
Suppose a kitchen records 120 sealed packs dispatched to one outlet. The receiving check produces the following record.
Illustrative receiving check| Receiving evidence | Quantity |
|---|
| Usable packs physically received | 116 packs |
|---|
| Damaged packs received and segregated | 2 packs |
|---|
| Difference still unexplained | 2 packs |
|---|
120 dispatched = 116 usable + 2 damaged + 2 unexplained
The gap against usable stock is four packs. Two of those packs are physically present but damaged. Only the remaining two packs are unexplained. The damaged packs need a recorded disposition under the organisation’s procedure. The unexplained packs need investigation.
Do not reduce usable stock for damage and then deduct those same packs again through a later disposal entry. The records should show where the packs are and how an authorised decision changes their status. Nothing in this example establishes theft or identifies a responsible person. Do not invent an explanation just to close the record.
Give the receiving record enough context
I would include these fields so another person can follow the movement without reconstructing a chat conversation. These are proposed operating fields, not a claim that every software package uses the same structure.
| Record area | Information to retain |
|---|
| Identity | Transfer reference, item and batch |
|---|
| Movement | Source, destination and both timestamps |
|---|
| Comparison | Common unit and dispatched quantity |
|---|
| Receiving result | Usable quantity, segregated quantity and unresolved balance |
|---|
| Investigation | Evidence reference, investigation owner and decision due time |
|---|
| Closure | Confirmed reason, authorised approver, correction reference and closed time |
|---|
Check the reporting cutoff
A delivery leaving the kitchen before a reporting cutoff may reach the outlet after it. The records can disagree at that moment without establishing a physical shortage. Compare timestamps before treating that movement as a loss. Retain a visible transit status where the workflow supports it.
Incorrect transfers and count mistakes are among the issues discussed in Fourth’s software-specific guidance. I would examine the underlying transaction and avoid forcing a transfer closed simply because a report is due. Stock reconciliation guidance.
Separate recording from adjustment authority
The dispatcher records what leaves. The receiver records what arrives. I would assign an inventory owner to investigate the difference and assemble evidence. A different person with the required authority should review and approve any proposed correction. Keep the reason and approval linked to the original difference.
In the illustrative example, the two unexplained packs remain open. Identify who will retrieve the evidence and when the result will be reviewed. A later correction should refer back to that original difference.
Test the method on one route
I would test one delivery route for five working days. This is a proposed trial period, not a universal standard. Record unresolved transfers and the effort spent checking them. Review whether the record helped someone make a sound decision. If every delivery still requires searching several conversations, the handoff itself may need improvement.
AI can be evaluated for matching references and flagging differences. The explanation still requires human verification. An AI suggestion should never become a stock adjustment merely because it sounds plausible. Include human checking and correction time when assessing any improvement.
Read the broader AI and operational transformation guide.
If your kitchen and outlet records keep disagreeing, bring one transfer to an operational needs conversation.
Discuss an operating need