> 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-layout-configuration.md).

# Store Layout Configuration

You control the order of everything on your store page. Sections, categories, and the SKUs inside each category can all be dragged into the arrangement you want.

## Why layout is worth spending time on

Layout is a conversion decision, not a cosmetic one. Where the player input field sits determines how many players start a purchase. When the payment channel appears determines how many finish it. How far a player has to scroll before they see the pack they came for determines whether they scroll at all.

You know your players better than a generated default does. This gives you a way to act on that, test it, and change it again next week if the first attempt was wrong.

## Reordering sections

The major building blocks of your store page can be dragged into any order:

* **Player input** — where players enter their player ID or account details
* **Payment channel** — where players choose how they want to pay
* **Catalogue** — your categories and SKUs
* **Short description**
* **Long description**
* **FAQs**

## Reordering categories

Within the catalogue, your categories can be dragged into whatever sequence suits you. This is the main lever for deciding which part of your catalogue a player meets first.

## Reordering SKUs within a category

Inside each category, individual SKUs can be dragged into the order you want. Use this to put your best-performing or highest-margin packs where they'll be seen, rather than wherever the catalogue import happened to place them.

For controlling how *prominent* a SKU looks as well as where it sits, see [Presenting your catalogue](https://docs.coda.co/coda-webstore/coda-webstore-builder/catalog-design-configuration.md).

## Saving and publishing

Drag your sections, categories or SKUs into position and save. The new order is written to your sandbox store, where you can view it as a player would.

When you're happy with the arrangement, publish it to production.


---

# 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-layout-configuration.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.
