Most pricing analysts spend their time watching prices. They track competitor price changes, monitor their own price positioning relative to category norms, and review conversion rates as a lagging indicator of price sensitivity. What they rarely look at alongside that data is inventory depletion rate — the speed at which units are selling down against available stock. That metric, which we call demand velocity, is often the cleaner signal for where pricing headroom actually exists right now.
The oversight is understandable. Pricing and inventory management have traditionally sat in separate systems, owned by separate teams with different workflows. The pricing analyst pulls from their analytics stack; the inventory planner works in their warehouse management system or ERP. The data exists in both places, but connecting it in real time for pricing decisions isn't part of most teams' standard workflow. It should be.
What Demand Velocity Actually Measures
Demand velocity, at its most basic, is units sold per day divided by total units on hand — a percentage depletion rate. A SKU with 200 units in stock selling 20 units per day has a velocity of 10% per day, meaning it depletes in roughly 10 days at current pace. A SKU with 400 units in stock selling 4 units per day depletes in 100 days.
That depletion rate, on its own, is useful for inventory planning. What makes it useful for pricing is the interaction with your competitive price position. A fast-depleting SKU with no meaningful competitive pressure — meaning you're already priced at or above competitors and still selling quickly — has pricing headroom. The demand is there at your current price. That's an argument for a modest price increase test, not a price hold.
A slow-depleting SKU where competitors have recently undercut your price is a different story. The velocity has likely been suppressed by the competitive price gap. That gap, combined with the slow depletion, is a signal to either match or cut price to restore velocity — or to examine whether the SKU belongs in your active catalog at all.
The Four Quadrants That Guide Decisions
Mapping demand velocity against competitive price index — how your price compares to the median price for comparable items in your competitive set — creates a simple four-quadrant framework that tells you where each SKU sits relative to its optimal pricing position.
High velocity, competitive at market or above: This is the headroom quadrant. You're selling fast and you're not underpriced. A modest price increase — typically 3 to 8% — is worth testing. Watch the velocity response over 5 to 10 days. If velocity holds, the market is telling you the price increase is sustainable. If velocity drops more than 15%, pull back. The test costs you a small number of marginal conversions; the upside is a permanent margin improvement on your best-moving SKU.
High velocity, underpriced vs. competitive set: This is the recovery quadrant. You're leaving money on the table at scale because you're converting well at a price below market. Here the repricing case is stronger than in the headroom quadrant — you're not testing willingness to pay, you're correcting a structural mispricing. Move price toward market and monitor for velocity sensitivity.
Low velocity, underpriced vs. competitive set: This is the investigate quadrant. The SKU isn't moving despite being priced below competitors, which suggests the issue is not price. It could be product photography, placement in your navigation, missing variants, or a product that simply doesn't resonate with your audience. Don't cut price further here — the velocity issue isn't price-driven and you'll just erode margin without solving the problem.
Low velocity, priced above competitive set: This is the markdown candidate quadrant. Your price is likely a contributing factor to the slow movement, and competitors are positioned more aggressively. Depending on your inventory position and target gross margin on this SKU, a price reduction toward market is warranted — either to restore velocity or to accelerate depletion if you're looking to clear the inventory.
A Practical Example With Real Numbers
Consider a DTC outdoor gear brand with a hydration pack SKU — 28L capacity, mid-range price point. The SKU has 340 units in stock. Over the past 14 days, they've sold 68 units — a daily velocity of 4.9 units per day. At that pace, the stock depletes in roughly 70 days, which lands well after the peak summer selling season.
Their current price is $79. Competitors in their defined competitive set are priced between $68 and $86 for comparable products. The brand is positioned in the middle of the competitive range — not underpriced, not overpriced, sitting comfortably at the median.
Now add the velocity context. If average daily velocity for this category in peak summer is 8 to 10 units per day and this SKU is running at 4.9, the depletion rate relative to the selling season is concerning. The competitive set isn't the problem — the brand is priced at market. The low velocity is a product-or-positioning signal, not a pricing signal. Cutting price here would accelerate depletion but would cost margin without addressing the underlying issue.
Compare that to a second SKU — a 20L daypack priced at $59, with 180 units in stock and a daily velocity of 22 units. At that pace, it depletes in about 8 days. Competitors are priced between $62 and $71 for comparable packs. This SKU is in the underpriced-high-velocity quadrant: strong demand, clear pricing headroom. A $4 to $6 price increase toward the competitive midpoint is a defensible call. If the velocity holds even at 18 to 20 units per day after the adjustment, the brand has permanently improved margin on a top-moving SKU.
Why This Requires Real-Time Data
The catch with demand velocity as a pricing input is that it's time-sensitive in a way that weekly reviews can't fully address. Velocity is a snapshot metric — a 14-day trailing average is more stable than a 3-day average, but it still goes stale. A SKU that was in the low-velocity quadrant on Monday might be in the high-velocity quadrant by Thursday if a competitor goes out of stock and traffic shifts. The pricing opportunity that existed Thursday may be gone by Monday's review.
This is the core argument for continuous monitoring of both velocity and competitive position simultaneously, rather than tracking them in separate workflows on different schedules. The interaction between the two signals is what creates actionable recommendations. Either signal alone, reviewed on a weekly cadence, is context without clarity. Together, and updated frequently, they tell you which SKUs are worth reviewing now and which can wait.
What We're Not Claiming
We're not saying demand velocity is sufficient to drive repricing decisions on its own. Price elasticity varies by product category, customer segment, and brand positioning. A velocity signal that suggests pricing headroom in a commodity category may not apply in a brand where price is part of the value proposition. A slow-depleting SKU in a luxury-adjacent category might reflect deliberate scarcity rather than pricing error.
What we are saying is that velocity data belongs in the same decision flow as competitive price data when you're evaluating repricing recommendations. Without it, competitive intelligence tells you how your price compares to the market but doesn't tell you whether the market price is working for you. Velocity closes that gap. It's the inventory system telling the pricing team what the demand signal looks like in real time — a signal that deserves a seat at the table when decisions get made.