> 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/set-up-limio-cpq.md).

# Setup

One-time setup to turn on quoting in your Salesforce org.

{% hint style="info" %}
**Requires** Limio for Salesforce v13.24 or later. Upgrade before following these steps.
{% endhint %}

If you have installed a version of the package that includes the quoting components, you can proceed with the steps below.

## A. Update the Opportunity layout

1. Surface the **Generate Limio Quote** action button on the Opportunity page.
2. Add **Limio Quotes** to the related lists section.

## B. Create an override of the "Generate Checkout Link from Limio Quote" flow

1. Open the out-of-the-box **Generate Checkout Link from Limio Quote** flow in Salesforce Flow Builder.
2. In the left-hand panel, go to the **Manager** tab.
3. Find the **domain** variable.
4. Click the variable and set its default value to your Limio domain (for example `https://yourdomain.limio.com`).

   > **Note:** Because the Preview and Checkout screens both reference this variable in their **Limio Initiate Checkout** components, updating it here means you only need to set it once — the value is used automatically in both screens.

   <figure><img src="https://284256719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUgE12kxtw8dDbuEZGzbI%2Fuploads%2Fgit-blob-cbb7286d440ca0a05ec46288d99d5faba520bd24%2Fimage%20(310).png?alt=media" alt=""><figcaption></figcaption></figure>
5. In the **Cart + new sub link** screen you will see two **Limio Initiate Checkout** components. They are meant to contain different page tags — one for preview, one for checkout.

   * In each component's properties panel, set **Limio Page Tag** to the correct value.

   <figure><img src="https://284256719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUgE12kxtw8dDbuEZGzbI%2Fuploads%2Fgit-blob-7cc5368baf0831b781957cbe5b6ea598db7e7e41%2Fimage%20(311).png?alt=media" alt=""><figcaption></figcaption></figure>
6. If the update page of your shop is not at `/update`, open the **Cart + update sub link** screen. In the **Limio Update Checkout** component, set **Update page tag**.
7. Click **Save As**. On v13.37 or later, save your changes as an override of the packaged flow. Before v13.37, save them as a new flow.
8. Activate the override or the new flow.

{% hint style="info" %}
From v13.37, the packaged flow is overridable. An active override runs in place of the packaged flow wherever the packaged flow is referenced, also on the Limio Quote record page. An upgrade does not change your override. Before v13.37, the packaged flow was a template, and **Save As** made a new flow.

Without an override, the links use the placeholder domain `https://your-shop.example.com/`.

On v14.41 to v14.43, the packaged flow references protected custom labels, and it can fail in an installed org. Upgrade to v14.44 or later.
{% endhint %}

{% hint style="warning" %}
Quotes can need approval, or reps must not handle payment details. In these cases, remove the choice `Submit_Order_choice` from the field `Select_quote_action` in your override. Do this before you activate it. Keep the field, because it also holds the preview and checkout choices. Each override made on v14.41 or later shows [Submit Order](https://docs.limio.com/salesforce/cpq/submit-order.md) to all users of the record page.

If your override, or a flow that you made from the template, is older than v14.41, it does not have Submit Order. An upgrade does not change it. To get Submit Order, do section B again on v14.44 or later. Then make your own changes again. If the record page runs a flow that you made from the template, also do section C, and select the packaged flow.
{% endhint %}

## C. Update and activate the Limio Quote Lightning record page

1. From the Opportunity record, click the **Generate Limio Quote** button you just added, select an offer, click **Next**, and **follow the link** to the newly created Limio Quote record.

   <div data-with-frame="true"><figure><img src="https://284256719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUgE12kxtw8dDbuEZGzbI%2Fuploads%2Fgit-blob-e26af4b3932de359fdc74a004bbe73b09da84812%2Fimage%20(2).png?alt=media" alt=""><figcaption></figcaption></figure></div>
2. On the top right, click the gear icon, then **Edit Page**.
3. Open **Limio Quote Record Page** from the Lightning pages list.
4. Click the flow component in the main area of the page. Make sure that it runs the packaged **Generate Checkout Link from Limio Quote** flow. **Pass in the recordId.** Salesforce runs your active override in its place. If your org still uses a flow that it made from the template before v13.37, select that flow instead. If you made an override in section B, select the packaged flow.
5. **Save and Activate** the page, and assign it as Org Default.

<figure><img src="https://284256719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUgE12kxtw8dDbuEZGzbI%2Fuploads%2Fgit-blob-2a75d3b31212782f0179316b19581c605724da6c%2Fimage%20(312).png?alt=media" alt=""><figcaption></figcaption></figure>

## D. Set up the email actions

The record page has the actions **Send Quote By Email** and **Send Quote Preview By Email**. Their packaged flows use the placeholder domain `https://your-shop.example.com/` and email templates that the package does not include. To send links to your shop, do these steps:

1. Save a copy of the flow **Limio Quote - Send Quote By Email**, and a copy of **Limio Quote - Send Quote Preview By Email**.
2. In each copy, set the **domain** variable to your Limio shop domain.
3. Create the email templates `Limio_Quote_Checkout_Template` and `Limio_Quote_Checkout_Preview_Template`, or set **EmailTemplateName** in each copy to a template of your own.
4. Activate each copy. A quick action can use only an active flow.
5. On the Limio Quote object, create a quick action of type Flow for each copy.
6. Add your quick actions to the Limio Quote record page in place of **Send Quote By Email** and **Send Quote Preview By Email**.

The email goes to the **Bill To Contact** of the quote. In each template, add the merge field of the link: **Checkout Link** or **Preview Link** of the Limio Quote.

Each flow checks only its own link field: **Checkout Link** or **Preview Link**. When that field is empty, the flow generates both links again. **Edit Limio Quote** does not clear the link fields. To get new links each time, set the variable **regenerateCheckoutLink** to true in each copy.

On the packaged record page, **Send Quote By Email** shows only when **Approval Status** is Approved or Not Required. Give your own action the same visibility rule. See [Approvals](https://docs.limio.com/salesforce/cpq/quote-approvals.md).

## Next

{% content-ref url="/pages/0tveGHaq4B5L9q7fQ6Db" %}
[New Quote](https://docs.limio.com/salesforce/cpq/new-quote.md)
{% endcontent-ref %}


---

# 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/set-up-limio-cpq.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.
