Planogram Compliance: The Gap Between the Plan and the Shelf

A planogram is a plan. The shelf is what actually happened.

You negotiate a category. You build a planogram. You assign every SKU a position, a facing count, and a sequence that maps to how you think the shopper buys. Then you ship that plan to every store and assume the shelf looks like the file.

It does not. Industry shelf audits put planogram compliance somewhere between 50 and 70 percent at any given moment. That means a third or more of your shelf does not match the plan you built your category strategy and your trade dollars around. The plan is a document. The shelf is reality, and reality drifts the day after the reset.

This is the gap that quietly breaks category management. You manage to the plan. You report on the plan. You pay suppliers against the plan. But the shelf is running its own version, and nobody in the building has a current, store-level read on how far it has drifted.

This post is about why compliance drifts, what a non-compliant shelf costs you, and why the usual fix, sending a field rep to look, is too slow and too expensive to catch it.

Why compliance drifts the moment the reset is done

Drift is not one problem. It is four, and they compound.

The first is resets that never happened. You schedule a category reset, the work order goes out, and at some stores it gets done late, gets done wrong, or does not get done at all. A late reset means the old set is selling against your new trade terms. A skipped reset means you are paying for a plan that exists only on paper.

The second is out-of-stocks faced over. When a SKU runs empty, the night crew spreads the neighbors to fill the hole so the shelf looks full. The gap is gone, but so is the planogram. The featured item you negotiated has just been replaced on the shelf by whatever was next to it.

The third is local override. A store manager decides the endcap sells better with the regional brand, or shrinks a facing to make room for a fast mover, or quietly drops a slow SKU the plan still calls for. Each decision may be locally rational. In aggregate they erase the national plan.

The fourth is labor shortcut. The crew works fast, places what is easy, and skips the fiddly low-velocity items at the bottom of the bay. The plan assumed every facing gets set. The labor reality is that the hard 20 percent of the set gets the least attention.

Audits are stale the day they finish

The standard answer to drift is the audit. A field rep walks the store, photographs the set, scores it against the planogram, and files a report. It works, for that store, on that day.

The problem is coverage and cadence. A rep can audit a handful of stores a day. A 200-store chain on a quarterly audit cycle is looking at any given store four times a year. The shelf drifts in days. You are auditing a process that changes weekly with a tool that fires quarterly.

So the audit tells you the shelf was 62 percent compliant in March. It cannot tell you it dropped to 48 percent in April when a reset got skipped and three top SKUs went out of stock and got faced over. By the time the next rep visit catches it, you have lost a quarter of sales on the items you most wanted to feature.

What a non-compliant shelf actually costs

Non-compliance is not a tidiness problem. It is a revenue problem, and it hits the items you can least afford to lose.

Featured SKUs are the first casualty. You put a new item in the plan at eye level because you expect it to sell. If the store never set it, or set it on the bottom shelf, or faced over it when it ran out, the launch fails. Then everyone reviews the sell-through data and concludes the item is weak, when the truth is it was never on the shelf where the plan put it.

Promotion execution breaks the same way. You run a feature, the ad drops, and the shopper arrives to find the promoted item missing or buried. The promotion drives traffic and the shelf cannot convert it. You paid for the demand and gave it to a gap.

Then there is trade-fund accountability. Suppliers pay you for placement, facings, and position. When the shelf does not match what you sold them, you are out of contract. Either you are exposed on a compliance clause, or you are leaving money on the table because you cannot prove the placement you delivered. A shelf you cannot verify is a trade agreement you cannot enforce.

The stack is the same shape every time. The plan was sound. The shelf did not execute it. Sales on featured and promoted items came in light. The data looked like a merchandising failure when it was an execution failure, and the difference is invisible unless someone is watching the shelf at the store level, continuously.

Image recognition versus data signal

There are two ways to close the gap between the plan and the shelf without flooding every store with reps every week. They are not the same, and they cost very different amounts.

The first is image recognition. You put cameras on the shelf, or you put a phone in every clerk's hand, and software scores the picture against the planogram. Done well, it is precise. It sees a missing facing, a wrong SKU, a price tag out of place. It also needs hardware, store labor to capture images, and a constant feed of reference images to stay accurate as packaging changes. It is the most direct read and the most expensive to run at scale.

The second is data signal. You already generate the evidence of non-compliance in your POS and inventory systems, and nobody reads it as a compliance signal. A SKU the planogram puts at eye level with a top facing count, showing near-zero sales while the category sells, is telling you something. Either it is not on the shelf, it is in the wrong spot, or it is out of stock and faced over. The shelf is reporting itself through its own velocity.

Data signal does not see the shelf the way a camera does. It infers. It cannot tell you the SKU is on the third shelf instead of the second. But it can tell you, every day, across every store, which planogrammed items are behaving like they are not set right, without sending anyone anywhere. It turns the data you already have into a non-compliance alarm.

The smart play is to use the signal to aim the camera. Let velocity tell you which 30 stores out of 200 have a likely problem this week, then spend your expensive verification, the rep visit or the image capture, only where the signal says to look.

How to measure planogram compliance

Compliance is not one number. It is four, and stating a single percentage without saying which one is why vendor and retailer figures never agree.

