Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hello,
Hmmm ... what's the best approach ?
For the same SaaS, I have different plans : plan A, plan B and plan C.
Are these plans differents products or the same product with different prices ?
Thanks for your answer ;).
V
Hey Vincent,
Definitely go with One Product -> Multiple Prices.
Having architected a few different SaaS platforms over the years, this is the standard and most scalable approach. If Plan A, B, and C are just feature tiers of the exact same application, Stripe is perfectly designed to handle them as distinct recurring Prices attached to a single Product.
In this cas, how is it possible to display the features for each price ?
Stripe doesn't have any way to give details on prices, it's just possible for products.
So the details for each price can only be defined in the application and not in Stripe ?
Are these plans differents products or the same product with different prices ?
@vincent15000 Only you can answer that.
Well ... users can use swap and change plans.
There will be different plans like for example :
plan A : functionalities 1, 2, 3, only one user
plan B : functionalities 1, 2, 3, 4, 5, up to 10 users
plan C : all functionalities, 10+ users
Do you call this different entitlements ?
What would you choose in this case ? one product and different prices ? or different products with one price ?
Hmmm I think I have understood ...
Plan A = product A / payment monthly = price A1 / yearly = price A2
Plan B = product B / payment monthly = price B1 / yearly = price B2
Plan C = product C / payment monthly = price C1 / yearly = price C2
Can you confirm please ?
Please or to participate in this conversation.