Why Customer Tag Rules Require Login

Customer tags in DC Order Limits let you create rules that target (or exclude) specific groups of customers — VIPs, wholesale buyers, employees, or any other segment. But there's a critical requirement that trips up most merchants: tag-based rules only work when the customer is logged in.

This article explains why that is, what happens when a guest encounters a tag-based rule, and how to set up your rules so nothing slips through.

Why tags require login

Shopify stores customer tags on the customer account, not on the browsing session. When someone visits your store without logging in, the app can't see their tags while they browse and add items to cart.

Here's the nuance: when a non-logged-in customer enters their email address at checkout, Shopify can look up their customer record at that point — so the app can eventually see their tags. But this creates a frustrating experience:

• A logged-in customer → the app sees their tags immediately, from the moment they land on the store ✅
• A non-logged-in customer → the app has no tag data while they browse and add to cart. The tag check only kicks in at checkout when they enter their email address. ⚠️

This means a customer who isn't logged in can browse your store, add restricted products to their cart, get all the way to checkout — and then get blocked when they enter their email. That's a confusing and annoying experience for the customer.

This is why enforcing login is strongly recommended for tag-based rules. When a customer is logged in, the app knows who they are from the start and can enforce limits immediately — before they add anything to their cart. No surprises at checkout.

What are you trying to do?

Before setting up tag-based rules, ask yourself what you actually want to achieve:

Most merchants only need the first option. The two-rule pattern is for exclusive products where non-tagged customers shouldn't be able to purchase at all.

The simple case: limit tagged customers only

If you just want to limit how much tagged customers can buy — while letting everyone else purchase normally — you only need one rule:

Result:

• Customers with the tag → limited to 1 (tracked across all orders)
• Customers without the tag → no limit applies, they can buy normally
• Guests → blocked until they log in (so the app can check their tags)

This is the right setup when you want to cap purchases for a specific group without restricting everyone else.

When tagged customers aren't being limited

"I set up a Customer Purchase Limit for customers with tag RD3-PS5, but anyone who's logged in can still buy — even without the tag."

This is expected behavior. When you target a rule at "Customers with Specific Tags," the rule only applies to customers who have that tag. Everyone else is unaffected:

• Customers with the tag → limited (e.g., max 1)
• Customers without the tag → no rule applies to them at all
• Guests → no rule applies (unless you set guest handling to block)

If this is what you want (limit tagged customers, let others buy freely), you're done — the single rule above is all you need.

If your goal is to only allow tagged customers to purchase (and block everyone else), you need the two-rule pattern below.

The two-rule pattern: restrict access to tagged customers only

To limit a product so that only customers with a specific tag can buy it (and everyone else is blocked), you need two rules working together:

Rule 1 — Block everyone by default

This rule sets the limit to zero for everyone, but excludes tagged customers — so they're not affected by the block.

Rule 2 — Set the limit for tagged customers

This rule enforces the actual purchase limit for tagged customers and tracks their lifetime purchases.

Result:

• Guests → blocked (can't buy at all — Rule 1 sets max to 0, and Rule 2 requires login)
• Logged-in, no tag → blocked (Rule 1 sets max to 0)
• Logged-in, with tag → limited to 1 (Rule 1 skips them, Rule 2 applies)

Handling guest customers

When setting up tag-based rules, you'll want to decide what happens to guests. DC Order Limits gives you three options under Guest Customer Handling:

For tag-based rules, "Block and require login" is almost always the right choice. Without it, a customer can browse freely, add restricted products to their cart, and only hit the tag-based limit when they enter their email at checkout — a frustrating experience. Requiring login up front means limits are enforced from the moment they land on the store, and logged-in customers without the tag are handled by your blocking rule.

⚠️ Bypass risk: Because tag-based rules rely on customer identity, a shopper can attempt to evade limits by using a different email address or checking out as a guest (where no customer record is matched). "Block and require login" is the strongest defense — it forces every purchase through an account, making it much harder to circumvent tag-based restrictions.

Setting up VIP or membership tiers

If different customer groups should have different limits (e.g., Standard customers get 1, VIP customers get 3), create separate rules per tier:

1. Standard rule — Customer Purchase Limit, max 1, applies to all customers, excludes tag VIP
2. VIP rule — Customer Purchase Limit, max 3, applies to customers with tag VIP

Both rules can target the same products. The app evaluates each rule independently, and a customer only needs to satisfy the rules that apply to them.

Having issues?

If your tag-based rule isn't working as expected, see Troubleshooting: Why My Order Limits Aren't Working → Customer Purchase Limit Issues section.

That guide covers all common issues, including:

• Customers not being recognized (login requirements)
• Tags not matching (case sensitivity)
• Targeting vs. excluding tags
• Guest customer handling settings

Related articles

• Which Limit Type Should I Use?
• Setting up customer purchase limits in Shopify with DC Order Limits
• Using exclusion rules in DC Order Limits