# Channels

**Transaction Channels** define where transactions originate — for example, from an online store, mobile app, or in-store POS.\
They help you organize, segment, and analyze transactions from different sales environments.

Each channel has its own **name**, **code**, and optional **description**, and can be used when importing or manually creating transactions.

{% hint style="info" %}
💡 **Tip:** Configuring separate channels for each sales source makes it easier to track program performance by channel (e.g., eCommerce vs. POS).
{% endhint %}

<figure><img src="/files/NpqFMzflURhfNyE1pXfw" alt=""><figcaption></figcaption></figure>

***

### Accessing transaction channels

In the **Admin Panel**, go to:\
**Transactions → Transaction channels**

You’ll see a list of all existing channels with their identifiers.

***

### Channel list

The list includes two main columns:

| Column         | Description                                                                              |
| -------------- | ---------------------------------------------------------------------------------------- |
| **Name**       | The display name of the channel (e.g., *eCommerce 1*, *POS 2*).                          |
| **Identifier** | The unique system code used in imports or API integrations (e.g., *ecommerce1*, *pos2*). |

***

### Adding a new channel

Click **Add channel** to create a new transaction channel.\
You’ll be asked to provide:

<table><thead><tr><th width="207">Field</th><th>Description</th></tr></thead><tbody><tr><td><strong>Channel name</strong>*</td><td>The visible name used in the admin interface.</td></tr><tr><td><strong>Channel code</strong>*</td><td>A unique identifier used when importing transactions or integrating via API.</td></tr><tr><td><strong>Channel description</strong></td><td>(Optional) Short note describing the purpose or location of the channel.</td></tr></tbody></table>

<figure><img src="/files/U5GYU5huwO4hSXwjQ1ve" alt=""><figcaption></figcaption></figure>

After completing the form, select **Add channel** to save.

***

### Editing a channel

To modify a channel, click the **⋯ (three dots)** menu next to it and select **Edit channel**.\
You can change:

* Channel name
* Channel code
* Description

<figure><img src="/files/8IoBB0cjEPMlaEk7qxSC" alt=""><figcaption></figcaption></figure>

Click **Save changes** when done.

***

### Best practices

* Use short, clear **codes** — avoid spaces or special characters.
* Keep **names** human-friendly for admin users.
* Align channel identifiers with your source systems (e.g., use the same code as in your eCommerce platform).
* Avoid duplicate codes — each must be unique within a tenant.

***

#### Next steps

➡️ Learn how to [Add or Import Transactions](/main-features/transactions/add-or-import-transactions.md).


---

# Agent Instructions: 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://help.openloyalty.io/main-features/transactions/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.