Separate Stripe Products from Prices before changing a SaaS pricing page

A SaaS pricing page is easier to change when Stripe Products and Prices are treated as separate decisions. The product is what the customer buys. The price is how that product is charged: amount, currency, billing interval, usage type, trial context, or regional variant. Mixing those concepts makes every pricing experiment feel like a catalog migration.

Stripe Prices API documentation represents price objects separately from products, and Stripe’s pricing table documentation uses configured pricing data to present checkout choices. The useful planning rule is to keep product identity stable when the feature package remains the same, then create or select prices for the charge pattern. That avoids turning a monthly-to-annual test, regional currency addition, or launch discount into a confusing product rename.

Before changing the visible pricing page, record product name, customer-facing promise, included limits, active price IDs, archived or legacy price IDs, checkout surface, entitlement mapping, tax or currency assumptions, and migration rule for existing subscribers. If the page shows “Pro,” the billing system should know whether Pro monthly, Pro annual, and Pro launch discount are prices for the same product or meaningfully different packages.

This separation also helps support. A customer asking why their invoice changed should not force the team to reconstruct old pricing from screenshots. Stable product identity plus explicit price history makes billing changes auditable, explainable, and less risky during small SaaS experiments.

Separate Stripe Products from Prices before changing a SaaS pricing page

// COMMENTS

ON THIS PAGE