Amazon Dynamic Pricing vs Competitive Repricing: Why Sellers Who Confuse These Two Lose Margin

Last updated: September 2026

Dynamic pricing and competitive repricing are not the same thing. They respond to different signals, use different data, and produce different outcomes when applied to an Amazon seller's catalogue.

Dynamic pricing responds to demand signals: when demand rises, the price rises. When demand falls, the price falls. Airlines use this. Hotels use this. Uber uses this during surge periods. The algorithm senses changes in the demand curve and adjusts price accordingly.

Competitive repricing responds to competitor signals: when a competing seller changes their price, your repricer responds. The signal is a competitor's action, not a buyer's demand. Most Amazon sellers who believe they need dynamic pricing actually need competitive repricing, and the distinction matters because applying dynamic pricing logic to a competitive repricing tool produces a strategy that responds to the wrong signal.

TL;DR: Dynamic pricing is demand-based: prices rise when buyer demand rises and fall when it falls. Competitive repricing is competition-based: prices adjust in response to what other sellers do. Amazon FBA sellers operate in a competitive marketplace where the primary pricing signal is what other sellers charge for the same product on the same listing. Competitive repricing addresses this correctly. The one exception is velocity-based repricing, where sales rate is used as a demand proxy, this is the closest Amazon repricing comes to true dynamic pricing.

What dynamic pricing actually is and where it came from

Dynamic pricing is a revenue management strategy where prices adjust automatically in response to real-time changes in demand. The price goes up when more buyers want the product than there is supply to meet them. The price goes down when demand weakens. The demand signal drives the price, not the competitive environment.

The origin is airline revenue management, developed in the 1970s and 1980s after US airline deregulation. Airlines discovered that the same seat on the same flight had different values to different buyers at different times before departure. A seat booked 90 days out had less demand pressure than a seat booked the day before. Yield management algorithms set prices to extract maximum revenue from the demand curve at each point in time.

Hotels followed the same model: room rates rise when occupancy is high and fall when it is low. The same room on a Tuesday in December costs less than on a Friday in July because the demand curve is different. The algorithm reads the occupancy signal and adjusts price accordingly.

Ride-sharing platforms use surge pricing: the ratio of driver supply to rider demand triggers automatic price increases during high-demand periods. The signal is purely demand-side, how many riders are requesting rides relative to how many drivers are available.

The common thread: in all these dynamic pricing implementations, the price responds to a measurement of demand relative to supply. There is no reference to what a competitor is charging. An Uber driver during surge pricing does not check what Lyft charges before setting the rate. An airline does not set prices by matching what United charges for the same route. The demand signal is primary.

How demand-based pricing logic works and why Amazon's marketplace is not the right environment for it

True dynamic pricing requires two things that most Amazon FBA sellers do not have: real-time demand measurement at the product level and a market structure where price rises during high demand without losing sales to competitors.

Requirement 1: Real-time demand measurement

Airlines know their own demand in real time because they control the booking system. Every seat request is a data point. They know exactly how many seats are sold at each price point and how many remain.

An Amazon FBA seller on a competitive listing does not have this visibility. They see their own sales velocity (units sold per day) but they do not see the buyer demand for the product, the total number of buyers searching for and considering the product. Amazon holds this data. Sellers do not.

Without real-time demand visibility, true dynamic pricing is not possible. A seller who raises prices because it is Q4 is applying a seasonal heuristic (a reasonable one), not reading a demand signal.

Requirement 2: A market structure that allows price increases during high demand

Airlines, hotels, and ride-sharing platforms have differentiated products where buyers accept price variation. There is only one seat in row 15A on a specific flight, you pay the price or you do not fly on that flight.

An Amazon competitive listing with 5 FBA sellers does not have this structure. If one seller raises their price during a high-demand period, the other 4 sellers hold the Buy Box at the previous price. The buyer who would have paid a higher price buys from a competitor at the lower price. Dynamic pricing logic on a competitive Amazon listing typically produces lost Buy Box time rather than higher prices.

