Fulfillment, support and marketing all want to treat a first order differently from a customer's fifth — a first order might get a handwritten note or extra QA; a fifth might skip straight to your fastest fulfillment lane. Neither is possible if nothing on the order itself says which one it is.
Why Shopify doesn't tag this natively
Shopify tracks how many orders a customer has placed, and shows it on their profile — but the order itself carries no tag saying "this was their first" or "this was their fourth." Two common workarounds both fall short:
- A saved search or filtered view — useful for looking something up, but it's a query you run, not a fact stamped on the order that a fulfillment app, an export, or a staff member scanning tags can act on directly.
- A Shopify Flow workflow reading order count — Flow can check a customer's order count on an order-created trigger, but it has no simple way to also apply the inverse tag consistently, and a workflow that only ever adds never gives you a clean "was this a repeat customer" filter across your order history.
The fix: a rule that tags the order itself
An auto-tagging rule can read the customer's order count at the moment an order is placed and tag the order directly:
If this is the customer's first order → tag first-order.
Because the tag lands on the order — not just somewhere in a report — it's visible in the order list, filterable in a saved search, and readable by any downstream automation (including Shopify Flow itself, which can trigger off a tag it didn't apply).
Because it's a rule, you can build both directions:
- The inverse rule — "not the customer's first order" tags every repeat purchase, so your order list cleanly splits into two populations without a single order landing in neither.
- Combine with other conditions — a first order over a certain cart value, or a first order from a particular country, if you want the tag to only fire in specific circumstances.
- Catch up on recent orders — turning the rule on sweeps your recent order history the same way, not just orders placed from today onward, so a report built on this tag isn't starting from a blank slate.
Why catching up on history matters here specifically
This is one of the clearest cases where only tagging new orders isn't enough. If you install a tagging tool today and it only starts tagging from today, every report built on "first order" vs "returning" undercounts your returning-customer population until enough time passes for the tag to catch up naturally. A tool that sweeps your recent order history the day you turn it on gives you a useful picture immediately, rather than waiting months for it to catch up on its own.
Rules2Tag is being built to do exactly this — apply a rule going forward on every new order, and sweep it across your recent order history too, so a fact like "was this their first order" is useful from day one, not just from the day you installed it.