Run everything you never had time to implement. Define your process once, and keep it running with Qore.

All Articles
Platform Overview

10min read

Dynamic Pricing Examples: Real Scenarios for Amazon and Walmart Sellers

Posted:
November 5, 2026
|
 Last Updated:
November 5, 2026
Geoffrey Martlin

A pricing rule that looks sensible on paper can sell your best SKU below cost or strand it out of stock. Dynamic pricing, meaning software that changes your price inside limits you set, exists to catch both, and to find the price that earns the most when nothing is going wrong. This post walks through six ways Amazon and Walmart sellers use it, each with the condition the operator sets and what the system does inside it.

Quick answer: when dynamic pricing is most useful

  • Where it pays off: dynamic pricing is most useful when stock is running short, a competitor moves, demand swings with the calendar, fees shift under a stale floor, two marketplaces drift apart, or a steady SKU has room to earn more.
  • The pattern: every rule is a condition the operator defines, an action the system takes when it is met, and a limit the action can never cross.
  • The two limits: a minimum price keeps a rule from automating a loss, and a maximum price keeps it inside your MSRP and Amazon's pricing policies.
  • The opportunity: the same rules run forward, not only in defense. A profit test steps a price up while profit per day keeps rising.
  • The risk: a rule is only as good as the limit behind it, and a wrong floor loses money on every unit.

If you want the broader framework first, our guide to implementing a dynamic pricing strategy covers types of pricing, implementation approaches, and drawbacks. This post is the worked-numbers companion to it.

Every pricing rule is a condition, an action, and a limit

Before the scenarios, it helps to fix the vocabulary, because the pattern repeats in each one.

  • Condition: the observable fact that triggers a change, such as days of inventory cover, the current Featured Offer price, or units sold per day.
  • Action: the price move the system makes when the condition is true, usually a step up, a step down, or a hold.
  • Limit: the minimum price, the maximum price, or a margin requirement that the action cannot break. The maximum matters more than it looks: on Amazon, a price that climbs above MSRP or well above its recent reference price can cost you the Featured Offer or get the listing suppressed.

This is what separates dynamic pricing from editing prices by hand or from a tool chasing whatever number a competitor posts. Qinetix, our ads and dynamic pricing platform, runs pricing this way: the operator defines the guardrails, and the system executes inside them. For the difference between this and simple repricing, see dynamic pricing vs. repricing.

Example 1: An inventory-cover trigger slows sell-through before a stockout

Inventory cover is the number of days your current stock will last at the current sales rate. It is the most useful pricing condition for a seller with a long restock lead time, because a stockout costs more than a slightly higher price.

Illustrative setup:

  • SKU price: $40.00
  • Units on hand: 1,000
  • Sales rate: 50 units per day, which is 20 days of cover
  • Restock lead time: 45 days
  • Rule: if cover falls below 30 days, raise the price in 5% steps, up to a maximum of $46.00

What the system does: The 20 days of cover is already under the 30-day threshold, so the rule moves the price from $40.00 to $42.00. Suppose the higher price slows sales to 40 units per day. Cover is now 25 days, still under 30, so the rule steps to $44.10 and the rate drops again. At an assumed 32 units per day, cover is about 31 days and the rule holds.

The assumed sales-rate drops are the weak point of this example, and they are meant to be. You do not know your price sensitivity in advance, which is why the maximum price exists. If the rate never falls, the price stops at $46.00 and you have still earned more per unit on stock that was going to sell out anyway. The ceiling also keeps you under MSRP and inside Amazon's pricing policies, so a stock-driven increase never turns into a suppressed listing.

The same logic applies to advertising. A SKU with three weeks of stock left should not keep full ad spend either, and we cover that side in inventory-aware PPC. Ads and pricing run as parallel mechanisms with shared visibility, so you set the ad rule and the pricing rule separately.

Example 2: A competitor price move is matched only down to your floor

Dynamic pricing is used most often on Amazon for competitive rules: price relative to the Featured Offer (the listing that holds the Buy Box) or to the lowest offer in the marketplace. The mistake it prevents is chasing a competitor below your own cost.

Illustrative setup:

  • Your price: $25.50
  • Landed cost per unit: $12.00
  • Fees and fulfillment per unit (assumed): $5.50
  • Minimum price: $22.50, which leaves $5.00 per unit, about 22% of the price
  • Rule: price $0.10 below the current Featured Offer, never below the minimum

What the system does:

  • The Featured Offer sits at $25.00. The system moves you to $24.90.
  • A competitor drops the offer to $23.00. The system moves you to $22.90, still above the floor.
  • A competitor drops the offer to $21.00. Matching would put you at $20.90, below the floor. The system holds at $22.50 and does not follow.

That third step is the point of the example. Holding at $22.50 means you may lose the Featured Offer for a while, and the rule is doing what you told it to do: protect $5.00 per unit rather than buy volume at a loss. Whether to go lower is a decision for a person, made with the facts in front of them. The same rule works in the other direction: when you hold the Featured Offer with room between you and the next offer, it can step up toward that gap instead of leaving margin on the table. Our Amazon dynamic pricing guide walks through the competitive rule types Amazon supports and where each one fits.

