Use Shopify Flow to add order tags as a triage queue: pick a trigger that carries order data, add a condition that isolates the orders you actually need to review, then apply the Add order tags action. Staff filter the Orders list by that tag instead of receiving an alert for every event. Tags are case sensitive, and other apps can overwrite them, so verify each workflow after launch.
Why a review queue beats an alert
An alert asks someone to act now. A review queue asks someone to act when they next work the queue. For independent retailers and small ecommerce teams, the second model is usually more honest about capacity. You are not staffing a 24/7 fraud desk; you are trying to catch the handful of orders that need a human look before fulfilment.
Shopify Flow is the automation layer inside Shopify admin. A workflow has three parts: a trigger (the event that starts it), optional conditions (the filters that decide whether the workflow continues), and actions (what happens if it does). The Add order tags action adds a tag to the order that triggered the workflow. That is the whole mechanism. The design work is choosing which orders deserve a tag.
What does the Add order tags action actually do?
The action adds one or more tags to the order that triggered the workflow. Tags are case sensitive, so review and Review are different tags. You can enter tags one at a time, or comma-separate them; whitespace between commas is removed, so tag1, tag2, tag3 becomes three separate tags. The order ID is supplied by the trigger and cannot be changed in the action.
The action can be used in workflows that begin with triggers that contain order data, including Order created, Order paid, Order fulfilled, Order canceled, Order risk analyzed, Order transaction created, Fulfillment created, Fulfillment event created, Refund created, and Tender transaction created. If your trigger is not on that list, the action has no order to tag.
How do you design the trigger, condition and action logic?
Think in three sentences before you open Flow:
- Trigger: "Start when an order is created." (Or paid, or risk analyzed, depending on when you can actually judge the order.)
- Condition: "Continue only if this order matches the pattern I care about."
- Action: "Add the tag
review-queue."
The condition is where most noisy setups fail. A condition like "order total is greater than X" tags a lot of ordinary orders. A condition that combines two or three signals tags fewer, more meaningful ones. Shopify's own template library shows this pattern: the "Tag orders by payment gateway" template runs on Order created, uses a condition to check the payment gateway, and only then adds tags. The "Cancel and tag orders from deny-listed email addresses" template checks against a list of known bad emails and domains you supply before tagging or cancelling.
Example (hypothetical, illustrative figures only): a store decides that an order should enter the review queue if the billing country differs from the shipping country and the order total is above a threshold the owner sets. The workflow triggers on Order created, checks both conditions, and adds review-queue. The owner does not claim this catches all fraud; it simply routes a smaller set of orders to a human.
A reusable worksheet for your first workflow
Write these down before building anything:
| Field | Your answer |
|---|---|
| Trigger event | e.g. Order created |
| Condition 1 | e.g. shipping country is not X |
| Condition 2 | e.g. order total is above Y |
| Tag to add | e.g. review-queue |
| Who reviews | name or role |
| Review cadence | e.g. each morning |
| Removal rule | when the tag comes off |
The removal rule matters. A queue that never empties becomes another ignored alert. Decide now whether staff remove the tag manually after review, or whether a second workflow removes it later.
How do you verify the tag actually stuck?
Shopify's own documentation flags a common issue: Flow reports that it added a tag, but the tag is not visible in the admin. The stated reason is that an app or an admin user overwrote the tag. Many apps listen to the same events as Flow, such as Order created. Flow often finishes first, and then another app edits the order without accounting for the new tags.
The documented solutions are: check whether the app offers a Flow action you can call after Flow runs; if not, contact the app to ask how to avoid overwriting your tags; and if that fails, try inserting a Wait step in Flow to delay when tags are added.
A practical verification method: after launching, place or simulate a test order that meets your conditions, then open that order in the admin and confirm the tag is present. Repeat after any app installation or update. If the tag disappears, you have an overwrite problem, not a Flow problem.
What mistakes should you avoid?
- Tagging too broadly. If most orders get the tag, the queue is just the Orders list with extra steps.
- Ignoring case sensitivity.
Reviewandreviewwill not filter together. - Assuming the tag is permanent. Other apps can overwrite it; verify after changes.
- Skipping the removal rule. Decide how the tag comes off before you launch.
- Treating the tag as a decision. A tag routes an order to a human. It does not approve, cancel or refund anything by itself.
Where this fits for UK and US stores
This is operational logic, not tax or legal advice. A UK or US store can use the same trigger-condition-action pattern; what changes is the condition you choose, because your risk signals, payment mix and fulfilment promises differ. If you are still deciding whether Shopify is the right platform for this kind of automation, our comparison of WordPress or Shopify: Compare the Full Cost covers the budget side, and WooCommerce to Shopify: Is Migration Worth It? covers the migration trade-offs.
Follow-up questions
Can I add more than one tag in a single action?
Yes. You can enter tags one at a time, or separate them with commas. Whitespace between commas is removed, so tag1, tag2, tag3 becomes three separate tags. Remember that tags are case sensitive.
What if my trigger is not an order trigger?
The Add order tags action can be used in workflows that begin with triggers that contain order data, including Order created, Order paid, Order fulfilled, Order canceled, Order risk analyzed, Order transaction created, Fulfillment created, Fulfillment event created, Refund created, and Tender transaction created. If your trigger is not one of these, the action has no order to tag.
