> For the complete documentation index, see [llms.txt](https://studio-docs.sandbox.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio-docs.sandbox.game/monetization/add-the-store.md).

# Add the store to your game

Open `Store Manager` once, then ask your agent to add the store. The agent copies the default store into your project, fills in your game ID, and checks that the engine has the UI widgets the store needs.

The agent uses the monetization skills already in the project. What those skills cover is on [How monetization works](https://studio-docs.sandbox.game/monetization/how-monetization-works.md).

## Step 1: Open Store Manager

Open your project in the editor. From the main menu, open `Store Manager`.

That first visit creates your game ID. `Store Manager` shows that your game sells nothing yet. Your agent cannot create the ID. A store is never added to a game by accident.

{% hint style="info" %}
*TIP: If you have already opened `Store Manager` in this project, the game ID exists. Go to Step 2.*
{% endhint %}

## Step 2: Ask your agent to add the store

In your agent, ask:

```
Add the premium store to my game.
```

Wait until the agent finishes the install.

{% hint style="info" %}
*TIP: If the agent reports that your game has no ID, open `Store Manager` from the main menu, then send the same request again.*
{% endhint %}

## Step 3: Open the store in Play mode

Enter Play mode. A shop icon appears in the top-right corner. Press `B` to open the store.

The default store includes:

* `Shop` and `Inventory` tabs
* One-click buying
* Get Silicon, which opens Xsolla checkout without leaving the game
* A sign-in popup for players who are not signed in, also without leaving the game
* Placeholder art for each item type, until you add your own images

It is built with the engine's [UI kit](https://studio-docs.sandbox.game/the-editor/game-ui-kit-widget-reference.md), so it matches the look of a game made with that kit. What the player does from here is on [How monetization works](https://studio-docs.sandbox.game/monetization/how-monetization-works.md).

## Step 4: Check the store against your pause menu

Ask your agent:

```
Pause the game while the store is open, and make sure it doesn't conflict with the pause menu.
```

Enter Play mode, press `B`, and open your pause menu. The game should be paused, and the store should not use the same control as the pause menu.

## Make the store look like your game

The store's source is copied into your project. Ask your agent to restyle or rearrange it. When the store is updated later, the install keeps your store settings.

## What You've Done

The store is in your project, and Play mode opens it with `B`. Choose what each item is on [What you can sell](https://studio-docs.sandbox.game/monetization/what-you-can-sell.md), then create the items on [Create and manage items](https://studio-docs.sandbox.game/monetization/create-and-manage-items.md).


---

# 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://studio-docs.sandbox.game/monetization/add-the-store.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.
