Multi-Branch Stock Transfer Controls: Dispatch, Receiving and Reconciliation

Why simple stock adjustment is not enough

Reducing stock at one branch and increasing it at another hides what happened during transport. Management cannot see whether goods were dispatched, lost, damaged or still waiting to be received.

A proper transfer creates a traceable movement between two defined locations.

1. Start with a transfer request

The receiving branch or central planning team should state which products and quantities are required. The request should include:

• Requesting branch
• Supplying branch or warehouse
• Product and unit
• Requested quantity
• Required date
• Reason or replenishment rule
• Priority

This separates genuine demand from informal phone instructions.

2. Check availability before approval

The supplying location should confirm available stock after considering reservations, pending orders and minimum stock levels.

The system should not approve a transfer that makes the source branch unable to serve its own committed customers without authorized exception.

3. Use approval limits

Routine transfers may be approved by a branch manager, while high-value, unusual or inter-company transfers may require higher approval.

Approval should be based on value, quantity, product sensitivity or distance—not only the number of lines.

4. Create a pick list

The warehouse team needs a clear document showing product, batch, expiry, rack, unit and approved quantity. Barcode scanning can reduce selection errors where suitable.

The picker should record shortages instead of silently substituting products.

5. Verify before dispatch

A second check can compare picked goods with the transfer document. For high-value items, capture package count, weight, seal number or photos.

Do not allow the same person to request, approve, pick and dispatch every sensitive transfer without management review.

6. Move stock into an in-transit location

At dispatch, stock should leave the source's available quantity but should not immediately become available at the destination. An in-transit status shows that the company still owns the goods while the destination has not confirmed receipt.

This is especially important when transport takes several days.

7. Generate a dispatch note

The document should identify:

• Transfer number
• Source and destination
• Dispatch date and time
• Products, units and quantities
• Batch or serial details where required
• Vehicle or courier information
• Dispatcher
• Approved receiver
• Package count

8. Confirm receipt independently

The receiving branch should count the goods and compare them with the dispatch note. The receiver should not simply click “received” before physical verification.

For batches, expiry dates or serial numbers, verify the exact identifiers.

9. Record differences clearly

Common differences include:

• Short quantity
• Excess quantity
• Wrong product
• Wrong batch
• Damaged goods
• Expired or near-expiry stock
• Package seal broken

The system should record accepted quantity and disputed quantity separately.

10. Resolve discrepancies through an approved process

Do not use a hidden stock adjustment to make the transfer balance. Investigate dispatch records, transport evidence and receiving count.

Resolution may involve acceptance, return, damage write-off, transporter claim or correction after approval.

11. Support partial dispatch and partial receipt

A request for 100 units may be dispatched in two shipments or received on different dates. The software should preserve the original request while showing each movement.

12. Control units and conversions

When one branch transfers cartons and another records pieces, use the product-specific conversion factor. The base quantity must remain consistent.

Our unit conversion guide explains the risks of applying one rule to all products.

13. Track transfer cost where relevant

Management may need transport, loading, insurance or cold-chain costs. Decide whether these costs are recorded separately, added to inventory value or reported operationally.

Accounting treatment should be approved by the business accountant.

14. Protect stock valuation

A transfer should move quantity and value consistently between locations. It should not create artificial profit or change total company stock value merely because goods moved internally.

15. Monitor open transfers

Use an aging report showing transfers that are:

• Requested but not approved
• Approved but not dispatched
• In transit
• Partially received
• Received with differences
• Awaiting closure

Old in-transit stock should be investigated promptly.

16. Reconcile branch stock

Branch-level stock should reconcile with purchases, sales, returns, transfers, adjustments and physical counts. Review both quantity and value.

Repeated differences may indicate training, unit conversion, permission or process problems.

17. Handle returns to warehouse

Branch returns should use a separate controlled transfer reason. Record damaged, excess, seasonal, expired or recalled stock accurately rather than reversing the original transfer informally.

18. Set role-based permissions

Define who can request, approve, dispatch, receive, cancel and close a transfer. Use the POS and ERP permissions guide when designing these roles.

19. Useful transfer reports

• Transfers by branch and product
• In-transit stock value
• Average transfer time
• Short and damaged receipts
• Cancelled transfers
• User activity
• Repeated discrepancies by route
• Products frequently transferred after stockout

20. Test the complete workflow

Before go-live, test full, partial, damaged, rejected and cancelled transfers. Confirm that both branch stock and consolidated company stock remain correct.