> For the complete documentation index, see [llms.txt](https://docs.colt.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.colt.net/on-demand/on-demand-lso-portal/ordering.md).

# ORDERING

## CONVERT A QUOTE TO AN ORDER 

Orders are generated from valid quotes, i.e. that are in a “<mark style="color:$primary;">READY</mark>” state. Orders cannot be generated form quotes that have expired (or failed).  &#x20;

To place an order, first select the relevant quote from the list on the main **Quotes** page and select the **Order** option.&#x20;

<sup><sub>Note: The Orders page displays orders that are in the delivery queue, and should not be used to generate a new order.<sub></sup>

<figure><img src="https://content.gitbook.com/content/VLSaOIDXVwkVeVU0OgDq/blobs/prkoathnUqinfbx7lvnx/order%202.jpg" alt=""><figcaption></figcaption></figure>

Then select a **Site** for the B end customer location (the A end is the existing hub location). &#x20;

In data centre locations, the “**Default Shared Area**” should be selected. &#x20;

In enterprise office locations, select the “**Choose site**” option and either select an existing PoP site (e.g. 4th floor comms room) or request to deliver at a new PoP site. &#x20;

<figure><img src="https://content.gitbook.com/content/VLSaOIDXVwkVeVU0OgDq/blobs/lgVXrZpQ21X8nORpdP1O/order%201.jpg" alt=""><figcaption></figcaption></figure>

Next, enter the **site contact details** as requested (name, email, phone). Enter separate on-site and technical contacts as required.&#x20;

Then select a **hub** and assign a **VLAN ID**. &#x20;

Note that only hubs located within the hub metro location assigned to the quote will be displayed. (For example, where the Paris metro is selected as a hub location only hubs located in Paris will be displayed).&#x20;

The “**use next available VLAN**” option is not recommended if non-On Demand circuits are attached to the hub.&#x20;

<figure><img src="https://content.gitbook.com/content/VLSaOIDXVwkVeVU0OgDq/blobs/rTi7KV7it2ihbvHSSIL7/order%203.jpg" alt=""><figcaption></figcaption></figure>

Finally, enter a reference and select the “**Summary**” option to review and then place the order.&#x20;

<figure><img src="https://content.gitbook.com/content/VLSaOIDXVwkVeVU0OgDq/blobs/kjRrUtOlhWrMgHkPTHRD/order%204.jpg" alt=""><figcaption></figcaption></figure>

&#x20;&#x20;

&#x20;

&#x20;


---

# 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.colt.net/on-demand/on-demand-lso-portal/ordering.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.