A practical guide for operations leads: follow stock from replenishment and receipt through holds, reservations, picking, dispatch and reconciliation.
Inventory management is the work of deciding what stock to buy and hold, recording what happens to it, and keeping it available for the orders or production that need it. It connects purchasing decisions with receiving, storage, use, dispatch and the checks that keep the records trustworthy.
For an operations lead, its practical job is to make the next decision dependable. A buyer needs to know whether to reorder. A salesperson needs to know what can be promised. A picker needs to know where to find stock they are allowed to take. Each can need a different answer about the same goods.
Stock management is often used to mean much the same thing. Stock control usually describes the narrower work of maintaining accurate quantities, locations and movements. The boundaries overlap, but inventory management also includes demand, replenishment and the cost of holding stock.
Follow the stock through the business
The process begins before a delivery arrives and continues after an order leaves. The following stages are a useful way to follow that work; businesses divide responsibilities differently.
Decide what to replenish
Review expected demand against usable stock, existing commitments and expected receipts. Supplier lead times affect when to order; storage costs and the risk of deterioration affect how much to hold. Buying more can reduce a shortage risk while leaving cash tied up in goods that do not move.
Record the item, quantity, unit of measure and expected delivery against the purchase order. That gives receiving a delivery to check and planning a supply expectation to revisit if the supplier is late. Raising an order does not put those goods physically on hand.
Receive and check
Count what arrives and inspect it as the product requires. Record the actual receipt, including shortages, damage and any stock awaiting a check. Where batches or expiry dates matter, capture those details against the goods received.
The next decision is whether that stock can be used or sold. Recording an entire delivery as available before the required inspection is complete makes a promise the receiving process has not yet justified. A partial delivery must also leave the outstanding quantity visible to purchasing.
Put away and preserve
Move goods into suitable storage and confirm the destination. The record needs enough detail to find the right item in the right quantity, including its location and condition. A case and an individual unit must not become interchangeable numbers.
Subsequent movements need confirmation too. Moving goods between locations inside a warehouse changes where stock is held without changing the warehouse’s physical total. Stock in reserve storage may still need a confirmed replenishment into a picking location before a picker can use it.
Allocate, use and dispatch
Allocation decides which demand stock will serve. A reservation records that commitment without moving the goods. Picking then moves the selected stock towards fulfilment; production may instead consume materials and record the output separately.
Record what people actually take, including short picks or substitutions permitted by the process. Picking goods into dispatch staging still leaves them on the premises. The business needs a defined dispatch event so warehouse completion and the stock record agree about when goods have left. Cancellation needs a corresponding decision about releasing any reservation.
Count, reconcile and improve
Compare physical counts with records, investigate differences and record authorised corrections with a reason. A count can establish that a location is short. It cannot, by itself, establish whether the cause was an unrecorded movement, a receipt error or an incorrect unit conversion.
Use the investigation to change the failing step. Returns need a defined route back through receiving and checking, often into quarantine until someone decides their condition. Stock that comes back is not automatically sellable. Counts, returns and actual usage also inform the next replenishment decision, so the cycle continues.
Why 100 on hand can mean 50 available
Consider an illustrative wholesaler receiving 100 units of one item into a single location. Ten need an inspection and are held. The other 90 are eligible for sale, and 40 of those are reserved for existing orders.
The wholesaler’s policy allows new promises only against eligible physical stock that has not already been reserved. The held ten are separate from the reserved forty. Under that policy, 100 minus 10 minus 40 leaves 50 units available to promise.
Event completed | Physically on hand | Held for inspection | Reserved for existing orders | Available for new promises |
|---|---|---|---|---|
Receipt, hold and reservation recorded | 100 | 10 | 40 | 50 |
Inspection passed and hold released | 100 | 0 | 40 | 60 |
Reserved 40 dispatched | 60 | 0 | 0 | 60 |
Passing inspection releases the ten held units for sale. Nothing arrives or leaves, so on-hand stock stays at 100. Existing orders still have their forty reserved units; the quantity available for new promises rises to 60.
For this example, the wholesaler records dispatch when it confirms the goods have left its premises. Dispatching the reserved forty reduces physical stock to 60 and clears their reservation. Availability remains 60 because those forty were already excluded from new promises.
This example excludes incoming supply, safety stock, sales channels and other demand. Real availability policies may include further conditions, such as a customer’s required remaining shelf life. An available-to-promise figure needs a declared policy and time horizon. It is not a universal subtraction formula.
Check whether your system’s categories overlap before subtracting them. A figure labelled unavailable may already include reserved stock; subtracting both would remove the reservation twice. Also check the scope of each number: item, warehouse, location, batch and unit of measure. A warehouse total cannot tell a picker which shelf to visit.
Find the break between the task and the record
The wholesaler could count all 100 units correctly and still make a wrong promise. If the inspection hold never reaches the availability calculation, sales could promise goods that have not been cleared. If a reservation is recorded late, two orders could each be promised the same stock. Another count would not resolve either recording failure.
When investigating a shortage, follow the events behind the number. Establish which rule makes stock eligible, who confirms that rule has been met, and which record changes when they do. Then check whether the person making the next decision sees that change in time.
Inventory records, warehouse execution and financial valuation answer different questions. A quantity and movement history explains what the system believes happened. Warehouse instructions tell someone what to move next and how to confirm it. Financial valuation determines the monetary value assigned to inventory. A system may support all three, but a ledger or stock list alone does not direct a replenishment task. Our guide to choosing warehouse management software explains how to assess support for that work.
Shape the system around the work
Keel is an operations platform shaped around how a business needs to work. For inventory, that means connecting the receiving and release process with the experience of the people promising and picking stock.
In an implementation of this example, the receiver would record the delivery and hold. The person responsible for inspection would complete the release check, and the people allocating stock would see the resulting availability. The release requirement would live in the same operational system as the task used to complete it, with reporting to show stock still awaiting inspection.
Keel supports tailored operator tools, workflows that combine human input with processing steps, and business rules expressed in code. Those capabilities let the implementation change the release check and the team’s working screens together as the process improves. The stock movements, eligibility rules, reservations, permissions and integration behaviour still need to be defined and tested. The example describes a proposed implementation. Keel leads implementation and agrees the handover with your team.
If your existing system captures these distinctions and people can execute the process reliably, improving that process may be enough. Remove avoidable steps before reproducing them in new software. Where your operation needs its own rules and task interfaces to evolve together, talk to Keel about your receiving-to-dispatch process. Bring one stock journey, including the point at which goods become available and the event that confirms they have left.
