What you configure
| Field | What it is |
|---|---|
| Customer | The customer whose count to clear |
| Rule ID | The exact ID of the repurchase-limited rule, from its edit page rather than its name |
See Finding a rule's ID for Shopify Flow.
Why it exists
A repurchase limit is a blunt instrument on purpose. Two units per customer per 30 days does not know that this particular customer is replacing a damaged unit, or that this account is a reseller you actually want buying more.
Until this action, the only ways to make an exception were to widen the rule for everybody or to tell the customer to wait. Both are worse than clearing one counter.
Four workflows worth building
Support resolves a legitimate dispute. A customer was stopped by a repurchase limit and has a good reason for the extra order. Trigger this action from whatever your support team already uses, a helpdesk macro, a form, a chat command, so the reset happens the moment support approves it, without needing someone with app access.
Approve a one-time wholesale exception. A wholesale account occasionally needs more than their limit allows. Reset their counter after a manual approval step rather than removing the rule for them, so the limit is back in force for their next order.
Close the loop on a flag. Pair it with the Repurchase limit reached trigger. Once your team reviews a flagged customer and decides the pattern is legitimate, resetting their counter resolves it.
Bulk-clear a reviewed segment. If flagged customers are collected into a segment for periodic review, run this action inside a step that iterates the segment, clearing everyone your team has already approved in one pass.
Common mistakes
- Using the rule's name. The field takes an ID.
- Expecting it to change the rule. It clears one customer's usage. The cap and the window are exactly as they were, and that customer starts accumulating again from zero.
- Forgetting it is per rule. A customer tracked under two repurchase rules keeps their usage on the one you did not target.
- Assuming the customer knows. Nothing is sent. If they should hear that the block is lifted, add that step to the workflow.