This article explains the settings and evaluation of weight 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 weight. Other rules still apply. |
Limit | Set a minimum weight, a maximum weight, or both. |
Cannot purchase | Disallow eligible purchases. No minimum or maximum weight is required. |
Enter minimum and maximum weights greater than 0 in the rule's weight unit. If you set both, the maximum must be greater than or equal to the minimum.
Decimals are supported to 4 places. The input field rounds the fifth decimal place.
Leaving one field blank means no lower or upper limit on that side. You cannot leave both fields blank when Limit is selected.
Weights below the minimum or above the maximum are restricted. A weight equal to either boundary meets the condition. You cannot set a weight increment.
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 a weight.
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.
The weight unit applies to the whole rule. Each group's minimum and maximum weights are stored as values in that unit.
Setting | Description |
|---|---|
Weight unit | Choose Kilograms (kg), Grams (g), Pounds (lb), or Ounces (oz). |
When product weight unit differs | Convert and include in calculation converts to the rule's unit before totaling. Exclude from calculation leaves products with a different unit out of the total. |
If Exclude from calculation removes every eligible product, that group's minimum weight is not evaluated. A cart that contains only excluded products does not trigger the minimum weight limit.
A group set to Cannot purchase does not evaluate weight. Orders that contain eligible products are blocked even for excluded products or products with a weight of 0.
Changing the weight unit does not convert the minimum and maximum weights already set. Only the input field suffix, the summary, and the message units follow the change. After changing the unit, check the values.
Eligible product weights are totaled at the following level.
Applicability | How weights 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 weight cannot force the customer to add it.
Evaluation uses the weight and weight unit registered on the Shopify product variant.
The weight of each variant is multiplied by its quantity and then totaled.
A variant with no weight registered is treated as 0. When you set a minimum weight, check that the eligible products have a weight registered.
When the rule's weight unit differs from the product's weight unit, the When product weight unit differs setting decides the behavior.
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 weights below the minimum, weights above the maximum, and blocked purchases. |
Display timing | Choose Cart updated and checkout or Checkout only. |
Available variables are {{tierName}}, {{minWeight}}, and {{maxWeight}}. Use {{tierName}} for a blocked-purchase message. Translate group names and messages by selecting Translate on the details page.
Weight variables are replaced with the unit included, such as 1.5kg. Trailing zeros are not shown. Product messages require the app embed, and this feature does not control the quantity input.
No limit removes restrictions only within this rule. It does not override existing weight rules, weight limits by product, or other restrictions.
There is no variable for the current cart weight. Because totals are evaluated per group, messages show the upper and lower values instead.