Warehouse operations
A clear handoff, from receiving to the next location.
Organise warehouses and locations, record receipts and control transfers in Tellency. Give warehouse teams a working record that connects to purchasing, stock reporting and finance.
By the Tellency team · Updated
Start with the warehouse structure
Tellency includes warehouse and warehouse-location records. Map your actual stockholding locations before loading balances: central stores, retail branches, production areas and other physical stock points.
Agree product identifiers, units and the responsibility for each location. Use the same structure in receiving, transfers and counts so the quantity being discussed has an unambiguous physical meaning.
Separate an expected receipt from accepted stock
A purchase order records a commitment; a receipt records what arrived. Demonstrate the goods-receipt process with a partial delivery, the intended destination and any lot or expiry requirements.
Identify what happens when the delivery is damaged or the quantity differs. Define who records the issue and how purchasing resolves it before the supplier bill is accepted.
Follow dispatch and receipt as separate events
Transfer orders support approval, shipment, receipt and posting. A warehouse dispatcher and a receiving branch should be able to demonstrate their own actions and review the same movement.
Use an illustrative transfer of 24 units, with 23 accepted at the destination. Agree how the missing unit is investigated and corrected. The example is a test scenario, not a claim about a customer deployment.
Build a repeatable count process
Cycle counts let the team plan and record counts, complete them and seek review. An approved count can create a draft adjustment. Review the adjustment through its own posting controls.
Choose high-value, fast-moving or discrepancy-prone products for the first count programme. Document the count cut-off, stock movements during the count and the person responsible for reconciliation.
Connect the warehouse without assuming every WMS feature
Use the shared ERP records to review purchasing and stock movements alongside sales and production requirements. Demonstrate the exact financial posting and inventory reports expected at the end.
If you need wave picking, handheld scanner workflows, label printing, automated storage, carrier labels or advanced slotting, bring those requirements to discovery. The implementation scope should identify supported configuration, integrations and any additional work.
Your questions, answered
Is this a standalone warehouse system?
This page covers warehouse operations within Tellency ERP. Compare your requirements against the demonstrated receiving, location, transfer and count workflows.
Can warehouse staff and branch staff have different permissions?
Tellency includes role permissions and approval workflows. Demonstrate the intended access for each role and location before accepting the configuration.
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