#Mister_Punk
vital sable
flint adder
Hello! Do you have a question about that?
viral bear
yeah we were doing API ID like moBasic247 which was for our monthly basic $247 plan, this helped us know what plan it is by API ID plus it allowed us to match the price ID on live and test to be the same
today I noticed we can no longer personalize the API ID
so now we have a problem we can't add a new price plan anymore
flint adder
Are you getting an error from the API when you try to specify an id?
viral bear
on stripe interface this option no longer exists
when i add a new price in stripe web interface
flint adder
Yeah, it's no longer available in the Dashbord.
viral bear
it used to have a text box to write a custom API ID
ok is this feature going to be completely removed and wont be possible to have personalized API IDs?
flint adder
We very much discourage custom IDs, but I believe they are still possible via the API. Let me confirm...
viral bear
why do you discourage this?
its super useful for us
makes plans easily identifiable
and allows us to match test vs live
because now if we add to test and live the same price will have a different ID which is a problem
as until now all our prices had the same ID in test vs live
saved us a lot of hassle of having to keep separate IDs for test vs live
the product copy feature is pretty bad, it doesn't copy with the same product id
have no clue why its copying and generates a new ID instead of keeping the same
on my next zoom meeting with stripe product team will mention this issue.. we're mostly sorting out subscription editing to make it better/easier... but the IDs is a technical thing so am trying to understand why it has been removed
flint adder
I honestly don't know the specifics of why we discourage it. We recommend you keep track of your own internal IDs and things of that nature using metadata: https://stripe.com/docs/api/metadata
viral bear
prices dont have metadata
flint adder
viral bear
cant edit it on dashboard
flint adder
They also have a lookup_key you may be interested in as well: https://stripe.com/docs/api/prices/create#create_price-lookup_key
viral bear
we use the dashboard all the time so if we cant do it or see it on dashboard its useless to us
thats backend only, we need to be able to see it on the dashboard
ok so adding metadata to prices on dashboard thats one more thing that needs doing lol
flint adder
The only Dashboard option would be the Price description:
viral bear
need to write it all down for the next product meeting hehe
meanwhile there's a bug on interface:
Product Prices - bug when deleting a price, it doesn't update interface and shows the delete dialog again after deleting
i dont know if you guys do only API or also sort out dashboard issues
flint adder
This server is focused on developer and technical issues. Most of what you're asking about falls outside that scope and you'd likely be better off working with Stripe support instead. 🙂
viral bear
ahh okay will sort out with stripe product team when we have next call
ok so is it possible to create a price with custom API ID through API?
flint adder
Doesn't look like it, no. I got an error. Might be possible on an older API version though...
viral bear
i guess it was deprecated then so best to move on lol 😄
will have the dev separate the API ID from test vs live from now on
will present the use cases to the product team see if they will put that back or if there's a big enough reason not to have it 🙂
flint adder
Looks like custom IDs can be set on Products and Plans, but not Prices.
viral bear
on products also no option on dashboard to set a custom ID
so i think it has also been removed
is there a way to move prices from one product to another?
because right now all our plan recognition is done based on prices so we have 1 product then several prices in that product
then we use the price API ID to recognize that
this allows us to aggregate all prices of a price plan into 1 product rather than multiple products as it would be a mess
flint adder
No, it's not possible to move a Price to a different Product. The recommendation would be to archive the existing Price and create a new Price under the other Product.
I'm not sure I completely understand your use case, though. Can you tell me more about the difficulty you're having? Why would using multiple Products be a mess?
viral bear
we use primarily the dashboard to look at stats etc
we have 3 plans.. Basic, Growth, Pro
so we want to see for example how many subscriptions we have in each plan
so we have 3 products matching the plans
then dif prices as we update/change prices over time and have clients in several dif prices but same plan
so would be like 10 dif prices in Basic etc.. but we want to see how many Basic subscribers we have
when we look at dashboard stats the way its done is by showing MRR per product
on Billing Analytics
flint adder
Okay, that all makes sense to me so far.
viral bear
products is a broader view
then plans = prices thats a drill down view
which means products should not be plans they should be a category of plans
like here is a plan analytics
it only shows 4 top ones sadly
no option to see more lol
if we had products used as plans then the "Plan" option would become useless
since products and plans would show the same stats
am guessing this would also be true for ecommerce if you have same shirt in dif colors you'd want to have that shirt as a product then dif colors as a price in the product, not each as a product
on dashboard point of view allows to see which shirts sell best then also drill down to see which color of each shirt sells best
on API of course you can see whatever you want so organizing things looks like it makes no difference as you use metadata.. but if you dont consider the dashboard way of organizing data then it will render the dashboard useless
flint adder
Yeah, honestly I don't use the Dashboard that much, especially not to look at the stats you're talking about, so I'm out of my depth.