#Alex - Subscription Limit
timber violet
The use case I'm trying to solve:
there is a company managing subscriptions for multiple users. So in our case customer == company
long latch
Hmmm...that seems like a problematic implementation. I saw in the SO thread it was suggested that multiple prices be grouped together under individual subscription records.
Is this not a feasible approach?
timber violet
in our case we have a company with thousands of customers. those customers have pretty much different billing cycles.
From what I understand we cannot simply create a single subscription with multiple prices as there will be a single billing cycle
Because billing cycle is attached to subscription and not to the price, correct?
just imagine that there is a manager who is turning on/off some service for people for different periods.
long latch
Billing cycles are set in the Price but each subscription can only have multiple prices with the same cycle
But just to clarify, the new limit for active Subscriptions for a Customer is at 500 presently
In that case you may need to split up the "customer" across multiple Customer records if you want to cover thousands of subscriptions
timber violet
Yeah but then each customer would need to have its own payment methods and billing history wouldn't be shared
Unless there is a way to somehow group customers under the same umbrella
timber violet
I see... So based on what you said (if i understood you correctly) here is what I can try to do:
- create a customer representing some company
- create a subscription with needed products
- when there is a need to subscribe a new user to some of those products we just bump the quantity. + store somewhere that information that this particular user is also subscribed to this product
With this approach we'll have a single billing date. Once the billing occurs we'll get the list of users who're subscribed to this product and will give them permission to use our product till next billing date. is it right?
long latch
Yes, using quantity for a specific price to represent the number of end-users associated with a specific Produce/Price would be the most sensible way to go
timber violet
ok I see, that makes sense for now. let me think on it. Appreciate your help a lot! 👍