#fartimusgladiolas

1 messages ยท Page 1 of 1 (latest)

junior basinBOT
smoky wind
#

Hi there

finite shard
#

hey @smoky wind !

smoky wind
#

Honestly I would probably go the other route and just create Prices as needed

finite shard
#

ok good to know! why so?

smoky wind
#

Will be much easier to handle reconciliation/reporting and stuff when you aren't dealing with high quantities

#

And there is no limit on the number of Prices you create

#

So basically each time you create a Sub you list your Prices (or check your database) for if a Price for that amount already exists

#

If so, reuse it

#

If not, create a new one

finite shard
#

gotcha ok. then if a customer wants to change their subscription (which they frequently do), leave the price as existing and dont' delete it or clean it up?

smoky wind
#

Well you need to update to the new Price you want to change to and remove the old Price

#

Otherwise you will charge them for both Prices

finite shard
#

right

smoky wind
#

But yeah, don't inactivate the Price you are moving away from

#

Can always re-use that Price for future Subs

finite shard
#

yup gotit

#

any gotchas with prorations to bear in mind?

smoky wind
#

I mean you want to handle proration as you see fit ๐Ÿ™‚

finite shard
#

(I wasn't sure how well prorations would work with quantities that large)

smoky wind
#

The quantity doesn't really matter

finite shard
#

(if we were going the quantity route)

smoky wind
#

It is all about the total amount from the previous Price and the amount of time compared to the same for the new Price/time

#

So proration should be the same here either way

finite shard
#

ok got it.

#

This is incredibly helpful. Thank you @smoky wind !

I'm going to need to relay this reasoning to my boss. Is there any way you could be more specific about the problems we will come up against regarding reconciliation/reporting with the high-quantity approach?

smoky wind
#

It really is up to you

#

I guess you could argue the alternative

#

But I think that pulling data based on 5 users using Price B for $10 is easier than pulling data of Price B of quantity 10 used 5 times

#

Overall either way works and it is really just up to you

finite shard
#

ah ok, thank you. Another follow up question - Again thank you so much @smoky wind I know your time isn't free. I really appreciate this.

Our business wants the ability to grant any kind of percentage discount. e.g. 37% on one customer for the next 3 months, 19% on another for 1 month, etc. It seems like the way to go with applying these discounts to a subscription would be to create a coupon on the fly (or reuse if it exists), similar to the pricing approach you mentioned?

smoky wind
#

Yep

#

You can create coupons with specific percent off and durations

finite shard
#

๐Ÿ‘