> 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/quick-start/readme/1.-start-your-journey-with-acc.md).

# 1. Start Your Journey with ACC

The very first step in this Quick Start journey is to **create a new project in** [**ACC**](https://apidocs.akinon.com/products/acc). This project will serve as the foundation for all other services and configurations that follow. Here’s how to set up your project:

{% stepper %}
{% step %}

### Log in to ACC

* Visit <https://console.akinoncloud.com/>
* Use the credentials provided to you by Akinon.

{% hint style="warning" %}
To kick-start your project, your ACC account must already be set up.\
If you haven’t received your login info yet, please reach out to Akinon.\
Alternatively, you can try the **Reset Password** option on the login page using your registered email.
{% endhint %}

* ACC uses email-based One-Time Password (OTP) for authentication. An OTP will be sent to your authorized email address—use it to log in securely.

<figure><img src="/files/vCKntaK4TFGylm4FpoFw" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Create a New Project

* Once logged in, navigate to the **"Projects"** page.
* Click the **+ NEW PROJECT** button to start creating a new project.

<figure><img src="/files/AjURKO1vbaGDxqF0n9az" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Fill in the Project Information

* A form will appear asking for the project details.
  * **Project Name**: Enter a clear and descriptive name (e.g., your brand name).
  * **Project Slug**: This is a unique identifier used internally and across services. For example, the slug is required when creating a dedicated Sentry account for monitoring.
* After filling out the information, click the **APPLY** button. You will then be redirected to the plan selection screen.

<figure><img src="/files/FlF2HwGCDmgSz5UxclqV" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Choose a Plan&#x20;

* The “Choose a Plan” screen is currently under development.
* Simply click **CHOOSE PLAN** to proceed.

<figure><img src="/files/jebiVmJsknDwJ8V5r08b" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Accept the Licence Agreement

* The “License” step is also under development.
* Just click **ACCEPT & COMPLETE** to finalize the license agreement and complete your project setup.

<figure><img src="/files/5jO4SQIIFTeq2OWURJYD" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Welcome Page

* Once the project is successfully created, you will be greeted with a **Welcome Page**.
* From here, you can follow provided links to visit the project overview or view its applications.

<figure><img src="/files/aGhFOW7jOW4NCOQVtJJd" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Access Your Project Detail Page&#x20;

* You can either: use the shortcut on the welcome page, or find your project in the left-hand navigation menu and click on it to open its detail page.

<figure><img src="/files/0MGu6oWVjwVBtf878B2p" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Omnitron Deployment Begin Automatically

* As noted on the welcome page, the **Omnitron and Omnitron Frontend** services will automatically start deploying as soon as the project is created.

  > * &#x20;**Omnitron** is the core backend service used for managing product data, catalogs, and essential commerce configurations.
  > * **Omnitron Frontend (FE)** provides the admin interface where you can interact with this data through a user-friendly UI.

  There’s no manual action needed at this stage—just give it a moment to finish deploying in the background.

<figure><img src="/files/LIPhNqOGImSn4fZPFBgy" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Check Deployment Status

* When the installations are complete, both services will show their setup deployment status as **Deployed**.

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

Different deployment statuses may be displayed depending on the current state of the deployment process. Below is a list of possible statuses and the actions that need to be taken for each:

<table><thead><tr><th width="151.76171875">Status</th><th width="284.390625">Description</th><th>Action Required</th></tr></thead><tbody><tr><td><strong>Deploy Needed</strong></td><td>The service has been added, but a version has not been deployed yet.</td><td>A new deployment must be initiated.</td></tr><tr><td><strong>Pending</strong></td><td>The deployment is queued and waiting to be processed.</td><td>No action required. Wait for it to progress.</td></tr><tr><td><strong>Initializing Setup</strong></td><td>Add-ons are currently being installed.</td><td>No action required. Wait for initialization to complete.</td></tr><tr><td><strong>Addon Failed</strong></td><td>An error occurred during the installation of one or more add-ons.</td><td>Akinon support must investigate and resolve the issue.</td></tr><tr><td><strong>Deploying</strong></td><td>A version is currently being deployed.</td><td>No action required. Wait for the deployment to complete.</td></tr><tr><td><strong>Failed</strong></td><td>The deployment process failed.</td><td>Review the Deployment Logs to identify and fix the issue, then redeploy.</td></tr><tr><td><strong>Deployed</strong></td><td>The deployment was successful and the service is up and running.</td><td>No action needed.</td></tr></tbody></table>

> * If the status is **Addon Failed**, Akinon needs to take action to resolve the issue.
> * If the status is **Failed**, review the **Deployment Logs**, fix the root cause, and trigger a new deployment.
>   {% endstep %}

{% step %}

### Accessing Omnitron

* After the deployment is successful, you will receive an email with:
  * The **URL** to access Omnitron Frontend, and
  * A link to **set your password** via "Update Password".
* Use these credentials to log into Omnitron.

<figure><img src="/files/qKnY7jTfHwvh9BkZC31E" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Add Additional Services to Your Project

* Depending on your contract, you may need to add additional services.
* Common services within the Akinon ecosystem include:
  * Seller Center
  * Instore
  * OMS
  * Commerce
    {% endstep %}

{% step %}

### Adding the Commerce Service

* One of the most commonly used services is **Commerce**.
* To add it:

  * Go to your project’s detail page.
  * Click the **+ NEW SERVICE** button in the upper-right corner.
  * Select **Commerce** from the list.

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

{% endstep %}

{% step %}

### Confirm the Deployment&#x20;

* A validation popup will appear.
* Click **YES, PROCEED** to begin the deployment.

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

{% hint style="danger" %}
If the Omnitron deployment is not yet complete, you will see a warning message.\
You must wait for Omnitron to be deployed before you can add any new services.
{% endhint %}

<figure><img src="/files/ssnwTIbbvH4n1pNJcYP1" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Deployment of Commerce Service

* The Commerce service will begin deploying immediately after confirmation.

<figure><img src="/files/QAkVp0I37WHrbFQaailr" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Deployment Status Update

* Once completed, the status will be updated to **Deployed**, indicating it is ready for use.

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

Different deployment statuses may be displayed depending on the current state of the deployment process. Below is a list of possible statuses and the actions that need to be taken for each:

<table><thead><tr><th width="151.76171875">Status</th><th width="284.390625">Description</th><th>Action Required</th></tr></thead><tbody><tr><td><strong>Deploy Needed</strong></td><td>The service has been added, but a version has not been deployed yet.</td><td>A new deployment must be initiated.</td></tr><tr><td><strong>Pending</strong></td><td>The deployment is queued and waiting to be processed.</td><td>No action required. Wait for it to progress.</td></tr><tr><td><strong>Initializing Setup</strong></td><td>Add-ons are currently being installed.</td><td>No action required. Wait for initialization to complete.</td></tr><tr><td><strong>Addon Failed</strong></td><td>An error occurred during the installation of one or more add-ons.</td><td>Akinon support must investigate and resolve the issue.</td></tr><tr><td><strong>Deploying</strong></td><td>A version is currently being deployed.</td><td>No action required. Wait for the deployment to complete.</td></tr><tr><td><strong>Failed</strong></td><td>The deployment process failed.</td><td>Review the Deployment Logs to identify and fix the issue, then redeploy.</td></tr><tr><td><strong>Deployed</strong></td><td>The deployment was successful and the service is up and running.</td><td>No action needed.</td></tr></tbody></table>

> * If the status is **Addon Failed**, Akinon needs to take action to resolve the issue.
> * If the status is **Failed**, review the **Deployment Logs**, fix the root cause, and trigger a new deployment.
>   {% endstep %}
>   {% endstepper %}


---

# 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://docs.akinon.com/quick-start/readme/1.-start-your-journey-with-acc.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.