> 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/catalog-design-configuration.md).

# Catalog design configuration

Your catalogue is the part of the store players spend the most time looking at. Beyond deciding the order your SKUs appear in, you control how each one is presented.

## SKU box variants

SKU boxes come in several distinct visual treatments. These aren't recolours of the same box — each variant gives the SKU a materially different character, so you can pick one that sits with your art direction.

One of the available variants is a **glass** treatment.

## SKU width

You can set the width of each SKU box.

This is a merchandising control more than a layout one. Width is how a store signals importance: the pack you most want players to buy should take up more room than the ones around it, and the filler SKUs shouldn't be competing with your hero pack for attention.

Because width is set per SKU in Coda Portal, you can retune that hierarchy whenever a campaign changes, rather than living with a fixed treatment across the whole catalogue.

## Particle effects

Individual SKU boxes can carry particle effects, adding motion to the catalogue without requiring you to restyle the whole page.

Used sparingly, this is an effective way to draw attention to a single SKU — a limited-time pack, a new release, or whatever you're currently pushing.

## Motion across the catalogue

Alongside particle effects, your catalogue supports animated treatments such as running borders and shimmer. These are applied through the element override system — see [Customising elements](https://docs.coda.co/coda-webstore/coda-webstore-builder/store-design-customization.md).

A static catalogue reads as a form. A catalogue with motion in it reads as part of a game. For most titles, that difference is worth the setup time.

## Highlighted promotions

Every AI-generated store arrives with a highlighted promotion already running.

This means your store isn't a bare catalogue on day one — it's a working storefront with live ops in place from the moment it's generated. You don't have to configure one to have a store that looks merchandised.

## Ordering

For controlling the order of categories and the SKUs within them, see [Arranging your store layout](https://docs.coda.co/coda-webstore/coda-webstore-builder/store-layout-configuration.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://docs.coda.co/coda-webstore/coda-webstore-builder/catalog-design-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.
