An ERP inventory management module records every stock movement (receipt, issue, transfer, adjustment and sale) against an item, a location and often a batch or serial number, and posts the value of each movement to the general ledger. Done well, the quantity in the warehouse, the quantity in the system and the inventory balance in the accounts all agree.
That three-way agreement is the real test of an inventory module. Plenty of tools can count boxes; fewer keep the count, the location and the money in step through returns, transfers, write-offs and price changes. This guide covers the decisions that matter when you specify, configure or build one: valuation, reorder logic, cycle counts, traceability and multiple warehouses.
What should an ERP inventory module do?
At minimum, it should maintain a perpetual record of quantity and value by item and location, and drive purchasing and sales from that record. Everything else builds on that foundation.
| Capability | What it means | Who relies on it |
|---|---|---|
| Item master | Codes, units of measure and conversions, categories, costing method, tracking rules | Everyone |
| Locations | Warehouses, zones and bins, plus in-transit and quarantine locations | Warehouse, finance |
| Stock movements | Receipts, issues, transfers, adjustments, returns, each with a reason code | Warehouse, audit |
| Valuation | Cost per movement, posted to the ledger automatically | Finance |
| Replenishment | Reorder points, min and max levels, suggested purchase or transfer orders | Purchasing |
| Counting | Cycle counts and full counts with variance approval | Warehouse, finance |
| Traceability | Batch or lot and serial numbers, expiry dates, supplier origin | Quality, customers |
| Reporting | Stock on hand, ageing, slow-moving stock, valuation, turnover | Management |
If your stock processes are unusual, for example made-to-order components, consignment stock or regulated batches, a module designed around them is often the deciding factor. Our ERP development service builds individual modules like this, and manufacturers can see how production and stock fit together on our manufacturing ERP software page.
Which inventory valuation method should an ERP use?
Use the method your accounting framework allows and your accountants approve, and configure it per item group before go-live. Changing the method later is an accounting event, not a settings tweak.
What the standards say (checked October 2026):
- IFRS (IAS 2 Inventories), used widely in the UK and UAE, measures inventory at the lower of cost and net realisable value. The cost formulas it names are specific identification for items that are not ordinarily interchangeable, and first-in, first-out (FIFO) or weighted average cost for items that are. Last-in, first-out (LIFO) is not among them.
- US GAAP (ASC 330), as amended by FASB's ASU 2015-11, measures inventory valued with FIFO or average cost at the lower of cost and net realizable value. LIFO is permitted under US GAAP, and inventory measured with LIFO or the retail inventory method stays on the lower of cost or market rule.
UK companies reporting under FRS 102 rather than full IFRS should confirm the permitted methods with their accountants.
| Method | How the ERP calculates cost | Good fit | System implications |
|---|---|---|---|
| FIFO | Issues consume the oldest cost layers first | Perishables, items with changing purchase prices | Must store cost layers per receipt; heavier data |
| Weighted average | Recalculates average unit cost after each receipt | Interchangeable commodities, high volume | Simpler; sensitive to back-dated receipts |
| Specific identification | Each unit carries its own cost | Serialised, high-value or unique items | Requires serial tracking on every movement |
| Standard cost | Fixed cost per item, variances posted separately | Manufacturing with stable routings | Needs a process to review and update standards |
| LIFO (US GAAP only) | Issues consume the newest cost layers first | US companies that have chosen it with their tax advisers | Not available under IFRS; layer tracking required |
Two design points cause most of the trouble. First, landed costs: freight, duty and insurance should be added to the item cost when they are known, and the system needs a way to apportion them across receipt lines. Second, back-dated transactions: a supplier invoice at a different price, entered after stock has been sold, changes cost of goods sold. Decide in the specification how the module revalues stock already issued.
Net realisable value is a judgement, not a calculation the ERP can make alone. A good module supports it by reporting slow-moving and expired stock so finance can decide write-downs.
How should reorder points and replenishment work?
A reorder point triggers a purchase or transfer suggestion when available stock falls to a level that covers demand during the supplier lead time, plus a safety buffer. The ERP calculates it; people should still review it.
The basic formula is:
Reorder point = average daily demand multiplied by lead time in days, plus safety stock
Illustrative example (hypothetical figures): an item sells about 20 units a day, the supplier delivers in 10 days, and the business keeps 60 units as safety stock. The reorder point is 20 times 10 plus 60, which is 260 units. When available stock (on hand, minus reserved, plus already on order) drops to 260, the ERP suggests a purchase order.
Specification decisions to make:
- Available, not on hand. Calculate against stock on hand minus quantities reserved for sales orders, plus open purchase orders. Using on-hand alone causes duplicate orders.
- Demand source. Use history for stable items and sales or production forecasts for seasonal or project-driven items.
- Order quantity. Fixed quantity, up to a maximum level, or rounded to supplier pack sizes and minimum order quantities.
- Per location. Each warehouse needs its own reorder settings; a central warehouse may replenish branches by transfer before anything is bought.
- Review cycle. Reorder parameters go stale. Schedule a quarterly review, with exceptions flagged automatically.
Suggestions should flow into purchasing, where approval rules apply. Our guide to the ERP procurement module covers that side.
How do cycle counts keep inventory accurate?
Cycle counting means counting a small set of locations or items every week instead of the whole warehouse once a year. It finds errors while their cause is still traceable.
A common approach is ABC classification: rank items by value or movement, count the high-value A items most often, B items less often and C items least. The ERP should:
- Generate count lists by class, location or item, without showing the expected quantity to the counter (a blind count).
- Freeze or flag movements on the location while it is counted, or record the count time so later movements are excluded.
- Calculate variances in quantity and value.
- Route variances above a threshold to a supervisor for recount or approval.
- Post approved adjustments to the ledger with a reason code.
- Report variance trends by item, location and reason, so the root cause gets fixed.
When do you need batch, lot or serial tracking?
Track batches or lots when you must recall or trace a group of units made or received together, and serial numbers when each unit must be traced individually. If customers, regulators or warranties require traceability, it has to be designed in from the start.
- Batch or lot: food, chemicals, pharmaceuticals, cosmetics, anything with an expiry date. The ERP should support first-expiry-first-out picking and block expired stock.
- Serial: equipment, electronics, anything with a warranty or service history.
- Both directions: you need forward tracing (which customers received this batch) and backward tracing (which supplier batch went into this product).
Adding tracking after go-live means re-labelling stock and reconciling history, so decide early. If you are moving from spreadsheets, our ERP data migration plan explains how to load opening stock by location and batch.
How should an ERP handle multiple warehouses?
Treat each warehouse as a set of locations with its own stock, reorder settings and permissions, and make transfers between them a two-step movement through an in-transit location.
Multi-warehouse design checklist:
- Location hierarchy: site, warehouse, zone, bin, agreed before configuration
- In-transit location so stock is never counted in two places or none
- Transfer orders with dispatch and receipt confirmation, and discrepancy handling
- Inter-company transfers if warehouses belong to different legal entities, with transfer pricing agreed by finance
- Location-level user permissions, so a branch sees and moves only its own stock
- Reservation rules: which warehouse fulfils which orders
- Valuation by warehouse or across the company, agreed with your accountants
- Barcode or mobile scanning for receipts, picks and counts
- Reports: stock by location, ageing, slow movers, transfer variances
Distributors face extra questions about pick-pack-ship, drop shipping and channel stock. Our sibling guide on ERP for distribution companies covers them.
When is an ERP inventory module not the right approach?
A full ERP inventory module is more than you need when stock is simple, low in value or managed elsewhere.
- Single-location retail with few lines: a point-of-sale system with built-in stock may be enough.
- E-commerce only, outsourced fulfilment: the fulfilment provider's system is the stock record; integrate it rather than duplicate it.
- Service businesses with consumables: expensing small purchases is often simpler than tracking them.
- No discipline at the warehouse door: if receipts and issues are not recorded when they happen, no module will be accurate. Fix the process first.
Specialist warehouse management systems also exist for high-volume operations with complex picking. In that case, the ERP keeps the financial stock record and the warehouse system manages the floor.
How to start: specifying your inventory module
Write down how stock moves today before choosing or designing anything. Prepare:
- Item count, item groups and units of measure
- Locations and how stock moves between them
- Valuation method agreed with your accountants
- Traceability requirements and who imposes them
- Current count accuracy and the biggest sources of variance
- Reports finance and operations need each month
Our software requirements brief template structures these answers. Then discuss the project with us. Timeline Digital builds 2 to 3 key modules as a free pilot before the full project starts, and inventory is often one of them because its accuracy is easy to measure.