#zen-price

1 messages · Page 1 of 1 (latest)

crystal fern
#

That's correct it's not possible to do in the API. Only the Dashboard can mostly to support quickly correcting a typo
If you want to change the price of a product you add a new Price object. This ensures that you have good reporting/analytics in the future too

#

it only seems messy because you're manually testing a lot, which wouldn't mirror what you do in production

abstract nebula
#

I was planning to create prices based off a script (I want to create Product Variations), so let's say Print Sizes being the variable and creating let's say 4 prices for multiple products. It may become messy in production as well if a mistake or a change of mind in the price occurs.

#

Guess the only way to do it then would be to archive the mistakes if the amount of entries is too much to edit.

#

Is there a place where we could perhaps post suggestions for (possible) improvements? Or are these threads already being pushed forward whenever something of interest pops up?

crystal fern
#

That's the thing. You think it'll be messy, but it'd be messier to have a product for $19.99 today and next week it's $24.99 and then you want to A/B test your pricing. Having separate Price objects is the better implementation/abstraction, they are all tied to the same product and allow you to do analytics, price improvements, etc. while also rolling out the price changes only to a subset of customers

#

You can always flag this to our support team https://support.stripe.com/contact and we flag feedback internally ourselves too. That one though we do hear a lot from new users before they understand the upsides/power of having the right product catalog modeling

abstract nebula
#

I do understand that A/B-ing is useful to do, but for prices that never reached the light of day it seems odd to keep intact. But ah well, I'll go the archive route and perhaps create a flag in the metadata so I know the difference between archived prices and the ones I 'delete-archived'.

#

Thank you btw :)!

crystal fern
#

that makes sense, I do agree it's annoying for Test mode but if we supported it in Test mode, then you'd build your entire app based on that assumption 😅