> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/help-and-support/faqs/what-billing-models-does-marketplace-support-for-items.md).

# What billing models does Marketplace support for items?

SoftwareOne Marketplace currently supports three billing models that determine how you are charged for an item. These include usage-based, quantity-based, and one-time billing models.&#x20;

For all items, the billing model is shown on the **Items** page and in the **Items** step during purchase and change order workflows.&#x20;

<div data-with-frame="true"><figure><img src="https://1674205915-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ5DNbniz33mXCZoO62Rm%2Fuploads%2F4Jnpzvgzd6d6P66VEz4t%2Fimage.png?alt=media&amp;token=9c20c90b-b50f-40a1-814d-2e131f7285fa" alt=""><figcaption><p>The <strong>Select items</strong> step showing billing models when creating a purchase order.</p></figcaption></figure></div>

### Usage‑based billing <a href="#quantity-based-subscriptions-reservation" id="quantity-based-subscriptions-reservation"></a>

Usage-based billing means you are charged based on actual consumption of a product or service. This model is also known as pay-as-you-go. In this model, your usage is calculated and billed at the end of your billing period or commitment term.&#x20;

In  Marketplace, usage‑based billing applies to consumption‑based products sold as subscriptions, such as Microsoft Azure, FinOps for Cloud, AWS, and more. Products that are usage‑based clearly indicate this model during the purchase process.

For usage-based subscriptions, you cannot change the quantity after purchase, as you are billed according to actual usage, rather than a predefined quantity.

### Quantity-based billing

Quantity-based billing means you are charged based on the number of licenses you purchase.&#x20;

When placing an order, you select the quantity, and at the end of your billing period or commitment term, you are billed according to the total quantity purchased.

Quantity-based billing applies to subscription-based products, such as Microsoft 365. This billing model is displayed during the order workflow and on the [subscription details](/modules-and-features/marketplace/subscriptions.md#subscription-details) page after the order completes.

For quantity-based subscriptions, you can adjust the quantity at any time by adding or removing licenses.&#x20;

### One-time billing

In this model, you make a single, non-recurring payment for indefinite use of the product.&#x20;

This payment grants you a perpetual license, allowing you to use the software indefinitely. Once purchased, the license doesn't require any recurring payments or renewals.&#x20;

In Marketplace, perpetual licenses purchased through one-time billing are managed via [Assets](/modules-and-features/marketplace/assets.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform.softwareone.com/help-and-support/faqs/what-billing-models-does-marketplace-support-for-items.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
