#ryan3358_best-practices

1 messages ยท Page 1 of 1 (latest)

frigid hamletBOT
#

๐Ÿ‘‹ 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/1316440670759551057

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

timber aspen
#

To my understanding, subscriptions currently use the current date as the start date for calculating proration amount. Just want to know if we can pass a start date in instead due to individuals purchasing for the future ahead of today.

leaden hullBOT
spice harness
timber aspen
#

With a subscription schedule, will it still send the proration invoice when its created? or will it send on the subscription schedule start date

oblique aspen
#

The goal is for us to start the subscription at a custom start datetime (different than purchase datetime), and collect money immediately

timber aspen
#

then from there act on the normal billing schedule on the first of the month thereafter

oblique aspen
#

Can we do a quick audio call thru discord with you @spice harness ?

spice harness
#

That's a more complex flow.

You'll want to:

  • process a one-time payment, likely via a one-off Invoice
  • create a Subscription Schedule to create the Subscription in the future, and also use a trial period, coupon, or $0 Price to have the Subscription that gets created avoid charging the Customer for the first billing period.
#

Sorry, we don't offer calls here.

#

Let me know if any of that is unclear though and we can discuss it further.

frigid hamletBOT
oblique aspen
#

We're still a little confused on best way to continue without manually calculating a TON of prices for each product

#

We have a monthly rate we want to pro-rate, and the daily rate will change based on how long month is (28 days, 29 days [leap year], 30 days, 31 days)

#

Then once we have the daily rate, we have to multiply by number of units (ie. "days remaining in month") - so there would be hundreds of prices for just one product

#

are there any price_ID limits?

daring cargo
#

There is not a limit on how many prices a product can have, no. Since your set up is a bit more complex the above is what would use.

timber aspen
#

This seems a bit overly complex no? Given that when you create a subscription the current execution time is used to calculate the proration, why is it not possible to set a proration date?

#

Hypothetically, if we were to start a trial on the current execution date that ends on the custom start date, would it calculate the prorated amount based on the custom start date until the next start of billing cycle?

daring cargo
#

Yes, and I highly recommend that you test this using your tesk API key.