> 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/fast-tutorial/set-up-channels.md).

# Step 2: Set Up Channels

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

Channels connect your sales stores (Shopify, Amazon, etc.) to your warehouses. Moselle uses this link to track where inventory is being drawn from and to surface at-risk items accurately.

**Time required:** 5–10 minutes

{% embed url="<https://youtu.be/8UkDwkAs9Iw>" %}

***

## Create a Channel

1. Click on your **avatar** at the top right corner of your dashboard page
2. From your settings click on the **Channels** tab
3. Click the **+ Create channel** button in the top right corner
4. Enter a **Channel Name** and click **Create**

Your new channel will appear in the **Existing channels** table. From here you can configure each channel inline:

***

## Configure Your Channels

* **Data sources** — Click **+ Attach** on the channel row. A modal will appear — select your integration from the **Pick a data source** dropdown and click **Attach** to link it. This connects your integration's sales data directly into the channel.
* **Fulfilment location** — Select a warehouse from the dropdown. This tells Moselle which warehouse to pull stock from when calculating demand and your replenishment plan.
* **Forecast** — Choose **Daily** or **Monthly** depending on your channel type (Daily for DTC, Monthly for wholesale/B2B).
* **Payment terms** — Set how many days after an invoice your customer is expected to pay (e.g., Net 30).
* **Payout lag** — Enter the number of days between when a sale occurs and when funds land in your account.

{% hint style="info" %}
If your channels require to be split by different sales and locations, please reach out to <support@moselle.io> for this to be customized for you.
{% endhint %}

{% content-ref url="<https://github.com/Moselle-io/moselle-docs/blob/master/getting-started/onboarding/setting-up-channels/README.md>" %}
<https://github.com/Moselle-io/moselle-docs/blob/master/getting-started/onboarding/setting-up-channels/README.md>
{% endcontent-ref %}

***

## Don't Have Historical Sales Data Yet?

That's fine — channels don't need historical data to work. If your integration is still syncing or you're starting fresh:

* Set up the channel now with the correct store link
* In Step 4, Mo can build your forecast directly from your existing sales spreadsheets instead of relying on synced history

{% hint style="info" %}
Mo can work from the spreadsheets you already have. You don't need to wait for a full data sync to start planning.
{% 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, and the optional `goal` query parameter:

```
GET https://learn.moselle.io/getting-started/fast-tutorial/set-up-channels.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.