Support for quantity in APIs

• When creating subscriptions, ability to specify a quantity (e.g. price=$20/mo, quantity=$2 => invoiceItem recurring amount=$40). Related: #1434
• When creating external charges, specifying a quantity should be reflected into the invoice (e.g. price=$20, quantity=$2 => invoiceItem amount=$40)

[shaun-forgie]

You need to ensure the conceptual integrity of your framework is maintained. Define things in the catalog. Assign the catalog values to the subscription when creating it and update them as needed. A per seat usage cost for a given range of seats (top tier policy) can be defined in the catalog giving users price per seat costs for a given number of seats.

You then need to be able to query the system catalog for the per seat price at a given quantity so that this can then be used to update the subscription. In cases where only the quantity changes but the seat price remains the same only the quantity should be updated.

System logic on pricing and quantity breaks needs to be controlled at the server end. The client should ask the server for a change to the quantity of seats that are being applied to the subscription in much the same way that happens when previewing changes on future dated invoices with a dry run. Business alignment and approval rules can then also be applied to the change request.

Hope that helps.

[pcasaretto]

Got it. Just wanted to minimize the chance of duplicated effort.