> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/omnitron/settings/how-to-add-and-configure-a-new-sales-channel-in-omnitron.md).
# How to Add and Configure a New Sales Channel in Omnitron?
This tutorial provides step-by-step instructions for managing Sales Channels in Omnitron.
## Step 1: Access to Omnitron
* Get access to the Omnitron panel.
* Enter your *Username* and *Password*, and then click the **Sign In** button.\
## Step 2: Navigate to Sales Channels Page
* Navigate to **Settings > Sales Channels** sidebar and click the **Sales Channels** page.
* Sales Channels allow you to access the available platforms where products are listed for sale.
## Step 3: Adding a New Sales Channels
* Click the **+New Sales Channel** button or the name of any sales channel on the list to access the form to **Add/Edit Sales Channel**.
* Complete the form by filling in the following fields:
* **Channel Name:** The name of this sales channel.
* **Catalog Name:** The catalog to which this sales channel will be linked.
* **Channel Type:** This field is used to determine the type of this sales channel (Shop, Unified, Other, etc.). The available options are Hepsiburada, Gittigidiyor, N11, Web, Feed, Trendyol, Morhipo, Morhipo v2, Amazon, Lidyana, Allegro, Unified, Ali Express, Gördüm Aldım, Pazarama, FLO, Modanisa, and Sales Channel. This field has been added in order for the Partner or Service Team to configure the marketplaces that are not available in the drop-down.
* **Status:** The Active/Passive status of the brand on this Sales Channel.
* Once you have filled in the relevant fields, click the **Save** button.
After creating a Sales Channel using this form, re-access the Sales Channel detail to see the dynamic fields displayed based on the input selected in the **Channel Type** field. Below, you can find the inputs based on the Sales Channel schema for **Trendyol**.
Below, a sample configuration is provided for a failed integration, which includes a JSON data type value in the schema configuration:
```
{
"order": {
"RETRY_INTERVAL": 28800,
"EXPIRATION_DATE": 57601,
"MAX_RETRY_COUNT": 3
},
"DEFAULT": {
"RETRY_INTERVAL": 28800,
"EXPIRATION_DATE": 57601,
"MAX_RETRY_COUNT": 2
},
"product": {
"RETRY_INTERVAL": 28800,
"EXPIRATION_DATE": 57601,
"MAX_RETRY_COUNT": 2
},
"productprice": {
"RETRY_INTERVAL": 28800,
"EXPIRATION_DATE": 57601,
"MAX_RETRY_COUNT": 2
},
"productstock": {
"RETRY_INTERVAL": 28800,
"EXPIRATION_DATE": 57601,
"MAX_RETRY_COUNT": 2
},
"sent_to_remote": {
"EXPIRATION_HOUR": 6
}
}
```
The sample config contains different properties and their corresponding values. It is divided into sections as follows:
* `order`: Configuration related to orders.
* `default`: Default configuration.
* `product`: Configuration related to products.
* `productprice`: Configuration related to product prices.
* `productstock`: Configuration related to product stocks.
* `sent_to_remote`: Configuration related to sending to a remote location.
Under each property, there are specific configuration values such as "RETRY\_INTERVAL" (Retry Interval), "EXPIRATION\_DATE" (Expiration Date), and "MAX\_RETRY\_COUNT" (Maximum Retry Count). Additionally, the "sent\_to\_remote" section includes the "EXPIRATION\_HOUR" (Expiration Hour) property.
This configuration can be used to define parameters such as retry intervals, expiration dates, and maximum retry counts for specific operations.
Under Bulk Price and Stock Update, Users can update certain products using the **+Update by Uploading Files** button by uploading a CSV file or use the **Update All** button to update the Product Information, Price, Stock, and Image of all products within the linked catalog on the relevant Sales Channel.
---
# 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://docs.akinon.com/tutorials/omnitron/settings/how-to-add-and-configure-a-new-sales-channel-in-omnitron.md?ask=&goal=
```
`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.