Shopify Flow automations every D2C should set up

Shopify Flow is a free, Plus-only automation engine that runs your back-office rules for you — hold a high-risk order, tag a wholesale customer, alert staff when stock is low, promote a repeat buyer to VIP, route an order to the right warehouse. Every trigger fires server-side after an event, so it never touches your store speed. The recipes below are the ones I build first for D2C brands.

I am a senior Shopify developer in Delhi, and I set up and untangle Flow workflows for D2C brands on Plus in India, the US, UK, and UAE. This is the practical version — what to automate first, the exact trigger-condition-action shape, and where Flow stops and a developer or Functions should take over.

What is Shopify Flow, and do I need Plus?

Flow is Shopify's native workflow builder. You pick a trigger (an event like "order created"), add conditions (filters like "order total over ₹15,000"), and chain actions (tag the order, hold fulfillment, send an email, call an external system). It runs on Shopify's servers, so unlike a theme app it adds nothing to your storefront load — a real concern I cover in why your Shopify store is slow and app overhead and performance.

The catch: Flow is a Shopify Plus feature. On Basic, Shopify, or Advanced you cannot install it, and you fall back to third-party automation apps that cost extra and sit outside the platform. On Plus it is bundled free. Here is where that lands on plan pricing:

Always verify current numbers on shopify.com/in/pricing — plan prices move. If you are weighing the jump, when to upgrade to Shopify Plus and is Shopify Plus worth it at your revenue are the honest reads. Flow alone rarely justifies Plus, but it is one of several features (Functions, B2B, Markets, checkout customization) that together do.

Which Flow automation should I set up first?

If you build nothing else, build the fraud hold. It has the clearest ROI: it stops chargebacks and mistaken shipments before they cost you money. After that, order tagging, low-stock alerts, VIP tiers, and fulfillment routing — roughly in that order. Here is the priority list with what each one saves you:

The rest of this post walks each one as a concrete recipe.

How do I hold high-risk orders automatically?

This is the single most valuable Flow for most D2C brands. Shopify runs a risk assessment on every order; Flow can read it and act before anything ships.

Recipe — fraud hold and review:

• Trigger: Order created (or "Order risk analyzed" if you want to wait for the full assessment).
• Condition: Risk level is High. Optionally add: order total over ₹15,000, OR shipping address country differs from billing, OR first-time customer.
• Actions: Hold the order's fulfillment, add tag review-fraud, send an internal email or Slack message to your ops team.

Nothing ships until a human clears it. For a store doing cash on delivery — the norm across Indian D2C, which I unpack in Shopify Payments, COD, and GST — you can extend the same pattern: tag high-value COD orders for a confirmation call before dispatch, cutting return-to-origin losses on fake or impulse orders.

A word of caution I give every client: hold and review, do not auto-cancel. It is tempting to add a "cancel order" action on high risk, but Shopify's risk scoring is not perfect, and auto-cancelling turns a false positive into a lost genuine customer. Let a person make the cancel call. Flow's job is to surface the order, not to reject it.

How do I tag orders and customers automatically?

Tags are the connective tissue of a well-run Plus store. Almost every downstream automation — routing, reporting, segmentation, exports to your 3PL — keys off tags. Get tagging right and everything else gets easier.

Recipe — order tagging by attributes:

• Trigger: Order created.
• Conditions and actions (branching):
  • If order contains a subscription product → tag subscription.
  • If order total over ₹25,000 → tag high-value.
  • If discount code used → tag promo-<code>.
  • If shipping to a metro pin code → tag metro; else tag non-metro.

Recipe — customer tagging by behaviour:

• Trigger: Order paid.
• Condition: Customer's total orders equals 1 → tag customer first-purchase; if 3 or more → tag repeat.

These tags then power your email flows (Klaviyo and similar read Shopify tags), your reporting, and your fulfillment rules. The one rule that saves you pain: never let a tagging workflow trigger another tagging workflow that re-tags the same object — that is how you get infinite loops. Keep each tag written once, by one workflow.

How do I get alerted before I run out of stock?

Stockouts are silent revenue leaks — you only notice when a bestseller goes to "sold out" and the sales stop. Flow closes that gap.

Recipe — low-stock alert:

• Trigger: Inventory quantity changed.
• Condition: Available quantity is less than or equal to your reorder point (say 20 units), AND the product is active/published.
• Actions: Send an email to your inventory owner, add product tag reorder-now, optionally post to a purchasing channel.

For a fast-moving category — beauty, food, apparel — set the threshold high enough to cover your supplier lead time. If your reorder takes 10 days and you sell 5 units a day, alert at 50, not 20. You can run a second, tighter workflow at a critical threshold (say 5 units) that also hides the product from a "back in stock soon" collection or flips it to a pre-order state, so you never oversell.

