A Retail Velocity Report That Tells You What to Do Next

A specialty food CEO opens Monday's retail velocity report. Artisan Marinara scanned 4.1 units per store per week at Kroger, down from 4.8 last quarter. The report states the number. It does not state whether to run a promotion, pull the SKU from underperforming stores, shift production volume, or prepare a defense for the upcoming line review. The CEO closes the report and calls the broker.

The broker gives an opinion. It may be correct. It is not derived from the data that generated the question.

This is the gap in every velocity report: the numbers describe what happened, but they do not prescribe what to do. The velocity decision tool closes that gap. Nine decision modes, same underlying scan data, each one answering a different operational question with a specific recommendation.

The retail velocity report is not the point

Velocity data (units per store per week, scans per point of distribution, dollars per door) sits in every retailer portal and every syndicated data subscription. The data is not scarce. What is scarce is the translation layer between the number and the decision.

A CEO who sees velocity declining at specific stores needs to know: Is this a shelf-defense problem (the buyer is about to cut facings), a production-planning problem (the forecast is wrong), a distribution problem (the wrong stores carry the product), or a pricing problem (the last promotion trained customers to wait for deals)?

Each interpretation leads to a different action. Each action has a different cost. Picking the wrong one is not neutral. It spends trade dollars or operational resources on a problem the brand does not have while the actual problem advances. The revenue lifecycle from contract to cash includes enough cost layers that misdirected effort compounds quickly.

Nine modes, nine questions

Portfolio Health is the default landing view. It aggregates risk indicators across every decision area and surfaces what needs attention immediately. The CEO starts here and drills into the mode that answers the specific question.

Shelf Defense answers: Is this SKU about to get delisted? It flags items where velocity has dropped below the retailer's category threshold for two or more consecutive periods. The output is not "velocity is declining." It is "this SKU is at risk at these stores, and here is the trend the buyer will cite in the line review." The time-series view shows the trajectory. Brands that see the trend before the buyer raises it control the conversation; brands that hear it for the first time in the review do not.

Production Planning answers: How much should I produce over the next four weeks? It translates velocity trends into production forecasts by SKU, accounting for promotional lifts, seasonal patterns, and store-count changes. A brand that produces from shipment data (what it sent last month) and a brand that produces from scan data (what actually sold last week) will build different quantities. The scan-based forecast is the one that avoids both overstock waste and short-ships.

Promo ROI answers: Should I run that promotion again? It calculates the incremental lift, the trade cost, and the post-promotion velocity dip for each historical promotion. A promotion that lifts volume 30% during the event but depresses baseline velocity for three weeks afterward may have a negative net return even though the in-period numbers looked strong.

Distribution Expansion answers: Which stores should I pitch next? It identifies doors where the brand is not present but the category velocity suggests above-average potential. The pitch to the buyer is not "we want more doors." It is "these specific doors sell this category at 2x the average and we are not in them."

Distribution Pruning answers: Which stores are not earning their shelf space? The inverse of expansion. Doors where velocity has fallen below the cost of servicing them (including broker commission on the incremental volume, delivery cost, and compliance risk) are candidates for voluntary withdrawal before the retailer makes the decision involuntarily.

SKU Rationalization answers: Which SKUs should I cut or keep? It ranks the portfolio by contribution and velocity across all doors, flagging items that are wide but dead (high distribution, low velocity) and items that are hidden gems (low distribution, high velocity). Cutting the former and expanding the latter improves portfolio economics without changing total door count.

Launch Trajectory answers: Is my new product on track? New items get a dedicated time-series view benchmarked against the brand's historical launch curves. A new SKU that underperforms its category benchmark by week 8 is not "still ramping." It has a placement problem, a merchandising problem, or a product problem, and the data shows which.

Pricing Power answers: Should I promote this SKU again, or has it trained the customer to wait? It identifies items where promotional frequency has eroded baseline velocity: the customer buys on deal and skips the regular price. The signal is a widening gap between promoted and non-promoted weeks.

Decisions, not dashboards

The tool runs on Cinderhaven Provisions: a synthetic $25M specialty food brand, 50 SKUs across six retailers, with 1.2M rows of weekly scan data spanning a 902-store scan universe. Promotional history, seasonal patterns, stockout events, and new product cannibalization are all present in the dataset. The company is invented; the decision logic and the operational questions are real.

Each mode includes a data grid, a chart, and a narrative "so what": not a summary of the numbers, but a statement of what the numbers mean the CEO should do next. The purpose of the tool is to make the report itself unnecessary. The report is the intermediate artifact between the data and the decision. If the tool can go from data to decision directly, the report adds a step without adding value.

See the tool live: portfolio health view loads first, nine decision modes available from the navigation. If your Monday velocity report ends with "interesting" instead of "here's what we do," that's the conversation.