Inventory management process map

A swimlane map of the inventory cycle (receipt, stock records, replenishment, cycle counting, and review and write-off) across the warehouse, the inventory controller, production, procurement and finance. It is a map of a loop rather than a line, which is what makes inventory hard to describe in a list.

Open this map in the editor

Opens a copy in the editor and saves it in this browser. No account, nothing sent anywhere.

What is in this map

20 steps across 5 swimlanes and 5 phases, with 3 decision points.

Swimlanes (who does the work): Warehouse, Inventory controller, Production, Procurement and Finance
Phases (left to right): Goods receipt, Stock records, Replenishment, Cycle counting and Review and write-off

Why map this process

Inventory is not a process with a beginning and an end; it is a set of routines that keep a record and a warehouse in agreement. Replenishment triggers off the record, cycle counting corrects the record, write-off reconciles the record with reality one last time. Drawn as a sequence it makes no sense. Drawn as a map with lanes and a loop, the relationship between the three is obvious in one look.

The controller lane is the one to pay attention to. In most companies inventory accuracy is somebody's part-time responsibility, and this map makes visible how many of the steps land on that person, which is usually the argument for either resourcing the role or automating the count.

Every step in the map

This is the spreadsheet behind the diagram. The numbers in “Goes to” are row numbers, which is exactly what the editor’s “Line to” column holds — so you can read the flow here and retype any part of it.

Every step in the Inventory management process process map, in the order the editor numbers them.
#	Step	Shape	Swimlane	Phase	Goes to
1	Receive delivery at goods-in	Start	Warehouse	Goods receipt	2
2	Check delivery against the order	Control	Warehouse	Goods receipt	3
3	Put away to bin location	Process	Warehouse	Goods receipt	4
4	Update stock record and bin quantity	Registry	Inventory controller	Stock records	5
5	Consume stock on the works order	Process	Production	Stock records	6
6	Post issues to the stock record	Process	Inventory controller	Stock records	7
7	Check on-hand against the reorder point	Process	Inventory controller	Replenishment	8
8	Below reorder point?	Decision	Inventory controller	Replenishment	9 (Yes), 12 (No)
9	Raise replenishment requisition	Process	Inventory controller	Replenishment	10
10	Place order with approved supplier	Process	Procurement	Replenishment	11
11	Book receipt against the open order	Process	Warehouse	Replenishment	3 (Goods in)
12	Schedule cycle count by ABC class	Process	Inventory controller	Cycle counting	13
13	Count stock in the assigned bins	Process	Warehouse	Cycle counting	14
14	Variance within tolerance?	Decision	Inventory controller	Cycle counting	16 (Yes), 15 (No)
15	Investigate the variance cause	Process	Warehouse	Cycle counting	13 (Recount), 16 (Confirmed)
16	Post stock adjustment	Process	Inventory controller	Cycle counting	17
17	Review obsolete and slow-moving stock	Process	Inventory controller	Review and write-off	18
18	Write-off approved?	Decision	Finance	Review and write-off	19 (Approved), 20 (Rejected)
19	Write-off posted to the ledger	End	Finance	Review and write-off	End
20	Stock retained on the books	Reject	Inventory controller	Review and write-off	End

The decision points

Every branch in the map, with the label on each outgoing line. These are the questions the process has to be able to answer.

8. Below **reorder point?**

Owned by Inventory controller · Replenishment
- Yes → step 9
- No → step 12
14. Variance within **tolerance?**

Owned by Inventory controller · Cycle counting
- Yes → step 16
- No → step 15
18. **Write-off** approved?

Owned by Finance · Review and write-off
- Approved → step 19
- Rejected → step 20

Notes on specific steps

These notes travel with the map. In the editor they live in the Notes column and appear when you open a box.

4. Update stock record and bin quantity: Post the receipt and the bin location in the same transaction. Stock that is physically on the rack but not yet in the record is the most common cause of a stock-out on an item you already own.
7. Check on-hand against the **reorder point**: State the rule, not just the number: expected demand over the replenishment lead time plus safety stock. Review it when lead times or demand change, otherwise it quietly goes stale.
14. Variance within **tolerance?**: Set the tolerance in both units and value before go-live, for example 2 percent or 100 on a C item and zero on serialised parts. Without it every count difference becomes a debate.
17. Review *obsolete* and *slow-moving* stock: Bring one pack to the decision: ageing, last movement date, quantity, book value and the proposed disposal route. Reviewing line by line from a raw stock list never finishes.

Making it yours

Start from the cycle-counting phase and work outwards; it is the routine most companies run differently from the textbook. Encode your count frequency and your variance tolerance as branch labels rather than prose, then use the Notes column to record which system holds the authoritative stock figure: that single fact resolves more arguments than the rest of the map put together.

What to watch out for

A count variance is not automatically an adjustment. There is a decision between them (investigate first, adjust only when the cause is known) and maps that skip it describe a process where the record is edited to match whatever was counted, which destroys the audit trail.
Replenishment triggered by a system and replenishment triggered by a person are different paths with different failure modes. If you run both, branch them.
Write-off needs an approval step in the finance lane. It is the only step in the cycle that reduces the value on the balance sheet, and it is the one an auditor will look for.

Frequently asked questions

Where does this map start if inventory is a continuous cycle?

At goods receipt, because that is where stock enters the system and it is a real, datable event. The map then runs through the routines and loops back: cycle counting returns to the stock-record phase rather than terminating. A loop with an honest entry point is more useful than a map that pretends the cycle has an end.

Should production have a lane if they only consume stock?

Yes, because consumption is an event the record has to capture, and unrecorded consumption is one of the two main sources of drift (the other being unrecorded receipt). A lane with two boxes in it is still telling you something important about where accuracy is lost.

How is this different from the goods receiving map?

Goods receiving is one event, mapped in detail: what happens on the bay in the hour a lorry arrives. This is the ongoing cycle, mapped at a coarser grain, in which receiving is a single step. They connect at exactly that point, which is why both exist.

Open the map and start editing

The editor loads this chart with the spreadsheet underneath it. Change a cell and the diagram redraws — no drawing, no signup.

Open this map in the editor