Example 3: Peak and off-peak demand call for different ceilings

Price sensitivity changes with the calendar. A rule that raises price when sales velocity spikes and lowers it when stock stops moving lets the same SKU behave differently in a peak event and in a slow month.

Illustrative setup:

  • Base price: $30.00, minimum $27.00, maximum $34.00
  • Baseline sales rate: 20 units per day
  • Peak event sales rate: 60 units per day

What the system does:

  • Peak: velocity is triple the baseline, so a velocity-based rule steps the price toward the $34.00 ceiling as long as inventory cover stays healthy. The ceiling keeps you from overshooting into a price shoppers will not pay.
  • Off-peak: velocity falls below baseline and stock sits. The same rule steps the price down toward $27.00 to keep units moving, and stops there.

The two limits do different jobs. The minimum protects margin in the slow month, and the maximum protects conversion in the busy one. Set them from your own price history, and our price elasticity calculator is a reasonable way to test how much room you have before you commit to a ceiling.

Example 4: A margin floor has to move when fees move

A minimum price set at launch goes stale. Fees rise, costs change, and a floor that once protected your margin quietly stops doing so.

Illustrative setup:

  • Landed cost per unit: $10.00
  • Fees and fulfillment per unit: $4.00
  • Required margin: 15% of the selling price

The floor is the price where revenue minus cost and fees leaves 15%. That works out to $14.00 divided by 0.85, so a minimum price of about $16.50.

Now suppose fees rise by $0.25 per unit. The same calculation gives $14.25 divided by 0.85, or about $16.80. If the minimum price stays at $16.50, every sale at the floor leaves less than the 15% you required. Fees did move in this market in 2026: Amazon raised FBA fees in January, and a 3.5% fuel and inflation surcharge took effect on April 17. The $0.25 above is a round figure for the illustration, not Amazon's number.

What to do about it: treat the floor as a calculated value, not a typed one. Recompute it whenever fees, costs, or the required margin change, and review floors on a schedule. Qinetix shows margin after fees, so the floor can be checked against real numbers. Qore, the workflow layer that turns a manual review into a repeatable routine, can run that floor check on a schedule and stage any change for approval, since actions default to manual approval.

Example 5: Amazon and Walmart prices drift apart unless someone watches both

Sellers on both marketplaces face a different problem: the same product ends up at two prices for reasons nobody chose. A promotion on one side, a fee change on the other, or a manual edit left in place can open a gap.

Illustrative setup:

  • Amazon price: $35.00
  • Walmart price: $38.00 after an old manual edit
  • Walmart fees and fulfillment differ from Amazon's, so each marketplace has its own floor

What the operator sets: a rule that flags any gap larger than a set amount, a separate minimum price for each marketplace, and a decision about which marketplace leads. The system's job is to make the gap visible and to hold each price above its own floor. Where the gap should close is still your call, because a higher Walmart price can be intentional if it protects a distributor relationship or a MAP policy.

Dynamic pricing tools differ in how much of this they automate on Walmart versus Amazon, so check what your tool executes and what it only reports before you rely on it. For the marketplace-specific pricing mechanics, see our Walmart pricing strategy guide. If a MAP policy sets your hard floor, 8 ways to defend and execute your MAP policy covers enforcement.

Example 6: A profit test finds the price that earns the most, not just the price that is safe

The first five examples defend something. This one goes looking for upside. A SKU that holds the Featured Offer comfortably and sells at a steady rate may be underpriced, and the only way to know is to test the price upward and watch what happens to profit per day, not units per day.

Illustrative setup:

  • Price: $20.00, landed cost plus fees: $12.00, so $8.00 per unit
  • Sales rate: 100 units per day, which is $800 per day in profit
  • Maximum price: $24.00, the MSRP
  • Rule: raise the price in $1.00 steps while profit per day rises, step back when it falls, hold at the best price found

What the system does:

  • $21.00: sales ease to 96 units per day, profit is $864 per day. Keep going.
  • $22.00: sales ease to 88 units per day, profit is $880 per day. Keep going.
  • $23.00: sales drop to 72 units per day, profit falls to $792 per day. Step back to $22.00 and hold.

The sales-rate drops are assumptions, as in Example 1, and your curve will look different. The point is the direction. A rule that only waits for trouble leaves this $80 a day on the table indefinitely. The maximum price keeps the test inside your MSRP and inside Amazon's pricing policies, which can pull the Featured Offer or suppress a listing that climbs well above its reference price.

The six examples side by side

ExampleCondition the operator setsWhat the system doesLimit that keeps it safeOutcome
1. Inventory coverCover below 30 daysRaises price in 5% stepsMaximum price of $46.00Earns more per unit, avoids a stockout
2. Competitor moveFeatured Offer price changesPrices $0.10 below itMinimum price of $22.50Stays competitive, never below margin
3. Peak and off-peakSales velocity vs. baselineSteps toward the ceiling or the floor$27.00 minimum, $34.00 maximumCaptures peak demand, keeps stock moving
4. Margin floorFees or costs changeFloor is recomputed, then reviewed15% required marginFloor stays true as fees rise
5. Cross-marketplaceGap between Amazon and WalmartFlags the gap, holds each floorA separate minimum per marketplaceGap surfaced, each floor held
6. Profit testProfit per day at the current priceSteps up while profit per day rises$24.00 maximum (MSRP)Finds the price that earns the most

