> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/coda-webstore/coda-webstore-builder/store-sandbox-and-production-environment.md).

# Store Sandbox and Production Environment

Every store you manage exists in two environments: a **sandbox** store and a **production** store.

## The sandbox store

Your sandbox store is a complete, working copy of your storefront. It has your real catalogue structure, your real layout, and your real styling — and it can process real test transactions through the Coda Pay sandbox.

It is where all of your editing happens. When you drag a section into a new position, change a button colour, or switch a SKU box to a different variant, that change lands in sandbox.

Because the sandbox is fully functional rather than a static preview, you can do more than look at your changes. You can walk through the entire purchase journey the way a player would — including login and payment — before deciding whether to ship it. See [Testing your store](broken://pages/7b170de7dec87e56ecddbb55d6da1cd9abecc4d4).

## The production store

Your production store is what your players see. It only changes when you publish.

## The workflow

{% stepper %}
{% step %}

## Make your change

Reorder sections, restyle an element, change a SKU treatment.
{% endstep %}

{% step %}

## Save

The change is written to your sandbox store.
{% endstep %}

{% step %}

## Test

Open your sandbox store and check the result. Run a test transaction if the change touches the purchase flow.
{% endstep %}

{% step %}

## Publish

The change goes live on your production store.
{% endstep %}
{% endstepper %}

Saving and publishing are deliberately separate steps. You can accumulate as many changes in sandbox as you like, over as long as you like, and publish them when you're satisfied with the whole set.

## Sandbox availability by market

Your sandbox store is available in every country where the Coda Pay sandbox environment exists, so you can validate market by market rather than testing one geography and assuming the rest behave the same way.


---

# 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.coda.co/coda-webstore/coda-webstore-builder/store-sandbox-and-production-environment.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.
