Grocery Shelf Replenishment: The Labor Hours You Can't See

Replenishment is the biggest labor bucket, and you can't see it

Replenishment is the single largest controllable labor expense in a grocery store. It beats checkout, beats receiving, beats deli prep. Every case that moves from a backroom pallet to a shelf face costs labor minutes, and a 40,000-SKU store moves a lot of cases.

Yet most chains can't tell you what replenishment actually costs per store, per category, or per case. They know total store labor. They know it runs roughly 12 to 16 percent of sales depending on format and union status. They cannot break out the slice that goes to stocking shelves, and they definitely cannot tell you whether that slice is going to the products that sell.

That gap is the whole problem. You are spending your biggest labor line on a process you don't measure, and the people doing the work are following a plan that has nothing to do with how fast things sell.

This post is about what happens when you measure replenishment labor against velocity. The numbers are not small.

The night crew stocks to a planogram nobody reweighted

Walk a store at 11pm. The night crew is working a planogram. They face the shelf, fill the holes, rotate the stock, and move to the next bay. The planogram tells them where every SKU goes and how many facings it gets. It does not tell them how fast each SKU sells.

So the crew spends the same care on a slow-moving specialty mustard as on the top-selling national-brand ketchup. They open a case of the mustard, place six units, and the case is done for the night and probably the week. They open a case of the ketchup, place twelve units, and it is half empty again by noon.

The labor cost of touching those two products is similar. The sales they support are not. One case of mustard might represent two weeks of velocity. One case of ketchup might represent six hours. The crew treats them as equal because the planogram treats them as equal.

This is the core inefficiency. Replenishment labor is allocated by shelf geography, not by how often the shelf empties. The store works the whole set on a fixed cadence, and the fixed cadence is wrong for almost every SKU on it.

Minutes per SKU vary wildly, and nobody tracks it

Time the same task across categories and the spread is large. A case of canned soup is fast: stable cases, clean rotation, shelf-ready. A case of yogurt is slow: date checking, tight rotation, refrigerated aisle, fragile cups. Loose produce is slower still, with cull, trim, and display work that has no case-pack logic at all.

Industry time studies put simple center-store replenishment around one to two minutes per case and perishable replenishment at three to five minutes or more once you count rotation and quality work. Across 40,000 SKUs and thousands of cases a week, those per-case minutes compound into the largest labor pool in the building.

Almost no chain tracks minutes per case by category at the store level. They track total hours. The detail that would let you move labor toward velocity sits in nobody's report.

Case-pack mismatch forces you to over-replenish slow movers

Here is a cost that hides in plain sight. Your case pack is set by the supplier and the distribution center, not by store velocity. When the pack is too big for how a SKU sells, the store is forced to over-replenish.

Take a slow specialty item that sells two units a week. The case pack is twelve. To put one case on the shelf, you commit six weeks of supply to a single facing. The labor to stock it is the same as any other case, but now you are also carrying six weeks of working capital on a product nobody is asking for, and you have backstock that has to be touched again later.

Multiply that across the long tail. A grocery store carries thousands of slow movers, and a large share of them have case packs sized for a faster store than yours. Every one of them ties up cash and shelf and backroom space, and every one of them gets the same labor attention as a fast mover on the night crew's standard pass.

The fast movers have the opposite problem. The case pack is too small for daily velocity, so the shelf goes empty between deliveries and the crew makes multiple trips to the same bay. Small packs on fast movers mean more touches per unit sold, which is the most expensive way to stock a shelf.

Case-pack mismatch is a labor problem and a working-capital problem at the same time. You over-stock the slow tail and under-stock the fast head, and you pay labor inefficiency on both ends.

Empty shelves on top movers cost more than all of it

Now flip to the revenue side, because the labor waste and the sales loss are the same problem viewed from two directions.

On-shelf availability in grocery is worse than most operators think. FMI and industry shelf audits routinely find out-of-stock rates in the high single digits at any given moment, and the rate spikes during peak hours and weekends, exactly when your best sales happen. The items that go empty first are the top movers, because the top movers empty fastest and the replenishment cadence doesn't bend to catch them.

So your highest-velocity SKUs, the ones carrying the category, are the ones most likely to be a hole on the shelf Saturday afternoon. A shopper who wants the leading bread brand and finds a gap does one of three things: buys a substitute, skips the item, or buys it somewhere else. Two of those three cost you the sale, and the third trains the shopper that your store can't be relied on for the basics.

The math is brutal because it stacks. You spent labor over-stocking the slow tail. That labor was not available to chase the fast head. The fast head went empty during peak. You lost the highest-margin, highest-velocity sales in the store. Then the night crew came in and refilled the slow tail again.

