> For the complete documentation index, see [llms.txt](https://shop-docs.xorosoft.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shop-docs.xorosoft.io/getting-started/workflow/orders.md). # Orders This page provides information on order import actions.

1. **Import By Date Range**: This option allows you to import Shopify orders within the specified date range. Simply select a **start date** and an **end date**, and click on import. This will fetch all the Shopify orders that were created within that date range and add them to the order import queue for (re)processing.

2. **Import By Order**: This option allows you to import a specific group of orders by either a Shopify order number, order ID, or a custom query. 1. **Order Number**: This field allows you to import a single Shopify order by its order number. 2. **Order ID**: This field allows you to import multiple Shopify orders by their ID. This ID can be found in the URL *(.../orders/\)* of an order. Each order ID needs to be separated by a comma (,). 3. **Custom Query**: This field allows you to run a custom query to import order(s). This is an advanced query field that should only be used if you are familiar with Shopify GET order queries.

--- # 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://shop-docs.xorosoft.io/getting-started/workflow/orders.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.