> For the complete documentation index, see [llms.txt](https://help.orderdesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orderdesk.com/api-documentation/getting-started/folders.md).

# Folders

Every order is contained in exactly one folder. Folders represent the stages that an order moves through in your store. A typical store has folders such as New, Prepared, Closed, and Canceled.

The `folder_id` field is used throughout this API, so it is worth understanding before you begin.

### Retrieving Your Folder IDs

Folder IDs are specific to each store. Query the `GET /store` endpoint to retrieve them:

```json
{
  "folders": {
    "21654": "New",
    "21655": "Prepared",
    "21656": "Closed",
    "21657": "Canceled"
  }
}
```

These should be retrieved once and cached. The IDs shown above belong to the example store and will not match your own.

### Where Folders Are Used

When creating an order, omitting `folder_id` places the order in your first folder. Pass a value to place it elsewhere.

When searching, `folder_id` filters to a single folder, or to several when the IDs are separated by commas. The `folder_name` parameter performs the same filter using the folder's exact name.

To move existing orders, use the `POST /move-orders` endpoint rather than updating each order individually.

{% hint style="info" %}
Please note that moving an order between folders triggers relevant folder change rules existing in your store. A folder change entry will also be added to the order history. 
{% endhint %}

### Folders and Updates

An update that omits `folder_id` leaves the order in its current folder. This is the one field that is not blanked when omitted, so that routine updates do not move orders unintentionally.


---

# 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://help.orderdesk.com/api-documentation/getting-started/folders.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.