> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-commerce/tutorials/build-a-store/installation.md).

# Installation

Installing Umbraco Commerce on your Umbraco site.

The first thing you need to do is set up an Umbraco site with Umbraco Commerce installed.

## Prerequisites

To follow this tutorial, you'll need the following:

* Umbraco.CMS version 15.1.0+
* Umbraco.Commerce version 15.0.0
* SQL Database (LocalDB or any SQL server)
* Visual Studio or your preferred IDE
* [Umbraco CMS Requirements](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/requirements)

## Setup your Umbraco Project

To set up your Umbraco project, see the [Installation](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/install) article.

## Installing Umbraco Commerce

Once your Umbraco site is up and running, you can install the [Umbraco Commerce package](/umbraco-commerce/getting-started/install.md).

{% hint style="info" %}
If you installed Umbraco CMS using a SQLite database, you will need to configure [SQlite support](/umbraco-commerce/how-to-guides/configure-sqlite-support.md).
{% endhint %}


---

# 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.umbraco.com/umbraco-commerce/tutorials/build-a-store/installation.md?ask=<question>&goal=<user_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.