This pairs well with the demand spikes I describe in Diwali and festive readiness — during a sale window, a low-stock Flow is the difference between reordering on time and going dark on your best SKUs mid-campaign.

How do I build a VIP or loyalty tier with Flow?

You do not need a loyalty app to identify your best customers — Flow can maintain the segment for you, and your email and on-site tools can act on the tag.

Recipe — VIP tier tagging:

• Trigger: Order paid.
• Condition: Customer's lifetime amount spent is over ₹50,000 (or total orders over 5).
• Actions: Add customer tag vip, send an internal note, optionally trigger a "welcome to VIP" email via your ESP.

Now your storefront and marketing can treat vip customers differently: early access to drops, free shipping thresholds, a hidden VIP collection. On Plus you can go further and combine this with a Function that gives vip-tagged customers an automatic checkout discount — that is the Flow-plus-Functions pattern I explain below and in Shopify Functions examples. Flow maintains the segment; Functions rewards it at checkout.

A subtle design point: decide whether VIP is sticky or rolling. Sticky (once VIP, always VIP) is one workflow. Rolling (VIP only if they spent ₹50,000 in the last 12 months) needs a companion workflow to remove the tag when they lapse — otherwise your VIP list only ever grows and stops meaning anything.

How do I route fulfillment to the right warehouse?

Multi-location brands lose money on split shipments and wrong-warehouse dispatch. Flow can tag orders so your fulfillment system — or your 3PL — routes them correctly.

Recipe — fulfillment routing by region:

• Trigger: Order created (or paid).
• Conditions and actions:
  • If shipping state is in North India → tag wh-delhi.
  • If shipping state is in South India → tag wh-bangalore.
  • If order is international → tag wh-export and hold for a compliance check.

Your warehouse or 3PL then listens for these tags. In India, Shiprocket and Delhivery fulfillment usually sit downstream of exactly this kind of tag — so a clean routing workflow in Flow becomes the backbone of your dispatch logic, not an afterthought. For international orders sold through Shopify Markets, routing plus a hold-for-compliance step keeps customs paperwork from becoming a fire drill.

When routing needs to reach an external system, Flow's Send HTTP request action posts order data to your warehouse's API or a 3PL webhook. That is usually the point where you want a developer to build and test the payload — a mis-mapped field here means orders silently going to the wrong place.

Flow vs Functions: which do I actually need?

These get confused constantly, so the clean split:

Flow is your operations automation layer. Functions is your checkout logic layer. A serious Plus store runs both: Flow tags a customer vip, a Function reads that tag and applies a VIP discount at checkout; Flow holds a fraud order, a Function blocks an invalid cart before it becomes an order. If you are choosing between platforms first, that Plus-only power is part of the calculus in Shopify vs custom-coded store cost and is Shopify worth it in India.

When should I bring in a developer?

Flow's visual builder genuinely handles the simple recipes above — you can and should build your first fraud hold and tagging workflows yourself. Bring in help when:

• Workflows branch heavily or share tags, and you need someone to map dependencies so they do not loop or race.
• You need Send HTTP request to talk to a 3PL, ERP, or custom endpoint — payload mapping and error handling are where silent failures live.
• Flow and Functions must work together (VIP tag → checkout discount, fraud hold → cart validation).
• You are on a B2B/wholesale setup — Flow rules for Shopify Plus B2B and wholesale get complex fast around company-level tagging and approval routing.

For scope, a focused Flow-and-Functions engagement on an existing Plus store runs about ₹1,50,000–₹4,00,000, and a full Plus theme build with Flow and Functions baked in is ₹5,00,000–₹8,00,000 (roughly $1,800–$9,500 at ~₹83/$). Those are the same ranges on my Shopify Plus developer page — no agency layer, you work with the person writing the code.

What's next

If you are on Plus (or deciding whether to be) and want your back office running itself — fraud holds, tagging, inventory alerts, VIP tiers, and fulfillment routing built to fit how your store actually operates — the Shopify Plus developer page lays out how I work, with fixed pricing and named case studies. Tell me your platform, your order volume, and the manual work eating your team's day at /start, and I will map which Flow and Functions recipes will pay off first.

Related reads

• Shopify Functions examples — the checkout-logic layer that pairs with Flow.
• When to upgrade to Shopify Plus — whether Flow and the rest justify the jump.
• Shopify Plus B2B and wholesale — where Flow tagging and routing get genuinely complex.

Sources

• Shopify — Shopify Flow
• Shopify Help Center — Shopify Flow
• Shopify — Plus plan and pricing