Green rows add profit, amber rows defend it, and purple rows keep the other rules honest. Read the limit column twice either way: each rule works only as well as the limit behind it, and the limits are inputs you own.

What dynamic pricing will not do in these examples

Dynamic pricing is a control system, and a control system needs good settings. Four limits apply to every scenario above, including the profit test:

  • It does not know your price sensitivity. The sales-rate changes in Example 1 were assumptions. Real sensitivity varies by SKU and season, so start with narrow ranges and widen them as you see results.
  • It does not replace a floor. Without a minimum price, competitive rules can follow a competitor below your cost.
  • It does not set strategy. Whether to defend the Featured Offer or protect margin is a business decision. The rule executes the answer you give it.
  • It does not coordinate with ads on its own. Pricing and advertising are separate mechanisms with shared visibility, so a price change does not automatically retune bids.

How to turn these examples into your own pricing rules

  1. Pick one condition per SKU group. Start with the one that hurts most: inventory cover for long-lead products, competitor price for commodity items, margin for anything with rising fees.
  2. Calculate the floor first. Use landed cost, current fees, and your required margin. Write down the formula so it can be recomputed.
  3. Set a ceiling. Use price history or an elasticity check, not a guess.
  4. Choose step sizes. Small steps, such as 2% to 5%, make the effect of each change readable.
  5. Log every move. Each automated change should leave a timestamp, the old price, the new price, and the rule that fired.
  6. Review on a schedule. Monthly for most catalogs, sooner after any fee change.
  7. Then test for upside. Once the defensive rules hold, pick a steady SKU and let a profit test step the price up inside its ceiling.

If you are still choosing between approaches, dynamic pricing vs. repricing and our Amazon pricing strategy guide help frame the decision.

Where Trellis fits: rules that run, and a review that keeps them honest

Every example above can be built by hand in a spreadsheet and a weekly review. Most sellers run out of hours before they run out of SKUs, and that is where Trellis' dynamic pricing earns its place. Qinetix runs the rules: Buy Box-aware competitive repricing, Days on Hand rules that react when cover drops, margin visibility after fees, and continuous evaluation of each price for profitability inside the floor and ceiling you set. Every change is logged with the rule that fired, so a price move always has a reason you can read.

Qore covers the review. The floor recompute in Example 4 and the parity check in Example 5 are the kind of recurring work an operator does by hand until they stop doing it. In Qore you describe the check once, lock it as a skill, and it runs on a schedule with any change staged for your approval. The result is the habit this post keeps returning to, done without the Sunday-night spreadsheet: limits set by you, execution handled, nothing changed that you did not sign off on. Qore is in open beta, and ads and pricing stay separate mechanisms with shared visibility.

Conclusion: start with the floor, then go looking for upside

The six scenarios differ in their conditions, but they share one habit: the operator decides the limit before the system acts. Get the minimum price right for each SKU and marketplace, add one trigger at a time, watch what it does in the logs, and then let a profit test show you where a steady SKU has room. If you want to see how that setup looks on your catalog, book a walkthrough and we will show you Qinetix and Qore running these rules in one place.

Frequently Asked Questions

A common example is a rule that prices $0.10 below the current Featured Offer but never below a set minimum. If a competitor drops to $23.00, the system follows down to $22.90. If the competitor drops below your floor, the system holds at the floor instead of following.

The operator sets a threshold in days of cover, meaning how long current stock lasts at the current sales rate. When cover falls below the threshold, the rule raises the price in small steps, up to a maximum, to slow sell-through until the restock arrives.

Yes, if the limits are wrong. Without a minimum price, a competitive rule can follow a competitor below your cost. A floor calculated from landed cost, current fees, and required margin, and reviewed when fees change, is the main protection.

They overlap, but simple repricing usually matches a competitor's price, while dynamic pricing also reacts to conditions such as inventory cover, sales velocity, and margin, all inside operator-set limits. Our comparison post covers the difference in detail.

The logic carries over: condition, action, and limit. What differs is how much a given tool executes on Walmart versus only reports, and Walmart fees differ from Amazon's, so each marketplace needs its own floor. Check what your tool automates before relying on it.

On a fixed schedule, monthly for most catalogs, and immediately after any change to fees, landed cost, or your required margin. A floor set at launch goes stale when those inputs move.

No. Every figure in this post is a round, hypothetical number chosen to make the arithmetic clear. They are not customer results or benchmarks, so use your own costs, fees, and sales data when you set rules.

Yes. Inventory-cover rules, velocity rules, and a profit test all step prices up inside a maximum you set. The ceiling matters on Amazon, where a price above MSRP or well above its reference price can cost you the Featured Offer or get the listing suppressed.

Spending too much time managing prices by hand?
Trellis’ Dynamic Pricing automates adjustments daily - helping you sell more, raise prices smartly, and grow revenue.
Schedule a Demo