Automatically block a buyer after a chargeback with Shopify Flow
Yes, in two steps. Shopify Flow's Dispute created trigger fires when a chargeback or inquiry is opened (Shopify Payments stores only), and Refund created fires on refunds. Flow itself runs after orders exist, so it cannot block the next checkout; but its action can add the buyer's email and phone to a checkout blocklist such as OrderGate's, whose rules run inside checkout validation and stop that buyer before their next order exists.
Why Flow alone is not enough
Flow is the natural place to react to a chargeback, and the usual advice is to tag the customer or cancel their next order. Both act after the next order already exists: the payment has been taken and the fee charged. A Shopify staff member has said directly that Flow does not run in checkout.
What Flow is good at is noticing the event. The missing half is something that remembers the buyer and refuses them at the next checkout.
The workflow
- Trigger: Dispute created. It starts when a chargeback or an inquiry is opened on an order, and it is only available to stores on Shopify Payments.
- Condition: dispute type is chargeback, if you want to leave inquiries alone. Shopify notes that both open the trigger, and an inquiry does not pull funds.
- Action: Add to OrderGate blocklist. Map the order's email to Email address and the order's phone to Phone number; put something like "chargeback" in Reason so the rule's note says why it exists.
- Not on Shopify Payments, or the problem is serial returns rather than chargebacks: use Refund created as the trigger instead, with a condition that fits your store so a single ordinary return does not block anyone.
What the action does
Each run adds up to two enabled rules: one for the exact email address and one for the phone number. Empty fields are skipped, and a number or address already on the list is not added twice, so a re-delivered run changes nothing.
If a value cannot become a rule, for example a phone number with too few digits, the run is refused with a reason you can read in Flow's run log, and nothing is half-applied.
Limits to know before relying on it
- The rules only block when the store is in enforce mode. In log-only mode they are recorded and reported, not enforced.
- Each chargeback can add two rules. On OrderGate's Free plan, which runs five rules at a time, the list fills quickly; once it is full the Flow run is refused with that reason in the run log.
- An exact-email rule stops that address only. A buyer who changes email is still caught by the phone rule, as long as the phone number is required at checkout.
- Chargebacks opened long after the order still trigger Dispute created, which is why it is more reliable than templates that wait a fixed number of days after the order and then check.