Overview
How might we design dynamic pricing so people can trust and act on AI output?
When this pattern fits
- Perfect for e-commerce platforms, marketplaces, and services where AI-powered dynamic pricing optimizes revenue and competitiveness.
When to skip or lighten it
- Regulated price floors or fixed-rate contracts.
- B2C contexts where unexplained personal pricing erodes trust.
- Low-volume SKUs with no data for stable models.
States
State model coming soon
Key UX elements
Key UX elements coming soon
Anti-patterns to avoid
Surge multiples with no cap or explanation.
Different prices per user with no disclosure where required.
Flickering prices every refresh on PDP.
Dynamic pricing on essentials during emergencies.
How products use it
| Product | Implementation |
|---|---|
| Uber | Surge indicator with multiplier before ride confirm. |
| Amazon | Frequent offer changes with third-party price trackers. |
| Airlines | Fare calendars showing demand-based shifts. |
| Hotel booking sites | Date-flex views with price heat by night. |
Implementation
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Dynamic Pricing" AI interface design pattern.
Pattern Definition:Frequently asked questions
What should buyers see?
Current price, recent range if policy allows, and plain reason when surging.
Lock price at checkout?
Hold quoted price for a short window so cart does not change mid-payment.
Dynamic pricing vs price drop alerts?
Dynamic pricing sets prices. Alerts tell buyers when those prices fall later.
Seller dashboard needs?
Rules, floors, competitor bounds, and simulation before publish.