> 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/instore/install-instore-service-on-acc-project.md).
# Install Instore Service on ACC Project
To add the Instore service to an existing or newly created project on the ACC platform, you first need to go to the project detail screen. If you want to create a new Instore project, you need to click on the **Add New Service** button on the project detail screen. When you click the button, a dropdown menu will appear listing the available services on ACC. You can initiate the installation process by selecting the Instore service. To install Instore, the project must have Omnitron, Omnitron FE, and Commerce services.
To proceed with the Instore installation, "name" and "slug" information of the Instore project to be installed must be entered in the pop-up form that appears. After entering the necessary information, the installation process can be started by clicking the **Apply** button.
During the Instore installation process, the "Setup Status" column displays "Initializing Setup", "Deploying", and "Deployed" sequentially. To complete the Instore installation, the Setup Status must transition to the "Deployed" state.
Initializing Setup Status
Deploying Status
Deployed Status
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.akinon.com/tutorials/instore/install-instore-service-on-acc-project.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
