Static prices cost margin. Demand fluctuates, purchase prices move with it, competitors test daily. With dynamic pricing, you automatically control for margin, inventory pressure and competitive signals-withoutspreadsheet gymnastics. Result: more stable net margin, better position in channels and less dead inventory.

A good pricing system works with clear, explainable rules:
Minimum margin (hard): never below purchase × (1 + margin%).
Include channel costs: fees, shipping and return rates → drive by net margin per channel.
Curves & brand consistency: €34.90 instead of €34.87 (or whatever suits your brand).
Stock logic: high stock + low rotation → slight price drop; tightness → hold or slightly up.
Competitive bandwidth: moving along within ±x%, never below bottom.
Purchase price + discounts (current).
Channel costs (ads/marketplaces/fulfilment).
Stock & rotation (days on hand).
Demand/elasticity: effect of price on CTR/CR.
Competition: price + delivery time (legal sources).
Return impact: return ratio per SKU in your net margin.
Choose one category (≥50 SKUs) with stable demand.
Define lower bound: purchase + margin + channel cost + return buffer (e.g., +3%).
Put 3 lines live:
Rule A: if stock > 60 days, price -2% (respect bottom).
Rule B: as 3rd most expensive within your cohort, price -1% (up to bandwidth).
Rule C: Hero-SKUs move less; priority availability.
Frequency: 1× daily for entire category; hourly deltas for top SKUs.
Logging: old/new price, margin, position, CR; review after 2 weeks.
You don’t have to build a full econometric model. Start with steps:
Test ±1-3% price steps and log CR/sales per SKU.
Label 3 buckets: inelastic (CR remains), neutral, elastic (CR reacts).
Allow elastic SKUs to move faster; inelastic less (availability > price).
Overreact to noise → use moving averages (7-14 days) and minimum interval between price changes.
Cannibalization → set max range per week (e.g. ±5%).
Treat all SKUs equally → distinguish hero, long-tail and bundles.
Ignoring delivery time → fast delivery time sometimes justifies a higher price.
Net margin per order (after fees & returns).
Buy-box/position on marketplaces (without margin damage).
Stock rotation (days on hand toward target).
Price elasticity per SKU (CR change at increments).
POAS/ROAS: more stable due to healthy margin buffers.
Change budget: max number of price changes per day/SKU.
Approval rules: log jumps >5% and manual approval if necessary.
Version control: save rule sets (v1, v2) + rollback.
Transparency: pricing rules ≠ marketing promo; communicate clearly internally.
In niche shops (like our Padel cases), variant level is crucial. One size/color “out of stock” pushes the CR on the entire product. Pricing + stock logic at variant level keeps product detail healthy.
Pricing Smarter Together
Read
Why This Works
for our approach or schedule a
consultation
.
OnlineMarketingMan
Build. Automate. Expand.