Dispatch and receipt answer different questions
For a small business with two shops, the transfer is not complete just because the sending shop prepared a box. The dispatch record answers what was handed over, when, and to whom. The receiving record answers what arrived in acceptable condition. A difference between the two needs its own review; changing the dispatch quantity to make the numbers agree hides what happened.
This guide follows a fictional East African shop moving stock between its town-centre and market branches. The method can help teams elsewhere in English-speaking Africa, the UK, and other markets, but local document, tax, transport, and accounting requirements should be checked with the appropriate adviser. This is a physical-control procedure. Valuation and accounting entries remain subject to the business’s approved policy and accountant.

Keep the request, dispatch count and handover evidence tied to one transfer reference.
A fictional transfer from request to arrival
The market branch requests 12 units of item SKU-204, a rechargeable lantern. The stockkeeper at the town-centre branch picks 12 and counts them against the authorised request TR-581. Before dispatch, one unit is found cracked and is put aside. The source therefore records 11 units dispatched, not 12. The supervisor approves the changed quantity or asks for a revised request, according to the business’s own authorisation rule.
The stockkeeper records the count, time, handover person or carrier, and any dispatch reference. At the market branch, another staff member counts the arriving stock before it is added to available stock. If 10 usable lanterns arrive, the receipt shows 10 accepted and a shortage of 1 against the dispatch. It does not overwrite the dispatch record.
Prepare, dispatch, then verify
Before the goods leave
Use a transfer request that identifies the source and destination, item or SKU, requested quantity, reason, requester, and approving person if approval is required. Pick and count against that request. Record substitutions separately and get approval before sending them; a similar-looking item is not necessarily the same item.

Count the stock against the approved request before the goods leave the source location.
At handover
The dispatch entry should be made at the source location and retain the request reference. Record the quantity actually handed over, date and time, person releasing it, person or carrier taking custody, and any seal, waybill, or other evidence reference used by the business. If the count changes before handover, record why and who approved the change.
On arrival
Count before shelving or making the items available for sale. Record accepted quantity and condition. Keep shortage, damage, wrong item, and unapproved substitution as distinct exception types. Attach or reference evidence such as a receiving note or delivery photo where appropriate, following the business’s privacy and retention rules.

At arrival, record what was accepted and route any difference to a named reviewer.
Assign each difference to a named reviewer. The transfer stays open until the reviewer records a disposition, such as locating the missing item, approving a correction, arranging a replacement, or documenting another decision under company policy. The reviewer should not silently edit the original dispatch record.
Transfer reconciliation slip
Use this paper or digital worksheet as a control aid. It does not prescribe inventory valuation or accounting treatment.
| Field | Entry |
|---|---|
| Transfer reference / date | ______________________________ |
| Source / destination | ______________________________ |
| Item reference and description | ______________________________ |
| Requested / authorised quantity | ______________________________ |
| Picked quantity and condition | ______________________________ |
| Dispatched quantity / time | ______________________________ |
| Handover person / carrier / evidence reference | ______________________________ |
| Quantity received / accepted | ______________________________ |
| Variance and condition notes | ______________________________ |
| Evidence reference | ______________________________ |
| Reviewer / decision / date | ______________________________ |
| Closure status | Open / resolved / other: __________ |
Reconcile each line: requested, dispatched, and accepted quantities should remain visible as separate facts. If a line has a variance, record its owner and next action rather than closing it as a routine receipt.
Adapt the record to each market
For teams across English-speaking Africa, agree consistent branch identifiers and decide whether the transfer reference works across sites with intermittent connectivity. In the UK or another market, check local transport paperwork, record retention and any applicable reporting requirements with a qualified local adviser. The worksheet deliberately uses no currency, tax rate, or valuation method.
How Maduuka supports stock transfers
Maduuka supports multi-warehouse stock tracking and stock transfers, including separate dispatch and receipt confirmation and review of a short or damaged arrival. Visit the Maduuka website for product details.
Bring a redacted branch-transfer example to a Maduuka demonstration and discuss how the workflow fits your locations. Maduuka with Chwezi
Sources and scope
The worksheet and procedure are editorial guidance for physical movement evidence. Microsoft Dynamics 365 documentation describes outbound shipment and inbound receipt in that product’s inventory context; it is an example, not a universal rule for every system. Microsoft Learn: Transfer inventory between locations
This article covers physical movement evidence and does not prescribe an accounting entry, valuation method, or national rule. The proposed search phrases are hypotheses, with no search-volume or ranking claim.