Your Retail Problem Isn't Demand. Prove It With the Sales Export You Already Have.

When a product underperforms on retail shelves, the story writes itself: 'customers just aren't buying it.' It is a comfortable conclusion because it lets everyone off the hook. It is also, most of the time, wrong. The demand is usually there. The execution is not. And you can prove which one it is with a file you almost certainly already have — the raw sales export from the retailer.

'Our product isn't selling' is a demand claim. 'Your stores aren't executing' is an execution claim. The export tells you which one is true.

The 7-step execution audit

The goal is to separate a demand problem (people don't want it) from an execution problem (people can't find, reach, or buy it). Here is the sequence:

1. Normalize the export. Clean the raw retailer file into consistent units, stores, and weeks so you can actually compare like with like.

2. Segment stores into velocity tiers. Group locations into low, mid, and high sellers. Velocity is your proxy for execution quality on the ground.

3. Compare units per store per week across tiers. If the top tier moves several times the volume of the bottom tier for the same product, demand exists — something is different about how the low tier is executing.

4. Look at distribution and availability, not just sales. A store selling zero may be a store that never had stock on the shelf, not a store with no interested shoppers.

5. Model realistic upside. Estimate the gain if low-tier stores merely reached mid-tier velocity. Never model everyone hitting top-tier — that is fantasy and it destroys your credibility.

6. Read online demand as corroborating evidence. If the same SKU over-indexes online in a region where it stalls in stores, that is a strong signal of in-store availability or placement failure, not lack of interest.

7. Translate findings into store-level actions. Point to the specific tier, the specific gap, and the specific fix.

Why velocity tiers are the whole game

The single most persuasive view is units per store per week, split by tier. Demand-level factors — how appealing the product is, whether people want the category — apply roughly evenly across all your stores. So when identical products sell fast in one tier and stall in another, the difference is not demand. It is shelf placement, stock, staff, signage, or the retailer's own operations. The tier spread is the fingerprint of an execution problem.

The honesty that protects your credibility

The fastest way to lose a buyer's trust is to model the low-tier stores suddenly performing like your best doors. Nobody believes it, and you shouldn't either. Model the low tier reaching the middle. That is a grounded, defensible number, and it is usually more than enough to justify the fix. Conservative math you can stand behind beats aggressive math that gets you laughed out of the meeting.

Get the data before the meeting, not in it

This whole analysis depends on one unglamorous prerequisite: you need access to the raw sell-through data before you walk into the room. Request supplier-portal and retail-media access early, and find out who actually controls your reporting. If your only window into your own performance is a commissioned rep agency or a middleman, you are negotiating blind and they know it. Never let someone whose incentives differ from yours be your sole source of truth on how your product is really moving. Own the export, and you own the conversation.

How the conversation changes

Walk into a retail review with this analysis and the discussion shifts. You are no longer defending your product against a vague charge that it doesn't sell. You are pointing at a specific set of underperforming stores and a specific execution gap, with the retailer's own data on the table. 'Our product isn't selling' becomes 'these stores aren't executing, here's the evidence, and here's the upside if we fix it.' Same file. Completely different meeting.

And notice what this does to your own team's story. 'We tried retail and it failed' is one of the most expensive sentences in consumer goods, because it closes a door that data might have kept open. An execution audit forces the harder, more useful question: failed how? In which stores, at what velocity, with what availability, over how long a window? Define the failure with numbers before anyone's memory gets a vote. More often than not, what looked like a dead market turns out to be a fixable execution problem hiding behind a tidy conclusion.