Shopify App

Order Tag Rules — tag every order the moment it lands

Write conditions on payment method, order value, city, SKU, customer history, discount code, risk level or courier. Tags apply on order creation and on status change, then drive Flow automations, fulfilment routing and reporting.

Order Tag Rules builder showing a condition set for high-value cash on delivery orders in secondary cities

What Order Tag Rules does

Order tags are the cheapest routing mechanism Shopify gives you. Flow triggers read them, fulfilment teams filter by them, reports group by them. Doing it by hand does not survive a sale weekend. Order Tag Rules turns your operating logic into rules: a high-value cash on delivery order to an upcountry city gets tagged for a verification call, a repeat prepaid buyer in Karachi gets tagged for same-day dispatch. Rules run automatically and can be tested against past orders first.

What you get

Multi-condition rules

Combine payment method, total, city, SKU, quantity, discount code, risk level, courier and tags already present with and or logic.

Customer history conditions

Match on lifetime order count, previous refusals, returned parcels or total spend, so first-time COD buyers are treated differently from regulars.

Creation and status triggers

Rules fire when an order is created, and again when payment, fulfilment or cancellation status changes, so tags reflect the current state.

Rule tester

Run a draft rule against historic orders and see exactly which ones would have matched before you let it write anything live.

Flow and routing handoff

Tags become triggers for Shopify Flow, filters for your fulfilment queue, and conditions for which courier an order is booked with.

Rule order and conflicts

Set priority so overlapping rules resolve predictably, with an execution log showing which rule tagged which order and when.

How it works

  1. 1

    Define a rule: pick the conditions, the tags to apply or remove, and when the rule should fire.

  2. 2

    Run the tester against past orders to confirm the match set is what you expected before going live.

  3. 3

    Activate. New orders are tagged at creation, and existing ones retagged as their status changes.

  4. 4

    Point Flow automations, fulfilment filters and reports at the tags, and review the execution log weekly.

Why merchants run it

Risky COD caught early

High-value cash orders from first-time buyers get flagged before packing, so verification happens while cancelling still costs nothing.

Fulfilment routed automatically

Tags decide which courier, which warehouse and which priority queue, removing the daily manual sort your dispatch team currently does.

Reporting that matches the business

Group revenue by payment type, city band or discount campaign because the tags were applied consistently from day one.

Rules survive staff turnover

Operating knowledge sits in rules rather than in one person's habits, so quality does not drop when that person is on leave.

Pricing

Starter

[PRICE] per month. A limited number of active rules, order creation triggers and basic conditions on payment, value and city.

Growth

[PRICE] per month. Adds status-change triggers, customer history conditions, the rule tester and priority ordering.

Scale

[PRICE] per month. Unlimited rules, multi-store, retroactive tagging of historic orders, execution log export and API access.

Frequently asked questions

How is this different from Tag Toolkit?

Tag Toolkit is bulk manual cleanup across products, customers and orders: merging duplicates, renaming, stripping tags in one pass. Order Tag Rules is automatic and forward-looking, applying tags to orders as conditions are met. Most stores clean up first, then automate.

Can it tag orders that already exist?

Yes, on the higher tier. A rule can be run retroactively across a date range so historic orders carry the same tags as new ones, which matters when you want a report that goes back further than the day you installed the app.

Why not just use Shopify Flow?

Flow can tag orders, and many merchants start there. This app adds a condition set built around local operations, a tester against past orders, priority handling between overlapping rules and an execution log. It writes tags that Flow then consumes rather than replacing Flow.

Can rules use courier or city groupings?

Yes. Cities can be grouped into zones, so one rule covers all upcountry destinations instead of listing every town. Courier conditions let you tag differently for TCS, Leopards, M&P, PostEx or Trax bookings.

Put your order handling rules into software

We will map your current manual sorting into rules and test them against your order history.

Talk to our team