# The Reset Repurchase Counter Action

> Source: https://primemoq.app/help/automations/action-reset-repurchase-counter
> Collection: Automations
> Updated: 2026-08-26

Clear one customer's tracked purchase count for one repurchase-limited rule, without editing the rule or making them wait out the window.

**Short answer.** Reset repurchase counter" clears a specific customer's cumulative purchase count for a specific repurchase-limited rule, giving them a fresh allowance immediately rather than waiting for the rule's rolling window to pass. It needs both a customer and a Rule ID, and it changes nothing about the rule's own cap or window.

## Key takeaways

- Scoped to one customer and one rule at a time.
- The rule's cap and window are untouched. Only that customer's usage returns to zero.
- It is silent. The customer is not notified unless your workflow tells them.
- A customer tracked by two repurchase rules needs two resets.

## Before you start

- A rule with a repurchase limit set.
- The Rule ID of that rule, copied from its edit page.

## 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](https://primemoq.app/help/automations/rule-id-for-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](https://primemoq.app/help/automations/trigger-repurchase-limit-reached).
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.

## FAQ

### Does this notify the customer that their limit was reset?

No. It is a silent change. Add your own email or message as a separate step in the workflow if the customer should know they can order again.

### Can I reset a counter for a customer who was never flagged?

Yes. The action works on any customer and rule pair, whether or not the Repurchase limit reached trigger has ever fired for them.

### Can I see a customer's current usage before deciding to reset it?

Not from this action. Check the rule's own reporting, or the quantity used figure carried by the Repurchase limit reached trigger event, before deciding.

### Does the reset apply retroactively to past orders?

It clears the tracked count, so past orders stop counting against that customer's allowance under this rule. The orders themselves are untouched.

### What happens if I reset the same customer twice?

Nothing harmful. The second reset finds a count already at zero and leaves it there, so a workflow that runs twice does not compound.

**Best for:** Support teams and account managers who need to clear a repurchase limit for one customer without editing the rule everyone else is on.

**Applies to:** Pro plan