Your competitor repriced its best sellers forty times while you slept. Amazon reportedly adjusts millions of product prices every day, airlines reprice seats continuously as a flight fills, and the ride-share fare you see at 5 p.m. is not the fare you would have seen at 3 p.m. If your prices still change only when you remember to update a spreadsheet, you are competing against algorithms with a price list. This guide explains how dynamic pricing works, which version fits a small business, where the legal lines sit, and how to keep your books coherent when no two sales happen at the same price.
What dynamic pricing actually is
Dynamic pricing is any strategy that changes prices in response to current conditions — demand, inventory, competitor moves, time of day, or input costs — instead of holding one fixed price. The changes can be automatic (software reprices your listings every few minutes) or scheduled (weekday vs. weekend rates), and they can move in both directions: up when demand surges, down when stock needs to clear.
Three related terms get mixed together, and the distinctions matter because customers and regulators react to each one differently:
- Dynamic pricing responds to the market. The price moves because demand, supply, or competition moved. Every shopper sees the same price at the same moment.
- Surge pricing is one type of dynamic pricing: prices rise when demand outstrips supply, then fall back. Ride-share fares during a rainstorm are the classic example.
- Personalized (surveillance) pricing responds to the individual, not the market. Two shoppers see different prices for the same item at the same time because the algorithm scored their browsing history, location, or device differently. This is the version drawing regulatory scrutiny, covered below.
For most small businesses, "dynamic pricing" in practice means the first kind: market-responsive prices with clear rules, not individualized quotes per visitor.
The five signals pricing algorithms watch
Whether it is a simple repricing rule or a machine-learning model, every dynamic pricing system reads some combination of the same five inputs:
1. Demand velocity
How fast is the item selling right now relative to its baseline? A product moving three times its normal daily rate can absorb a price increase; one sitting unsold for weeks needs a cut. Airlines pioneered this logic decades ago: the first seats sell cheap to guarantee a full plane, and the last seats sell dear to travelers with no flexibility.
2. Inventory position
Price is the fastest lever for moving stock. High inventory plus slow sales means markdowns; low inventory plus steady demand means holding or raising the price. Grocers mark down perishables in the evening and fashion retailers clear seasonal stock the same way — dynamic pricing just applies that instinct continuously and per SKU.
3. Competitor prices
For sellers on marketplaces, this signal dominates. On Amazon, winning the Buy Box — the default "Add to Cart" seller — depends heavily on landed price, so sellers run repricers that check rival offers constantly and adjust within a band they set. For marketplace sellers this is usually the input that moves prices most often, which is why floors matter so much (more on those below).
4. Time and context
Time of day, day of week, season, local events, even weather. Hotels charge more on Friday nights, ski shops discount in April, and parking apps price the hour before a stadium event differently from a Tuesday morning. If your demand has a predictable rhythm, scheduled price variation captures it without any fancy software.
5. Costs and margin floors
The signal sellers forget. Shipping rates, payment-processing fees, ad costs, and wholesale prices all move, and a price that held a healthy margin in January can be break-even by June. Good repricing setups work backward from a floor — the lowest price that still covers costs plus a target margin — rather than chasing competitors off a cliff.
Where you already meet it
You do not need to look far to see each model working:
- Airlines and hotels run the oldest dynamic pricing engines in business, adjusting fares and room rates against booking pace, remaining capacity, and how close the date is.
- Ride-share surge multiplies fares when rider demand exceeds nearby drivers, which both rations scarce rides and lures more drivers onto the road. The multiplier collapses as supply arrives.
- Marketplace repricers let even small Amazon, eBay, and Walmart sellers reprice catalogs of thousands of SKUs automatically — rule-based ("stay 2% below the Buy Box winner, never below $18.50") or algorithmic (software picks the price to maximize profit or Buy Box share).
- E-commerce storefronts on Shopify and similar platforms use apps that schedule sales, segment discounts by customer group, and test price points — scheduled and segmented variation rather than second-by-second repricing.
- Digital menus and shelf labels let food and retail chains push price changes to every screen at once, which is what made off-peak discounting newly cheap to operate.
Industry analyses of e-commerce adoption — including widely cited McKinsey figures — put the revenue lift from deliberate dynamic pricing in the 5 to 10 percent range, with margin gains on top when floors are enforced. The gains come less from charging more on average than from stopping the two silent leaks: selling too cheap at peak demand and holding dead stock at full price.
Rule-based vs. algorithmic repricing: which fits a small seller
If you sell on a marketplace, you will eventually face this choice. The two approaches differ in cost, control, and failure mode:
Rule-based repricers do exactly what you tell them: match the lowest competitor, undercut by a fixed amount, hold position N in the offer list — always between the minimum and maximum you set. They are cheap (many start free or under $30 a month), transparent, and predictable. Their failure mode is a race to the bottom: two rule-based sellers undercutting each other by a penny can walk a price down to both floors in an afternoon.
Algorithmic repricers use software models to choose prices against a goal you pick — maximize profit, win Buy Box share, clear slow stock — weighing competitor prices, sales velocity, and your margins together. They cost more (often $100-plus a month for serious tools) and their decisions are harder to audit, but they avoid penny-war spirals and can actually raise prices when the data supports it.
For most small catalogs, the sensible path is staged: start rule-based with strict floors, learn which SKUs actually respond to price moves, and graduate your winners to algorithmic repricing once the catalog or the competition outgrows hand-written rules. Mixed setups are normal — tight algorithmic control on high-volume listings, simple rules on the long tail.
Whatever you choose, set three guardrails before you automate anything: a floor (never below cost plus minimum margin), a ceiling (never above a level that invites buyer complaints or marketplace fair-pricing flags), and a maximum change per cycle so one bad data feed cannot halve your prices overnight.
The legal lines: what you can and cannot price on
Dynamic pricing itself is legal in the United States. What regulators police is which inputs move the price and whether buyers are misled. Four lines matter:
Line 1: Market signals good, personal characteristics bad
Pricing off demand, inventory, costs, and competition is ordinary competition. Pricing off race, gender, religion, or other protected characteristics violates federal and state civil-rights law — including California's Unruh Act, which reaches any business serving Californians. The compliance risk is indirect: an algorithm fed browsing history, ZIP code, or device type can reconstruct protected characteristics without ever naming them. If you personalize prices, audit what your inputs proxy for.
Line 2: Dynamic pricing vs. surveillance pricing
The FTC now draws an explicit distinction: dynamic pricing responds to market conditions, while "surveillance pricing" responds to data about the individual shopper. The agency has ordered information from pricing vendors and opened inquiries into individualized pricing built on personal data, and state attorneys general have launched their own sweeps. Market-responsive repricing is not the target of this scrutiny; per-visitor price discrimination built on tracking data is.
Line 3: The Robinson-Patman layer for B2B goods
If you sell tangible goods to business buyers, the Robinson-Patman Act of 1936 adds a rule: price differences between competing buyers must be justified by genuine cost differences (manufacturing, shipping, quantity), not by willingness to pay. It does not cover services or retail sales to consumers, but wholesalers and distributors running dynamic B2B pricing need cost justification behind their spreads — and the FTC has shown renewed interest in enforcing it.
Line 4: Deception is always actionable
Section 5 of the FTC Act bans unfair or deceptive acts, and state consumer-protection laws echo it. A price that jumps between the shelf and the register, a "discount" off a reference price you never charged, or drip-priced fees revealed at checkout can each trigger enforcement regardless of what algorithm set them. Transparency is the cheapest compliance program: show one price, honor it, and disclose fees early.
None of this should frighten a small seller off market-responsive pricing. Price on the market, keep receipts showing your inputs are market data, and disclose the price the buyer will actually pay.
How to run it without losing customer trust
The technology is rarely what sinks a dynamic pricing rollout — the framing is. In 2024 a major fast-food chain mentioned "dynamic pricing" on an earnings call, the public heard "surge pricing for burgers," and the backlash forced a hasty clarification that the plan had been off-peak discounts, not peak surcharges. The economics of the two are cousins; the psychology is night and day. Five practices keep you on the right side of it:
- Discount the trough instead of taxing the peak. Mathematically similar, emotionally opposite. "20% off weekday mornings" earns goodwill; "20% more on Saturday" earns screenshots.
- Explain the mechanism in one sentence. "Prices update nightly based on demand and availability" on a hotel page, or "Sale ends Sunday" on a storefront, converts suspicion into understanding.
- Change prices on a rhythm, not a twitch. Customers accept nightly, weekly, or seasonal updates; prices that move while they stare at the page feel rigged. Even algorithmic sellers can batch changes.
- Grandfather quoted prices. If a customer saw a price in a quote, cart, or booking flow, honor it through checkout. Mid-funnel repricing is the fastest way to manufacture a complaint.
- Watch the fairness hotspots. Emergency supplies during a disaster, essential goods with no substitute, and prices that vary by who is asking all attract disproportionate outrage — and, in emergencies, price-gouging statutes with no sense of humor.
Bookkeeping when no two sales share a price
Here is the part pricing guides skip: dynamic pricing quietly complicates your books. When every unit sells at a different price, three disciplines keep the numbers honest.
Record gross revenue per transaction, not per price list. Your revenue line should reflect what buyers actually paid. If a marketplace payout bundles hundreds of orders at different prices minus fees, book the gross sales and the fees as separate lines — never the net payout as "revenue," or your margins will look healthier than they are and your fee deductions will vanish at tax time.
Track average selling price per SKU, not just units. Units sold tells you volume; average selling price tells you what the repricer actually earned. A listing that sold 100 units at an average of $24 after fees is a different business than the same 100 units at $31. Most sellers learn this by pulling payout reports into a spreadsheet monthly; sellers with accounting software reconcile payouts against orders so the average falls out automatically.
Reconcile payouts against orders, not against expectations. With moving prices, you cannot eyeball a payout and know it is right. Match each settlement report to its orders, confirm fees and refunds line by line, and investigate the residue. For the mechanics of that matching on marketplace payouts, see the payout-reconciliation guides in the docs.
In a plain-text ledger, a week of variable-price sales might look like this — one entry per settlement, gross sales booked to income and the platform's cut booked to fees:
2026-10-15 * "Marketplace payout #4821" "42 orders, avg $26.40/unit"
Assets:Checking 987.65 USD
Expenses:Fees:Marketplace 121.15 USD
Income:Sales:Widgets -1108.80 USDWhen prices move daily, that average-price memo becomes the figure you actually manage: it is the number your repricer's floor and ceiling exist to protect. Visualizing the trend per SKU over time — average price against units sold — is where a dashboard earns its keep; the Fava web interface renders balance and income reports straight from the same ledger file.
Your first-week checklist
Start narrow, measure, then widen:
- Pick 5–10 high-traffic SKUs or one service with obvious peak/off-peak demand.
- Compute each one's floor: unit cost, fees, shipping, and minimum acceptable margin.
- Set a ceiling and a maximum single change (10–15% is a sane start).
- Choose rule-based repricing or a simple peak/off-peak schedule — not both at once.
- Write the one-sentence customer explanation and put it where buyers see the price.
- Log every price change with its reason for two weeks, then compare revenue, units, and average selling price against the prior two weeks.
- Only then extend to the rest of the catalog — and revisit floors quarterly as costs move.
Dynamic pricing is not about charging the maximum the market will bear every minute. It is about stopping the quiet losses: the peak-hour sale at an off-peak price, the dead stock gathering dust at full ticket, the competitor's cut you answered a month late. Fix those three leaks with clear rules and honest books, and the algorithm is just the messenger.





