Subscription Fundamentals
Last reviewed: 16 November 2026
This page explains what a subscription business is and how BillHive models one. If you are new to recurring billing, start here.
What is subscription management?
A subscription business charges customers again and again for continued access to a product or service. Subscription management is everything needed to run that relationship over time:
- deciding what you sell and how it is priced (the catalogue),
- signing customers up and keeping track of what each one has (subscriptions),
- billing them on schedule and collecting payment (invoices and payments),
- handling changes: upgrades, pauses, cancellations, renewals,
- recovering failed payments (dunning), and
- measuring the business (MRR, churn, retention).
A one-off sale ends at the invoice. A subscription begins there: every month or year the system has to decide what to bill, bill it, collect it, and react to whatever the customer changed in between.
Subscription business models
| Model | How the customer pays | Typical example | BillHive building blocks |
|---|---|---|---|
| Flat recurring | Same amount every period | ₹499/month streaming plan | Rate plan with a flat price |
| Per seat / per unit | Price × quantity | ₹800 per user per month | Per unit price, quantity on the order |
| Tiered or volume | Unit price falls as quantity grows | First 10 users ₹800, next 40 ₹650 | Graduated or volume price |
| Usage-based (metered) | Pay for what was used | ₹0.20 per API call | Usage component plus usage events |
| Hybrid | Platform fee plus usage | ₹5,000/month + ₹0.15 per SMS | Several components on one price |
| Prepaid credits | Buy credit up front, draw it down | ₹10,000 pack with ₹1,000 bonus | Prepaid Credits |
| Fixed-term contract | Commit for N periods | 12-month contract billed monthly | Fixed price with term length 12 |
| Freemium / free trial | Free first, then paid | 14-day trial, then ₹999/month | Trial on the rate plan price |
The full list of price types is in Pricing Models.
B2B versus B2C
| B2C | B2B | |
|---|---|---|
| Buyer | One person | A company, often several contacts |
| Sign-up | Self-serve: pricing table and hosted checkout | Sales-led: an admin creates the order in the portal |
| Payment | Card, UPI, UPI Autopay | Bank transfer, cheque, eNACH, invoice with payment terms |
| Pricing | Public list prices, coupons | Negotiated prices, price overrides, contract terms |
| Invoices | Automatic, paid on the spot | Net 15/30/45 days, GST details, PO references |
| Changes | Customer uses the self-serve portal | Account manager makes changes |
BillHive supports both. Many businesses run both at once: self-serve for small customers, sales-led for large ones.
How BillHive models a subscription business
| Object | What it is | Where |
|---|---|---|
| Product | What you sell, e.g. “CRM Suite” | Catalogue > Products |
| Rate plan | A package of the product, e.g. “Growth” | Product > Rate plans |
| Price | What the rate plan costs in one currency and billing frequency, e.g. ₹2,000/month | Rate plan > Pricing |
| Add-on | An optional or mandatory extra billed with the plan | Product > Add-ons |
| Charge | A one-off or event fee, e.g. a setup fee | Product > Charges |
| Offer | A discount or coupon | Catalogue > Offers |
| Customer account | The company or person who pays | Customers |
| Order | A request to create or change a subscription. Every lifecycle action is an order. | Customers > Orders |
| Subscription | The running agreement: plan, price, term dates, status | Customer > Subscriptions |
| Invoice | A bill for one or more order lines | Customers > Invoices |
| Credit memo | Money owed back to the customer | Customers > Memos |
Subscription management versus traditional billing
| Traditional billing | Subscription billing |
|---|---|
| One invoice per sale | An invoice every period, automatically |
| Price fixed at sale | Price can change mid-term, so it must be prorated |
| Payment collected once | Payment collected repeatedly, often by auto-debit |
| A failed payment is a collections task | A failed payment threatens the whole relationship, so dunning matters |
| Revenue = sales | Revenue = recurring revenue (MRR/ARR) plus one-offs |
Key challenges in subscription businesses
- Mid-term changes. Upgrades and downgrades must be charged or credited fairly. BillHive handles this with proration.
- Failed payments. Cards expire and mandates hit their limits. BillHive retries and emails the customer through dunning.
- Churn. Customers who leave quietly. Track it on the Revenue Board.
- Tax. GST must be correct on every invoice, credit and refund. See Taxation Settings.
- Pricing experiments. New plans must not break existing subscribers. In BillHive, existing subscriptions keep their price until you change them.
Next
- Subscription Lifecycle: every stage from sign-up to expiry.
- Pricing Models: how prices are calculated.
- Glossary: terms used throughout these docs.