> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/guides/revops-guides/guide-what-are-the-most-common-subscription-pricing-models.md).

# Guide: What are the most common subscription pricing models?

There are many different kinds of subscription pricing models to choose from, but some of the most common ones are below. No one model is better than the others; each one is designed to support specific product/service types and customer needs. Here’s how they work:

1. **Flat fee pricing:** A flat fee price is used for each product, as defined in your product catalog.
2. **Usage (or consumption) pricing:** A price is based on usage. For example, an internet provider might offer 2GB of data for $10/month and 5GB for $15/month.
3. **Per unit pricing:** A pre-negotiated price per license. This pricing model is important for self-service because it doesn’t require negotiations with sales reps to purchase more.
4. **Volume pricing:** Similar to tiered pricing, a user has a number of licenses that fall into a pricing band. For example, add-on support is offered based on the number of licenses as they fall into a given band. 1-10 users may be $5.00 License where as 11-50 may be priced at $4.95 per license. If the user has 12 licenses, their price would be $4.95\*12.
5. **Tiered pricing:** A price based on quantity bands or tiers. For example, a company selling enterprise software might charge $200 for 1 to 5 licenses, $150 for 6 to 10, and $100 for over 11. Unlike volume pricing, tiered is cumulative. If the user had 6 licenses, their price would be $200\*5+$150\*1.

Some companies — like software-as-a service (SaaS) companies — have subscriptions in their lifeblood. (We’re one of them.) But don’t let that fool you into thinking that subscriptions aren’t right for you, too. In fact, subscription pricing has touched every B2B industry.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/guides/revops-guides/guide-what-are-the-most-common-subscription-pricing-models.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.