> For the complete documentation index, see [llms.txt](https://awecommerce.gitbook.io/awe-color-swatches/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://awecommerce.gitbook.io/awe-color-swatches/faq-and-support/frequently-asked/swatches-not-showing.md).

# Why are swatches not showing on my store?

A quick checklist when swatches don't show on your store.

Work through this list in order — most issues are solved in the first two steps.

{% stepper %}
{% step %}

### The app embed is on

The **AWE Color Swatches** app embed must be on in your **published** theme. See [Enable the app embed](/awe-color-swatches/getting-started/enable-app-embed.md).
{% endstep %}

{% step %}

### The option has a style

In **Option styles**, check the option isn't set to **Shopify default** (product page) or **No show** (collection page), then **Save**.
{% endstep %}

{% step %}

### You're looking at the right page

New options start with **No show** on collection pages. To see swatches on collection cards, pick a style under **Collection page display**.
{% endstep %}

{% step %}

### The values aren't all sold out and hidden

With **Sold-out variant display** set to **Hidden**, sold-out values disappear. See [Settings](/awe-color-swatches/getting-started/settings.md).
{% endstep %}

{% step %}

### Product groups are active

A product group shows only when it's **Active**, has at least 2 products, and its products are published on your Online Store.
{% endstep %}
{% endstepper %}

Still not right? Click **Get quick fix!** on the **Option styles** page — our team checks your theme for free.

***

💬 If you have any related questions, please contact us via **Live chat** in the app.


---

# 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://awecommerce.gitbook.io/awe-color-swatches/faq-and-support/frequently-asked/swatches-not-showing.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.