The exception is when a seller is the only FBA offer on a listing. In that case, raising prices does not result in losing sales to a direct competitor on the same listing. But even then, the seller is competing against Amazon's own offers, substitutable products, and the buyer's ability to source elsewhere.

What Amazon repricing actually does: responding to competitor signals, not demand signals

Competitive repricing monitors other sellers' prices and adjusts your price to maintain a competitive position relative to theirs. The trigger is a competitor's action. The algorithm does not know whether buyer demand is high or low at the moment the competitor changes their price.

The competitive repricing signal chain:

1. A competing FBA seller on your listing changes their price

2. Amazon's SQS feed notifies Repricer.com of the event within seconds

3. Repricer.com evaluates the event: is this seller within your competitive set filter?

4. If yes: calculates the response price within your floor and ceiling

5. Submits the new price to Amazon via the Selling Partner API

6. The price goes live on your listing

At no point in this chain does the repricer evaluate whether buyers are searching more or less frequently for the product. It evaluates competitor behaviour.

This is the correct primary signal for an Amazon FBA seller. The Buy Box algorithm compares offers on the same listing. The most immediate determinant of whether you hold the Buy Box is whether your price is competitive relative to the other sellers who are currently listed. The competitive signal directly produces the Buy Box outcome. The demand signal does not directly produce it.

Where the confusion originates:

Amazon itself uses demand-based dynamic pricing on its own inventory. Amazon's first-party selling operation adjusts prices on millions of its own products in real time based on demand signals. When you see Amazon's price on a product change significantly, this is Amazon's own dynamic pricing in action, not competitive repricing.

Amazon seller tools also often use the word "dynamic" to describe any automatic price-changing functionality. This collapses the distinction. A tool that "dynamically reprices" as a feature description might be competitive repricing (responding to competitors) or velocity-based repricing (responding to sales rate) or genuinely demand-sensing, all described with the same word.

Book a Demo, configure competitive repricing rules in Repricer.com that respond to the correct signal for Amazon FBA sellers: competitor behaviour, not demand assumptions.

When Amazon sellers apply dynamic pricing logic to competitive repricing tools and what goes wrong

The most common error: configuring repricing rules as if the tool responds to demand signals when it actually responds to competitive signals. This produces strategies calibrated to the wrong driver.

Error 1: "Raise my prices when it's Q4 because demand is high"

A seller who wants prices to be higher in Q4 because Q4 demand is elevated is applying a reasonable market insight, but the mechanism they often use is wrong. Configuring a rule to "raise prices by 10% in November and December" without updating ceilings from Keepa seasonal data is a time-based rule, not a demand-based one.

The correct approach: update ceilings to the Q4 historical Buy Box price high from Keepa data before Q4 begins. The historical data shows the prices the listing has sustained in prior Q4 periods, a proxy for demand-supported pricing based on evidence rather than assumption. The repricer then raises toward this evidence-based ceiling when competitive conditions allow.

Error 2: "Lower my prices when I have too much stock"

A seller with excess inventory wants to increase sell-through rate. Lowering prices does increase velocity, but manually setting lower prices as a demand response is not the same as competitive repricing. A competitive repricer responds to competitors, not to inventory levels. The inventory-driven price reduction needs to be implemented through the ceiling (lowering the ceiling to compress the repricing range toward the floor) or through a specific clearance configuration, not through expecting the competitive repricer to sense the inventory situation.

Error 3: "I have high demand so I should raise my floor"

The floor protects margin, not demand. Raising the floor because demand is strong is the correct intuition (you want to capture more margin during high demand) but the mechanism is the ceiling, not the floor. Raising the floor reduces the repricer's room to compete for the Buy Box. Raising the ceiling allows the repricer to capture higher prices when competitive conditions support them.

