> ## Documentation Index
> Fetch the complete documentation index at: https://codebeans-payment-rules-pro.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Advanced customization

> Up to five conditions with And / Or, sub-conditions, and a choice of function input.

Everything a simple rule does, plus multiple conditions, sub-conditions, and a choice of function input. Requires the **Advanced** plan.

## Choose function input

A section that does not exist on simple rules, and the one worth understanding first.

A *function input* is the set of checkout data your rule is allowed to read. Requesting less data makes the rule faster; requesting the wrong set means a condition you need is unavailable.

| Input | Use it for |
| - | - |
| **Standard input** | The default. All commonly used fields — cart, customer, shipping. Start here. |
| **Date input** | Rules keyed off dates or weekdays. |
| **Market input** | Rules keyed off Shopify Markets. |
| **Discount input** | Rules that inspect discounts on the cart. |
| **Customer input** | Rules needing extended customer fields. |
| **Attribute input** | Rules reading cart or line-item attributes. |

![Choosing a function input](https://mintcdn.com/codebeans-payment-rules-pro/0guf-DxrSbw6Ls57/images/advanced-function-input.jpg?fit=max\&auto=format\&n=0guf-DxrSbw6Ls57\&q=85\&s=3f71d0569b8ab5a381c60b169ac4a83c)

If a condition you expect is missing from the picker, the function input is almost always why.

## Set condition to run this customization

![The condition group header, showing the counter and the And / Or joiner](https://mintcdn.com/codebeans-payment-rules-pro/0guf-DxrSbw6Ls57/images/advanced-conditions.jpg?fit=max\&auto=format\&n=0guf-DxrSbw6Ls57\&q=85\&s=95eafad3416d3447c808767adfc3dd81)

The header shows a counter — **1/5**. You may add up to five conditions.

### And / Or

A radio pair above the conditions, applying to the whole group:

* **And** — every condition must be true. Narrows.
* **Or** — any one condition being true is enough. Widens.

See [Combining conditions with And / Or](https://codebeans-payment-rules-pro.mintlify.site/conditions-and-actions/and-or.md) for how to handle rules that seem to need both.

### Each condition

Numbered **#1 condition**, **#2 condition**, and so on, each with its own **Remove** button. Inside, the same picker-operator-value trio as a simple rule.

### Add sub condition

Beneath each condition. A sub-condition refines its parent rather than standing alongside it — *Cart contains products* narrowed by *collections of product in cart*, or *tags of product in cart*, or *vendor of product in cart*. Use sub-conditions to describe one thing precisely; use extra conditions to describe separate things.

## Operations and payment methods

Identical to a simple rule: tick **Hide**, **Sort**, and/or **Rename**, then toggle the methods in **Hide, sort or rename payment methods** and use **Edit** for per-method settings.

## Reading the Description panel

With five conditions the form gets long, and the right-hand **Description** becomes the reliable check. It renders the whole rule as one sentence with the **and** / **or** joiner shown as a badge. Read it aloud before saving. If it does not match your intent, the rule is wrong regardless of how the form looks.

## A worked example

*Hide bank transfer for logged-out customers on small orders.*

1. Function input → **Standard input**
2. Joiner → **And**
3. Condition #1 → **Cart total**, **Less than**, **2000**
4. Condition #2 → **Customer logged in**, **is not logged in**
5. Operation → **Hide**, toggle **Bank Deposit**
6. Status **Active** → **Save**


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.