> For the complete documentation index, see [llms.txt](https://shoppad.gitbook.io/infinite-options/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shoppad.gitbook.io/infinite-options/inputs-and-field-settings/create-swatches/how-to-make-swatches-required.md).

# How to make Swatches required

By default, swatches work like radio buttons. One value is always pre-selected when a customer lands on the product page. If you'd rather have customers make an active choice, there are two ways to set that up.

#### **Option 1: Keep standard swatches and add a required prompt**

Leave **Allow for Multiple Selections** turned off. One swatch will still be pre-selected by default, but you can mark the field as required to prompt customers before they add to cart.

<figure><img src="/files/O5pZZebcjTF11QCEh3y1" alt=""><figcaption></figcaption></figure>

This works well if you want a clean look and are okay with a value being pre-selected.

#### **Option 2: Use multiple selections to require an active choice**

Enable **Allow for Multiple Selections** and check **This option is required**. With this setup nothing is pre-selected when the page loads, and customers have to click a swatch before they can add to cart. \
\
By default the minimum is set to 1 with no maximum, but you can adjust those limits in the field settings.

<figure><img src="/files/HONRIDJ23Dz9soJSMVfh" alt=""><figcaption></figcaption></figure>

The tradeoff is that swatches behave a little differently here. \
\
Customers click once to select and again to deselect, which is different from the standard experience.

{% hint style="info" %}
Not sure which to use? If you just want to make sure customers don't miss the swatch, Option 1 is usually enough. If you need nothing pre-selected, go with Option 2.
{% endhint %}
