Flow Wait Steps or a Lifecycle Tool for a 90-Day Win-Back?
Long-running Flow sequences are a BUY at a lifecycle platform once a journey crosses Shopify's ceiling. A workflow must have 40 or fewer wait steps, and total waiting across all of them can't exceed 90 days. Flow covers shorter operational sequences free on every plan from Basic upward. Omnisend's Standard tier starts at $16/month and Klaviyo's email tier at $20/month (verified Sep 2026).
Your profile — see how the verdict shifts
- Confidence
- High — Read Shopify's Flow limits reference: workflows must have 40 or fewer wait steps, the total time waited across all wait steps can't exceed 90 days, every workflow section has a combined upper execution limit of 36 hours, a store is capped at 1,000 workflows, and Flow warns above 10 active workflows using the same trigger (verified Sep 2026). That page now canonicalizes into the Flow troubleshooting article, and every figure survived the merge. Read Shopify's Flow overview: Flow is a free app on the Basic, Grow, Advanced and Plus plans. Read the monitoring page: workflow runs are stored for 14 days after a run completes, then removed. Fetched three App Store listings: Klaviyo at 4.7★ across 3,264 reviews, Omnisend at 4.8★ across 2,965 reviews, and MESA at 5.0★ across 153 reviews, with plan prices copied from each listing. A 90-day win-back therefore consumes Flow's entire waiting budget in one workflow, which is the arithmetic behind the verdict.
- Reference scenario
- $20M–$200M GMV · Shopify Plus · an ops team building automations in Flow · 20–60 live workflows · a lifecycle program with waits measured in weeks, not hours
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Operational waits under 7 days | WAIT | A fraud hold, a review request, a fulfillment nudge. Two or three wait steps and a few days of total waiting sit nowhere near the 40-step or 90-day ceilings. |
| Lifecycle sequences inside 40 steps and 90 days | CUSTOMIZE | Flow can carry a 60-day onboarding or reorder nudge, but design it knowing the whole budget is spent. Track the running total of waits per workflow before you add another branch. |
| Win-back and reactivation past 90 days | BUY | A 90-day win-back consumes Flow's entire waiting budget in a single workflow, leaving no room for the follow-up. A lifecycle platform prices this at $16–$20/month to start (verified Sep 2026). |
| Full lifecycle marketing across email and SMS | BUY | Segmentation, send-time logic, deliverability and SMS credits are a product category, not a workflow. Flow was never the cheaper path here, only the one already installed. |
What Long-Running Flow Sequences Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Retention & LTV | High | A win-back sequence reaches lapsed customers at the point their repurchase probability is still recoverable, which is the whole reason the waits are measured in months. |
| Revenue — indirect | High | Reactivation revenue arrives weeks after the trigger event, so a sequence that silently stops at Flow's ceiling costs sales nobody attributes to the failure. |
| Operational efficiency | Medium | Long operational holds, such as staged supplier follow-ups, run unattended instead of sitting on someone's calendar reminder. |
| Data & insight | Medium | Stage state written to customer metafields stays queryable in Shopify long after Flow removes the run history at 14 days. |
Spend ceiling: Spend on the journey, not on the engine. A lifecycle platform at $16–$20/month to start (verified Sep 2026) replaces a five-figure orchestrator for anything that sends messages; reserve build budget for sequences whose every step writes Shopify records.
What buying enables (top apps)
- + Journeys measured in months rather than inside a 90-day waiting budget
- + Segmentation, send-time logic and deliverability that Flow was never built to provide
- + Free tiers to test the journey first: Omnisend up to 250 contacts, Klaviyo up to 250 email contacts (verified Sep 2026)
- + Reporting on journey performance that survives well past Flow's 14-day run retention
What building additionally unlocks
- + No waiting ceiling at all, because cohort state replaces open wait steps entirely
- + Every stage transition written to Shopify data your team can query and join later
- + A run log you keep as long as you want, rather than the 14 days Flow retains
- + Operational stages that move records and inventory, which a marketing platform will not touch
Find Your Verdict in 3 Questions
Does the sequence need more than 90 days of total waiting or more than 40 wait steps?
Yes: Go to question 2.
No: Your verdict: WAIT — Flow carries it free on every plan from Basic upward, with no second subscription.
Do the steps send messages to customers, rather than write Shopify records?
Yes: Your verdict: BUY — a lifecycle platform starts at $16–$20/month (verified Sep 2026) and brings segmentation Flow never had.
No: Go to question 3.
Does every stage write to Shopify data your team queries later?
Yes: Your verdict: BUILD — hold stage state on customer metafields and sweep the cohort daily instead of chaining 40 waits.
No: Your verdict: BUY — rent the journey engine and keep Flow for the operational steps around it.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A lifecycle platform installs and imports contacts in days; a custom orchestrator runs an estimated 5–10 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | Lifecycle platforms price on contacts and sends, so the bill grows with the list; Flow itself stays free on every plan from Basic upward. | ||
| Maintenance & upgrades | Vendor-maintained journeys versus your own state machine, which someone has to own when a cohort gets stuck mid-sequence. | ||
| Switching & exit | Journey logic in a vendor canvas does not export; sequence state held on customer metafields moves with the store. | ||
| Risk | |||
| Vendor risk | Klaviyo and Omnisend are among the most reviewed apps on the store, at 3,264 and 2,965 reviews; category churn risk is low. | ||
| Security & compliance surface | A lifecycle platform holds customer contact data and consent state; a Flow-only sequence keeps the data inside Shopify. | ||
| Platform-deprecation exposure | Flow's wait ceilings are documented limits that can move; a design pinned to exactly 90 days has no headroom if they tighten. | ||
| Value | |||
| Fit to requirement | Multi-month journeys with branching, holdouts and send-time logic are what a lifecycle platform is built to express. | ||
| Time to market | A win-back journey ships in a week on a platform; the orchestrator takes a month or more. | ||
| Performance & scale | Flow's 1,000-workflow cap and its warning above 10 active workflows on one trigger bite before a lifecycle platform's limits do. | ||
| Data ownership & AI-readiness | Sequence state on customer metafields stays queryable in Shopify; journey membership inside a vendor canvas is exportable only as reports. | ||
| Focus & opportunity cost | Rebuilding a mature marketing-automation category is the clearest example of work you should rent. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify Flow | Native — Per july 2026 research. Shopify's own automation layer — the WAIT option to exhaust first | Free at entry volumes; scales with volume (verified Sep 2026) | Operational sequences that finish well inside 90 days of total waiting |
| Klaviyo: Email Marketing & SMS | Live — 4.7★, 3,264 reviews. Journey logic, segmentation and send-time control live in Klaviyo's own canvas, not in Flow's editor, so ops staff work in two tools. Contact-based pricing means the bill tracks list growth rather than message volume. | Free forever for up to 250 email contacts and 150 SMS/MMS credits; SMS from $15/month for up to 1,250 credits with carrier fees included; Email from $20/month for 251–500 contacts, scaling with the list (verified Sep 2026) | Multi-month win-back, reactivation and post-purchase journeys with real segmentation |
| Omnisend Email Marketing & SMS | Live — 4.8★, 2,965 reviews. Pre-built automations on the free tier make it the cheapest way to test whether a journey belongs outside Flow. Starting prices cover a contact count and rise as the list grows, so model the list you expect in a year. | Free to install for up to 250 contacts and 500 emails/month; Standard from $16/month for up to 500 contacts with 6,000 emails/month; Pro from $59/month for up to 2,500 contacts with SMS from $0.007/message (verified Sep 2026) | Testing a long journey outside Flow before committing to a contact-priced contract |
| MESA: Workflow Automation | Live — 5.0★, 153 reviews; 7-day trial on all paid plans. A multi-step automation platform that reaches further across your stack than Flow's own actions. Useful for orchestrating a bulk job's surrounding steps, though it is an automation tool rather than a bulk-editing one, so it does not remove the need for a real bulk lane. | Basic $12/month; Flex $29/month; Pro $99/month; Unlimited $299/month (verified Sep 2026) | Long operational sequences that drive records and integrations rather than emails |
| Custom cohort orchestrator | Build lane — Sequence state written to customer metafields, re-evaluated daily by a Scheduled time trigger rather than held open in 40 chained waits. Removes the 90-day ceiling entirely and keeps every record inside Shopify. Justified only when the sequence drives Shopify data, not messages. | $15,000–$45,000 one-time plus roughly 15–20% a year in upkeep (Deploi estimate, illustrative) | Multi-month operational programs whose every step writes to Shopify records |
The Build Path
- State on the customer record, not in open waits: Write the stage and the next-action date to customer metafields, then let a daily Scheduled time trigger pick up whoever is due. Flow's Scheduled time trigger runs at most once every 10 minutes and supports repeating intervals up to one year (verified Sep 2026), which is more than a daily sweep needs.
- Short workflows chained by state, not by waiting: Each workflow does one stage and exits, so no single workflow spends the 90-day budget or approaches 40 wait steps. Watch the warning Flow raises above 10 active workflows using the same trigger, because a daily sweep is a shared trigger by design.
- Your own run history: Flow keeps workflow runs for 14 days, then removes them. A multi-month program needs its own log, written to a warehouse or an external store at each stage transition, or nobody can answer why a customer skipped step four in March.
- Batch limits in the sweep: Get data actions run on lists up to 100 items long (verified Sep 2026), so a daily cohort sweep pages through segments in chunks rather than pulling one large list. Size the batch before the program launches, not after the first backlog.
- Effort band
- $15,000–$45,000 build — Deploi estimate (illustrative). A single-stage sweep with metafield state lands in the $10–25K contact-form band; a branching multi-stage program with its own run log and reporting lands in the $25–75K band
- Typical timeline
- 5–10 weeks (Deploi estimate, illustrative): about two weeks for the state model and the sweep, the rest for stage logic, backfill and the run log
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $2,200–$9,000/yr (Deploi estimate, illustrative) for stage-logic changes, Admin API version bumps and keeping the run log queryable. Flow itself adds no subscription line.
- What you own — and what you take on
- You own: the stage model, the cohort state on customer metafields, the run log and every rule that moves someone forward. You take on: stuck-cohort triage, backfilling customers who entered mid-program, and the reporting a lifecycle platform would have handed you.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $4,000–$12,000 (journey design and migration) | $15,000–$45,000 |
| Years 1–3 (recurring) | $10,800–$36,000 (contact-tier subscription) | $6,600–$27,000 (maintenance) |
| 3-year total | ≈$14,800–$48,000 | ≈$21,600–$72,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy path: a lifecycle platform on a mid-size contact tier, modeled above the published entry prices of $16/month and $20/month (verified Sep 2026) because contact-based pricing rises with the list.
- † Build path: a metafield state model, a daily scheduled sweep, three stages and an external run log; three-year horizon; message sending excluded from the build lane.
What the Sticker Price Hides
On the buy path
- — Contact-based pricing rises as the list grows, so the entry tier prices the list you have, not the one you're building
- — Journey logic lives in a second editor, which means two places to look when someone asks why a customer got that email
- — SMS credits and carrier fees are metered separately from the contact tier
- — Migrating a journey off the platform means rebuilding it by hand, since canvas logic doesn't export
On the build path
- — Flow's 14-day run history means a multi-month program is undebuggable without your own log
- — The warning above 10 active workflows on one trigger arrives quickly once a daily sweep is the pattern
- — Get data actions cap at 100-item lists, so cohort sweeps need paging from day one
- — Roughly $2,200–$9,000/yr in upkeep (Deploi estimate, illustrative) that no invoice makes visible
What Merchants Say
Ops leads describe hitting the wait ceiling late: the workflow builds fine, then Flow refuses the last step because the earlier waits already spent the 90 days.
Automation-app reviews cluster on visibility over long horizons: a sequence that spans months leaves no trace to inspect once the run history rolls off.
If You Change Your Mind Later
If you bought and outgrow it
Journey logic drawn on a vendor canvas leaves as a screenshot, not as configuration, so budget a rebuild if you switch platforms. Export contacts, consent state and engagement history while the account is live, because consent records are the part that is genuinely painful to reconstruct.
If you built and want out
Nothing is stranded: stage state on customer metafields stays queryable in Shopify, and the run log is already yours. Moving to a lifecycle platform later means importing customers with their stage already set, which is a far easier migration than the reverse direction.
When This Answer Changes
We're watching for:
- ▸ Any change to Flow's 40-wait-step or 90-day total-waiting limits (both current as of September 2026)
- ▸ Flow run retention moving beyond 14 days, which is what makes long programs hard to audit
- ▸ Lifecycle platforms shifting away from contact-based pricing, which is the main driver of the three-year buy total
Verdict change log:
No changes since first publication (September 2026).
Common Questions
How long can a Shopify Flow workflow wait?
Shopify caps total waiting at 90 days across all wait steps in a single workflow, and a workflow must have 40 or fewer wait steps. A 90-day win-back therefore spends the entire budget in one sequence, with nothing left for a follow-up nudge. Every workflow section also carries a combined upper execution limit of 36 hours.
Can I chain workflows to get past Flow's 90-day limit?
Yes, by handing off through a customer tag or metafield instead of a wait step, so each workflow starts fresh with its own 90-day budget. Two costs come with the pattern: Flow warns above 10 active workflows using the same trigger, and run history is kept only 14 days, so a six-month chain leaves no trail to debug.
Should a 90-day win-back live in Flow or in a lifecycle platform?
A lifecycle platform, because the sequence consumes Flow's whole 90-day waiting budget before the first follow-up. Omnisend starts at $16/month and Klaviyo's email tier at $20/month (verified Sep 2026), which buys segmentation, send-time control and deliverability that Flow never offered. Keep operational waits under a week inside Flow, where they cost nothing.
Your Next Steps
If you're going with BUY(matches your selected profile)
- Add up the total waiting in the sequence you want and compare it against the 90-day budget
- Count the wait steps against the 40-step limit before you design the branches
- Trial a free tier first: Omnisend is free to install up to 250 contacts (verified Sep 2026)
- Model the contact tier you expect in twelve months, not the one you have today
- Keep the operational steps in Flow and let the platform own only the customer-facing journey
If you're going with CUSTOMIZE
- Split the journey into stages, each its own short workflow, handed off by tag or metafield
- Write the stage and next-action date to customer metafields so no workflow holds an open wait
- Drive the sweep from a Scheduled time trigger, which runs at most once every 10 minutes
- Page cohort queries in chunks, since Get data actions run on lists up to 100 items
- Log every stage transition outside Shopify, because Flow removes run history after 14 days
Official Docs & Sources
- Flow limits and troubleshooting (wait steps, waiting total, workflow caps) — Shopify Help Center
- Shopify Flow plan availability — Shopify Help Center
- Scheduled time trigger — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Flow Loops or Bulk Operations for Hundreds of Shopify Records?
Flow's Get data actions run on lists of up to 100 items, so a For each loop cannot sweep a large catalog. Catalog-wide edits need a real bulk lane.
Your App Has No Flow Connector: Build the Bridge or Wait?
Only an app's own developer can ship its Flow tasks. Outbound automation needs just Send HTTP Request; inbound needs a bridge app from $29/month (verified Sep 2026).
Flow Failure Alerting on Shopify: Build the Watcher or Buy One?
Shopify ships no store-wide Flow alert. Build a watcher on the Workflow error occurred trigger, which fires once per workflow version within a 30-day window.
Flow Workflow Retries on Shopify: Build Your Own Safety Net?
Flow retries transient errors like step timeouts and 5XX statuses, and never retries permanent ones. Critical workflows need their own error branches.
Should You Build or Buy Site Search on Shopify?
Site search on Shopify splits by catalog size: native to ~1,000 SKUs, buy in the middle, build at big-catalog, search-led scale.
Hitting Flow's 90-day wall?
We map which sequences belong in Flow, which belong on a lifecycle platform, and which need a cohort orchestrator that keeps every record in Shopify.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Flow's wait ceilings are published limits and can change, so confirm the current figures on Shopify's own reference before you design against them.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.