> 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/publish-take-down-and-delete-items.md).

# Publish, take down, and delete items

Publishing an item makes it visible and buyable in your published game. Publish, take an item down, or delete it from `Store Manager`, or ask your agent to do it.

Changing the name, description, Silicon price, or image is on [Create and manage items](https://studio-docs.sandbox.game/monetization/create-and-manage-items.md).

| Action    | What happens                                                       |
| --------- | ------------------------------------------------------------------ |
| Publish   | The draft becomes live. Players can see it and buy it.             |
| Take down | The item returns to draft. Players can no longer see it or buy it. |
| Delete    | The item is removed from the store.                                |

## Step 1: Check the item is ready

Use an item you have already bought in the editor. That test is on [Test purchases without spending Silicon](https://studio-docs.sandbox.game/monetization/test-purchases.md).

Before you publish it:

1. The name is clear, and the description says what the item does in one line.
2. The item has its own image, in place of the placeholder art.
3. The price is set in Silicon, or the item is deliberately free.

## Step 2: Publish your game

A live item appears only in a published game. Publish the game on [How to Publish](https://studio-docs.sandbox.game/publishing/how-to-publish.md).

Each item is linked to you and your game when it is created.

## Step 3: Publish the item

In `Store Manager`, select the draft and select `Publish`.

Or ask your agent:

```
Publish the Crisp Apple item.
```

The item is live. Open the published game and open the shop. The live item is there. Drafts are not.

## Step 4: Take an item down

{% hint style="warning" %}
*WARNING: Leave a live item that players have already bought as it is, including its price. Taking it down or deleting it removes that item from the shop.*
{% endhint %}

In `Store Manager`, select the live item and select `Take down`. The item returns to draft. Players can no longer see it or buy it.

Or ask your agent:

```
Take down the Crisp Apple item.
```

## Step 5: Delete an item

In `Store Manager`, select the item and select `Delete`. The item is removed from the store.

Or ask your agent:

```
Delete the Crisp Apple item.
```

Deleting a draft that nobody has bought removes that draft. For a live item players have bought, follow the warning in Step 4.

## What You've Done

The item is live in your published game, and players can buy it with Silicon. Take it down to return it to draft, or delete it to remove it from the store.


---

# 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/publish-take-down-and-delete-items.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.
