Shrinkage by Department: Where Grocery Stores Lose

Most grocery operators are looking at the wrong shrinkage number

Here is something that will not surprise you if you have ever run a grocery store: you are losing somewhere between 1.5% and 2.5% of your total sales to shrinkage. That number shows up in your annual physical inventory, your controller sighs about it, and then everyone goes back to doing what they were already doing. The industry treats this like a law of physics, an unavoidable cost of doing business with perishable goods and human beings.

But here is the thing nobody talks about at the NGA conferences (or if they do, it is over drinks rather than on stage): that store-wide average is almost completely useless for actually fixing anything. Shrinkage is not evenly distributed across your store. It is not even close to evenly distributed. Some of your departments are running at 0.5% shrinkage and doing fine, while others are hemorrhaging at 8% or more, and the blended average makes everything look like a manageable 2% problem. This is roughly equivalent to a doctor telling you "on average, your body temperature is fine" when your left hand is frostbitten and your right hand is on fire.

The moment you start breaking shrinkage down by department, the comfortable narrative that "shrinkage is just a cost of doing business" falls apart, and you start seeing specific, fixable operational problems with specific dollar amounts attached to them. Which, I would argue, is the entire point.

The department-by-department reality is not what you expect

Let me walk through what the numbers actually look like when you decompose that pleasant-sounding 2% average into its constituent parts, because the variation is dramatic.

Your produce department is almost certainly your single largest source of shrinkage, running somewhere between 5% and 8% of department sales. This is a department that might represent 10-15% of your total store revenue but accounts for 25-30% of your total shrinkage dollars. The math here is brutal: if you are doing $500K in weekly sales and produce is 12% of that, you are moving $60K a week through produce and losing $3,000 to $4,800 of it. Every week. The causes are almost boringly predictable (spoilage from temperature fluctuation, damage from customer handling, the inherent biological reality that strawberries are trying very hard to become mold from the moment they leave the field), but the dollar impact is anything but boring.

Meat and seafood runs at 4-6% shrinkage, which sounds lower than produce until you remember that the average unit cost in this department is dramatically higher. A single misrotated case of ribeyes represents more loss than an entire shelf of wilted lettuce. When a $200 lobster tank crashes overnight or someone leaves the seafood case door ajar for two hours, you have just wiped out days of department profit in a single incident. FMI data consistently shows meat and seafood contributing 20-25% of total store shrinkage while accounting for only 8-10% of sales. The department is punching well above its weight in the worst possible way.

The deli and prepared foods department is, in my experience, the most systematically underestimated source of shrinkage in the entire store, running at 6-10% of sales. The reason operators underestimate it is fascinating and reveals something important about how we think about loss: most of the shrinkage happens before the product ever reaches the display case. The deli manager who slices 20 pounds of turkey breast on Friday morning and throws away 8 pounds on Monday does not think of that as shrinkage in the way they would think of a stolen package of cheese as shrinkage. It is "production waste" or "prep" or simply "how the deli works." Your P&L statement does not care what you call it. The dollars are gone either way.

Bakery shrinkage ranges from 5-8% and is notable mostly for how much of it is the result of deliberate (if poorly calibrated) business decisions rather than uncontrollable spoilage. Every store has a day-old policy. Every store over-bakes to some degree because empty cases look bad and customers who arrive at 3 PM expecting fresh bread do not want to hear that you sold out at noon. The stores that bake in smaller batches throughout the day tend to land at 5%, while the stores that load everything at 5 AM and pray tend to land at 8% or higher. The difference between those two approaches, in a department doing $15K weekly, is about $450 a week or roughly $23,000 a year. That is a meaningful number for a decision that is entirely within your operational control.

