Shopify Flow for DTC Brands: The 8 Automations Every Store Should Have Running

Trigger: Order created or customer updated

This is the highest-ROI single workflow for most DTC brands and the one almost nobody has set up correctly. The workflow checks a customer's cumulative spend and order count after every purchase, then assigns them to a tier: Bronze, Silver, Gold, or Platinum. Those tags flow into Klaviyo and drive segmented campaigns, early access drops, and exclusive offers.

The data on timing is stark. Customers who receive VIP recognition within 24 hours of qualifying show 30 to 40% higher retention rates than those tagged manually weeks later, or never. Most brands discover they have Gold-tier customers who have never received a single acknowledgement because nobody noticed they qualified. Flow fixes this permanently.

Set your thresholds based on your own AOV and order frequency. A common starting point: Bronze at 2 orders or £100 lifetime spend, Silver at 4 orders or £250, Gold at 7 orders or £500, Platinum at 12 orders or £1,000. These tiers then drive your retention strategy in Klaviyo, not the other way around.

Trigger: Scheduled time-based check on last order date

This is the most direct revenue recovery workflow available to any DTC brand. The logic: if a customer has not placed an order in 90 days and does not already have a 'win-back-90' tag, apply the tag and signal Klaviyo to start the win-back sequence. At 180 days, apply 'win-back-180' and fire the deeper offer, typically a 20% discount or a free gift threshold.

The reason to use two triggers rather than one is that your messaging should change. The 90-day reach is relationship-driven. The 180-day reach is offer-driven. Running both, with the 90-day one acting as a soft re-engagement, protects your offer economics. You do not discount customers who just needed a nudge.

Once a customer repurchases, a separate flow removes both tags. They start the cycle fresh. This workflow running silently in the background is the single most consistent source of recovered revenue I have seen across every brand I have worked with.

Trigger: Order created with risk level medium or high

Platform-level risk scores are a starting point, not a solution. Shopify Flow lets you build layered fraud logic that catches patterns a single-order score misses. The two most useful checks are velocity (multiple orders from the same IP or card in a short window) and mismatch patterns (B2B orders where the billing address does not match the shipping address, which is a common commercial card fraud signal).

The workflow auto-holds the order for manual review rather than auto-cancelling, which matters because legitimate high-value orders can trigger false positives. Your ops team gets a notification with the specific flag that triggered the hold, so they can resolve it in 30 seconds rather than rebuilding context from scratch.

Fraud detection workflows reduce chargebacks by 40 to 60% in most implementations. For a brand processing 500 orders per month at a 1% fraud rate, that is typically £12,000 to £24,000 per year in recovered losses. The workflow takes 25 minutes to build.

Trigger: Refund request or return initiated

Manual refund processing is one of the highest-cost, lowest-value tasks in DTC operations. Flow can auto-approve refunds that meet all three of the following conditions: the order is under £150, the customer has 3 or more previous orders with no refund history in the past 180 days, and confirmed delivery was more than 7 days ago.

This pattern approves 60 to 70% of legitimate refund requests instantly, without anyone touching them. The remaining 30 to 40% that do not pass the conditions go to your team with a clear flag on what failed and why. Your support team stops processing routine approvals and starts focusing on edge cases where human judgment actually matters.

Customers who receive an instant refund approval spend 22% more in the following 90 days than those who wait 3 to 5 days for manual processing. The trust signal from instant resolution is a retention lever, not just an efficiency one.

Trigger: Order created or fulfilled

This workflow reads what a customer bought and applies a product-category tag that Klaviyo can act on. A customer who bought a starter kit gets tagged 'starter-kit-buyer'. A customer who bought a refill gets tagged 'refill-buyer'. A customer whose order contained a specific hero SKU gets a flag that determines which post-purchase sequence they receive.

Without this, most brands send the same post-purchase flow to every customer regardless of what they bought. With it, your Klaviyo flows become genuinely relevant: starter-kit buyers receive education about the product, refill buyers receive replenishment reminders timed to their consumption cycle, and bundle buyers receive cross-category recommendations.

This is the infrastructure that makes personalisation real rather than theoretical. The data is already in your orders. Flow just organises it into a format your email platform can act on.

Trigger: Inventory quantity drops below threshold

Stockouts are one of the most expensive and avoidable events in DTC. A customer who hits an out-of-stock page does not wait. They leave, often to a competitor. Flow can notify your ops or buying team the moment inventory on any SKU drops below a defined threshold, before it reaches zero.

The more useful version of this workflow adds a condition: if the SKU is in an active campaign or generating above-average daily orders, the threshold triggers earlier and the notification goes to a wider distribution list. A product moving at 5x its normal rate needs a different response than one selling at baseline.

A secondary workflow pairs with this one: when a product goes out of stock, Flow automatically adds it to a restock notification list and tags any customers who viewed the product in the last 30 days (via a Klaviyo back-in-stock trigger). These customers convert at 21% when the product returns, compared to 2 to 3% for cold traffic.

Trigger: Order created with unverified or flagged address

Auto-fulfilment is efficient until it ships 200 orders to malformed addresses and your re-delivery and refund costs wipe out a week of margin. Flow can intercept orders before they hit fulfilment if the shipping address fails basic validation: missing apartment numbers, known PO box restrictions for your carrier, international format issues, or addresses flagged by your 3PL.

The hold is automatic. Your ops team gets a notification and a link directly to the order. They correct the address or contact the customer in minutes. The order then releases to fulfilment. No returns processing, no re-delivery costs, no customer service thread about a missing parcel.

This workflow pays for itself on the first week it catches a batch of address errors. The labour cost of fixing an address before shipping is trivial. The cost of a failed delivery, customer service escalation, and replacement shipment is typically 3 to 5x the original order value when all costs are included.

Trigger: Customer reaches Platinum tier or 5th order

Every DTC brand has customers who account for a disproportionate share of lifetime revenue. Most brands treat them identically to everyone else because there is no system telling the operator when a customer crosses into that tier. Flow fixes this by triggering an internal notification the moment a customer hits a defined threshold: 5 orders, £1,000 lifetime spend, or a single order above £300.

The notification goes to the founder or a senior team member. Not to a generic support inbox. The goal is a personal email or direct message that the customer did not expect and would not receive anywhere else. A handwritten thank you. An early preview of a new product. An invitation to a tasting or event.

The brands with the highest retention rates are not running the most sophisticated automations. They are using automation to identify the moments where a human touch has the most leverage, and then making that touch happen consistently rather than accidentally.