#jackyfreeds_best-practices
brave scarabBOT
đ 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/1435282908947546213
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
azure cove
hello
astral lotus
hey there, its likely that you have prices associated with those products, so they cannot be deleted (since prices cannot be deleted)
https://docs.stripe.com/api/products/delete
Deleting a product is only possible if it has no prices associated with it.
So archive is what you want to do to here
brave scarabBOT
rough jewel
hi there, taking over here from my colleague. the same holds true for the dashboard, products can't be deleted if they're already associated with a price
azure cove
Okay, but how do I delete the price? Is there anyway otherwise I have a lot of irrevlent information clean-up work to do when I was testing
rough jewel
you can only delete prices if they've never been used. otherwise the only alternative is to archive them https://docs.stripe.com/products-prices/manage-prices#delete-price
azure cove
So used means being associated to any catalog, even if they've never been used in a purchase?
rough jewel
that's correct
azure cove
hmmmm
okay, I have some more questions as well.
Would you recommend I built an area in my portal to configure features and packages easily so I don't need to always hardcode those packages through Stripe?
rough jewel
that's up to you, but you certainly can. you would use inline prices instead of defining them explicitly through Stripe
azure cove
interesting, specifically this is what I am trying to achieve
so without going through each of the features, I need a way to provide different entilements, features for the different plans.
However I don't want to find myself in a mess of things that have been hardcoded to each plan incase I want to change them - so anything I can do to make it modular I think would be best to scale.
rough jewel
got it, so have you been working with the Entitlements API? https://docs.stripe.com/billing/entitlements
this would allow you to share feature definitions between products, which might give you the modularity you're looking for
azure cove
I haven't started developing with it yet, but had a feeling thats what I'll need to do
I am using Loveable, so how would I prompt to assosciate a feature on more portal with a stripe entitlement?
rough jewel
I'm not really familiar with Loveable so I can't say. maybe there's a way to feed it links to the doc, so that it has examples of how to build?