> 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/guided-walkthroughs/orders-and-folders/organizing-orders-with-folders.md).

# Organizing Orders With Folders

Every Order Desk store starts with a few default folders:

* New
* Prepared
* Closed
* Canceled
* All Orders

When a new order is imported, it will be added to the *New* folder by default, however this can be changed with rules or certain integration settings.

To grasp the concept of folders, try thinking of them in the physical sense: if you received a paper order, you’d put it into the *New* folder. When that order is packed but not yet shipped, you’d remove the paper from the *New* folder and place it into the *Prepared* folder and so on.

It’s worth mentioning that when an order moves between folders, its status won’t automatically update across any integrations by default, but this is an option that you can configure. You’ll need to check the settings pages in your installed integrations or use the Rule Builder to tell Order Desk to update an order’s status when it’s moved between folders.

### How to Use Folders

For a visual walkthrough of how folders work in Order Desk, check out the following video:

{% embed url="<https://player.vimeo.com/video/604144133?dnt=1&amp;app_id=122963>" %}

### Create Folder

If you’d like to create a new folder, look under the **Settings** menu in the left sidebar and click on **Store Settings**:

![](/files/GV7ICaJmZ7fpSbycRREk)

On the Store Settings page, click on the Folders tab, then on Add Folder:

![](/files/nAYg9iyu2XLfl1ivKPxK)

A good method for setting up your folders is to think of where an order physically exists during the fulfillment process. For example, if you send orders to more than one vendor, or a different fulfillment or shipping integration, you can move orders into folders that say they’ve been sent but have not yet been fulfilled, such as “At Vendor X” or “At MWW” or “At ShipStation”.

![](/files/u8NlxvmHw9UG3UEMInM7)

### Moving Orders Through Folders

Remember, orders won’t move on their own unless your settings tell them to move somewhere.

Many integration include a setting that tells where to put an order after it’s imported or submitted for fulfillment. Here’s an example of what that might look like:

![](/files/ICAttII5ATZ1fJkkS1AD)

If sending to a third party vendor through an [export template](/guided-walkthroughs/templates-emails-and-order-documents/how-to-build-export-templates.md), you can tell the export template to place the order into a specific folder after it’s exported:

![](/files/XE3T65sdPcFmvO2YTfih)

If your business sends dropshipping emails to a third party vendor, you can even add an action in your rules to move the order into a specific folder after the email is sent:

![](/files/EYWWmQUHryzF3z2L4wvz)

If using an integration, check to see if you can change the folder when a shipment is added. If that isn’t an option, or if you aren’t using an integration for some orders, you can set up a rule to move orders to the closed folder when a shipment is added to an order:

![](/files/vdJl5ETnHfK0ELRODErL)

Another option with custom folders is filtering orders, whether to flag them for review, assign them to a specific person on your team, or send them to a hold folder that sets them aside before they are ready to move to the next stage in the fulfillment process.

Once you create the folders you need, you can adjust them as you become more familiar with Order Desk and decide how you want to use the app to best process and fulfill each of your 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.orderdesk.com/guided-walkthroughs/orders-and-folders/organizing-orders-with-folders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.