#highgate-subscriptions

1 messages · Page 1 of 1 (latest)

calm zenith
hardy pine
#

Thanks! I'll try that right away.

#

But when creating a price, we need a "Product" right? Or create a new product using the "product_data" parameter.

I would preferably not create a new product every time, that will never be sold again, since each "one-off" payment is a new product?

Another option could be to have ONE product but with dynamic pricing?

#

The business case is that you need to have a subscription to be able to book certain things. Each booking will be a custom price based on the day and time booked.

#

So a typical invoice will be:

  • Monthly subscription $10
  • Booking 4.25 hours $8
  • Booking 2 hours $2

etc.

calm zenith
#

yep you need a Product, or can create one ad-hoc. What probably makes sense is to have one Product with a name like One-off booking charge and create all these dynamic Prices against that product.

#

alternatively you would have to create a bunch of Products (the description on the line item is always the name of the Product)

hardy pine
#

Each "One off booking" line on the invoice needs some custom description added to it (like booking reference), so that the customer could match the invoice line to the actual booking. So I guess the only way forward then would be to create a new "Product" for each booking?

calm zenith
#

unfortunately yep, that's the only option. It's a common pain point with how this is modeled, the line items on the Invoice come from Products directly so it's hard to customise them without a lot of proliferation of Products

hardy pine
#

No worries! Thanks a lot @calm zenith. This was very helpful ☺️