> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/ui-entitlements/managing-entitlements/change-the-offering-upgrade-downgrade.md).
# Change the offering (upgrade/downgrade)
Upgrade or downgrade a customer's rights by changing the offering attached to an entitlement, through either the UI or the API.
Changing offerings on an entitlement is an important workflow for a Software Vendor - it means upgrading or downgrading the end users' rights, which needs to be fast and easy for both parties.
This functionality makes it easy - through both the UI and the API - to allow an upgrade/downgrade from one offering to another.
This functionality will enable a clean and controlled process to move customers between your products/plans/editions vs. manually editing an existing entitlement. It also means they will seamlessly get more/less functionality based on fixed templates in the system vs. random changes on a per-customer or entitlement basis. It is much easier to manage in the long term.
{% hint style="info" %}
In many cases, you will sell your customers a specific set of rights, but they will want to change those over time. Upgrading, or downgrading, from one offering to another. To ensure this is controlled effectively, we use a specific routine, as below.
Remember, if you manually change an entitlement, doing an upgrade that adds features, etc, will **NOT** change the manual changes you made to that entitlement. Therefore, you should aim to make changes via this method, from one fixed offering to another, versus piecemeal changes for every entitlement to avoid issues with who has what.
{% endhint %}
If you wish to change the offering attached to an entitlement after you have added it, then you can do so and also remove the seats attached to the entitlement in the process.
 To change the offering on an entitlement, pick one from the list.
 Pick the 'three dots' icon on the top right.
 Select 'Change Offering.'
 Select the new offering from those available from the drop-down menu.
 Decide if you wish to force a seat limit change at this time by selecting the radio button.
 Click the "change" button to save the changes.
{% hint style="warning" %}
Values on the entitlement that have been overridden will not be modified.
{% endhint %}
{% hint style="info" %}
Please note that you can't undo a change to an offering, but you can simply change it again. There is no log for these changes, so it's important to record what you do in your CRM/billing/ERP system and associate these changes with some billing event. The original order ref ID remains on the entitlement.
{% endhint %}
{% hint style="warning" %}
**NOTES** If the change is a downgrade: If the new Seat count is lower than the current Seats used, we force a seat count change by removing the oldest active seats. In the same way we do with editing the seat count on an Entitlement.
If the value of Advanced features: elements used is higher than the new limit, we allow check-ins of elements only to prevent overuse and show a warning message.
{% endhint %}
---
# 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.nalpeiron.com/zentitle2-docs/ui-entitlements/managing-entitlements/change-the-offering-upgrade-downgrade.md?ask=&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.
