Tagging Subscription Orders in Shopify (And Why It Matters)

An order generated by a subscription renewal is an ordinary Shopify order. That is a feature — it works with your existing fulfilment, shipping and reporting — and it is a problem, because nothing distinguishes it until you make something distinguish it.

Tags are the mechanism.

What to tag

At minimum:

• subscription — the flag itself
• subscription-cycle-3 — which delivery this is
• plan-monthly-coffee — which plan generated it
• subscription-first — the first order in a subscription

Optionally, depending on your operation:

• prepaid — the order is against money already collected
• box-cohort-w1 — which ship cohort
• skip-recovered — this cycle followed a skip

What each one buys you

Cycle number is the most underused and the most valuable.

It lets you treat the first delivery differently — a welcome insert, extra QC, a different packing note. It lets you spot the churn cliff in fulfilment terms. And it lets support see instantly whether they are talking to a brand new subscriber or a loyal one, which changes the right response.

Plan identity lets shipping rules differ by plan. A prepaid annual subscriber might get free express; a monthly subscriber standard.

Prepaid flag matters for reporting: those orders are a cost against revenue already recognised, not new revenue. Reporting that counts them as revenue double-counts.

First-order flag drives your onboarding automation and lets you measure first-delivery experience separately, which is where most churn originates. Why.

Tag at creation

Tags must exist when the order is created, not be applied by a job that runs later.

Anything consuming tags — Shopify Flow, a 3PL integration, a shipping rule — evaluates the order as it arrives. An order that is untagged for ten minutes is an order those rules skipped, silently and permanently.

This is a reasonable question to ask a subscription app directly: are tags applied synchronously at order creation?

Downstream uses

Fulfilment routing. Send subscription orders to a different pick process or warehouse zone.

Shipping rules. Different service levels by plan.

Reporting. Filter subscription revenue from one-off revenue in Shopify’s own analytics, which otherwise blends them.

Support. The tag tells the agent the context before they ask.

Flow automations. “If cycle = 1, send the welcome sequence.” “If cycle = 12, send the anniversary offer.”

Keep the vocabulary stable

Tags become load-bearing. Renaming subscription to sub after six months breaks every rule, filter and saved report that referenced it — usually silently, because a rule matching nothing does not error.

Decide the scheme before launch, write it down, and treat changes as a migration rather than an edit. This is also the first thing to inventory when you switch subscription apps. Migration checklist.