> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/oms/pull-orders-from-omnitron.md).
# Pull Orders from Omnitron
This tutorial explains how to pull orders from Omnitron using the OMS screens. Pulling orders manually from Omnitron to Akinon OMS can be helpful for troubleshooting and managing your orders effectively.
## Step 1: Access Pull Orders from Omnitron​
* To add a new state transition, start by selecting the **Settings** tab under the Akinon OMS menu.
* Next, click on **Pull Orders from Omnitron**.
## Step 2: Pull Orders​
* In the provided menu, orders can be pulled manually from Omnitron to Akinon OMS. This functionality is useful for troubleshooting purposes.
* Enter the **Order No** of the order you want to pull. If multiple orders are to be pulled, they can be added by clicking the **"+"** button.
* After adding the order(s), click the **SAVE** button to initiate the pulling process.
* The pulled orders will now be available for viewing under **Akinon OMS > Orders**.
---
# 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.akinon.com/tutorials/oms/pull-orders-from-omnitron.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.
