- Record the source dispatch
- Confirm the destination receipt
- Resolve the difference once
A transfer should not become new stock for the business or disappear between the sending and receiving branches.
Illustrative decision process, not a product screenshot or customer result.Moving stock between restaurant branches is not the same as buying more stock. The business needs to account for the quantity leaving one location, the quantity accepted at the other and any difference while the movement is unresolved. Without a shared reference and clear responsibility, the same stock can be counted twice or disappear from explanation.
This guide describes a transfer-control method. It does not establish that Restrova provides automatic branch transfers, in-transit stock or every approval feature. Verify those requirements in the actual proposed setup.
Define the source, destination and unit
Use the same item identity and unit at both branches, or an explicitly agreed conversion. Record who authorises the transfer and who receives it. A message saying “send five boxes” is incomplete if the branches use different pack definitions.
Assign one transfer reference that both sides can recognise. Keep the quantity and any supporting document tied to that reference. Customer or staff personal details are not needed in a general stock-transfer analysis.
Work through a simple transfer
Suppose Branch A dispatches 10 kg of an ingredient to Branch B. Branch B physically accepts 9 kg. The one-kilogram difference needs a recorded explanation; it should not be silently added to the destination or deducted twice from the business.
| Transfer fact | Illustrative quantity | Responsibility to agree |
|---|---|---|
| Approved movement | 10 kg | Authorising manager |
| Dispatched from A | 10 kg | Sending branch |
| Accepted at B | 9 kg | Receiving branch |
| Unresolved difference | 1 kg | Named reviewer |
| Final resolution | Based on verified evidence | Authorised decision-maker |
The table describes the operating facts. Ask the supplier how its records represent them and how any in-transit state is handled.
Keep dispatch separate from receipt
The sending branch’s confirmation does not prove the receiving branch accepted the same quantity. Require an appropriate receipt step and a way to report a difference. If the software uses a different workflow, make sure it still preserves accountability for both sides.
Avoid creating a purchase receipt at Branch B simply because stock arrived there. That can inflate business-wide purchasing or stock totals. Use the correct movement type supported by the agreed system and reporting definitions.
Handle timing around a stock count
A transfer may leave one branch before closing and arrive at another afterward. If both branches count at different times, the movement must be reconciled against those boundaries. Otherwise the consolidated result can appear to gain or lose stock.
Record the relevant times and state of the transfer during each count. The weekly count guide explains why a physical observation and a later system balance need a common basis before comparison.
Investigate a transfer difference
Check the unit, dispatch quantity, accepted quantity, container or pack definition and timing. Review whether the item was recorded against the correct identity at both branches. Do not automatically attribute a difference to loss before checking these basic causes.
If an adjustment is approved, record which side changes and why. Avoid allowing both branches to independently “fix” the same discrepancy without coordination. The final business-wide explanation should account for the movement once.
Test access and correction responsibilities
Ask who can initiate, approve, receive and correct a transfer. In a demonstration, use the proposed staff roles rather than a shared administrator account. Test an action that a branch role should not be authorised to perform.
Use the permissions review to define those requirements. If some controls remain manual, document the review owner and decide whether the process is suitable for the volume of transfers.
Reconcile the business-wide picture
Ask how branch and combined reports treat the movement. A transfer changes location ownership of stock; it should not be mistaken for an external sale or purchase in the operating analysis. Confirm the actual report definitions and any accounting treatment through the business’s approved process.
Keep unresolved transfers visible at the end of the period. A clean-looking consolidated number is not useful if staff cannot explain where the stock is or which branch has accepted it.
Verify Restrova’s proposed branch scope
Review Restrova inventory management and multi-branch guidance. The inventory video introduces stock monitoring, not proof of every transfer feature in this guide.
Bring the 10 kg dispatch and 9 kg receipt example to a demo. Confirm the supported process, any manual steps and the agreed commercial scope on the pricing page and in the proposal.
Transfer questions
Is a transfer a new purchase for the restaurant group?
It is an internal movement of stock. Keep the operating records and report definitions distinct from an external purchase, and confirm formal accounting treatment separately.
Can the receiving branch assume the dispatched quantity is correct?
Use an agreed physical receipt check. Dispatch and acceptance are separate facts.
What should happen to an unresolved difference?
Keep it assigned and visible until an authorised review establishes the resolution. Avoid duplicate corrections at both branches.
Related Restrova demonstration
This inventory introduction shows the starting product context for a stock discussion. Verify the particular unit, receiving, permission, counting or transfer requirements in this guide in a live demonstration.
Restrova Inventory Demo | Restaurant Inventory & Stock Management System
Restrova’s inventory demonstration introduces stock items and inventory-level monitoring for day-to-day restaurant supplies.
Watch this demonstration on YouTube · Published
Written overview, not a transcript. Use a live demonstration to verify the specific requirements in this guide.