Presence compliance. Is every planogrammed SKU physically on the shelf. This is the easiest to measure and the closest to a revenue impact, because an absent SKU sells nothing regardless of where it should have been.

Position compliance. Is each SKU in its assigned location, shelf and horizontal slot. This is what trade agreements are usually written against, and it needs a visual check.

Facing compliance. Does each SKU hold its assigned number of facings. Facing drift is the most common failure and the least noticed, because a shelf can look correct while the top seller has quietly lost two facings to its neighbor.

Price and signage compliance. Is the tag present, correct, and matching the POS price. Cheap to fix, and it produces customer-visible failures out of proportion to the effort.

Report presence and facing compliance weekly, position monthly, and price on every audit. A chain reporting "68% compliance" is almost always quoting position compliance, which is the hardest bar and the one that makes the number look worst.

Planogram compliance benchmarks

Compliance decays predictably from the day of the reset, which is why a single annual figure tells you nothing about what the shelf looks like on an average Tuesday.

The week 4 row is the one to act on. Most drift at that point traces to out-of-stocks being faced over, which means the compliance problem and the availability problem are the same problem. Fixing on-shelf availability recovers a meaningful share of compliance for free.

The other lesson is that compliance is not a state you achieve, it is a rate you maintain. A chain that resets to 93% and has no correction loop is at 60% within a quarter, every quarter, and the reset labor buys three good weeks. That is the real economics of the reset calendar, and it rarely appears in the business case for one.

Tying compliance back to trade-fund accountability

Compliance data is worth the most when you point it at trade money, because that is where the dollars are concrete and the contracts are explicit.

Every trade agreement assumes execution. The supplier paid for a position, a facing count, a duration. If you can show, store by store, that the placement held for the contracted period, you can enforce the agreement and defend the funds. If you cannot, you are negotiating your next deal from a position of doubt, because both sides know the shelf may not have matched the plan.

This flips compliance from a cost center to a bargaining chip. A chain that can prove execution is a more valuable retail partner and can charge for it. A chain that catches its own drift before the supplier does protects the relationship and the renewal. The data that detects a faced-over feature is the same data that proves a kept promise, and both are worth real money. The proof is the asset, and most chains throw it away because they never capture it.

How Ward surfaces likely non-compliance without sending a rep

Ward is a read-only observability platform for multi-store retailers. We do not run your store and we do not touch your shelf. We watch the POS, ERP, and inventory data you already generate and tell you where the plan and the shelf have come apart.

The model is detect, decide, execute, audit. Ward detects likely non-compliance from sales-velocity and inventory signals. A planogrammed top SKU showing no sales while its category sells is the clearest tell: it is probably not on the shelf, not placed where the plan put it, or out of stock and faced over. You decide whether it is worth a look, because your team knows the store. Your team executes the fix or the rep visit. Then Ward audits whether the reset actually happened, by watching velocity return to where the plan said it should be.

Shelves get reset by people, reps get dispatched by people, and planograms get changed by people. Ward ranks which stores have drifted and by how much, so the verification time your team already spends lands where it pays.

And you do not get another dashboard. You get insight cards: one finding, one store, one SKU or set, the size of the gap, and what to check. A card might say that a featured launch SKU at three stores has logged near-zero units for nine days while the rest of the category sells normally, which reads as a reset that did not happen. That is something a category manager can act on today, not a quarterly audit to wait for.

The point is to make the shelf visible without walking it. Compliance drifts in days and gets audited in quarters. Ward closes that gap by reading the drift in the data you already have.

Key takeaways

• Planogram compliance runs 50 to 70 percent, so a third of your shelf does not match the plan. You manage, report, and pay trade funds against a plan the shelf is not actually running.
• Compliance is four numbers, not one. Presence, position, facing, and price. A chain quoting a single low percentage is almost always quoting position compliance, the hardest bar. Report presence and facing weekly, position monthly.
• Compliance decays on a predictable curve. Presence runs 88 to 95% in week 1 and 55 to 72% by week 12. The commonly quoted 50 to 70% industry figure is the steady state, not the exception.
• Most week-4 drift is out-of-stocks being faced over. The compliance problem and the availability problem are the same problem, so fixing on-shelf availability recovers a meaningful share of compliance for free.
• Compliance is a rate you maintain, not a state you achieve. A reset to 93% with no correction loop is back at 60% within a quarter. The reset labor buys about three good weeks.
• Drift has four causes that compound. Resets that never happened, out-of-stocks faced over, local overrides, and labor shortcuts each erode the set, and together they erase the national plan within days of a reset.
• A non-compliant shelf kills featured and promoted items. Launches fail and promotions miss because the item was never on the shelf where the plan put it, and the data reads like a merchandising failure when it was an execution failure.
• Field-rep audits are stale the day they finish. A quarterly cycle audits a process that changes weekly, so the drift that costs you the most goes uncaught for months.
• Data signal catches what audits miss, every day, at every store. A top-facing SKU with no sales while its category sells is the shelf reporting its own non-compliance, with no rep required.
• Use the signal to aim the expensive verification. Let velocity flag the stores with a likely problem this week, then spend the camera or the rep visit only where it pays.
• Compliance data is a bargaining chip with suppliers. Ward detects likely non-compliance from velocity and inventory signals and audits whether resets actually happened, read-only, lane assist not autopilot, delivered as an insight card a category manager can act on.