Moving goods without a transfer record
Consequence: One branch shows stock it no longer has, while another appears short.
Solution: Record both the sending and receiving sides of each transfer.
A practical business example
A retailer receives 200 items and transfers 80 to a second branch. That branch sells 25 and receives two customer returns. If there are no other movements, its expected stock is 57. Use this example to explore transfers, returns and reconciliation.
Follow the process
- Check products and quantities when receiving stock.
- Record dispatch and receipt for branch transfers.
- Record sales and inspect returned goods.
- Compare stock counts and payment totals with recorded transactions.
Problems, consequences and solutions
Returning damaged goods to saleable stock
Consequence: Staff may sell an item that should have been held for inspection.
Solution: Check the returned item and record its condition and intended handling.
Combining all payment types into one total
Consequence: Cash discrepancies become difficult to distinguish from card or bank settlement timing.
Solution: Reconcile each payment method against its supporting records at daily close.
Work through a complete example
Use these illustrative cases to evaluate the workflow with the demonstration team. Confirm the available screens, controls and configuration for your scope.
Follow the quantities and amounts
Branch B receives 80 items, sells 25 and receives two returns. Its physical total is 57 if there are no other movements. If one return is damaged, only 56 are potentially saleable before reservations or other holds. Quantity reconciliation and saleable availability answer different questions.
Read the visual: compare each document or stage separately, then follow the reconciliation shown beside it.
Branch stock reconciliation
80Received
25Sold
2Returned
80 − 25 + 2 = 57 physically held
Inspect the two returns
56Potentially saleable
1Damaged / hold
57 physical items ≠ 57 saleable items
Documents and team handovers
- 01
Receiving and transfer
Count branch receipts against dispatch evidence and investigate transfer shortages.
- 02
Sales and returns
Retain the sale reference, returned quantity, item condition and approved refund or exchange decision.
- 03
Daily close
Reconcile each payment method and review stock differences with a clear cutoff and responsible reviewer.
When the normal process changes
Case 1: A transfer arrives short
Problem / consequence
The sending and receiving branches disagree about ownership of the missing goods.
Correction / prevention
Retain dispatch and count evidence, investigate the difference and approve any correction.
Case 2: A card settlement arrives later
Problem / consequence
The cashier's close is confused with the bank's settlement date.
Correction / prevention
Track the payment-method evidence and reconcile timing differences separately from cash shortages.
Case 3: A customer exchanges a product
Problem / consequence
Recording only a refund or only a new sale hides part of the stock movement.
Correction / prevention
Review the original item, replacement item and any price difference together in the demonstration.
Responsibilities, reports and controls
Modules to explore
Inventory, Sales, Purchasing and Finance. Confirm POS, barcode, payment-terminal and offline needs separately.
Reports to request
Branch stock, transfers, returns and payment-method reconciliation for a selected business day.
Implementation decisions
Agree units, branch ownership, damaged-stock handling, price/discount authority and daily-close responsibility.
Ask to see these cases in your demo
- Explain 57 physically held and 56 potentially saleable after one damaged return.
- Trace an interbranch transfer and a customer exchange.
- Reconcile cash and non-cash payments without hiding settlement timing differences.
Agree the results and any limitations in the implementation scope before launch.
Plan around your business
Bring sample documents and one difficult exception. We can use these to discuss required modules, setup, responsibilities and acceptance criteria.
See the implementation approach →
Request a Retail Demo