Table of Contents
Why Most Subscription Managers Are Stuck in Manual Mode
You already know what needs to happen. Swap the starter kit to full-size after order two. Apply the loyalty discount at six months. Convert prepaid plans to recurring when they run out. The logic is obvious. The execution is the problem.
Executing at scale means one of two things at most companies. Either you file a ticket with engineering and wait three sprints, or you export a CSV every Monday and spend hours doing surgery in a spreadsheet. Both options are bad, and the irony is thick. Subscription platforms promise automation, then make you build the actual automation yourself.
Skio Journeys close that gap. You build the workflow yourself in the dashboard, with clicks instead of code, and it runs forever in the background. This guide walks through exactly how, with four complete builds you can copy today. It's the tactical companion to how automation saves time for lean teams if you want the broader strategy first.
What You Can Actually Automate (Without Writing Code)
The short answer is most of the repetitive work eating your week:
Time-based actions. Swap products after X orders, apply discounts at milestones, sunset prepaid plans when the term ends
Behavior-triggered workflows. Tag high-value customers, react to product adds and removals, route subscribers into segments
Lifecycle automation. Onboarding sequences, retention plays, trial-to-full-size conversions
The key distinction to internalize early is automation versus bulk operations. Automation means you set it once and it runs forever, for every future subscriber who qualifies. Bulk operations are one-time fixes for subscriptions that already exist. You'll use both, and we'll cover exactly when to use which below. Full feature overview lives in the Journeys doc.
How Skio Journeys Work: The 3-Part Framework
Every Journey is built from the same three components.
Trigger. What starts the Journey. Options include subscription created, order processed, a specific order number reached, date-based delays, and status changes.
Condition. Who qualifies. Filter by product, plan type, customer tags, order count, or subscription value. Conditions are how you keep a Journey from firing on subscribers it shouldn't touch.
Action. What happens. Swap products, apply or remove discounts, add tags, pause subscriptions, send subscribers to segments, sunset prepaid plans.
That's the whole mental model. Trigger, condition, action. Once you think in those three parts, every workflow in this guide becomes a fill-in-the-blanks exercise. Setup mechanics are documented in how to set up a Journey.
Walkthrough 1: Starter Kit → Full-Size Swap After Order 2
The scenario. You sell a $15 starter kit on the first order and want subscribers automatically moved to the $45 full-size on order three.
Navigate to Retain > Journeys and click Create Journey
Set the trigger to Order Processed with the condition Order number = 2
Add a condition filtering to subscriptions that contain the Starter Kit variant ID
Set the action to Swap Product. Remove the starter variant, add the full-size variant
Test on a single test subscription before activating
Activate. The Journey now runs automatically for every qualifying subscription, forever
The classic mistake here is skipping step three. Without the product filter, this Journey swaps every subscription in your store after order two, including the ones that never had a starter kit. Filter by the exact variant ID, always.
Walkthrough 2: Auto-Apply a Loyalty Discount at 6 Months
The scenario. Reward subscribers with 15% off after six months to head off churn fatigue.
Create a Journey with the trigger Subscription Created plus a 180-day time delay
Add a condition checking the subscription is still active, so you're not discounting cancelled subs
Set the action to Apply Discount Code with your loyalty code
Optional but recommended, add a second action to Tag Customer with something like vip-subscriber
The tag is where this gets fun. Pair it with a Klaviyo flow that triggers on the tag and sends a "you've unlocked VIP status" email. The subscriber gets recognition, you get a retention bump, and nobody exported anything.
Walkthrough 3: Sunset Prepaid Plans Automatically
The scenario. A customer buys a 3-month prepaid plan. When the final order ships, you want them converted to monthly recurring instead of silently churning out.
Create a Journey triggered on Order Processed with conditions Prepaid plan = true and Remaining prepaid orders = 0
Set the action to Sunset Prepaid, which converts the subscription to recurring billing
Optional, apply a discount code to sweeten the transition, something like 10% off the first recurring order
Prepaid endings are one of the most predictable churn moments in subscriptions. The plan runs out, nothing happens, the customer drifts away. This Journey turns that cliff into a continuation. Edge cases are covered in the Sunset Prepaid action doc.
Walkthrough 4: Tag High-Value Subscribers for VIP Treatment
The scenario. You want every subscriber who hits 10 orders flagged for special handling.
Create a Journey triggered on Order Processed with the condition Order number = 10
Set the action to Tag Customer with vip-10-orders
Use that tag downstream. Klaviyo can trigger a VIP email, Shopify Flow can route special handling, your support team can see it on every ticket
You're auto-segmenting your best customers with zero exports and zero spreadsheets. Early access drops, exclusive discounts, and thank-you gifts all become one-tag operations.
When to Use Journeys vs. Bulk Operations vs. Rules
Three tools, three jobs. Confusing them is how things break.
Use case | Tool | When to use | Example |
|---|---|---|---|
Ongoing workflow | Journeys | Set once, runs forever for all future subscribers | Auto-swap starter kit to full-size |
One-time cleanup | Bulk Operations | Fix existing subscriptions right now | Remove a discontinued product from 500 subs |
Milestone rewards | Rules (Surprise & Delight) | Incentivize behavior with gifts | Free sample at order 5 |
The test is simple. If you want this to happen automatically for every future subscriber, it's a Journey. If you need to fix something that already happened, it's a Bulk Operation. If you're rewarding a milestone with a gift, it's a Rule. You can and should use all three.
How to Test Journeys Before Going Live
Never activate a Journey without testing on a single subscription first. Here's the routine:
Create a test subscription in your store with the exact product and plan the Journey targets
Manually trigger the condition. If your trigger is order number 2, process an order to get there
Verify the action executed. Did the product swap? Did the tag appear? Did the discount apply?
Check the subscription audit log to see exactly what the Journey changed and when
Two testing mistakes to avoid. Don't use your own personal subscription, which probably has edge cases from years of testing other things. And give async actions a beat to complete before declaring the test failed.
Troubleshooting: Why Your Journey Isn't Firing
Work through these in order:
Is the Journey actually active? This sounds insulting. It's also the number one cause
Does the subscription meet every condition? One missed filter means no fire. Verify with a test sub
Are you filtering by the correct variant ID? Product swaps need an exact variant match, not just the product
For time-based triggers, has enough time actually passed? A 180-day delay will not fire on day one
Check the Journey's execution history in Skio. It logs every run
If the history shows the Journey fired but the action didn't land, that's when you contact support. Full guide in troubleshooting Journeys.
5 Journeys Every Retention Manager Should Set Up
If you build nothing else, build these:
Starter-to-standard product swap after the trial period ends
Auto-apply loyalty discount at the 6-month or 12-month mark
Sunset prepaid plans to recurring billing after the final order
Tag high-LTV customers at 10+ orders for VIP segmentation
Pause subscriptions entering dunning so payment recovery can run without racking up failed charges
None of these are theoretical. Each one replaces a manual process someone at your company is currently doing, badly, in a spreadsheet.
How Journeys Stack with Other Skio Tools
Journeys handle the subscription logic. Other tools handle communication and offers, and the combinations are where the leverage lives.
Journeys plus Cancel Flows means you tag at-risk customers, then show them targeted save offers when they hit cancel. Journeys plus Quick Actions means a tagged customer gets a one-click upsell link in their next Klaviyo email. Journeys plus Loyalty means milestone discounts apply automatically while tier progression tracks itself. The pattern is always the same. The Journey detects and tags, the other tool acts on the tag.
What You Can't Automate (Yet), and the Workarounds
Being straight with you about the limits:
Inventory-based swaps. Journeys can't react to stock levels. Workaround, use a Bulk Operation when a product goes out of stock
External data triggers. A Klaviyo engagement score can't start a Journey. Journeys run on Skio data only
Direct email sends. Journeys don't send emails themselves. Workaround, the Journey tags the customer and Klaviyo sends based on the tag
Usage-based frequency changes. Journeys can't detect that someone uses product slower than they receive it. Workaround, let customers self-adjust frequency in the Customer Portal
Most limits dissolve when you combine Journeys with Klaviyo or Shopify Flow. The tag is the universal adapter.
FAQ
Can I automate subscription workflows without a developer?
Yes. Skio Journeys use a trigger, condition, and action framework you build entirely in the dashboard. No code, no engineering tickets.
What's the difference between Journeys and Bulk Operations?
Journeys run automatically forever for future subscribers. Bulk Operations are one-time fixes for subscriptions that already exist.
How do I test a Journey before activating it?
Create a test subscription, manually trigger the condition, verify the action executed, and confirm the change in the subscription audit log.
Can Journeys send emails to customers?
Not directly. Use a Journey to tag the customer, then trigger a Klaviyo flow from that tag.
What triggers can I use in Skio Journeys?
Subscription created, order processed, specific order numbers, time delays, and subscription status changes.
How do I automate prepaid plan sunsets?
Use the Sunset Prepaid action in Journeys to convert prepaid subscriptions to recurring billing automatically after the final prepaid order.
