The Repurchase Limit Reached Trigger

Fires when a customer's cumulative purchases under a repurchase rule reach the cap, so a pattern across several orders reaches a human.

Prime MOQ Team

Updated August 26, 2026 · 2 min read

Short answer

Repurchase limit reached" starts the moment a customer's tracked purchases under a repurchase rule hit the cap, and it always carries a real customer and the order that consumed the last of their allowance. Nothing was blocked. The checkout worked exactly as intended. The trigger exists to surface a pattern worth a human look, because six legitimate orders can be one reseller.

There is no guest case, since repurchase limits need a signed-in customer by definition.
It fires once per customer, per rule, per rolling window, on the order that crosses the cap.
Nothing was blocked, so this is a review signal rather than an enforcement event.
It is about a pattern across several orders, not a single attempt.

Before you start

A published rule with a repurchase limit set, described in Limit purchases per customer.
Event sending turned on from the Automations page.

What data you get

Field	What it is
Customer	The customer who reached the cap
Order	The order that consumed the last of their allowance
Rule name	Which repurchase rule fired
Limit quantity	The cap itself
Window in days	The rolling period the rule tracks
Quantity used	How much of the cap this customer has used

How it differs from a blocked order

The Order limit blocked trigger fires when something was stopped. This one fires when something succeeded.

That difference shapes every workflow built on it. There is no upset shopper to recover and no cart to rescue. The order went through, the customer is happy, and what you have is a fact worth knowing: this account has now taken everything the rule allows it for this window.

Whether their next order is blocked is decided by the rule's own repurchase logic, which runs whether or not Automations is set up. See Limit purchases per customer.

Five workflows worth building

Slack the team with the customer and the order. Post the customer's name or email and the order that triggered it. Low effort, and it keeps a person aware without building anything more complex. This is the shipped "Repeat buyer worth a look" template in Ready-made workflow templates.

Tag the customer for manual review. Tag them in Shopify with something like repurchase-limit-reached, so anyone opening that customer later sees the flag without going through Automations history.

Email the account rep with full context. If accounts have assigned reps, send the customer, rule, window and quantity used. That is enough for the rep to decide between a legitimate high-volume buyer worth calling and a pattern worth watching.

Add to a segment for batch review. Rather than reacting one at a time, add the customer to a Shopify segment, or a tag that feeds one, and review the whole segment on a schedule.

Pair it with a counter reset. Once your team has reviewed a case and decided the customer is legitimate, a second workflow using Reset repurchase counter clears their allowance without anyone editing the rule.

Common mistakes

Expecting it on every order after the cap. It fires once per customer, per rule, per window, on the crossing order only.
Reading it as a blocked-order signal. Nothing was blocked. Wording a notification as though something failed will confuse whoever receives it.
Assuming guests can trigger it. They cannot. Repurchase tracking needs a signed-in customer, so there is always a real customer and order attached.

Frequently asked questions

Does this mean the customer's next order will be blocked?

Not by this trigger. It only reports that the cap was reached. Whether future orders are blocked is decided by the rule's own repurchase period, which runs independently of Automations.

Can I see which specific products the customer bought?

Not from the trigger itself. It gives you the order reference, which a Flow step that fetches the order can expand into line-item detail if you need it.

Is there a way to clear the flag once we have reviewed it?

Not automatically, but the Reset repurchase counter action does exactly this on demand, so a reviewed customer can have their allowance cleared without anyone touching the rule.

Why did I get one event when the customer placed three orders?

Because only one of those orders crossed the cap. The two before it were still inside the allowance and the ones after are already past it, so neither produces a new event within the same window.

Does the window reset on a fixed date or per customer?

It is a rolling window measured against each customer's own purchase history, so two customers who reached the cap a week apart also come out of it a week apart.

Best for: Anti-hoarding and reseller-detection workflows, and any store that wants a person in the loop before acting on a repeat high-volume buyer.

Applies to: Pro plan

Did this answer your question?

Still stuck?

Tell us what you are trying to set up and we will reply within 24 hours.

Contact support