---
title: "Requirement lists"
---

A feature that lets you create lists that set **specific rules or conditions** that must be met to place successful orders.

Using requirement lists **is optional**, and they can be set up as needed to apply to:

1.  General purchase options, requirements the customer must meet in the cart and checkout.
2.  Customer groups, requirements for wholesale purchases or specific customer segments.
3.  Payment methods, to make options available depending on whether requirements are met.
4.  Enabling the invoice option for the order.
5.  Activating the order review flow.

## Activation and initial setup

> **Note**
>
> This feature is available from the Standard plan up, and does not require activation.
>
> ![](/media/425-1.webp)

### Initial setup

To create requirement lists and use this feature, go to the Bolder admin panel.

Go to Preferences > Purchase options > Requirement lists > Create new.

Once you choose a name, the list will be created and you will need to add the different **requirement types** to it.

<video src="https://files.slack.com/files-tmb/T033NDK04-F09AD8MFSSY-ab8de411c4/grabacio__n_de_pantalla_2025-08-13_a_la_s__15.38.11.mp4?pub_secret=822c5abf65" controls muted loop playsInline style={{ width: "100%" }} />

  

## Requirement types

**Minimums and maximums for**

-   Total cart amount (minus discounts)
-   Net amount
-   Total units
-   Units by type (any type or a specific one)
-   Units by product (any product or a specific one)
-   Units by variant (any variant or a specific one)
-   Items/lines in cart (count by variant)

> **Danger**
>
> These requirements **work together**, so if you add more than one, **the order must meet every one of them to be considered valid**

> **Note**
>
> **Example**
>
> ![](/media/425-2.webp)
>
> **Explanation:** I must have a total amount equal to or greater than $100.000, not buy more than 6 units per product (across all its variants) and not more than 3 units of the same variant.

**Presence of a product from the group**

Among the items added to the cart there must be a:

-   Specific product
-   Product linked to a specific collection
-   Product of a specific type
-   Product of a specific brand
-   Product with a specific tag

> **Danger**
>
> This type can appear multiple times in the same requirement list, as long as they contain different groups and values. **All requirements must be met even when they are of the same type.**

> **Note**
>
> **Example:**
>
> ![](/media/425-3.webp)
>
> **Explanation:** The cart must include a product of the type Seat or Desk, specifically the product "Kaap", and the minimum total amount must also be equal to or greater than $100.000.

**Absence of a product from the group**

Among the items added to the cart there must **not be a** (absence of):

-   Specific product
-   Product linked to a specific collection
-   Product of a specific type
-   Product of a specific brand
-   Product with a specific tag

Like the requirement type "*presence of a product from the group*", it can be repeated multiple times with different groups and values in the same requirement list.

> **Note**
>
> **Example**
>
> ![](/media/425-4.webp)
>
> **Explanation:** If the order is equal to or greater than $100.000, no product of the product type "Asiento" is found, no product from the collection "Destacamos" is found, and the product "Kaap" has not been added to the cart either, this requirement list will be considered met.

  

## Applying requirements

Purchase requirements are a set of conditions that you can optionally link to:

**1\. General purchase options**

When you link a requirement here, your customer or their order must meet it to move on to checkout.

You can only link one requirement list as purchase requirements, so you need to manage all the conditions in it and keep it up to date.

![](/media/425-5.webp)

**2\. Customer group**

When you link a requirement list to a group, all its members must meet it to move on to checkout.

![](/media/425-6.webp)

**3\. Payment methods**

You can link a requirement list to a payment method:

**When met:** Your customer can use it without problems.

**When not met:** This option will not be offered at checkout.

<video src="https://files.slack.com/files-tmb/T033NDK04-F09B088LDSL-e72f2a4798/grabacio__n_de_pantalla_2025-08-13_a_la_s__09.34.32.mp4?pub_secret=6d1ebc0fcf" controls muted loop playsInline style={{ width: "100%" }} />

**3\. Shipping options**

You can link a requirement list to a shipping option:

**When met:** Your customer can use it without problems.

**When not met** you can decide to:

-   Offer it with a percentage surcharge on the total shipping amount.
-   Offer it with a fixed surcharge.
-   Not offer it.

<video src="https://files.slack.com/files-tmb/T033NDK04-F09AM613DGR-1bfa7018cf/grabacio__n_de_pantalla_2025-08-13_a_la_s__13.23.21.mp4?pub_secret=d76670bf86" controls muted loop playsInline style={{ width: "100%" }} />

**4\. Option to request an invoice**

You can link a requirement list to the "Enable invoice option" setting. When met, your customers will see the option to request an invoice on their orders.

![](/media/425-7.webp)

**5\. Order review flow**

You can link a requirement list to the "Enable review flow" setting. When met, orders will go into this special flow.

![](/media/425-8.webp)

Once you have created your requirement lists, you will see the number of requirements and whether the list is linked to any of the features covered above.

![](/media/425-9.webp)
