> 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/pricing.md).

# Pricing Rules

## What it does

Pricing Rules give specific customers their own **custom B2B prices**. Instead of quantity tiers, a pricing rule adjusts the product price for the customers you choose. Use it for negotiated wholesale rates, VIP pricing, or market‑specific price lists.

A rule changes the price in one of three ways:

| Type                    | What it does                            | Example (on a $20 item)    |
| ----------------------- | --------------------------------------- | -------------------------- |
| **Percentage discount** | Takes a percentage off.                 | *20% off* → $16.00         |
| **Amount discount**     | Takes a flat amount off.                | *$5 off* → $15.00          |
| **Fixed price**         | Sets the exact price the customer pays. | *Fixed price $12* → $12.00 |

You control which products and customers a rule applies to, how the new price is shown on the storefront, and how it looks (badges and price colours).

## 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 Pricing Rules

From the Dashboard or the left navigation, click **Pricing Rules**. The list shows each rule's adjustment, priority, status, and schedule.

![Pricing Rules list](/files/zOmmAzEPkidkHVMQD1xU)

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

### 2. Name the rule and set the adjustment

On the **Product** tab:

* **Name** — an internal name for the rule.
* **Type** — *Percentage discount*, *Amount discount*, or *Fixed price* (see the table above).
* **Value** — the percentage, amount, or fixed price for the chosen type.

![New pricing rule form](/files/prZ1b8NMsxN6ohCDhr81)

### 3. Set how the price is displayed

Still on the **Product** tab, two options control how the new price looks to the shopper:

* **Price display** — *Strikethrough* shows the original price crossed out next to the B2B price; *Clean* simply replaces the price with the B2B price (no strike-through).
* **Apply discount from compare-at price** — when a product has a compare-at ("was") price, calculate the discount from that higher price instead of the selling price. Flicky only uses it when it produces a lower price, so customers always get the better deal.

![Price value and display options](/files/HE9CwMFAZkCa7pAVbwzx)

### 4. Choose what it applies to

On the **Applies to** card, target which products get the custom price. Pick one of:

* **All products** — the rule applies to your whole catalog.
* **Specific products, collections, or tags** — narrow it down. Selecting this reveals more options.

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

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 (products can be whole products or individual variants).
* **Exclude** — optionally carve out exceptions.

### 5. Choose eligible customers

On the **Customer eligibility** card, decide which customers get this price: all, logged-in, specific customers, customer tags, segments, markets, or B2B companies.

### 6. Set priority and schedule

* **Priority** — when multiple rules could apply to the same product and customer, the higher priority wins (see [Priority](#priority) below).
* **Schedule** — optional start and end dates. The list shows a computed status: *Active*, *Scheduled*, *Expired*, or *Inactive*.
* **Status** — *Active* or *Inactive*.

### 7. Style the price and badge (optional)

Switch to the **Design** tab to add a discount badge and colour the prices:

* **Badge** — turn on a badge near the price or product image. Choose a shape (pill, circle, ribbon, starburst, rectangle, or tag), set its colours and size, and write the badge text (with optional placeholder tokens — see below). Place it on the image (9 positions) or around the price (before, after, above, below).
* **Price colours** — set the colour of the B2B price and the crossed-out original.
* **Label** — an optional message shown with the price, e.g. *Your wholesale price*.

The badge text can include placeholder tokens that Flicky replaces automatically:

```
{{amount}}    the money saved (for example, $5)
{{percent}}   the percentage off (for example, 20%)
```

![Pricing Rule design tab](/files/ePjBuWpLIIqoo2fB91yJ)

### 8. Save

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

## Priority

When more than one rule could apply to the same product and customer, **priority** breaks the tie — the rule with the higher priority number wins. Use it to layer rules sensibly, for example a broad *25% off everything for wholesale* rule at low priority, and a sharper *fixed price* rule for a hero product at high priority.

You can test exactly which rule wins for a given product, quantity, and customer using the **Price resolution** preview on the rule's detail page.

## On the storefront

When the app embed is enabled and a rule is active, eligible customers see the adjusted price wherever the product appears — the product page and collection/listing pages:

* **Strikethrough** rules cross out the original price and show the B2B price next to it; **clean** rules show only the B2B price.
* If you enabled a **badge**, it renders on the product image or beside the price.

> **At checkout:** the saving is applied as an automatic discount, so the customer always pays the B2B price. On non-Plus stores the checkout line shows the original price minus the discount (rather than a "clean" overridden price) — this is a Shopify platform limit, and the storefront still shows your chosen clean/strikethrough display.

## Key fields explained

| Field                     | What it controls                                                                        |
| ------------------------- | --------------------------------------------------------------------------------------- |
| **Type / Value**          | How the price is adjusted (percentage off, amount off, or fixed price) and by how much. |
| **Price display**         | *Strikethrough* (original crossed out) or *clean* (replaced) on the storefront.         |
| **Apply from compare-at** | Calculate the discount from the compare-at price when it's higher.                      |
| **Applies to**            | Limits the rule to chosen products, collections, variants, or tags.                     |
| **Customer eligibility**  | Restricts the custom price to the customers you choose.                                 |
| **Priority**              | Breaks ties when more than one rule matches — higher priority wins.                     |
| **Badge & colours**       | Optional discount badge and price/label colours shown on the storefront.                |

## Tips & common setups

* **Wholesale price list:** *Percentage discount, 25% off*, applied to all products, eligible only to the `wholesale` customer tag, shown as strikethrough.
* **VIP fixed price:** *Fixed price* on a specific collection for a named set of customers, shown clean with a "VIP price" label.
* **Compare-at clearance:** turn on *Apply discount from compare-at price* so a percentage rule discounts from the original ticket price on items already on sale.

## Pricing Rules and Volume Discounts together

A Pricing Rule sets the **base price** a customer sees, while a Volume Discount applies a **quantity‑based discount** on top at checkout.

For example, a customer on a *25% off* wholesale pricing rule buys a $20 item (their base price becomes $15). If a volume discount of *10+ = 10% off* also applies and the two are allowed to combine, ordering 10 units takes each unit to $13.50.

Use **Priority** to control which pricing rule wins when several match, and review the **Combinations** settings on your volume discount to decide whether the two stack. By default a pricing rule does not combine with other product discounts — enable combinations if you want them to layer.

## Troubleshooting

**The custom price isn't showing for a customer.** Confirm the rule is **Active**, today is within its schedule, the customer is **logged in** (if eligibility requires it), and both the product ("Applies to") and the customer (eligibility) match the rule.

**Two rules conflict.** When multiple rules match the same product and customer, the one with the higher **Priority** is applied. Adjust priorities so the intended rule wins.

**The badge isn't appearing on the product image.** Some themes structure the product image differently. If an on-image badge can't be placed, Flicky falls back to showing it around the price. Check the rule is active, eligible, and that the badge is enabled with content.

**Prices look wrong on the storefront.** Make sure the app embed is enabled (see [Getting started](/flicky-docs/user-guide/getting-started.md)) and that no other discount or rule is overlapping unexpectedly.


---

# 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/pricing.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.