#meteograms=checkout

1 messages · Page 1 of 1 (latest)

urban cloak
#

Yeah if you hit this issue it usually means you didn't design your product/price catalog the right way

#

Prices should be price variations of the same product (like different currency and such)

#

if you sell different products then you should separate them as separate products

somber hornet
#

What I had in mind was a subscription with a recurring price, but also with an up-front payment price... I would conceptually consider these are really both the same 'product' (subscription plan).

urban cloak
#

hmmm yeah usually they are 2 separate products

#

otherwise you'd do one price to unify them

#

imagine an internet plan but with the physical setup

#

the set up is a separate product

somber hornet
#

Yeah it would be nice to be able to set up a recurring price with an option for an up-front payment... but I suppose that having a separate 'setup' (or 'joining fee') product would do the job.

#

just spotted this in the API docs... looks like it is possible to add a custom description... but maybe it's better just to use a separate product anyway

urban cloak
#

yeah I'd rely on the separate product for reporting

somber hornet
#

For a payment mode Checkout it's possible to enable adjustable_quantity so that the customer decides how many to purchase. Is it possible to do it the other way around... have a fixed quantity (e.g. 1) and allow the customer adjust the price? I'm thinking of a model where the customer chooses how much to pay up-front, and this then affects the graduated pricing model on a metered subscription... e.g. £10 up front gets first 10 per month free, £100 up from gets first 100 free, etc. EDIT: I suppose you can have a field (before Checkout) to specify the amount, and then create a price for that amount?

urban cloak
#

No we don't support that approach today

#

you'd have to build this logic upfront before sending them to Checkout