This is why replenishment is the bucket to fix first. Get it wrong and you pay three times: wasted labor, trapped working capital, and lost sales on the products you most want to sell.

What a chain finds when it measures replenishment against velocity

When a chain finally puts replenishment labor next to velocity, store by store and category by category, the same patterns show up almost every time.

The first finding is concentration. A small share of SKUs drives most of the velocity, and those SKUs are systematically under-served by a flat replenishment cadence. The crew is spending a large share of its case touches on items that turn slowly, because slow items still need facing and rotation and date work even when they barely sell.

The second finding is store-to-store variance that no central report would predict. The same category, same planogram, same case packs, behaves differently in a high-traffic urban store than in a suburban one. Velocity per facing diverges, so the right replenishment cadence diverges, but every store is running the one national plan. The stores that need more touches on the head get the same cadence as stores that need fewer.

The third finding is the case-pack tail. A measurable share of slow SKUs carry packs that represent a month or more of supply per facing. Each is a small amount of trapped cash, but they add up across thousands of items into real working capital sitting on shelves and in backrooms, getting touched and re-touched for almost no sales.

None of this is visible in a labor report or a sales report alone. It only appears when you put labor minutes and unit velocity in the same view at the store-category level. That is the join most grocery systems never make, because labor lives in one system and velocity lives in another and nobody owns the seam between them.

The savings show up as labor and working capital at the same time

The fix is not heroic. You shift replenishment effort toward velocity and you right-size the case packs that are most mismatched.

On the labor side, you stop spending equal touches on unequal SKUs. Slow movers get a less frequent pass. Fast movers get the attention and the timing they need to stay on the shelf through peak. Even a few points of reallocation against the largest labor bucket in the store is meaningful money, and it tends to repeat every week of the year.

On the working-capital side, you flag the slow SKUs with oversized packs and push to break the pack, change the pack, or cut the item. Each fix frees cash that was sitting in backstock and frees shelf and backroom space that was carrying weeks of dead supply. A chain that does this across its slow tail recovers working capital it did not know it had locked up.

And the sales you were losing on empty top movers start to come back, because the labor you freed from the slow tail is now available to keep the fast head in stock when it matters.

How Ward surfaces this without another dashboard

Ward is built for exactly this kind of cross-system blind spot. We are a read-only observability platform for multi-store retailers, and we do not run your store. We watch the data you already generate and tell you where the money is leaking.

The model is detect, decide, execute, audit. Ward detects the patterns above: the store-category combinations where replenishment labor is misaligned with velocity, the top movers going empty at peak, the slow SKUs with case packs that represent weeks of supply. You decide what to do, because your team knows the store. Your team executes, on your systems and your terms. Then Ward audits whether the change actually moved the number.

Orders, planograms, and labor schedules stay under your control. Ward watches the lane and speaks up when you drift out of it. Everything after that is your store team's call.

And Ward does not hand you another dashboard to check. You get insight cards: one finding, one store-category, the size of the problem, and what to look at. A card might say that a specific store is spending a large share of its center-store replenishment minutes on the slowest-turning third of the set while the top movers in that category run out before noon on weekends. That is a thing a manager can act on Monday, not a chart to interpret.

The point is to make the invisible labor visible. Replenishment is your biggest controllable bucket and your biggest blind spot. Put it in the light and the savings are sitting right there.

Key takeaways

• Replenishment is the largest controllable labor bucket in grocery, and almost no chain measures it. Store labor runs 12 to 16 percent of sales, and stocking shelves is the biggest slice, but it lives in nobody's report.
• Night crews stock to a planogram, not to velocity. A slow specialty item gets the same labor attention as a top mover, because the plan allocates effort by shelf geography instead of by how fast the shelf empties.
• Minutes per case vary widely by category. Center-store cases run one to two minutes, perishables three to five or more, and the spread is never tracked at the store level where it could be acted on.
• Case-pack mismatch forces over-replenishment of slow movers. Packs sized for a faster store trap weeks of working capital in the long tail while too-small packs on fast movers drive extra touches per unit sold.
• Top movers go empty during peak. Out-of-stock rates spike on weekends and high-traffic hours, and the items that empty first are the ones carrying the category, so you lose your best sales at your best times.
• Fixing it pays three ways. Reallocating labor toward velocity, right-sizing mismatched case packs, and keeping the fast head in stock returns labor hours, working capital, and lost sales at the same time.
• The insight only appears when labor and velocity sit in one view. Ward joins them at the store-category level and delivers it as an insight card a manager can act on, read-only, lane assist not autopilot.