davidthorand

[languid robin]

Hi
I'm sorry but this looks like a bit of a broad question! Is there a specific use case you're trying to account for?
I invite you start a first/test iteration and design according to your pricing strategy/models

[glacial mango]

Yeah, definitely! Just trying to learn from the wisdom of this community so I don't run into issues other people experienced before 😄

My current setup looks like this:

I have a product with 6 prices. The first 3 prices are my "tiers" with monthly billing and the last 3 prices are yearly billing. This works perfectly fine so far. Is this the recommended way? Also in terms of analytics later on?

An issue I have is the scenario of letting a user downgrade their subscription. I don't want them to downgrade instantly, instead with the end of their current billing period. How would I implement this?

[alpine notch]

👋 taking over for my colleague. Let me catch up.

I have a product with 6 prices. The first 3 prices are my "tiers" with monthly billing and the last 3 prices are yearly billing. This works perfectly fine so far. Is this the recommended way? Also in terms of analytics later on?
this seems fairly correct

[glacial mango]

So what about the downgrading scenario?

[alpine notch]

you can use billing_cycle_anchor: "unchanged" and proration_behavior: "none"

[glacial mango]

Oh well, that was easy. Thank you very much!