Shopify Flow recipes for flagged orders

Address Verifier writes two plain order tags, and Shopify Flow can act on them. Two recipes cover what most stores want: know about flagged orders, and stop them from shipping before someone looks.

The one quirk to understand first

Flow has no “order tag added” trigger (it exists for customer tags, not order tags). So you can’t fire a workflow directly off address-unverified appearing. The reliable pattern starts from Order created, waits briefly, then checks the tags:

Order created → Wait → Get order data → Condition on tags → Action

The Wait step matters twice over. Our tag lands seconds after the order is created, when the thank-you page runs verification, so a workflow that checks tags instantly can race it and see nothing. And many flagged orders fix themselves within minutes, because the buyer accepts the suggested address while still on the thank-you page, which swaps the tag to address-corrected and means there’s nothing to alert about. A 15–30 minute wait skips both problems.

One Flow gotcha: data fetched before a Wait step isn’t available after it. Always re-read the order with Get order data after the wait, and run your condition on that.

Recipe 1: an internal alert for flagged orders

For stores that just want a heads-up without watching a saved view.

1. Trigger: Order created.
2. Wait: 30 minutes.
3. Get order data for the triggering order.
4. Condition: the order’s tags include address-unverified.
5. Action: Send internal email, to you or your ops inbox, with the order number and shipping address in the body.

Orders the buyer already fixed never match the condition, so the alert only fires for ones that still need a human.

Recipe 2: hold fulfillment until the address is resolved

For stores where fulfillment is fast and automated. A 3PL that imports orders within minutes can ship to the bad address before the buyer ever sees the fix prompt; a hold removes the race.

1. Trigger: Order created.
2. Wait: 30 minutes.
3. Get order data for the triggering order.
4. Condition: tags include address-unverified.
5. Action: Hold fulfillment order, with a reason like “Address under review”.

Two things make the hold work well with the app. First, a held order is exactly the state our prompt expects: the buyer can still fix the address from their order status page, and the correction lands on the held order. Second, releasing is your decision point. Add a second Wait (say, 2 days) followed by another Get order data: if the tags now include address-corrected, use Release fulfillment order holds; if the order still says address-unverified, route it to a human, because at that point the buyer isn’t going to fix it for you.

Adjusting the recipes

Both conditions can be inverted or combined: hold only orders above a value threshold, alert only on international destinations, add the flagged orders to a spreadsheet instead of an email. The tags are ordinary order data inside Flow, so anything Flow can express works. If you build something that other merchants would want, email [email protected] and we’ll add it here.