Skip to main content
Pricing tables use immutable releases. Your integration always keeps the same pricing-table key; PriceOS chooses the right release for each customer.
  1. Create a pricing table, configure it, and select Go live. This publishes version 1.
  2. When your pricing changes, open the live release and select Create new release.
  3. Update the draft and select Go live.
The new release becomes the table shown to visitors and new subscribers. Existing subscribers keep seeing the release associated with their active Stripe subscription. They remain on that release when they switch plans within the same subscription. Once their subscription has fully ended, a later subscription receives the current release. Published and legacy releases are read-only. Keep using the same pricingTableKey in your landing page or app; create a separate table key only when the placement needs an independently managed table. For authenticated in-app pricing tables, configure the PriceOS server handler to identify the current customer. Do not trust a customer ID supplied by browser code to make entitlement decisions.