Restaurant Inter-Branch Stock Transfer: Request, Dispatch, Receipt and Discrepancies
A process guide to inter-branch stock transfers covering request, approval, dispatch, stock in transit, partial receipt, discrepancies and sensitive goods.
- Bahram Davoodi
One restaurant branch may run short while another has surplus stock. An unrecorded transfer makes both locations inaccurate and weakens accountability.
Core workflow
- The destination raises a request.
- The source checks available stock and safety stock.
- The approved quantity is picked and dispatched.
- The goods move into an in-transit status.
- The destination counts and inspects the delivery.
- Differences are recorded on the same transfer before closure.
Keep three quantities separate
A complete transfer has requested, dispatched and received quantities. They may differ and must not overwrite one another. The history should show who changed a quantity and why.
Stock in transit
Dispatched goods should leave usable stock at the source but should not become free stock at the destination until receipt is confirmed. This prevents double counting.
Partial and multi-stage deliveries
If ten packs are sent today and the remainder later, each dispatch should be a separate record linked to the original request. The destination should see open, in-transit and received quantities.
Sensitive goods
For food items, batch, expiry, packaging condition and transport requirements may need checking. Damaged or unacceptable goods should remain under review rather than entering usable stock.
Roles and approval
- Authorised destination user requests stock.
- Source manager approves dispatch.
- Destination user records receipt.
- A restricted role approves discrepancies or corrections.
Practical scenario
A branch requests 12 packs. The source can dispatch 10. The destination receives nine sound packs and one damaged pack. Nine enter usable stock, the damaged pack stays under review and the difference remains attached to the transfer.
Management indicators
- Request-to-dispatch and dispatch-to-receipt time
- Share of transfers with discrepancies
- Frequently transferred items and branches
- Value of stock in transit
- Transfers caused by weak purchasing or forecasting
How Lonio can help
Depending on the confirmed configuration, Lonio can support warehouses, stock history, scoped permissions and reports. In-transit status, approval rules, batch tracking and automated stock movements must be validated in the live setup.
Conclusion
A stock transfer is a two-sided process: confirmed issue from the source and confirmed receipt at the destination.
Frequently asked questions
When is a stock transfer complete?
After the destination counts and confirms the quantity and condition of the goods.
How should stock in transit be shown?
It leaves usable stock at the source but does not become free stock at the destination until receipt.
How is a partial receipt recorded?
Received, open and later dispatch quantities are recorded separately but remain linked to the original request.
What happens to discrepancies or damaged goods?
They stay on the same transfer with actual quantity, reason, acceptance status and review owner.
