Why a plan that never reaches the shelf is worth nothing
The best salsa deck I ever built died on a shelf in Fresno, which taught me that category plan implementation, not the plan itself, is what actually moves the shelf. The Sprouts buyer had signed off on everything: cut the two slowest Verde Fresca fresh SKUs, hand the fermented segment two more facings on the strength of its +28% YoY, hold the $3.99 / $4.99 / $6.49 price ladder. On paper the reset added maybe forty basis points of blended margin across the $18.4M category. Six weeks after the go-live date, I pulled velocity by store and the fermented lift was showing up in some stores and flat in others, and it took a store visit to find out why: a chunk of the 345 Sprouts stores were still merchandised on the old planogram. The new facings the plan promised had never physically gone up.
That gap, between the approved planogram and what is actually on the shelf in 345 stores, is where most category plans die. Steps 1 through 6 of the eight-step process are analysis and decision. Step 7 is the only step that touches a physical shelf, and it is the step suppliers pay the least attention to, because we do not run it. The retailer does. This chapter is about how to make implementation go right when you control almost none of it.
The category plan implementation checklist
A reset is seven workstreams running on the same clock toward a single go-live date. When I handed a plan to a Sprouts category manager, this is the table I attached, because the fastest way to watch a reset fall apart is to leave one of these rows unowned.
| Workstream | What it is | Who owns it | When it happens |
|---|---|---|---|
| Set the reset date | The go-live: the day stores physically re-merchandise the fixture | Retailer (buyer + space planning) | Fixed first; everything else counts back from it |
| Distribute the planogram | Get the final POG to stores, DC, and third-party merchandisers | Retailer / space-planning vendor | Reset date minus 4 to 6 weeks |
| Discontinued-SKU sell-down | Draw down inventory on cut SKUs so nobody is stranded | Supplier + retailer replenishment | Reset date minus 8 weeks through go-live |
| New-item cut-in + authorization | First order, item setup, DC slotting for added SKUs | Supplier (sell-in) + retailer | Reset date minus 6 to 8 weeks |
| Promo calendar load | Enter the agreed features into the retailer's promo system | Retailer merchandising | Load 8+ weeks ahead of the first feature |
| Store-level compliance audit | Confirm each store actually reset to the new POG | Retailer field team (supplier verifies after) | Reset date plus 2 to 6 weeks |
| JBP owner and cadence | The joint business plan that keeps all of this on a calendar | Named person on each side | Standing; reviewed monthly |
Two rows carry more weight than the rest. The reset date anchors everything, because every other workstream is defined by its distance from that date, and if the date slips without telling the sell-down team, you strand inventory on a SKU that is supposed to be gone. And the compliance audit is the row everyone treats as optional, which is exactly why plans fail silently instead of loudly. More on both below.
The discontinued sell-down
When the plan cuts the two slowest Verde Fresca fresh SKUs, Chunky Medium and Restaurant-Style, you cannot just stop shipping them on go-live day. Those two SKUs are sitting in 345 store back rooms and in the Sprouts DC on the reset date, and fresh refrigerated salsa carries a code date of roughly fourteen days. If the reset pulls the facing before the inventory clears, you are looking at markdowns, returns, or spoilage, and depending on the deal terms, some of that lands on the supplier.
So the sell-down runs on its own timeline, counting back from the go-live. Here is the shape I ran for a fresh-salsa discontinuation at Sprouts.
| Week (vs go-live) | Action on the cut SKUs | Inventory goal |
|---|---|---|
| Reset minus 8 | Stop new-item production; confirm final DC ship date | Last replenishment order placed |
| Reset minus 6 | Retailer stops DC-to-store replenishment on the two SKUs | DC inventory begins drawing down |
| Reset minus 4 | Stores sell through remaining facings at regular price | Store-level units falling toward zero |
| Reset minus 2 | Optional markdown on any store still carrying meaningful units | Clear the tail before the crew arrives |
| Go-live (week 0) | Facings pulled, new POG set, cut SKUs gone from the fixture | Zero stranded inventory |
The point of the timeline is that a clean cut has almost no markdown in it. If you find yourself marking down a discontinued SKU by 40% in the last week to move it, the sell-down started too late. On the two fresh Verde Fresca SKUs, running roughly $28 and $24 per store per week across 345 stores, the difference between an eight-week sell-down and a two-week scramble was a few thousand dollars of avoided markdown and returns, which is real money on a $1.42M brand. The fresh code date is what makes this unforgiving: a shelf-stable broth at Kroger tolerates a sloppy sell-down because the product keeps for a year, but you do not get that grace on refrigerated salsa.
Compliance is the step everyone forgets
Here is the worked example that matters most in this chapter, because it is the one nobody plans for.
Six weeks after the salsa reset went live, the fermented segment lift the plan promised was showing up unevenly across the 345 Sprouts stores. Total category dollars were up, but nowhere near the plan's number. The obvious conclusion, the one a junior analyst reaches for, is that the plan was wrong: the fermented bet did not pay out, the extra facings did not move units, kill it next cycle. I have watched people write exactly that slide.
Before you conclude the plan failed, you check whether the plan actually happened. I pulled a store-level compliance read, and it told a completely different story.
| Store group | Share of 345 stores | POG status at week 6 | Fermented facings added? | Category $ vs plan |
|---|---|---|---|---|
| Reset on time, correct POG | ~74% (255 stores) | New planogram, set correctly | Yes | On plan or ahead |
| Reset on time, partial set | ~14% (48 stores) | New POG, but fermented facings short | Partial | Slightly behind |
| Never reset | ~12% (42 stores) | Still on the old salsa planogram | No | Flat, dragging the average |
About 12% of the stores, 42 of them, were still on the old salsa planogram six weeks after go-live. In those 42 stores the fermented facings never got added, so the segment could not grow because the shelf never changed. Those stores were not evidence that the fermented bet failed. They were evidence that the bet was never placed. When I stripped the never-reset stores out and looked only at the 255 that set the POG correctly, the fermented lift was tracking the plan almost exactly. The 42 laggard stores were capping the win the plan promised, and the plan itself was fine.
This is why the compliance check comes before the verdict. If you feed "the reset underperformed" into the category review without a compliance read, you kill a working plan on the strength of stores that never ran it. The correct read of that data is not "fermented does not work at Sprouts," it is "fermented works, chase the 42 non-compliant stores." Those are opposite actions off the same topline number, and the only thing that tells them apart is the audit.
The supplier's role in implementation
Here is the uncomfortable truth about step 7 from the supplier chair: you rarely control any of it. The retailer sets the reset date. The retailer distributes the planogram. The retailer's field team, or a third-party merchandising crew, physically sets the shelf. The retailer loads the promo calendar into its own system. You can build the best category plan in the room and still watch it land in only 88% of stores, because execution is not yours to run.
So your leverage comes from making the retailer's execution as easy and unambiguous as possible, since you do not control it. Three things move the needle.
| Supplier lever | What good looks like | Why it protects the reset |
|---|---|---|
| A clean, unambiguous planogram | Every position labeled, facings counts explicit, no "merchandiser's discretion" gaps | An ambiguous POG is where the 14% partial-set stores come from |
| A merchandiser-friendly cut-in | New-item labels, shelf tags, and set instructions that a crew can execute in minutes | A hard cut-in gets skipped or done wrong under time pressure |
| A compliance read you bring back | Store-level velocity showing which stores set and which did not | It turns "did it work" into "here are the 42 stores to chase" |
The planogram you built in step 6 is the physical artifact being implemented here, and its quality directly determines how many stores set it correctly. A POG that reads cleanly to a merchandiser who has never seen the category and has twelve resets to do that night is worth more at go-live than a beautifully optimized one that needs interpretation. And the compliance read you assemble afterward is the single most useful thing a supplier can carry into the next review, because the buyer's own field team often does not have a clean store-level view of what set and what did not. If you can hand her "here are the 42 stores still on the old POG, and here is the category dollars you are leaving on the table in them," you have made yourself useful in a way that has nothing to do with your own facings. That is the version of category management that earns a supplier a seat at the next planning cycle.
Anti-patterns
Three ways I have watched implementation go wrong, each one avoidable.
No compliance check. The reset goes live, the topline comes in soft, and someone concludes the plan failed without ever confirming the plan reached the shelf. This is the 42-store trap from above. A soft post-reset number has two completely different causes, a bad plan or a bad execution, and they call for opposite responses. Without a store-level compliance read you cannot tell them apart, so you are guessing, and the guess usually kills a plan that would have worked.
Assuming the plan equals the shelf. The approved planogram is a document. The shelf in store 214 in Fresno is a physical fact, and the two are not the same thing until a crew makes them the same thing. Every reset has slippage, on-time-but-partial sets, stores that missed the window, a merchandiser who read the ambiguous position as one facing instead of two. Plan for a compliance gap rather than being surprised by it, and build the audit into the timeline from the start instead of bolting it on when the numbers disappoint.
No sell-down for cut SKUs. Discontinuing the two slow fresh SKUs without a sell-down plan strands inventory on a fourteen-day code, which turns into markdowns, returns, or spoilage that eats the margin the cut was supposed to create. The cut and the sell-down are one decision, not two. If the plan cuts a SKU, the plan owns drawing it down cleanly, and that timeline starts eight weeks before go-live, not on reset day.
Doing this in Scout
Scout does not run the reset and it does not track store compliance directly. It has no field team, it does not see the physical shelf, and it cannot tell you whether store 214 set the new POG. That part lives with the retailer, and honestly, it lives partly with a phone call and a store visit.
What Scout does is the two reads that bracket the reset. Before go-live, it assembles the plan the reset implements: the SKU-level cut/keep list, the segment-before numbers, the velocity cuts that justify the added fermented facings, all off the SPINS extracts as a saved view instead of a rebuilt pivot. After go-live, it gives you the store-level velocity cut that lets you infer compliance, which is the load-bearing move in this whole chapter. When the fermented facings go up, the fermented velocity in that store moves, and when they do not, it does not. Break post-reset velocity out by store and the 42 never-reset stores separate themselves from the 255 that set correctly, because their fermented number sits flat while everyone else's climbs. That is an inference from movement data rather than a direct compliance audit, but it is usually enough to hand the buyer the list of stores to chase. Scout assembles the before-plan and reads the after-results. The buyer's field team still runs the shelf.
The short version
- A category plan is worth nothing until it reaches the shelf, and the gap between the approved planogram and the actual set across 345 stores is where most resets lose their promised win.
- Run implementation as seven workstreams off a fixed reset date, and never cut a SKU without an eight-week sell-down, because a fourteen-day fresh code turns a late discontinuation into markdowns and returns.
- Always check compliance before you judge the plan: when 12% of stores never reset, the soft topline is an execution miss, not a bad bet, and the fix is chasing 42 stores rather than killing a plan that worked.
Related: The category review meeting, step by step · Planograms and shelf space to sales