Guide · Multi-location stock
Make every warehouse handoff accountable.
Use this checklist when moving stock between warehouses, retail branches or other stockholding locations. It separates the request, physical shipment, receiving observation and final reconciliation.
By the Tellency team · Updated
1. Define the request and the stock owner
Record source and destination, products, units, required quantities, reason and requested date. Identify the requester and the person who approves the movement.
Agree the meaning of each stock status. Determine when the source quantity changes and how in-transit goods are represented in the proposed configuration.
2. Check and record the dispatch
The sending team should confirm the actual products, quantities and relevant lot identifiers before shipment. Record the dispatch reference and the person responsible.
If the requested quantity is 24 but only 20 can be sent, keep the difference visible. Do not change the receiving record to imply a full shipment. Agree whether the remainder needs a separate movement.
3. Have the receiving team record what arrived
Count independently at the destination and record the actual receipt. Note damage, incorrect products and any quantity difference with enough detail for the sending team to investigate.
A transfer of 24 dispatched units with 23 accepted is an exception to resolve. Decide where the remaining unit sits in the records while the issue is investigated. This is an illustrative test, not a customer result.
4. Review posting and reconcile both locations
Tellency transfer orders include approval, shipment, receipt and posting stages. Demonstrate the role and status requirements for each action, and inspect the resulting source and destination records.
Test a duplicate action, an incorrect role and a cancellation at an allowed stage. Agree the correction process after posting rather than deleting the history to hide a mistake.
5. Keep an acceptance record
For your ERP demonstration, record the transfer number, request quantity, dispatch quantity, receipt quantity, discrepancy, approvals and resulting stock balances. Have both warehouse and finance reviewers sign off the scenario.
For transfers between legal entities or countries, add document, ownership and accounting requirements with your advisers. A branch transfer workflow does not establish every cross-border or intercompany requirement.
Your questions, answered
Which roles should we demonstrate?
At minimum, use a requester, approver, dispatch user, receiving user and reviewer. Confirm whether the same person may hold more than one role.
Should the receiving quantity always match dispatch?
Record the actual observation. A difference should trigger investigation and the agreed correction process rather than an artificial matching quantity.
Evaluate Tellency against your own workflows.
Bring your current systems, user count, and operating requirements. We’ll discuss the fit, migration scope, deployment, and total cost.
Book a personalised demo