> For the complete documentation index, see [llms.txt](https://flicky.gitbook.io/flicky-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flicky.gitbook.io/flicky-docs/user-guide/variant-table.md).

# Variant Table

## What it does

The Variant Table turns the product page into a **multi‑variant ordering grid**. Instead of picking one variant at a time, wholesale buyers see every variant in a table with quantity inputs and can add many of them to the cart in a **single Add All step** — ideal for products with lots of sizes, colours, or pack options.

For each variant the table can show the SKU, stock status, the B2B price (with the retail price crossed out), a quantity input, and a row total. You control which products and customers see the table, how it's laid out, and what quantity rules apply.

## Before you start

* Install Flicky and enable the storefront app embed — see [Install and Enable Flicky On Your Store](/flicky-docs/user-guide/getting-started.md).

## Step‑by‑step

### 1. Open Variant Table

From the Dashboard or the left navigation, click **Variant Table**. The list shows your table rules with their status and schedule. The page also has a **Settings** button for global table options.

![Variant Table empty state.](/files/Ym0ArhUpsyavUmlC2LKC)

Click **Create rule** to start a new one.

### 2. Configure the rule

On the **Targeting** tab:

* **Title** and **Description** — an internal name and notes for the rule.
* **Display position** — *Block* (you place a **Flicky Variant Table** block in the theme editor — the default) or *Auto* (Flicky inserts the table automatically on the product page).
* **Customer eligibility** — which customers see the table (all, logged-in, not logged in, specific customers, or customer tags).
* **Schedule** and **Status** — optional start/end dates and whether the rule is active.

![New variant table rule](/files/9QCzIoNR5z0d7eorxm4r)

### 3. Choose what it applies to

On the **Applies to** card, target which products show the variant table. Pick one of:

* **All products** — the table can show on any product page.
* **Specific products, collections, or tags** — narrow it down. Selecting this reveals more options.

![Applies to — specific products, collections, or tags](/files/ez7JhvnQZuJSf9sje8wj)

When you select **Specific products, collections, or tags**, you get:

* **Match logic** — *Any (OR)* applies when at least one group matches; *All (AND)* requires every group you fill in to match.
* **Include** — turn on **Products**, **Collections**, and/or **Tags** and pick the targets.
* **Exclude** — optionally carve out exceptions.

### 4. Choose a layout

On the **Design** tab, pick how the variants are arranged:

| Layout     | Best for                                                                                                                                                                                        |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Table**  | The classic list — one row per variant with SKU, price, stock, and quantity. Works for any number of variants.                                                                                  |
| **Grid**   | Image-led cards (2–5 per row) — good when the variant image matters, e.g. colours or patterns.                                                                                                  |
| **Matrix** | A grid of *option 1 × option 2* (e.g. size across the top, colour down the side) — fastest for apparel with two options. Falls back to a table if the product doesn't have exactly two options. |

You can also style colours, borders, and the stock badges. A live preview updates as you edit.

![Variant Table design and layout](/files/qW8yY3burETXy20vsGqb)

### 5. Set quantity rules (optional)

Still on the **Targeting** tab, the **Quantity rules** card lets you enforce how buyers order. Each group is optional — leave it off for no limit:

* **Per variant** — a minimum, maximum, and step (multiple) for each variant. A step of 6, for example, forces case quantities (6, 12, 18…).
* **Order total (all variants)** — a minimum and/or maximum quantity across all variants in the table.
* **Variant mix (distinct variants)** — the minimum and/or maximum number of *different* variants that must be ordered.

These rules block the buyer at the table until the order is valid, and they're enforced again at checkout so they can't be bypassed.

![Variant Table quantity rules](/files/FgInsmUKkwYdn4aD9rcr)

### 6. Adjust global settings (optional)

Click **Settings** on the Variant Table page to configure options that apply across **all** your table rules:

* **Low stock threshold** — the quantity at which a variant counts as "low stock".
* **Show retail price** — cross out the retail price next to the B2B price.
* **Out-of-stock display** — *disable* (show but block) or *hide* out-of-stock variants.
* **Price display** — show the unit price, a row total, or both.
* **Default columns** and other table-wide defaults.

![Variant Table settings](/files/1Zo3iBWuuqgdFrsCtFhF)

### 7. Save

A **Save bar** appears when you have unsaved changes. Click **Save** to publish.

## Stock & price display

Each variant shows a stock status badge with one of five states: **in stock**, **low stock**, **out of stock**, **back-orderable**, or **pre-order**. By default low stock doesn't reveal the exact count (you can turn that on in settings).

Out-of-stock variants can either be shown but disabled, or hidden entirely (back-orderable and pre-order variants are never hidden). When **Show retail price** is on and a customer's B2B price is lower, the retail price appears crossed out beside it.

## On the storefront

When the app embed is enabled and a rule is active, eligible customers see the table on matching product pages:

* They type quantities for as many variants as they like.
* They click **Add all** to add everything to the cart in one request.
* Quantity rules are checked as they go — the button stays disabled until the order is valid.

## Key fields explained

| Field                    | What it controls                                                                                                              |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| **Applies to**           | Which products display the variant table.                                                                                     |
| **Customer eligibility** | Which customers see the table on those products.                                                                              |
| **Layout**               | Table, grid, or matrix arrangement of the variants.                                                                           |
| **Quantity rules**       | Per-variant min/max/step, combined total, and variant-count limits.                                                           |
| **Status & schedule**    | Whether the rule is active and when it runs.                                                                                  |
| **Settings (global)**    | Table-wide defaults — low stock threshold, retail price, out-of-stock handling, price display, columns — shared by all rules. |

## Tips & common setups

* **Bulk apparel ordering:** use the **matrix** layout on an "Apparel" collection so buyers can enter quantities for every size × colour at once.
* **Case-pack enforcement:** set a per-variant **step** of 6 (or 12) so buyers can only order full cases.
* **Minimum order:** set a **combined total** minimum so the table won't submit until the buyer reaches your MOQ.
* **Wholesale‑only table:** restrict eligibility to a `wholesale` customer tag so retail shoppers keep the standard product page.

## Troubleshooting

**The table isn't showing on the product page.** Confirm the storefront app embed is enabled (see [Getting started](/flicky-docs/user-guide/getting-started.md)), the rule is **Active** and in schedule, and the product and customer match the rule's **Applies to** and eligibility settings. If the display position is *Block*, confirm you added the **Flicky Variant Table** block in the theme editor.

**Only some rules are active.** There's a limit on how many variant‑table rules can be enabled per store at once. If a rule won't activate, deactivate one you no longer need and try again.

**The matrix layout shows as a plain table.** The matrix layout needs a product with exactly two options (e.g. Size and Colour). Products with one or three+ options automatically fall back to the table layout.

**The table layout doesn't look right.** Check the rule's **Design** options and the global **Settings** — both affect how the table renders.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://flicky.gitbook.io/flicky-docs/user-guide/variant-table.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