These three errors share the same root: applying demand-side logic to a competition-side tool.

The one Amazon repricing feature that does respond to demand signals

Velocity-based repricing monitors your own sales rate (units sold per day or per week) and uses it as a proxy for demand. When your velocity is high, the assumption is that demand for your product is strong, and prices rise. When velocity is low, prices fall toward the floor to stimulate sales. This is the closest Amazon repricing comes to true dynamic pricing.

How velocity-based repricing works in practice:

Velocity is measured from your own order flow: how many units of a specific ASIN sold in the past 7 days, 14 days, or 30 days compared to a baseline or target rate. When velocity exceeds the target, the repricer raises prices. When velocity falls below the target, the repricer moves toward a lower price within the floor-to-ceiling range.

The underlying logic is demand inference rather than demand measurement: if units are selling fast, demand is probably strong. The repricer raises prices to capture more margin per unit while demand is elevated, even though it does not directly see buyer demand, only the output of demand (sales).

The limitation of velocity-based repricing on competitive listings:

Velocity on a competitive listing is a function of both demand (how many buyers want the product) and Buy Box share (what percentage of sessions your offer wins). High velocity while holding 40% of the Buy Box often indicates similar demand to lower velocity at 70% Buy Box share. Velocity-based repricing needs to be read alongside Buy Box win rate data to distinguish "high demand at current price" from "winning more Buy Box share because competitors are out of stock."

The BSR and velocity guide covers the BSR-velocity relationship and how to read velocity signals accurately alongside competitive data.

How to set your repricing strategy from competitive intelligence rather than demand guessing

The correct Amazon repricing strategy uses competitive data as the primary signal, historical price data as the ceiling input, and cost data as the floor input. Demand signals inform the ceiling update cadence and the ceiling level, but they do not drive individual repricing events.

The competitive signal: real-time

Your repricer responds to competing sellers' price changes in real time via the SQS event feed. This is competitive intelligence at its fastest. The response configuration (rule type, competitive set filter) determines how the repricer uses this signal.

Rule type by competitive density (from the win rate benchmarks guide):

• 1 to 2 FBA sellers on the listing: ceiling-hunt rules that probe toward the ceiling when the competitive set is thin

• 3 to 4 FBA sellers: position-targeting rules that maintain a specific win rate band

• 5+ FBA sellers: match rules that hold the competitive Buy Box price

The ceiling: historical demand evidence

The Keepa 90-day historical Buy Box price high is the best available evidence for the maximum price at which buyers have purchased the product from FBA sellers. This is demand-evidence rather than real-time demand sensing. Update ceilings quarterly to keep this evidence current. During Q4 or pre-Prime Day periods, pull the prior year's seasonal high as the ceiling input, this is seasonal demand evidence applied to the ceiling, which is the correct place for demand thinking.

The floor: cost precision

The floor is the minimum price that protects margin after all Amazon selling costs. Cost data, not demand data, produces the floor. The Net Margin Repricing page covers automatic floor recalculation when costs change.

The framework:

• Cost data → floor (competition-independent, static)

• Historical demand data (Keepa) → ceiling (updated quarterly)

• Competitive data (SQS feed) → repricing events between floor and ceiling

This framework uses demand evidence where it belongs (ceiling-setting) and competitive signals where they belong (event-level repricing decisions). It does not require real-time demand sensing, which Amazon sellers do not have access to.

Key Takeaways

• Dynamic pricing responds to demand signals. Competitive repricing responds to competitor signals. These are different data sources producing different pricing behaviours.

• Most Amazon FBA sellers need competitive repricing, not dynamic pricing. The primary determinant of Buy Box win rate is competitive pricing relative to other sellers on the listing, a competitive signal, not a demand signal.

• Applying dynamic pricing logic to competitive repricing tools produces three common errors: treating time-of-year as a demand signal (rather than updating ceilings from Keepa seasonal data), expecting the repricer to respond to inventory levels (rather than configuring ceiling compression for clearance), and raising the floor instead of the ceiling when demand is strong.

