> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/go-to-market/concepts/rate-cards.md). # Rates A tariff defines the price at which you sell Plenit services to your customers. It is the financial basis of all Go to Market: budgets calculate prices from it and billing relies on it. Understanding how a tariff works is understanding how you make money as a partner. ### The double layer: your cost and your price In Plenit there are two prices for each service: * The **PVD** (wholesale price) is what it costs you as a partner. It is the price we bill you at. * The **PVP** (retail price) is what you charge your end customer. The **margin** is the difference between both: what you earn. When you configure a tariff, you start from the cost (PVD) and apply the margin you want to set the sales price (PVP). > #### 📘 How the price is calculated from the margin > > The sales price is not simply the cost plus the margin percentage, but rather the cost divided by (1 minus the margin): `Price = Cost / (1 - margin)`. > > For example, with a cost of €100 and a margin of 25%: 100 / (1 - 0.25) = 100 / 0.75 = **€133.33**. Calculating it this way ensures that the margin on the final price is exactly what you are looking for. ### The three margin levels You do not have to set the same margin for everything. A tariff allows margin at three levels, from the most general to the most specific: * **General margin**: applies to the entire tariff. It is the starting point. * **Service margin**: adjusts a complete service (for example, a different margin for Servers than for Remote Desktop). * **Item margin**: fine-tunes a single line within a service. The most specific overrides the most general: if you define a margin for an item, it takes precedence over the service margin, and the service margin over the general one. The recommendation is to set the general margin first and refine it only where you need to. ### Billing periods A tariff is defined for a billing period: **Hourly** or **Monthly**. This determines how prices are expressed and how it fits with budget sizing, where the estimate of hours per month translates consumption into an amount. ### The recommended tariff and the default tariff We offer you a **recommended tariff**, adjusted according to the partner's country, as a sensible starting point if you do not want to build your own from scratch. In addition, you can mark one of your tariffs as a **default tariff**: this will be the one applied by default when creating new subscriptions and budgets. If there were no recommended one for your case, the one you have set as default is used. > #### 👍 Where to start > > If you are just starting out, begin with the recommended tariff and adjust it to your margins. > > When you have your model clear, create your own tariffs and mark the one you use most as default. ### Details worth knowing Some lines have a special treatment. The **licenses** can be with commitment and annual payment, and in **Servers** the items are grouped by region, because the price depends on where the service is deployed. The tariff you use affects three things at once: the creation of new subscriptions, the amounts you see in the panel, and the calculation of your budgets. ### Next steps * Create your first tariff by following [How to create a tariff.](/docs-en/go-to-market/how-to/how-to-create-a-rate-card.md) * Check all the fields in [Tariff details.](/docs-en/go-to-market/details/rate-card-parameters.md) * Use the tariff to prepare offers in [Budgets.](/docs-en/go-to-market/concepts/quotes.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 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.plenit.com/docs-en/go-to-market/concepts/rate-cards.md?ask=&goal= ``` `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.