> For the complete documentation index, see [llms.txt](https://learn.moselle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.moselle.io/getting-started/onboarding/setting-up-channels.md).

# Setting Up Channels

{% hint style="info" %}
**Quick Answer:** Go to **Settings** → **Channels**, click **+ Create Channel**, enter a name and optional data source, then configure the fulfillment location, forecast resolution, and payment terms in the Existing Channels table.
{% endhint %}

**Time required:** 5–10 minutes

## Creating a Channel

1. Click your **avatar** at the top right corner of the dashboard.
2. Go to **Settings** → **Channels**.
3. Click the **"+ Create Channel"** button — a pop-up will appear.
4. Enter a **Channel Name**.
5. Optionally, select a **Data Source** from the dropdown to link it to an integration you've already connected.
   * If you skip this, an empty channel will be created and you can attach a data source later.
6. Click **Create** to save.

***

## Managing Existing Channels

Once channels are created, they appear in the **Existing Channels** table. Each row shows the channel's configuration and lets you edit settings inline.

### Data Source

If you didn't attach a data source when creating the channel, you'll see a **+ Attach** button in this column. Click it to select and link an integration to this channel at any time.

### Fulfillment Location

Select a warehouse location from the dropdown. This warehouse acts as the **inventory node** for the channel — Moselle pulls stock from this location when calculating the demand and production plan.

{% hint style="info" %}
You'll need at least one warehouse set up before you can assign a fulfillment location. See [Setting Up Inventory](https://github.com/Moselle-io/moselle-docs/blob/master/getting-started/onboarding/setting-up-inventory.md) if you haven't done this yet.
{% endhint %}

### Forecast Resolution

Choose how demand is forecasted for this channel:

| Resolution  | Best For                                                                         |
| ----------- | -------------------------------------------------------------------------------- |
| **Daily**   | High-volume channels like DTC (direct-to-consumer) where order frequency is high |
| **Monthly** | B2B channels like wholesale or retail accounts where orders are less frequent    |

### Payment Terms

Select how many days after an invoice is issued your customer is expected to pay, using the dropdown (e.g., **Net 30**, **Net 45**). For example, if Sephora buys from you today but pays invoices 30 days later, set this to Net 30.

### Payout Lag

Enter the number of days between when a sale occurs and when the platform deposits the funds into your bank account. For example, if Shopify sales happen today but funds arrive at the end of the week, enter **7**.

### Last Synced

Displays the timestamp of the most recent data sync for this channel, so you can confirm your integration is up to date.

***

## Archiving a Channel

Click the **three-dot menu (⋯)** at the end of the channel row and select **Archive** to remove the channel from your active list.

***

{% hint style="info" %}
Need to split a channel by order type, region, retailer, or fulfillment method? See [Channel Segmentation](/getting-started/onboarding/setting-up-channels/channel-segmentation.md) to learn how your CSM can configure this for you.
{% endhint %}


---

# 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:

```
GET https://learn.moselle.io/getting-started/onboarding/setting-up-channels.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.