Pricing Models
Last reviewed: 16 November 2026
This page explains each way of pricing a subscription, with a worked example, and where to set it up in BillHive. The exact builder fields and API rules are in Price Components and Charge Models.
All examples exclude GST unless they say otherwise.
How BillHive builds a price
A rate plan price is made of one or more components. Each component has:
- a type: recurring (seats or a fixed amount each period) or usage (metered),
- a charge model: how quantity becomes an amount,
- optional included quantity, minimum and cap,
- a billing timing: in advance or in arrears.
One pricing engine prices estimates, orders, plan changes, renewals, invoices and MRR, so the amount you preview is the amount that is invoiced.
Summary
| Model | The customer pays | Best for | BillHive charge model |
|---|---|---|---|
| Fixed (flat) | The same amount each period | Simple plans | FLAT |
| Per unit | Unit price × quantity | Seats, licences | PER_UNIT |
| Volume | Every unit at the price of the tier the total lands in | Rewarding big buyers | VOLUME |
| Tiered (graduated) | Each band of units at its own price | Fair usage pricing | GRADUATED |
| Stair-step | One flat price for the band the quantity lands in | Size-based plans | STAIRSTEP |
| Package | Price per pack of N units | Bundled usage | PACKAGE |
| Percentage | A % of a money value | Commissions, payment fees | PERCENTAGE |
| Usage-based | Any of the above, on metered usage | APIs, messages, storage | Usage component |
| Hybrid | Several components together | Platform fee + usage | Several components |
Fixed pricing
One amount per billing period, whatever the usage.
Example. Starter: ₹999/month. A customer is billed ₹999 every month.
Per-unit pricing
Price per unit × number of units. The quantity is set on the order and can change later.
Example. ₹800 per user per month, 12 users = ₹9,600/month.
Volume pricing
The tier that the total quantity reaches sets the price for every unit.
Example. 1–10 users ₹800, 11–50 users ₹650, 51+ ₹500. With 30 users, all 30 are in the 11–50 tier: 30 × 650 = ₹19,500.
Tiered (graduated) pricing
Each band is charged at its own price. Units in the first band keep the first band’s price.
Example. Same bands, 30 users: 10 × 800 + 20 × 650 = 8,000 + 13,000 = ₹21,000.
Volume and tiered pricing with the same bands give different amounts. Volume is cheaper for the customer once they cross into a cheaper band.
Stair-step pricing
The quantity picks a step and the step’s flat price is charged, whatever the exact quantity in the step.
Example. Up to 100 contacts ₹800, up to 500 ₹3,000, above 500 ₹4,000. A customer with 250 contacts pays ₹3,000.
Package pricing
Units are sold in packs. A rounding rule decides what happens to a part pack: charge a full pack, ignore it, or charge the fraction.
Example. ₹500 per 1,000 API calls, 2,500 calls, rounding up: 3 packs = ₹1,500.
Percentage pricing
A percentage of a money value recorded in usage events: per transaction (with a fixed fee, minimum and maximum) or as slabs on the period total.
Example. ₹2 + 2% per payment, minimum ₹10, maximum ₹500. A ₹10,000 payment costs ₹202. See Percentage.
Usage-based pricing
The customer is billed for what they used in the period. Your application sends usage events to BillHive; BillHive adds them up per subscription and prices the total with the component’s charge model. Usage is normally billed in arrears, at the end of the period.
Example. ₹0.20 per SMS, 1,000 SMS included. In March the customer sent 18,500: (18,500 − 1,000) × 0.20 = ₹3,500, billed on the April boundary invoice.
See Usage-Based Billing.
Hybrid pricing
Several components on one price, for example a platform fee plus usage.
Example. ₹5,000/month platform fee (in advance) + ₹0.15 per message (in arrears). In a month with 40,000 messages, the next invoice carries ₹5,000 for the new month and ₹6,000 for last month’s messages: ₹11,000.
Recurring charges, one-time charges and setup fees
| Charge | What it is | In BillHive |
|---|---|---|
| Recurring | Billed every period | Rate plan or add-on price |
| One-time | Billed once, e.g. onboarding | One-time fee component, or a product Charge |
| Setup fee | A one-time fee at sign-up | One-time fee component charged at sign-up |
| Per-event fee | A fee each time something happens, e.g. a number port-out | Per-event fee, raised through the API |
| Pass-through | A cost you pass on unchanged, e.g. carrier fees | Pass-through |
Discounts, coupons and promotions
BillHive calls discounts and coupons offers.
| Kind | How the customer gets it |
|---|---|
| Discount | Picked from the offers that apply to the plan when the order is placed |
| Coupon | The customer enters a code at checkout or the admin adds it to the order |
| Coupon set | Many single codes generated or uploaded for one offer, e.g. for a campaign |
An offer takes off a Fixed amount, a Percentage, or grants a Custom Trial. It lasts Forever, for Single Use (first invoice only) or for a Limited Time (for example 3 months).
Promotional pricing example. “50% off for 3 months” on ₹1,000/month: Percentage 50%, Limited Time 3 months. Months 1–3 cost ₹500; month 4 onward ₹1,000.
See Offers & Coupons.
Contract-based pricing
A customer commits to a number of billing periods.
- Use a Fixed price with a term length, e.g. 12 monthly cycles. After 12 invoices the subscription stops renewing.
- Add a notice period and an early termination fee in the cancellation settings to enforce the commitment.
See Billing Cycles and Term Length and Contract terms.
Price overrides
An admin can set a custom price for one subscription when placing the order, for a negotiated deal. The Price Override setting must be on, and only signed-in portal users can do it; API key requests can’t. Renewals keep the custom price. See Custom Prices on an Order.
Prepaid credits
The customer buys credit up front, often with a bonus, and usage is drawn from it. See Prepaid Credits.
Proration
When a subscription changes mid-term, only the part of the term that is affected is charged or credited.
Formula (Actual days): amount × days left (counting the change day) ÷ days in the term.
Example. A ₹3,000/month plan changed on day 11 of a 30-day term: 20 days left. Credit for the old plan = 3,000 × 20/30 = ₹2,000.
BillHive offers three methods: Actual days (default), 30/360 and Whole months. See Proration & Credits.
Choosing a model
See Pricing Strategy.