Prompt
What should I use for billing when pricing changes often?
Latest observation
Nov 8, 2026
OpenAI APIWeb search: off
If your prices change often, the best billing approach is usually:
Use versioned pricing with effective dates
- Keep each price as a separate version.
- Store:
- product/service ID
- price amount
- currency
- start date/time
- end date/time
- Bill based on the price version active at the time of usage or subscription renewal.
For subscriptions
- Lock the price at signup for the current billing period.
- Apply changes only on the next renewal unless the contract says otherwise.
- Notify customers before price changes.
For usage-based billing
- Record usage with a timestamp.
- Apply the rate that was valid when the usage occurred.
- This avoids disputes if prices shift mid-cycle.
Good billing model options
- Price book / rate card if you have many changing prices
- Effective-dated pricing table if you need auditability
- Subscription plans with versioning if you sell recurring services
- Metered usage with historical rate lookup if prices depend on time
Avoid
- Overwriting the current price without keeping history
- Billing an entire month at whatever the latest price is if usage happened earlier
If you tell me whether this is for subscriptions, usage-based billing, or retail/invoicing, I can suggest a better structure.