Inventory

Inventory Positioning and the Carrying Cost You Can’t See

When a network cannot see what it already has and where, it buys to be safe. Every site carries a little more than it needs, and the total is real money sitting still.

Quick answer: Inventory positioning is deciding which facility each unit should sit in, based on where demand is, what it costs to hold it there, and what it costs to move it later. When a network lacks visibility into what it already has across sites, every facility over-buys to protect its own service level. Better positioning lets the network hit the same service level with less total inventory, and the difference between what it would have bought and what it now buys is the carrying-cost saving. That number usually does not appear in a labor ROI model, because it is not a labor number.

Most labor conversations stop at headcount. How many people on the floor, how many hours, what the plan versus actual looks like. There is a larger number sitting right next to it, and it rarely comes up in the same meeting: inventory in the wrong building.

A distribution network that cannot see its own inventory as one pool ends up buying more of it than it needs. Not because anyone decided to, but because each site protects itself. The cost of that shows up as carrying cost, and it is often bigger than the labor number everyone is focused on.

What is carrying cost, and why does positioning drive it?

Carrying cost is what it costs to hold inventory rather than sell or move it. Capital tied up in stock that is sitting. Warehouse space and handling for units that are not turning. Insurance, shrink, obsolescence, and the interest on all of it. Common estimates put annual carrying cost somewhere between 15 and 30 percent of the inventory’s value, and it climbs the longer a unit sits and the more places it sits in.

Positioning drives carrying cost because where a unit sits determines how long it sits and how much buffer the network needs around it. A unit placed close to its demand turns quickly and needs less safety stock behind it. The same unit placed in a facility that does not see that demand sits longer, and the sites that do see the demand hold their own buffer because they cannot count on the unit being reachable. Same total demand, more total inventory, higher carrying cost.

This is why positioning is a cost question, not a slotting question. Slotting is about travel time inside a building. Positioning is about which building, and it moves a line item that slotting never touches.

Why does a network over-buy when it can’t see itself?

Because each site plans for its own service level with the information it has, and the information it has usually stops at its own four walls. If a planner at one facility cannot see that the unit they are about to reorder is sitting in surplus two nodes over, they reorder. Multiply that across every facility and every SKU and the network is carrying a layer of duplicate buffer it does not know about.

The behavior is rational at the site level. A planner who runs out because they trusted a number from another building gets blamed for the stockout. A planner who carries a little extra does not. So everyone carries a little extra, and the network pays for all of it.

The fix is not more discipline from planners. It is giving them a view of what the network actually holds, so the safe choice and the lean choice become the same choice.

How should you think about where a unit should sit?

Three inputs, weighed together. First, where the demand is and how predictable it is. Stable, concentrated demand can sit close to it with a thin buffer. Volatile or spread-out demand needs either a central position or more buffer, and the choice between those two is itself a cost comparison.

Second, what it costs to position the unit there versus somewhere else. Inbound freight, handling, storage rate, and the labor profile of that building. A lower storage rate at a facility far from demand is not a saving if it forces expedited outbound later.

Third, what it costs to be wrong. If the unit is in the wrong place, what does the recovery cost, a transfer, an expedite, a lost order. High recovery cost argues for a more conservative position or better visibility so the call can be corrected early.

None of these are new ideas to a supply chain planner. What is usually missing is a single place to see all three across the network at once, rather than one facility at a time.

Turning better positioning into a number leadership recognizes

The ROI framing is simple and it is one an operator gave us directly: if the network buys less inventory because it is positioning what it has more effectively, the difference between what it would have bought and what it now buys is the return.

That is a cleaner number than most inventory-project benefits because it is a real change in spend, not a modeled efficiency. You can point at the reorder that did not happen because the unit was already in the network and reachable. Aggregate those over a quarter and you have a carrying-cost figure that finance can tie to the balance sheet.

It also compounds with the labor story rather than competing with it. Fewer units sitting means less handling, less space pressure, fewer touches, which shows up in the labor plan too. But the headline is the inventory the network no longer has to carry.

Why this doesn’t show up in a labor ROI model

Because a labor ROI model measures hours, and this is a change in inventory, not hours. The savings live on a different line, owned by a different team, and reported on a different cadence. A labor planning tool that quietly helps a network carry less inventory will not get credit for it in a labor business case, even though the mechanism, network-level visibility, is the same one that improves the labor plan.

The practical implication for a business case: if better positioning is part of the value, put it in as its own line with its own owner, measured as a change in purchase spend and average inventory on hand. Do not let it get folded into a labor number where it will be invisible.

This is the same attribution problem that shows up elsewhere in multi-site operations. A real improvement gets miscredited or lost because it does not fit the shape of the report it lands in.

What to look at first

A few questions that surface whether positioning is costing you: How much of your safety stock exists because a planner cannot see inventory at another site. When you run a stockout at one facility, how often is the same SKU sitting in surplus somewhere else in the network. What does a network transfer cost you, all in, and how often do you run one that better initial positioning would have avoided.

Then the spend side: over the last few quarters, how much did you buy that you would not have bought if every planner could see the whole network. That last number is hard to pin down exactly, which is part of the problem, but even a rough version of it usually reframes the conversation.

If the answers point at real duplicate buffer, the issue is visibility, not planning skill, and it is worth fixing at the network level rather than asking each site to be more careful.

Where CognitOps fits

CognitOps is built around network-level visibility, seeing safety, quality, inventory position, and cost across facilities as one picture rather than site by site. The same visibility that keeps a labor plan matched to throughput is what lets a network stop carrying duplicate buffer it did not know it had. Across 75-plus live facilities, customers see 8 to 12 percent lower cost per unit.

The broader framing is on the one view of safety, quality, inventory, and cost page, and the attribution problem this section touches on, real improvements getting lost in the rollup, has its own page. The 2026 State of Warehouse Labor Performance report has the cost-per-unit and productivity figures across the network.

Frequently asked questions

See what the network is carrying that it doesn’t need to

Give every planner a view of what the network holds, so the safe choice and the lean choice become the same choice.