#jacobjeppesen_best-practices
pure ospreyBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1328381665529298976
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
grave totem
*and additional usage should be named "Business plan (additional usage)".
steel burrow
No downsides that I can think of, our subscriptions are designed to manage up to 20 prices at once by default. Are there specific sticking points that you are forseeing that you are trying to think of how to address?
grave totem
Not directly, but I was wondering if the reason why the docs recommend to do it with a single product with multiple prices could be because of how integrated pricing plans and checkout sessions were made. So, I just wanted to be sure that by not following the docs, I didn't make something more difficult for myself down the road with some of those built-ins in Stripe(?)
*integrated pricing plan = embeddable pricing table
steel burrow
Ah gotcha, apologies I missed the pricing table aspect. Unfortunately pricing tables only support making Checkout sessions with a single price as far as I am aware. So that would be a limitation if you are using pricing tables, but if you use Payment Links or even create your own Checkout Sessions, you can separate them in to two prices
grave totem
Ah, ok. But I would need multiple prices either way, so I'd probably need to create my own checkout session anyways. I'll go with multiple products with a single price then 🙂
steel burrow
Yeah we reccommend using products to differentiate different things that you sell. So even Silver and Gold tier on the same account would normally be two different products. We reccommend using prices for different ways to pay for that same product. So like the monthly vs yearly price for a Silver tier plan
grave totem
Makes sense. Do you know why the docs propose two have a single product with multiple prices in https://docs.stripe.com/billing/subscriptions/usage-based/pricing-models#fixed-fee-overage ? It seems like the recommendation should be two products; one for the subscription fee and one for the additional usage.
steel burrow
I am honestly not immediately sure, especially because our tiers let you specify a flat fee themselves. I will ask my colleagues if they have a better idea
grave totem
I think avoiding the flat fee in the metered billing is because then it would be charged and the end of the cycle. With two different prices, the flat fee can be charged at start of cycle as normal fixed rate price, and any additional usage would then be charged and the end. But sounds like there's not a good explanation. Found this thread which proposed multiple products too: https://www.reddit.com/r/stripe/comments/1fpek7e/stripe_package_with_multiple_prices_for_platform/
steel burrow
Yep, good catch! Exactly what my colleague said, you can add a flat fee to the tiers of the usage based price if you want the flat fee charged at the end of the month, but if you want an upfront fee and usage based overage then two prices would be the way to go.
grave totem
Did your colleague say anything about the single product with multiple prices in the docs vs. multiple products with single prices from your recommendation? Otherwise it's all good, and I'll just go with your recommendation of multiple products with single prices to makes checkouts and invoices look much better.
steel burrow
I think that lines up with out general advice because this is representing paying for units of the same thing in this case. I think it is up to personal preference in this case. If you think it is clearer for your users to have these as separate products so that they have separate invoice items, that will result in the same price.