#lennard_best-practices

1 messages · Page 1 of 1 (latest)

inner capeBOT
undone raftBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

inner capeBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1259799743354376212

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

tranquil oasis
#

👋 happy to help

near oasis
#

Hey, thanks!

tranquil oasis
#

did the answer that my colleague gave you not appropriate to your use-case?

near oasis
#

It did help, but I would need the first 100 to be free. How can I include that?

tranquil oasis
#

you just need to specify that the first 100 unit's unit_amount is 0

near oasis
#

I can also just make a 42$ base plan instead

tranquil oasis
#

then you can say the same but instead of 0-100 you would do 0-1

#

which is the same

#

since you're dividing by 100

#

does that make sense?

near oasis
#

Yep so I'd just create a threshold field in my db, and once it's 100 i clear it and call a metered usage of 1?

tranquil oasis
#

no

#

wait

#

we need to separate 2 concepts

#

pricing per unit and quantity transformation

#

pricing per unit is when you have multiple tiers

near oasis
#

Right

tranquil oasis
#

so basically you can say from
0-1 -> 0$
2-100 -> 1$ per unit
101-10000 -> 0.5$ per unit etc

#

and quantity transformation is when you want to establish anything between 0-> 100 to be considered as 1 package

#

so you divide by 100 the usage record and you round up

#

so combining those 2 concepts

#

you can have a package based usage (using the quantity transformation) with the first 100 units for free (using the first pricing tier 0-1 -> 0$)

near oasis
#

What i dont understand here is- how do I select that here then?

image.png
#

In package i cannot set a pricing for the first 100

image.png
#

the first tier of the packages of 100

tranquil oasis
#

give me a minute please

near oasis
#

Sorry if i am missing something obvious

tranquil oasis
#

no you're not

#

ok it seems I was wrong

#

it's not possible to combine both tiered price and transformation_quantity

near oasis
#

What i see is

a) Packaged pricing

I can do 7$/100 but not make the 100 first free

Solution: Make the monthly pricing 42$ instead of 49$ which includes the first 100.
But I do not like it as it feels bad practice.

b) Tiered pricing

I could do 7$/1 and do the packages myself, or 7ct each.
But I would not have the billing per transformation.

near oasis
#

So I guess the easiest way is 42$/mo and then the packaged pricing? I would just be worried the users would not understand that and wonder why my pricing site says 49$.

tranquil oasis
#

I think the best is to just not report the first 100

near oasis
tranquil oasis
#

I'm not sure I understand

near oasis
#

Well if i would have a $7/100 packaged pricing the CLI forces me to set the quantity to 1 anyways. So the only way would be to set the main price to 42$.

#

I will do that then, seems the easiest to understand for the client

#

Appreicate your help, made me understand a lot more.

tranquil oasis
#

sure let me know if you need any more help

near oasis
#

Thanks a lot and same to your collegue!

#

No other questions from me