Auto-Tag First-Time vs Returning Customer Orders

No. Shopify tracks how many orders a customer has placed as a running total on their customer profile — you can see '1 order' or '12 orders' when you open a customer record — but that count lives on the CUSTOMER, not stamped onto each individual order. Looking at an order by itself gives you no way to tell whether it was their first or their twelfth without cross-referencing the customer profile separately, which is exactly the kind of manual lookup a tag is meant to remove. Nothing in Shopify's own admin applies a tag based on that count automatically — a merchant has to notice it, an app has to be built to read it, or a workflow has to be set up specifically to translate that number into something the order list, an export, or an email flow can actually filter by.

Generally, yes — Shopify still creates or matches a customer record behind a guest checkout, keyed off the email address used, so the running order count updates correctly even when nobody creates an account or signs in. That means 'first order' usually resolves the same way whether the buyer checked out as a guest or a logged-in customer. The edge case worth knowing about is email: if the same person checks out with a different email address next time — a personal address once, a work address later — Shopify has no way to know it's the same buyer, and their order count resets in effect, since it's matched by email rather than identity. That's a limitation of the underlying data, not of the rule itself. Before relying on a first-order tag for anything customer-facing, it's worth previewing the rule against a real guest checkout on your own store to confirm it behaves the way you expect.

Yes — the same underlying signal, how many orders this customer has placed in total, can gate a rule at any specific point, not just 'first' versus 'everything after'. Some stores deliberately avoid discounting the very first order at all, to protect margin or avoid training brand-new customers to expect a discount before they've even tried the product, and instead reward the SECOND order specifically to encourage a genuine repeat purchase. A rule can express that precisely — order count equals exactly 2 — so it fires once, on that one order, rather than matching 'more than one' and re-triggering on every order after the first. That precision is the difference between a welcome-back offer a customer sees once and a discount that quietly keeps firing on their fifth, tenth and twentieth order because the condition was written too loosely to notice it should have stopped.

No — and this is actually one of the simpler tags to reason about for exactly that reason. Whether a given order was a customer's first purchase is a fact fixed at the moment the order was created; it doesn't depend on anything that happens afterward, so once the tag is applied correctly it stays correct forever, with nothing to re-check or clean up. That's a meaningfully different shape from a tag describing the CUSTOMER's current status — something like 'new customer' as a badge on their profile — which does change as they place more orders and would need removing once they're no longer new. Order-level tags like this one are the easier half of tagging to get right precisely because they describe something that happened, not something that's currently true; a report built on this tag never needs re-verification months later the way a status tag would.