Dairy is the pleasant surprise in this analysis, typically running at 2-3% shrinkage. Longer shelf lives, more consistent cold chain infrastructure (dairy coolers tend to be better engineered than produce cases, for reasons that probably have to do with the dairy industry's longer history of refrigeration), and clearly printed date codes all contribute. The exceptions are predictable: seasonal items like eggnog spike Q4 shrinkage, and the proliferating universe of specialty yogurts and alternative milks creates a long tail of slow-moving SKUs that expire before anyone buys them.

And then there is center store, your shelf-stable grocery aisles, running at 0.5-1% shrinkage and barely registering as a problem. Most center store loss comes from theft and physical damage rather than expiration, which makes sense when you consider that a can of soup is not engaged in an active biological process trying to make itself unsellable. Seasonal overbuys and true slow-movers account for the expiry component. Center store shrinkage is real but it is not where your operational attention should be focused, which is itself a useful thing to know.

The causes are different in every department, and that matters more than you think

The industry-wide breakdown of shrinkage causes runs something like 45-50% spoilage and expiry, 30-35% theft (both internal and external, and the internal component is larger than most operators want to admit), and 15-20% damage and unknown causes. These numbers are roughly correct in aggregate and roughly useless for making decisions about any specific department.

In produce, spoilage and quality deterioration drive 70-80% of losses. Theft exists (someone is definitely eating your grapes in the aisle, yes) but it is a rounding error compared to the berries that went soft because the case ran at 42 degrees instead of 36, or the bananas that sat in a warm back room for four hours during a busy receiving day. The most insidious produce shrinkage lives in the gray zone between "sellable" and "unsellable," where individual associates are making dozens of subjective toss-or-keep decisions every day without clear standards. One associate throws away every apple with a single bruise, another leaves visibly deteriorating product on display because they hate waste. Neither approach is optimal, and the inconsistency means your actual shrinkage rate is essentially random, determined by who happens to be working the department on any given morning.

Meat and seafood shrinkage is 60-70% expiry-driven, but the theft component (20-25%) concentrates in high-value cuts in a way that makes it disproportionately costly. Your $40-per-pound ribeyes and $25-per-pound wild salmon fillets are among the most commonly stolen items in the entire store, which is economically rational behavior on the part of the thieves if not exactly helpful for your bottom line. Temperature abuse accounts for much of the remainder, and unlike produce where temperature issues cause gradual quality decline, a meat case temperature excursion can render an entire case unsellable in a matter of hours.

The deli is dominated by production waste, which as I mentioned earlier often does not even get categorized as shrinkage by the people generating it. FMI data suggests 50-60% of deli shrinkage occurs during production, before items ever reach the retail case. Retail expiry adds another 25-30%, concentrated in grab-and-go items with same-day or next-day sell-by dates. If you are not tracking production waste separately from retail shrinkage in your deli, you are not tracking deli shrinkage at all. You are tracking the smaller half of it and feeling good about a number that represents an incomplete picture.

Bakery occupies an unusual position because a significant portion of what gets recorded as shrinkage is actually the result of deliberate markdown programs. Day-old items sold at 50% off are "shrinkage" in many operators' tracking systems even though they generated revenue. True dead loss (product going straight to the dumpster or donation bin) typically represents 40-50% of what gets reported as bakery shrinkage, with overproduction and poor demand forecasting driving most of it. Customer damage exists (the kid who poked every donut is a universal grocery store archetype for a reason) but it is 10-15% of the total at most.

Measuring shrinkage properly is harder than it sounds, and almost nobody does it

The standard approach to shrinkage measurement in the grocery industry is an annual physical inventory that produces a single store-wide number. This is like getting an annual physical and having your doctor tell you "you weigh 185 pounds" without mentioning that you have gained 30 pounds of fat and lost 15 pounds of muscle since last year. The number is technically accurate and practically useless for making decisions.

The gap between what you know about and what you do not know about is itself enormously important. "Known shrinkage" is the stuff your employees scan out when they throw it away: the expired yogurt, the damaged cereal box, the produce that failed your quality standards. "Unknown shrinkage" is everything else, the difference between what your system says you should have and what you actually have when you count it. Unknown shrinkage encompasses theft, receiving errors (you got shorted on a delivery and nobody caught it), scanning errors (the cashier who rings up organic avocados as conventional ones is simultaneously creating margin leakage and phantom inventory), and disposal that employees did not bother to record.

In a well-run operation, known shrinkage should represent 60-70% of total shrinkage, because it means your employees are actually recording disposals rather than just tossing product in the compactor. If your known shrinkage is very low but your physical inventory reveals a large total shrinkage number, you have a recording compliance problem, a theft problem, or a receiving accuracy problem, and you cannot begin to address any of those until you know which one it is.

The operationally useful approach is cycle counting by department on a rotating schedule. Count produce completely one week, meat the next, dairy the week after, and so on. This distributes the labor burden (a full produce count runs 3-4 hours, meat 2-3 hours, dairy 1-2 hours) and gives you monthly visibility into every department rather than annual visibility into the store as a whole. A store doing $500K in weekly sales with 4% produce shrinkage is losing roughly $20K per month in that one department. A 4-hour monthly count that helps you identify and address the specific drivers of that loss pays for itself almost instantly.

The critical companion to counting is categorizing loss at the point of disposal. When an employee throws out a case of spoiled strawberries, that is a data point. The store that captures it immediately (product, quantity, reason code, date) can analyze patterns and take corrective action. The store that piles everything in the compactor and tries to reconstruct what happened at the end of the week learns nothing from the experience and is therefore doomed to repeat it.

Where to focus when you cannot fix everything at once

This is where the analysis becomes genuinely useful rather than merely interesting. If you are a grocery operator reading this and feeling mildly overwhelmed by the notion that every department has different shrinkage rates driven by different causes requiring different interventions, here is the good news: you do not need to fix everything simultaneously. The numbers themselves tell you where to focus.

The economic opportunity in shrinkage reduction is concentrated in a small number of departments. Produce, meat/seafood, and deli/prepared foods together typically account for 70-80% of total store shrinkage. If you improve shrinkage rates in those three departments by even one percentage point each, the impact on your store's bottom line dwarfs anything you could achieve by obsessing over center store losses.

For a store doing $10M in annual sales, reducing produce shrinkage from 6% to 5% on a department that represents 12% of sales saves $12,000 per year from that one change in that one department. Achieving a similar one-point improvement in meat (say 10% of sales) saves $10,000. A one-point improvement in deli (say 8% of sales) saves $8,000. You are looking at $30,000 in annual savings from modest, achievable improvements in three departments, and I have not even touched markdown optimization or ordering accuracy yet.

The contrarian insight here is that most shrinkage reduction programs fail not because the interventions are wrong but because they are applied uniformly across the store rather than concentrated where the opportunity is largest. The store manager who demands that every department reduce shrinkage by 0.5% is asking center store to achieve something that barely matters and asking produce to achieve something that does not go nearly far enough. The data-driven approach says: leave center store alone (or at least do not spend management attention on it), and pour your energy into produce rotation, meat temperature monitoring, and deli production planning, because that is where the money is.

Temperature monitoring with automated alerts catches problems before they destroy inventory. Date-code-based rotation (FEFO rather than FIFO, because a case of organic blueberries delivered today with a 3-day code should be shelved ahead of conventional berries delivered yesterday with 5 days remaining) prevents the most common and most preventable form of perishable shrinkage. A supermarket-focused inventory system that enforces this rotation logic removes the guesswork entirely. Ordering based on actual sales movement rather than gut feeling prevents the overstock that is the precursor to most spoilage. Proactive dead stock prevention through better ordering and early, aggressive markdowns on short-coded product (at 40-50% off, not the timid $0.50 reductions that do not change anyone's buying behavior) convert would-be shrinkage into recovered margin.

None of this is rocket science. All of it requires measurement, consistency, and a willingness to look at department-level data rather than hiding behind store-wide averages. The operators who do this consistently see 1-2 percentage point improvements in their highest-shrink departments within 90 days, which in a $10M store translates to $50,000 to $100,000 in annual savings. That is real money, recovered from real operational improvements, driven by the simple act of looking at the right numbers.

ShelfLifePro tracks expiry dates at the item level, generates FEFO rotation workflows, and gives you the department-by-department shrinkage visibility described above without the manual spreadsheet work. If you are serious about turning your shrinkage data into operational improvements, [take a look at what we do](/get-started).