> 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/sales-channels/sales-channel-settings/how-to-manage-instore-settings-in-omnitron.md).

# How to Manage Instore Settings in Omnitron?

This tutorial provides step-by-step instructions for managing Instore Settings in Omnitron.

## <mark style="color:red;">Step 1: Access to Omnitron​</mark> <a href="#step-1-access-to-omnitron" id="step-1-access-to-omnitron"></a>

* Get access to the **Omnitron** panel.
* Enter your *Username* and *Password*, and then click the **Sign In** button.\
  ![](/files/FQgto2ESMuyyETj02bTx)

## <mark style="color:red;">Step 2: Navigate to Instore Settings Page​</mark> <a href="#step-2-navigate-to-instore-settings-page" id="step-2-navigate-to-instore-settings-page"></a>

* Follow the **Sales Channels** sidebar and click on the **Sales Channel Settings** menu.
* Click on the **Instore Settings** cardbox to reach the **Instore Settings Form**.

{% hint style="info" %}
**Instore Settings** cardbox appears only when an *Instore Application* is installed to a related project and connected with the *Omnitron Application*.
{% endhint %}

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

* On the **Instore Settings** page, *Instore Application Settings* and *Configuration* for selected Sales Channel can be seen and edited.

## <mark style="color:red;">Step 3: View/Edit Application Settings​</mark> <a href="#step-3-viewedit-application-settings" id="step-3-viewedit-application-settings"></a>

* Clicking on the **Application Settings** step on the wizard, users have the option to set *Font, Logo, Button Color, Default Instore Language, Default Page* for related Sales Channel's Instore Application.
  * **Font:** The designated font for the Instore application UI. Users have the option to either use the default font or upload custom fonts according to their preference.
  * **Logo:** The brand logo displayed on the Instore UI.
  * **Favicon:** The Favicon that enhances the brand presence and is visible on the Instore UI.
  * **Button Color:** The color scheme applied to buttons featured in the Instore UI. Users can select their preferred button color through a color-picker pop-up.
  * **Language:** Users can set the default language for the Instore UI.
  * **Default Page:** Users can select the default landing page for the Instore application.<br>

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

{% hint style="info" %}
Users can only select;

* *.svg* type documents for *Logo*,
* *.ico* type documents for *Favicon*,
* *.otf, .ttf, .eot, .woff, .woff2* types of documents for *Regular Font*.
  {% endhint %}

## <mark style="color:red;">Step 4: View/Edit Configuration​</mark> <a href="#step-4-viewedit-configuration" id="step-4-viewedit-configuration"></a>

* Clicking on the **Configuration** step on the wizard, users have the option to set *Config Settings* and *Menu Settings* for Instore Application.
* Users can Enable/Disable listed Config Settings, such as “Send SMS When Signing Up, Customer Search with Name, etc.” in the **Config Settings** tab.<br>

  <figure><img src="/files/uojMrCkWCeeP4JuZORfj" alt=""><figcaption></figcaption></figure>
* Users can Enable/Disable menus that are shown in the Instore Application in the **Menu** tab.<br>

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


---

# 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/sales-channels/sales-channel-settings/how-to-manage-instore-settings-in-omnitron.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.