This article explains the settings and evaluation of price rules by customer group. The feature is available on the Full plan and evaluates one order at a time.
Each rule groups customers using customer tags or one customer metafield.
Setting | Description |
|---|---|
Rule name | A name for administrative use. |
Group condition | Choose Customer tags or Customer metafield. You cannot use both in the same rule. |
Namespace and Key | Specify these for a customer metafield. For example, enter custom.customer_type as custom for Namespace and customer_type for Key. |
Group name | The name substituted for {{tierName}} in product and alert messages. |
Condition | Specify up to 5 values per group. Matching any one value makes the customer eligible for that group. |
Choose one of the following 3 options under Limit for each group.
Limit | Setting and result |
|---|---|
No limit | This rule does not restrict the purchase amount. Other rules still apply. |
Limit | Set a minimum amount, a maximum amount, or both. |
Cannot purchase | Disallow eligible purchases. No minimum or maximum amount is required. |
Enter minimum and maximum amounts greater than 0 in the store currency. If you set both, the maximum must be greater than or equal to the minimum.
Leaving one field blank means no lower or upper limit on that side. You cannot leave both fields blank when Limit is selected.
Amounts below the minimum or above the maximum are restricted. An amount equal to either boundary meets the condition. You cannot set an amount increment.
The diagram below uses a JPY 5,000 minimum and a JPY 30,000 maximum. JPY 4,999 and JPY 30,001 fall outside the range; JPY 5,000 and JPY 30,000 meet this rule.
Only the first matching additional group, from the top, applies.
You can add up to 10 groups. Drag them to change their priority.
Member means logged-in customers who match no additional group; Guest means customers who are not logged in. The base groups stay at the bottom.
The base groups default to No limit. Additional groups start with Limit and require an amount.
Changing Group condition from Customer tags to Customer metafield, or the other way around, removes every group you added. The base groups retain their names and limits.
Customer tag and customer metafield conditions apply only to logged-in customers. Entering an email address at checkout alone still counts as a guest.
Condition | Matching behavior |
|---|---|
Customer tags | Matches if the customer has any specified tag. Matching is not case-sensitive. |
Customer metafield | Requires an exact match to the stored value. Single-line text, integers, and True or False are supported; list types are not supported. |
An unset value, a mismatch, or an unsupported metafield type does not match an additional group. The Member settings apply if the customer is logged in; Guest settings apply otherwise. Integer representations and letter case in strings are not normalized automatically.
Choose one of the following 4 amounts to compare with each group's minimum and maximum.
Price type | Amount evaluated |
|---|---|
Item total (before product discounts) | The amount for eligible items before product discounts |
Item total (after product discounts) | The amount for eligible items after product discounts |
Cart subtotal | The amount for the entire cart, excluding shipping and tax, before discounts |
Grand total | The amount for the entire cart, including shipping and tax, after discounts |
Cart subtotal and Grand total evaluate the entire cart. The Applicability and Eligible items selectors are hidden, and you cannot restrict evaluation to specific products. You can still choose display timing.
The diagram below compares eligible items A and B with ineligible item C. With Applicability set to Cart, item-based price types total only A and B; cart-level price types evaluate the entire cart, including C. This illustrates what is evaluated and is not an app screenshot.
For Item total (before product discounts) and Item total (after product discounts), eligible item amounts are totaled at the following level.
Applicability | How amounts are totaled |
|---|---|
Variant | Total each eligible variant separately. |
Product | Total the eligible variants belonging to the same product. |
Cart | Total eligible items in the cart. Ineligible items are not included. |
Choose all items, specific products or variants, specific collections, or products with specific tags. If an eligible item is absent from the cart, its minimum amount cannot force the customer to add it.
Variables in messages can be replaced with the values configured for the customer's group.
Setting | Description |
|---|---|
Product message | Configure separate messages for Limit and Cannot purchase groups. A blank message is not displayed. No message is displayed for No limit groups either. |
Alert message | Configure messages for amounts below the minimum, amounts above the maximum, and blocked purchases. |
Display timing | Choose Cart updated and checkout or Checkout only. |
Available variables are {{tierName}}, {{minPrice}}, and {{maxPrice}}. Use {{tierName}} for a blocked-purchase message. Translate group names and messages by selecting Translate on the details page.
Product messages require the app embed. This feature does not control the quantity input. Amount variables do not include a currency symbol, so check the currency wording in your messages.
Amounts are stored in the store currency used when the rule was created. Checkout converts them to the payment currency for evaluation, but amounts in product-page messages remain in the store currency.
Changing the store currency does not automatically convert existing minimums or maximums. Disable existing rules and recreate them in the new currency. A currency change may go undetected and cause unintended evaluation results.
No limit removes restrictions only within this rule. It does not override existing price rules, cumulative price rules, or other restrictions.