> 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/integration-setup-guides/sales-channels/bright-orders-integration.md).
# Bright Orders Integration
Order Desk can connect to your [Bright Orders](https://www.brightstores.com/bright-orders.html) account and automatically download orders then send shipment details back as orders are fulfilled.
### Setup
In Order Desk, click on **Manage Integrations** under the Integrations menu in the left sidebar. Under the **Shopping Carts** tab, find and enable Bright Orders.
Alternatively, search for Bright Orders from the available integrations search.
Once enabled, enter your store’s domain and API Token and click to connect.
Please note that Order Desk isn’t able to help find or reset your credentials, as they can only be provided by BrightStores.
#### Settings
Once connected, you can set your integration preferences.
#### Check for New Orders
Select how often you want Order Desk to look for and download new orders from Bright Orders.
#### Download These Orders
Select the types of orders you want Order Desk to download from Bright Orders.
#### Folder for New Orders
Select the folder where newly imported orders from Bright Orders should be placed.
For more information, see the [Working with Folders](/start-here/getting-started-series/quick-start-overview.md#working-with-folders) guide.
#### Sync Tracking Numbers
Enable this setting if you want Order Desk to send shipment details back to Bright Orders as they are added to your orders in Order Desk.
#### Send Email Confirmation
Enable if you want Bright Orders to email the customer a shipment notification as tracking is sent back on orders.
#### First Import Date
Any orders previous to the date set here will not import into Order Desk.
#### Order Prefix
If you need to, you can add a prefix of your choice that will be added to all orders downloaded from Bright Orders.
#### Store ID
To only import orders from specific Bright Orders stores, add the IDs here, separated by a comma.
#### Check for Canceled Orders
Select to run a check every 24 hours for any orders that have been canceled within Bright Orders.
#### Manually Import Orders
You can manually import orders from Bright Orders at any time. You can import recent orders in bulk, or import by a specific **Order ID** if you only need to import one order.
> **Tip: Advanced Download**
>
> If you want to import more orders from Bright Orders, you can use the Advanced Download option to paginate through the list of recent orders available to import.
>
> 
### Order Import Log
If an order from your cart hasn't come into Order Desk, the **Order Import Log** is a good place to start. It shows recent import attempts, including which orders were imported or skipped and any skip reasons.
Learn how to use the log in the [How to Troubleshoot Missing Shopping Cart Orders](/guided-walkthroughs/integration-specific-walkthroughs/how-to-troubleshoot-missing-shopping-cart-orders.md) guide.
---
# 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/integration-setup-guides/sales-channels/bright-orders-integration.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.