When Do Customers Need to Be Logged In for Order Limits?

Customers never need a storefront account for limits to enforce. Logging in only changes when some limits are enforced. Here's a clear breakdown.


Quick Answer

Limit Type Login Required? Why
Order Limits (Quantity & Price) ❌ No Limits apply to the cart, not the customer
Customer Purchase Limits ❌ No Enforced when the customer identifies by email at checkout
Tag-Based Rules ❌ No (recommended) Tags are checked once the customer is identified: at login, or when they enter their email at checkout

Detailed Explanation

Order Limits (Quantity & Price Limits)

Login required? No

These limits apply to the current cart/checkout, not to the customer. They work for everyone — logged in or guest.

Example: "Max 2 per order" works without login because it only checks the current cart.

Customer Purchase Limits (Lifetime Limits)

Login required? No

Customer Purchase Limits track what a customer has already purchased across all their orders. To do this, the app needs to identify who the customer is.

You do not need storefront customer account pages. As long as customers identify by email at checkout, the limit enforces. Entering an email at checkout links the order to a customer record, and the limit tracks against that record.

How identification works:

Customer State What Happens
Logged in ✅ Identified immediately. Limit enforced from cart page.
Guest (Allow option) ✅ Identified at checkout when they enter their email. Limit enforced at checkout.
Guest (Block option) ✅ Must log in before purchasing. Limit enforced from cart page.

Want the limit enforced before checkout? Set Guest Customer Handling to "Block and require login".

Why?

  • Logged-in customers are identified immediately
  • The limit is enforced before they even add items to cart
  • No surprises at checkout

→ Setting Up Lifetime / Once-Per-Customer Limits

Tag-Based Rules (Customer Eligibility by Tag)

Login required? No, but recommended

If you're using customer tags to:

  • Restrict products to VIP customers
  • Block certain customer segments
  • Give special limits to wholesale buyers

...the customer must be identified before the app can read their tags. Tags are stored on the customer record, so the app reads them at login, or at checkout when the customer enters their email.

What happens without login:

  • A customer visits your store and browses without logging in
  • The app can't see their tags while they browse and add to cart
  • The tag check happens at checkout, when they enter their email

Requiring login enforces tag rules earlier, from the cart page, instead of surprising the customer at checkout.

→ Why Customer Tag Rules Require Login

Guest Customer Handling Options

When setting up Customer Purchase Limits, you'll see a Guest Customer Handling setting:

Option What it does Best for
Allow guest checkout The limit enforces at checkout, when the customer identifies by email When you want frictionless checkout without requiring accounts
Block and require login Guests must create account/login; the limit enforces from the cart page When you want customers to see the limit before checkout (limited drops, anti-reseller)
Warn but allow Shows message but lets them proceed Balance between UX and awareness
Tip: Standard Order Limits apply to the cart itself, so they work the same for everyone and never involve customer identity. Use them when you only need per-order limits.
Use Case Recommended Setting
Limited product drop (1 per customer) Block and require login
Anti-reseller protection Block and require login
General "limit 2 per customer" Allow guest OR Block — your preference
Wholesale-only products Block and require login + Tag rules
Simple cart limits (max 5 per order) No login needed — use Order Limits

How to Enable "Require Login"

  1. Go to Order Limits → Your Customer Purchase Limit rule
  2. Find Guest Customer Handling
  3. Select "Block and require login"
  4. Save the rule

Customers will now be prompted to log in or create an account before they can purchase limited products.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us