> For the complete documentation index, see [llms.txt](https://support.ordereazi.com/central/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ordereazi.com/central/order-management/integrations/sales-channels.md).

# Sales Channels

Set up the workflow, warehouse, sales rep, and default client for orders that arrive from other systems.

Orders from your online shop or another system arrive without a sales rep or workflow of their own. A sales channel in OrderEazi decides what happens to them. It sets which workflow they follow, which warehouses fill them, which rep looks after them, and whether they're approved straight away. Each system sends its orders to its own channel.

### Before you start

You'll need the **Sales Channels** permission, in the **Integrations** permission group. If you don't have it, ask your OrderEazi administrator to add it to your role. The other system also needs an API key with **Write** on **For Project**. See [API Keys](/central/order-management/integrations/api-keys.md).

On the Enterprise licence, you also choose the warehouses that fill the channel's orders. On other licences, your first warehouse is used.

### How to create a sales channel

1. In the main menu, go to **Integrations** > **Sales Channels**.
2. Select **New Sales Channel**.
3. Enter the channel's name in **Application Name**, such as "WebShop". Use 2 to 32 letters and numbers, with no spaces.
4. Under **Created By**, choose the user the channel's projects are created as.
5. Choose the **Default Sales Rep**, who looks after the channel's projects.
6. Choose the **Assigned Workflow**.
7. If you use branches, choose the **Branch**. The sales reps are then limited to that branch's users.
8. Choose the other settings you need (see below).
9. On the Enterprise licence, on the **Warehouse** tab, link the warehouses that fill these orders, in order of priority.
10. Select **Create**.

You see "Sales Channels for" and the name "has been created."

> **Warning:** The other system sends orders to the channel by its name. If you rename the channel, change it in the other system too, or its orders stop arriving.

### The settings

* **Return Workflow:** This workflow is used instead when every line on an incoming order is a return.
* **Default Client:** This client is used when an incoming order has no company name.
* **Colour:** This is the colour of the channel's badge on projects and in My Workspace.
* **Auto Approve Orders:** Orders from this channel are approved as soon as they arrive.
* **Notify Sales Rep:** The rep gets an email when a new project arrives on this channel.

### Where sales channels show

* **On projects:** Each project from the channel shows its coloured badge.
* **In My Workspace:** You can filter by **Sales Channel** in the advanced filters.
* **On the project's branch:** If the client has no branch, the project uses the channel's branch.

**Example:** You create a "WebShop" channel with your "Online Orders" workflow, Lerato as the **Default Sales Rep**, **Auto Approve Orders** ticked, and your Johannesburg warehouse first. A client orders 3 mugs on your shop. The order arrives as a project on the Online Orders workflow, already approved, with Lerato as the rep and a WebShop badge. Your Johannesburg warehouse picks it first.

### When a channel can't be saved

If you see "The name of the sales channel is invalid.", the name is blank, already used, or has spaces or symbols. Use 2 to 32 letters and numbers.

If you see "At least one warehouse is required for this sales channel.", link a warehouse on the **Warehouse** tab.

### Related pages

* [API Keys](/central/order-management/integrations/api-keys.md): the key the other system uses
* [OrderEazi Commerce](/central/order-management/integrations/sales-channels/ordereazi-commerce.md): our own online shop