> 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/how-to/how-to-create-a-rate-card.md).

# How to Create a Rate

A rate defines the price at which you sell Plenit services to your customers, applying your margins over cost.

This guide walks you through creating it: the header and the margin configuration at its three levels.

### Before you begin

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on Go to Market.
* Be clear about which margin you want to apply. If you want to review the model, see [Rates: wholesale price, retail price, and margin.](/docs-en/go-to-market/concepts/rate-cards.md)

### Step 1. Open a new rate

In the panel, go to **Go to Market → Rates** and click **New Rate**. Fill out the header:

* **Rate name**: a name that identifies it in your list.
* **Billing period**: **Hourly** or **Monthly**.
* **Default rate**: check the box if you want this to be the one applied by default when creating subscriptions and quotes.

![Header of the new rate](/files/3c89af3dffccb01606c1bb7097a18590a6598771)

### Step 2. Define the general margin

In **Set up your margins**, start with the **General margin**: the percentage applied to the entire rate. It is your starting point and, in most cases, that is enough to have the rate ready.

![General margin of the rate](/files/c677baa17982bc7e31de83481e37e88cfd01cbf0)

> #### 📘 How the price is calculated
>
> The sale price comes from applying the margin over the cost with the formula `Price = Cost / (1 - margin)`.
>
>  For example, a cost of €100 with a 25% margin comes to €133.33. The column **RRP** for each line shows you the result instantly.

### Step 3. Fine-tune by service or item (optional)

If you want a different treatment for a particular service or line, you can fine-tune the margin without touching the general one:

* **Service margin**: in the header of each service (Remote Desktop, Servers, etc.) you have a field **Service margin (%)** that applies to all its lines.
* **Item margin**: in the column **Margin** for each line you adjust one.

The most specific takes precedence: the margin of an item overrides that of the service, and the service overrides the general one.

![Margins by service and by item](/files/3daada5552b70153ffdc19ac79ce67b4bb0c722e)

> #### 📘 Servers are grouped by region
>
> In Servers, the lines are grouped by region (Madrid, etc.), because the price depends on where the resource is deployed. 
>
> Each group indicates in parentheses how many items it contains.

### Step 4. Save the rate

When you have the margins the way you want them, save the rate. It will appear in **My Rates** with its name, whether it is the default one, its billing period, and the number of subscriptions that use it, ready to be applied in your quotes.

### Conclusion

Creating a rate is, above all, deciding your margins: you define a general margin and, if needed, fine-tune it by service or by item.

With the rate saved, your quotes will automatically calculate the sale prices from it, so you do the pricing work once and reuse it in each offer.

### Next steps

* Use the rate to prepare an offer in[ How to generate a quote.](/docs-en/go-to-market/how-to/how-to-generate-a-quote.md)
* See all fields in [Rate parameters.](/docs-en/go-to-market/details/rate-card-parameters.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/how-to/how-to-create-a-rate-card.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.