> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/salesforce/cpq/update-subscription-as-a-quote.md).
# Update Quote
Quote a change to a subscription the customer already has.
The **Update Quote** flow produces a quote for a change to a subscription the customer already has. It starts from an Opportunity and creates a `Limio_Quote__c` record with `Subscription_Id__c` set to the Limio subscription being changed.
To quote a brand-new subscription instead, see [New Quote](/salesforce/cpq/new-quote.md).
{% hint style="info" %}
**LFS version:** requires Limio for Salesforce v14.25 or later\
Individual features note their own version requirements.
{% endhint %}
## Create the quote
1. Open the Opportunity.
2. Click **Generate Limio Quote**.
3. On the **Select Quote type** screen, choose **Create a quote to update an existing subscription**.
4. Pick the subscription from the customer's subscription table.
5. On **Update Subscription Offers**, change the offer, add-ons and quantities, and confirm the **Bill To** and **Sold To** contacts.
6. Click **Next**, then follow the link to the new Limio Quote record.
## Work with the quote record
When you open a **Limio Quote** record:
**Main area (left)** — displays the **Cart Items** for the change. A CSR can edit the discount, price and quantity before sending the link. Below the items is a single **Update** link with a copy button.
**Order Start Date** is the date the change takes effect: today for an upgrade, and the subscription end date for a downgrade. A CSR can change it where the date picker allows it.
{% hint style="info" %}
The Limio API behind these links is documented in [Checkout and Baskets](https://docs.limio.com/api/checkout-baskets-api). To generate links programmatically instead of from the UI, see [Generate checkout and preview links from Apex](/salesforce/cpq/generate-links-from-apex.md).
{% endhint %}
## Update link properties
The **Limio Update Checkout** component builds the link. Set these properties to match your shop.
| Property | Default | Purpose |
| ----------------------------------------------------- | -------- | --------------------------------------------------------------------------------------- |
| Update page tag | `update` | The shop path for the update link. Change it when your update page is not at `/update`. |
| Input: Custom fields | — | A JSON object of custom fields to add to the order. |
| Input: Record Ids to add to the order tracking object | — | A JSON object of the Salesforce record ids to add to the order. |
{% hint style="info" %}
Unlike the acquisition link, the update link does not add record ids automatically. Add the quote, opportunity, contact, account and user ids in **Input: Record Ids to add to the order tracking object**.
To set the effective date, use **Selected order effective start date**. Do not use the deprecated **Effective Start Date** property. If no date is set, the change takes effect when the link is generated.
{% endhint %}
## Next
* [Override a price manually](/salesforce/cpq/manual-price-override.md) before sending the quote
* [Edit the quote](/salesforce/cpq/edit-a-quote.md) if the customer asks for changes
* [Route it for approval](/salesforce/cpq/quote-approvals.md)
* [Track its status](/salesforce/cpq/quote-statuses.md) through to Closed Won
---
# 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.limio.com/salesforce/cpq/update-subscription-as-a-quote.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.
.png?alt=media)