Dynamic Pricing 101: Why Most Merchants Get It Wrong And How to Fix It

Dynamic Pricing 101: Why Most Merchants Get It Wrong And How to Fix It

đź§  Dynamic Pricing 101: Why Most Merchants Get It Wrong And How to Fix It

By Dr. Julie Williams, Ph.D. in Artificial Intelligence


Dynamic pricing isn't a buzzword. It's a discipline. And like any discipline, most practitioners fumble it—not because the math is hard, but because they treat it as a black box instead of a system. If you're a merchant, retailer, marketplace operator, or someone building commerce infrastructure, this article is for you. We're going to walk through why dynamic pricing fails more often than it succeeds, what the failure modes actually look like, and how to fix them with a combination of sound economics, clean data, and a bit of AI.


You'll leave with a mental model you can apply on Monday morning, not just a list of best practices.


A Quick Refresher: What Dynamic Pricing Actually Is

Dynamic pricing is the practice of adjusting prices in response to changing conditions—demand, inventory, competitor moves, time of day, customer segment, even weather. The "dynamic" part is the key word. It's not a discount campaign. It's not a promotion. It's a continuous, data-driven re-pricing loop.


In its simplest form, the logic looks like this:


$$P _t = P_{t-1} \cdot \left(1 + \alpha \cdot \frac{D_t - \bar{D}}{\bar{D}} + \beta \cdot (C_t - \bar{C}) + \epsilon_t\right)$$


Where $P_t$ is the price at time $t$, $D_t$ is observed demand, $\bar{D}$ is the baseline demand, $C_t$ is a competitor signal, and $\epsilon_t$ captures noise. You don't need to run this exact equation, but the shape of it matters: price should respond to relative shifts, not absolute levels, and it should respond to multiple signals simultaneously.


Most merchants skip this nuance. They look at one number—revenue, or margin, or a competitor's price—and adjust from there. That's static pricing with a calculator.


Why Most Merchants Get It Wrong

Let's be specific. There are five recurring failure patterns, and I've seen all of them in the wild.


1. They optimize the wrong metric.


The classic mistake is chasing revenue or GMV (gross merchandise value) in isolation. But revenue without margin is just a vanity number. A merchant who raises prices and watches revenue go up might be quietly destroying profit. A merchant who discounts and watches units move might be buying volume with margin. The correct objective function is typically:


$$\ max \sum_t \left( P_t \cdot Q_t - C_t \cdot Q_t \right) \cdot \gamma^t$$


That's a discounted margin maximization. Notice it's margin, not revenue, and it's discounted—future profit matters more than today's snapshot. Merchants who don't think in margins are pricing in the dark.


2. They treat price as a single lever.


Price is not one number. It's a vector. The same product at 10 a.m. on a Tuesday should not necessarily cost the same as at 8 p.m. on a Friday. The same SKU sold to a first-time buyer shouldn't cost the same as one sold to a repeat customer. Merchants who run one price per SKU are leaving money on the table in both directions—overcharging low-sensitivity segments and undercharging high-sensitivity ones.


3. They don't account for elasticity properly.


Price elasticity of demand—the responsiveness of quantity to a price change—is not constant. It's not even smooth. It's a function of time, segment, inventory position, and competitive context. A common mistake is estimating elasticity once, quarterly, and then treating it as a fixed coefficient. It should be estimated continuously, or at least weekly, and it should be segmented:


$$E _{i,s} = \frac{\partial Q_{i,s}}{\partial P_{i,s}} \cdot \frac{P_{i,s}}{Q_{i,s}}$$


Where $i$ is the item and $s$ is the segment. Merchants who use a single elasticity number for the whole catalog are essentially guessing.


4. They let competitors set the pace.


This is the "match the leader" trap. If you're always one step behind a competitor, you're never in control of the market. You're a price-taker, not a price-maker. And in a price-taker position, you're the last one to adjust, which means you're either overpriced (losing sales) or underpriced (giving away margin). Dynamic pricing should be reactive, but not slavish. You should be responding to the market, not to one participant.


