> 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/submit-order.md).

# Submit Order

Submit a new-subscription quote as a Limio order from Salesforce, without a checkout link.

{% hint style="info" %}
**Requires** Limio for Salesforce v14.44 or later.
{% endhint %}

**Submit Order** sends a new-subscription quote to Limio as an order. The rep enters the payment details of the customer, so the customer does not need a checkout link.

## When Submit Order shows

On the Limio Quote record page, **Submit Order** is the third choice under **Pick a link to generate or submit the order**, after the preview and the checkout link. It shows only when all of these conditions are true:

* The quote is for a new subscription. **Subscription Id** is empty.
* The status is not **Completed** and not **Order Unconfirmed**.
* **Limio Order Id** is empty.

Quotes that update an existing subscription do not have Submit Order. See [Update Quote](https://docs.limio.com/salesforce/cpq/update-subscription-as-a-quote.md).

## Before you use it

The Limio Quote record page runs the **Generate Checkout Link from Limio Quote** flow, or your active override of it. See sections B and C of [Setup](https://docs.limio.com/salesforce/cpq/set-up-limio-cpq.md):

* Without an override, Submit Order shows to all users after the upgrade to v14.44. You cannot remove the choice from the packaged flow. To remove it, create an override (section B of Setup).
* An upgrade does not change your override, or a flow that you made from the template before v13.37. An override or flow made before v14.41 does not have Submit Order. To add it, do section B again on v14.44 or later. If the record page runs a flow that you made from the template, also do section C of Setup, and select the packaged flow.

Each version of the flow with Submit Order shows the choice to all users of the record page. Submit Order ignores permissions and the approval status of the quote.

{% hint style="warning" %}
A quote can need approval before the order, or an approval process can lock the quote. In these cases, remove the choice `Submit_Order_choice` from the field `Select_quote_action` in your override of the flow. See [Approvals](https://docs.limio.com/salesforce/cpq/quote-approvals.md).

If your reps must not handle payment details, also remove the choice. Keep the field `Select_quote_action`, because it also holds the preview and checkout choices. With Submit Order, the rep enters the payment details in the payment form of your payment provider. See [Payment Providers](https://docs.limio.com/salesforce/setting-up/detailed-salesforce-setup/payment-providers.md).
{% endhint %}

The flow writes the order reference to **Limio Order Id** and changes **Status**. Users who submit orders need edit access to both fields. The **Assisted Sales - Admin** and **Assisted Sales - User** permission sets give this access. If your org uses a cloned permission set, add the access to the clone.

## Submit the order

1. Open the Limio Quote record.
2. Select **Submit Order**.
3. Make sure that the customer will not pay through a link that you sent before for this quote.
4. Select **I have confirmed the customer will not pay through a link already sent for this quote**.
5. Enter the details that the flow asks for. These details depend on the cart and the country of the quote: the gift recipient, the delivery address, or the billing address.
6. Select a payment method.
7. Enter the payment details.
8. On the order summary, submit the order. This screen has no **Previous** button.
9. Wait for the result message. Do not close or refresh the tab before it shows. The flow updates the quote only after the order summary, so a closed tab leaves the quote without the order.

Submit Order does not cancel a link that you sent before. The customer can still pay through that link, and then the customer has two orders.

The order goes to the **Bill To Contact** of the quote. If the quote has no Bill To Contact, the order goes to the contact of the opportunity. If neither exists, the flow stops before the payment step and asks you to add a contact.

The order carries these record ids as custom fields: `quoteId`, `opportunityId`, `contactId`, `accountId`, `billToContact`, `billToAccount`, `soldToContact`, `soldToAccount` and `userId`. Use them to find the quote of an order.

## Results

After the order request, the flow updates the quote. The result tells you if Submit Order can show again for the quote.

| Result                                                                 | Message                                                                                                                                                                                                                                                                                                     | Quote after the result                                        | Submit Order shows again |
| ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | ------------------------ |
| Limio confirms the order                                               | "The order was submitted and this quote is now Completed."                                                                                                                                                                                                                                                  | **Completed**, with the order reference in **Limio Order Id** | No                       |
| Limio returns an order reference, but the order is not confirmed       | "Order {0} was sent to Limio but could not be confirmed. Do not resubmit; check this order in Limio."                                                                                                                                                                                                       | The order reference in **Limio Order Id**                     | No                       |
| Limio returns no order reference                                       | "The order request did not complete, so no order reference was recorded. The order may still have been created, so this quote is now set to Order Unconfirmed and cannot be submitted again. Check Limio for this customer; if no order exists, ask an administrator to set the quote back to In Progress." | **Order Unconfirmed**                                         | No                       |
| Limio returns an order reference, but the flow cannot update the quote | "Order {0} was placed but the quote could not be updated. Do not resubmit; contact your administrator."                                                                                                                                                                                                     | No change                                                     | **Yes**                  |
| Limio returns no order reference, and the flow cannot update the quote | "The order request did not complete, so no order reference was recorded, and this quote could not be set to Order Unconfirmed. The order may still have been created: check Limio for this customer before submitting this quote again."                                                                    | No change                                                     | **Yes**                  |
| The quote already has a different order reference                      | "Order {0} was placed, but this quote already records order {1}. Contact your administrator; do not resubmit."                                                                                                                                                                                              | No change                                                     | No                       |

{% hint style="danger" %}
If the flow cannot update the quote, an administrator must change the status of the quote to **Order Unconfirmed** at once. Submit Order then does not show. Then find the order in Limio.

In the two results with **Yes**, Submit Order shows again although an order can exist in Limio. The next rep who opens the quote can take a second payment. The flow cannot update a quote that an approval process locks, or a quote that the user cannot edit. A validation rule on Limio Quote can also stop the update. The rep cannot change the status for the same reason, so the rep must contact an administrator.
{% endhint %}

## After the order

{% hint style="warning" %}
Find the order in Limio before you change a quote that has an order. Each of these actions can lead to a second order:

* A change of **Status** to a value other than **Completed** or **Order Unconfirmed**, while **Limio Order Id** is empty. Submit Order then shows again. The **Assisted Sales - User** permission set can edit **Status**.
* The **Edit Limio Quote** action. It sets the status to **In Progress** each time it saves the quote.
* A change that clears **Limio Order Id**. Submit Order then shows again. The **Assisted Sales - User** permission set can edit **Limio Order Id**.
* A preview or checkout link. On a quote that is not **Completed**, the quote record page still offers these links after Submit Order.
* **Send Quote By Email**. The email action can send a checkout link, also for a **Completed** quote. It also changes the status to **Quote Sent to Customer**.
  {% endhint %}

An **Order Unconfirmed** quote can have an order in Limio. Find the customer in Limio. If no order exists, change the status to **In Progress**. Then Submit Order shows again.


---

# 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/submit-order.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.
