#derbytau_best-practices
cunning pollenBOT
👋 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/1422112003354263686
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
fathom junco
On our Platform every connected account can sell "Extension" these "Extensions" are SaaS products. So we implemented them as subscription based Products. Now we implemented different feature sets for the same product. so we used different prices of one Product to represent the feature set. But we need to distinguish them on the invoice.
So i tried to update the line item before the invoice was finalized. But the API answered with:
"message":
"You may only update tax_rates, tax_amounts, or discounts for a subscription typed line item.",
now i try to find another solution without making each feature set an own product
if it is helpful: we create subscriptions by first creating a subscriptionSchedule to prevent the instant invoice. This is because we need to patch the invoice footer before invoice finalization
tired egret
To clarify, did you use this exact API? POST /v1/invoices/:id/lines/:id?
It has a description parameter
fathom junco
yes it has the description parameter, but the system said: "You may only update tax_rates, tax_amounts, or discounts for a subscription typed line item."
So for subscriptions it seems like I need another solution
fathom junco
yes: req_TekCb6FIhMpQFq
tired egret
Ah I see
For now all of them display the same Product description? How are they look like?
fathom junco
for example the invoice line item looks like this:
The Product is called "Postmaster"
But the Product has two different Prices and it would be great to distinguish them
FYI this is a Screenshot from the production environment and the request was from the test-mode but the product names in the test-mode are a bit goofy
tired egret
I see. Sorry I think the easiest solution is using different Products... But my colleage will be here shortly and let's see if we can have better suggestion
cunning pollenBOT
fathom junco
and I will not run into problems in our next iteration when I implement "tarif-changes" between the variantions if they are different products?
Which is the use-case for different prices for one product then?
clever dagger
hey there! taking a look into this now to confirm
can you clarify your latest question please? what do you mean by 'tarif-changes', and what problem would be caused by using different products?
fathom junco
Im not sure this was just my first thought with subscriptions. In short term we will provide the customers to change their subscriptions to change their used feature-set and I was not sure (because for now I didnt test it) if it is possible to update a subscription price to a price of another product.
But this does not mean that it is not possible only that I did not check it yet and thought it could be a risk
clever dagger
it's possible to update an existing subscription to use a different Price (attached to a different Product), if that's what you're referring to
to keep the billing structure the same, but simply change the description on the subscription invoice line items, we'd recommend creating a Product identical to the original, but associated with another Product (to use the Product name as the description)
sorry, clarification: ***creating a new Price, identical to the original, but associated with another Product
fathom junco
ok than we will do that 👍 but im a bit curious. What is the use case for the prices then?