• Velocity-based repricing is the closest Amazon repricing comes to dynamic pricing. It uses sales rate as a demand proxy and adjusts prices accordingly. It is one tool feature, not the primary repricing mode for most FBA sellers.

• Demand thinking belongs in ceiling-setting. The Keepa historical Buy Box price high is demand evidence. Updating the ceiling to reflect seasonal patterns is the correct application of demand intelligence in Amazon repricing.

Action Plan

1. Identify which pricing problems you are trying to solve. If the problem is "I keep losing the Buy Box to competitors," the solution is competitive repricing. If the problem is "my prices do not rise when demand is strong," the solution is ceiling updates from Keepa seasonal data.

2. Check your current ceiling is set from Keepa historical data (the 90-day Buy Box price high for each ASIN). If it is set from an estimate or left at a round number, the ceiling is not evidence-based.

3. For Q4 or seasonal peaks: pull the prior year's seasonal Buy Box price high from Keepa for each active repricing ASIN. Set this as the Q4 ceiling before October.

4. Check your rule type matches the competitive density of each listing. Pull the active FBA seller count per ASIN and verify the rule type follows the competitive density framework: ceiling-hunt for 1 to 2 sellers, position-targeting for 3 to 4, match for 5+.

5. If you want velocity-sensitive pricing: confirm whether your repricer plan includes velocity-based repricing and what the velocity thresholds are. Configure the velocity threshold alongside your ceiling, not as a replacement for the ceiling.

Frequently Asked Questions

1. What is dynamic pricing on Amazon?

Dynamic pricing on Amazon refers to two different things depending on context. Amazon itself uses demand-based dynamic pricing on its own first-party inventory, adjusting prices in real time based on demand signals across its marketplace. For third-party sellers, "dynamic pricing" is often used loosely to describe any automatic repricing functionality, which is more accurately called competitive repricing. True demand-based dynamic pricing (prices rising when buyer demand rises, independent of competitor action) requires real-time demand measurement that Amazon third-party sellers do not have access to.

2. Is Amazon repricing the same as dynamic pricing?

No. Competitive repricing responds to competitor price changes and Buy Box status updates. The trigger is another seller's action. Dynamic pricing responds to demand signals, buyer demand, occupancy, requests, and adjusts prices based on the ratio of supply to demand. Amazon FBA sellers operating on shared product listings cannot see real-time buyer demand. They see competitor prices and their own sales velocity. Competitive repricing addresses the competitive signal that actually determines Buy Box allocation. Dynamic pricing logic addresses a demand signal that third-party sellers cannot directly measure.

3. How does a repricer use demand signals?

Most competitive repricers do not use demand signals directly, they respond to competitive events (competitor price changes, stock level changes, Buy Box status updates). The exception is velocity-based repricing, which uses your own sales rate as a proxy for demand. When units are selling quickly (high velocity), the repricer raises prices on the assumption that demand is strong. When velocity is low, the repricer moves toward the floor to stimulate sales. This is demand-proxy pricing rather than demand-signal pricing, because the repricer infers demand from the output (sales rate) rather than measuring it directly.

4. What is sales velocity repricing?

Sales velocity repricing is a repricing mode that monitors how quickly your units are selling (units per day or week) and adjusts prices based on whether that rate is above or below a target. When velocity exceeds the target, prices rise. When velocity falls below the target, prices move toward the floor. It is the closest Amazon third-party repricing comes to true dynamic pricing, because it uses sales rate as a demand proxy. It is most useful for sellers with private label or unique inventory where buy Box competition is limited, on shared competitive listings, velocity is as much a function of Buy Box share as of demand, which complicates the demand inference.

Book a Demo, configure competitive repricing rules and velocity-based repricing for your Amazon catalogue. See the Repricer.com features page for the full rule type and velocity configuration options.