5. They skip the feedback loop.


This is the big one. Dynamic pricing without measurement is just dynamic guessing. Merchants change prices and never close the loop: what did the price change actually do to conversion, to basket size, to repeat purchase, to margin? Without that loop, you can't tell if your pricing model is improving or just drifting.


How to Fix It: A Practical Framework

Here's the fix, broken into four layers.


Layer 1: Define your objective function explicitly.


Before you touch a single price, write down what you're optimizing for. Margin? Profit? Customer lifetime value? Market share? Pick one primary objective and one or two guardrails. For example:

  • Objective: Maximize weekly gross margin

  • Guardrail 1: No SKU price changes more than 15% in a 24-hour window

  • Guardrail 2: Discount depth never exceeds 40% off list price

Write it down. Show it to your team. Make it the contract.


Layer 2: Build a segmented pricing model.


Don't price one way. Price by segment. The segments that matter most for most merchants:

Segment

Example

Pricing Leverage

New customer

First-time buyer

Higher price tolerance, lower urgency

Repeat customer

3+ purchases in 12 months

Lower price sensitivity, higher loyalty value

High-intent

Cart abandoned < 1 hr ago

High urgency, high willingness to pay

Price-sensitive

Browsed 5+ competitors

Needs a nudge, not a discount

Bulk/bundle

10+ units

Volume discount, margin tradeoff

Each segment gets its own elasticity estimate and its own price adjustment rule. This isn't fancy. This is just... correct.


Layer 3: Use AI where it earns its keep.


This is where your doctorate in AI comes in handy, and I'll be honest about where AI helps and where it doesn't.


AI shines at:

  • Elasticity estimation at scale. You can't hand-estimate 50,000 SKUs. You can build a model that does it from clickstream, cart, and purchase data.

  • Demand forecasting. Short-horizon demand prediction (1–7 days out) is a well-solved problem and a massive lever for pricing.

  • Competitive signal ingestion. Scraping, parsing, and normalizing competitor prices across channels is tedious. Automate it.

  • Personalized price presentation. Not price discrimination (which can feel unfair), but smart presentation—showing the right price to the right segment at the right time.

AI doesn't shine at:

  • Setting the objective function. That's a business decision. AI can suggest, but you decide.

  • Guardrails and constraints. Those are policy, not prediction. You write them.

  • Customer trust. If your pricing feels arbitrary or unfair, no model will save you.

A good dynamic pricing system is 80% data infrastructure and 20% model. Merchants who invert that ratio end up with a fancy model on top of a leaky pipeline.


Layer 4: Close the feedback loop.


Track and report at least these five numbers weekly:

  • Average price per SKU (weighted by units)

  • Average margin per SKU (weighted by units)

  • Conversion rate by segment

  • Cart abandonment rate by segment

  • Repeat purchase rate by segment (lagged 30 days)

Plot them over time. Look for drift. When a price change doesn't produce the expected movement in conversion or margin, investigate. That's your model telling you it's wrong, and that's a gift.


A Simple Decision Heuristic

When in doubt, ask: "If I raised this price by 5%, what happens to units sold, and is the tradeoff worth it?"


If you can answer that question with a number and a confidence level, you're pricing dynamically. If you're answering it with "I think it'll be fine," you're pricing statically.


The Bigger Picture

Dynamic pricing is, at its core, a communication. You're telling your customers what you think your product is worth, right now, in this context. Do it well, and customers trust you. Do it poorly, and they game you. The merchants who get it right aren't the ones with the fanciest model. They're the ones with the clearest objective, the cleanest data, and the discipline to measure.


You don't need a PhD in AI to do this. You do need a PhD in attention. Pay attention to what's actually driving your numbers, and the prices will follow.


Dr. Julie Williamsis an AI researcher and commerce systems consultant. She spends her days building pricing and demand models for mid-market retailers, and her nights writing about where AI meets real business decisions.