archie_docs

[green cargo]

👋 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/1402020497855746170

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[obsidian tartan]

Hello, unfortunately we don't have a good way to do this at the moment. The most common workaround that I have heard of is creating duplicate prices/meters and adding them all to the same subscription. Unfortunately there is currently no way around the limitation of usage events being at the customer level as far as I am aware.

[pallid oracle]

OK, thanks. Would you point me to the most relevant docs for creating duplicate prices/meters?

[obsidian tartan]

We don't have a doc on that specifically, it is the same as creating the original meters and prices. You just do it again but with slightly different names https://docs.stripe.com/billing/subscriptions/usage-based/implementation-guide

Like for example you could create two meters, one with tokens-1 and the other with tokens-2 as the event name. Then you create two products named "Llama tokens" and prices for them. Then create a subscription that has both prices on it and report tokens-1 and tokens-2 events for the same customer

[pallid oracle]

We don't want to create more products but I suppose we could create different prices/meters?

What I'm imagining is:

1. Create a new meter dependent on an org

2. Create a new price for our usage-based enterprise plan specifically pointed at that meter

3. Add that price to the overall subscription

(all programmatically via the Stripe API)

Would that work?

[obsidian tartan]

Unfortunately you would need to create a new product as well, one product can only be assosciated with one meter

[pallid oracle]

Is there any way to prevent spamming my dashboard with new one-time products?

[obsidian tartan]

Unfortunately not, fixing this is one of the most common feature requests for usage based billing but there isn't currently a workaround that I'm aware of

[pallid oracle]

Could we use multiple customer objects and have them billed together?

Or, if that doesn't work, is there any way of breaking down on the invoice where usage came from? e.g. 1000 credits from project A, 2000 credits from project B, etc.?

[obsidian tartan]

Multiple customer objects would need to each have their own subscription object, which would mean separate invoices. So that wouldn't be unified billing unfortunately

And unfortunately there isn't a way to break down or designate usage, it all appears as one invoice item.

[pallid oracle]

Back to this, is there any way I can categorize products on my dashboard (like put them in a separate directory)? I just want to avoid clutter so I can easily manage the projects which aren't single-use

[obsidian tartan]

Not seeing a way to do that either. Apologies that that is turning in to a theme of this thread. That is a great feature request though, I have seen price/product clutter happen a few different ways.

[pallid oracle]

Can I submit this as a feature request? Would be very useful for us!

[obsidian tartan]

Yep, filing a request for that and adding to the one around more granularity for our new usage based billing subscriptions as well

[pallid oracle]

Is this one product or one price? On the dashboard I seem to be able to create two prices for the same product, associated with two different meters

[obsidian tartan]

My apologies, I was misremembering there. You are right that prices are what map to meters. So you would do many meters, one product, many prices here