> For the complete documentation index, see [llms.txt](https://help.dollarlabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dollarlabs.io/dollarlabs-b2b-custom-pricing/credit/over-limit-rules.md).

# Over-limit rules

Choose what happens at checkout when a buyer nears or passes their credit limit, or has an overdue invoice — warn, block, or ask for payment upfront.

{% hint style="info" %}
**Plan:** Credit limits & net terms are available on the Founding plan.
{% endhint %}

**Without rules, an order that takes a buyer over their limit is refused at checkout, by any payment method.** Rules change that. A rule checks a buyer's credit at checkout and, when it matches, does one of three things:

| Action                                   | What the buyer gets                                                           |
| ---------------------------------------- | ----------------------------------------------------------------------------- |
| **Show info/warning message**            | A message in the cart. The order still goes through                           |
| **Block orders**                         | Checkout is refused, with your message                                        |
| **Require a payment method at checkout** | Net-terms payment options are hidden, so the buyer must pick a payment method |

Open **Dollarlabs B2B → Credit → Rules**.

## Templates

The fastest start is **Start from a template**. Select **Use** on a card; the rule editor opens filled in. Adjust it, select **Apply**, then **Save** in the bar at the top.

| Template                                    | When                                 | Does                                                                                                 |
| ------------------------------------------- | ------------------------------------ | ---------------------------------------------------------------------------------------------------- |
| **Require payment upfront when over limit** | No credit left after this order      | Hides net-terms options and **lets the order through** — the buyer pays now instead of being refused |
| **Block when an invoice is overdue**        | An invoice is more than 30 days late | Blocks: "Your account has an overdue invoice. Please settle it to place new orders."                 |
| **Require payment upfront when overdue**    | An invoice is more than 30 days late | Hides net-terms options; over-limit orders are still refused                                         |
| **Warn at 80%**                             | More than 80% of the limit used      | Shows "You're close to your credit limit" in the cart                                                |
| **Company-wide block at limit**             | The company's limit is used up       | Blocks every contact of that company (stores with B2B companies only)                                |

<figure><img src="https://2844543096-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcVBfwy7Yj4tU8TsxkHEr%2Fuploads%2Fgit-blob-2cc76d04a29a07173be500668cb2782be6294e15%2Fcredit-rules-templates-annotated.png?alt=media" alt="Rules page with five templates and the Summary card saying orders over the limit are blocked at checkout."><figcaption><p>Start from a template. Until you add rules, the Summary says over-limit orders are blocked.</p></figcaption></figure>

## Build a rule

Select **Add rule** (or **Use** on a template).

<figure><img src="https://2844543096-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcVBfwy7Yj4tU8TsxkHEr%2Fuploads%2Fgit-blob-c25420e7372dab324ebf8904586be38092ffc446%2Fcredit-rule-editor-annotated.png?alt=media" alt="Add rule dialog: Check credit at Company, Location and Customer; condition Available credit limit is Exhausted; action Require a payment method at checkout; Let these orders through even when over the limit is ticked." width="682"><figcaption><p>The rule editor, filled in from the Require payment upfront template.</p></figcaption></figure>

### Rule name and Only fire when

Give the rule a **Rule name**. **Only fire when** decides how its conditions combine:

* **All rules pass** — every condition must match
* **Some rules pass** — one matching condition is enough
* **No rules pass** — fires when none of the conditions match

### Check credit at

Shown on stores with B2B companies. Tick **Company**, **Location** and/or **Customer**. The rule fires when its conditions match for any ticked level, each checked against that level's own limit and balance.

{% hint style="warning" %}
**A new rule checks only Customer.** Templates tick all three. If you build a rule yourself and your limits are on companies or locations, tick those levels too — otherwise the rule never sees them.
{% endhint %}

### Conditions

Add at least one. Each condition can be used once per rule.

| Condition                  | Meaning                                                                             | Compare with                                 |
| -------------------------- | ----------------------------------------------------------------------------------- | -------------------------------------------- |
| **Available credit limit** | Limit minus what's owed. "Exhausted" means nothing left                             | **Exhausted** / **Not exhausted**            |
| **Days past due**          | Days since the oldest unpaid invoice passed its due date. 0 when nothing is overdue | **Greater than**, **Less than**, **Between** |
| **Utilization (%)**        | Owed ÷ limit, as a percent. An account with no limit has no utilization             | same                                         |
| **Outstanding amount**     | Total unpaid balance now, in your store's currency                                  | same                                         |

At checkout, **Available credit limit** and **Utilization** include the order being placed — they're the figures *after* this order. **Between** includes both ends.

### When this rule matches

* **Show info/warning message** — shown in the cart; the order still goes through. To show it in checkout too, add the checkout block (Shopify Plus). See [What buyers see](https://help.dollarlabs.io/dollarlabs-b2b-custom-pricing/credit/what-buyers-see.md#checkout-block-shopify-plus).
* **Block orders** — the buyer can't place the order.
* **Require a payment method at checkout** — hides net-terms methods and Shopify's "Choose payment method later". To hide other methods too, tick them under **Also hide any other method buyers shouldn't use**, or type a name under **Add a payment method by name** (for example "Invoice — Net 30") and select **Add**.

{% hint style="warning" %}
**Require a payment method doesn't collect payment, and it doesn't remove a company's Shopify payment terms.** A contact at a location with Net 30 keeps those terms: the order can still show "Due today $0.00" with the balance due later. To change that, change the location's payment terms in Shopify. For tag-based buyers, tick or add your manual payment method (for example "Invoice — Net 30") on the rule, so they can't choose it.
{% endhint %}

### Let these orders through

**Let these orders through even when over the limit** (not shown for **Block orders**) is **off** by default.

* **Off:** the rule shows its message or hides payment methods, but the credit limit still refuses an over-limit order.
* **On:** an over-limit order is placed and lands in [Needs review](https://help.dollarlabs.io/dollarlabs-b2b-custom-pricing/credit/review-orders-and-activity.md#needs-review), where you decide.

This is the only way to let a buyer past a limit. It applies to the levels the rule checks: if the rule checks only **Customer** and the company is over its limit, the company limit still refuses the order.

### Message shown to the buyer

Open **Message shown to the buyer** to set a **Headline** and **Message**. Select a chip to insert a figure:

`{available_limit}` `{total_limit}` `{available_limit_post_order}` `{outstanding}` `{utilization}` `{days_past_due}`

| Action          | Default headline      | Default message                                                             |
| --------------- | --------------------- | --------------------------------------------------------------------------- |
| Warn            | Heads up              | This order leaves {available\_limit\_post\_order} of {total\_limit} credit. |
| Block           | Order blocked         | This order is blocked by a credit rule.                                     |
| Require payment | Full payment required | Full payment is required for this order.                                    |

Left unchanged, buyers see the built-in wording in their own language. Once you edit it, your text shows in every language.

Select **Apply** to add the rule to the list, then **Save** in the bar at the top. **Apply alone doesn't save.**

## When several rules match

**Block** wins over **Require payment method**, which wins over **Warn**. When two matching rules share an action, the buyer reads the message of the rule listed first. Inactive rules are ignored.

At checkout the app checks in this order:

```mermaid
flowchart TD
    start["Buyer checks out"] --> hold{"Account on hold?"}
    hold -->|"Yes"| refusedHold["Refused:<br/>account on hold"]
    hold -->|"No"| block{"A Block rule<br/>matches?"}
    block -->|"Yes"| refusedRule["Refused:<br/>the rule's message"]
    block -->|"No"| over{"Over any limit?"}
    over -->|"No"| ok["Checkout continues"]
    over -->|"Yes, and a matching rule<br/>lets it through"| review["Order placed<br/>lands in Needs review"]
    over -->|"Yes, nothing<br/>lets it through"| refusedLimit["Refused:<br/>over the credit limit"]
```

## Manage your rules

**Your rules** lists every rule with its condition, action and an **Active** switch. Use the icons to edit, duplicate or delete. Tick rows for bulk **Set action…**, **Mark active**, **Mark inactive** or **Delete**. **Export CSV** downloads your rules as a backup.

The **Summary** beside the list restates each rule in plain words, for example "When utilization > 80 → buyers see a warning in cart but can still order".

<figure><img src="https://2844543096-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcVBfwy7Yj4tU8TsxkHEr%2Fuploads%2Fgit-blob-dc65239380b56e671743971fea97a721289a4e8e%2Fcredit-rules-list-annotated.png?alt=media" alt="Your rules table with Require payment upfront when over limit, Warn at 80% and Block when an invoice is overdue, each with an action badge and an Active switch."><figcaption><p>Each rule has an action and an Active switch.</p></figcaption></figure>

## Next

* [What buyers see](https://help.dollarlabs.io/dollarlabs-b2b-custom-pricing/credit/what-buyers-see.md) — where warnings and blocks appear
* [Review orders & activity](https://help.dollarlabs.io/dollarlabs-b2b-custom-pricing/credit/review-orders-and-activity.md) — decide on orders that went through over a limit
