Why flows go quiet after the move
Recharge and Loop send subscription events to Klaviyo out of the box. Your dunning, cancel and upcoming order flows run on them. Checkout Champ's Klaviyo plugin sends orders only. So on cutover day:
- The old events stop. Flows built on them sit live with nobody entering.
- Nothing replaces them until you set up Checkout Champ postbacks.
- First rebills on Checkout Champ don't reach Klaviyo, because the rebill toggle is off by default.
HolySwish moved from Loop to Checkout Champ in September 2026. Their Loop events dropped to near zero, and Klaviyo saw only first orders. In October we set up the event bridge and rebuilt the subscription flows on Checkout Champ events. Events were flowing within days.
Map your old events to Checkout Champ
| Your flow | Loop event | Checkout Champ replacement |
|---|---|---|
| Subscriber onboarding | Loop Subscription Started | Subscription Started postback, or Ordered Product with ItemType RECURRING |
| Upcoming order | Loop upcoming order event | Pre-Billing postback, or next bill date on the profile |
| Failed payment | Loop Billing Attempt Failed and will be Retried | Rebill Decline, then Recycle Failed |
| Renewal processed | Loop Order Processed | Recurring Order postback, or Placed Order with rebills on |
| Cancel winback | Loop Subscription Cancelled | Cancel postback |
| Paused | Loop paused event | Pause postback |
| Skipped | Loop skip event | No Checkout Champ trigger |
| Card expiring | Loop Payment Method Expiring | No Checkout Champ trigger |
Recharge sends matching events under its own names, such as "Subscription started on ReCharge". Map them to the same Checkout Champ replacements.
2 flows have no direct replacement. Skip has no postback trigger, so an order skipped flow can't run. Checkout Champ has no card-expiring event, so use the pre-billing reminder and Account Updater instead, and let failed payment emails do the rest.
The safe order for a move
2 weeks before cutover
- List every Klaviyo flow, segment and campaign filter that uses a Recharge or Loop event or property.
- Map each one using the table above.
- Set up the Checkout Champ Klaviyo plugin, with rebills ticked and a Rebill Success route.
- Set up the subscription postbacks into Klaviyo. See subscription events in Klaviyo.
Cutover week
- Clone each subscription flow and swap the trigger. Klaviyo can't change a live flow's trigger, so these are new flows.
- Update every portal button. Old Recharge or Loop portal links break. New buttons open the right page in the customer's Checkout Champ portal: update card, resume, reactivate and pause.
- Turn off Checkout Champ's autoresponders for anything Klaviyo will send.
- Keep the old flows live for a few days, for subscribers still on the old app.
After cutover
- Watch the first real events: one per subscription, the right brand, the right fields.
- Check the first rebill run reaches Klaviyo as an order.
- Turn off the old flows once their events stop.
Running Loop or Recharge and Checkout Champ side by side
Some brands don't move everything. They keep Shopify subscriptions on Loop or Recharge and sell funnel subscriptions through Checkout Champ. This works, but Klaviyo sees 2 separate worlds.
- Checkout Champ subscribers never fire Loop or Recharge events. A Loop-triggered dunning flow misses every Checkout Champ subscriber. On one account we audited, Checkout Champ took a large share of daily orders, so the gap was big.
- Shopify order emails may not go out for Checkout Champ orders. Checkout Champ sends an order to Shopify when the campaign where the sale happens has a Shopify plugin attached.
- Segments double up. A "subscribers" segment built on Loop properties misses Checkout Champ subscribers.
What we do for brands running both:
- Build each subscription flow twice, one per platform, with the same copy and design. Or build one flow with 2 triggers where Klaviyo allows it.
- Build one subscriber segment that includes both platforms.
- Name events clearly, like "Checkout Champ - Cancel", so nobody mixes them up.
Checkout Champ lists Recharge and Loop as data source plugins, so some brands connect them. The Recharge plugin pulls subscription details into Checkout Champ; the Loop plugin leaves subscriptions in Loop and uses Checkout Champ only for billing.
Coming from Konnektive
If you are coming from Konnektive, don't assume your postbacks, routes or Klaviyo settings carry over. Check them in your Checkout Champ account before the first renewal, and map each old flow trigger to a Checkout Champ event with the table above. Check that routes and postback URLs point at the right campaigns.
Checkout Champ vocabulary
If you come from Shopify, the terms are different.
| Checkout Champ term | Plain meaning | Shopify, Loop or Recharge equivalent |
|---|---|---|
| Rebill | A renewal charge | Recurring order, renewal |
| Recycle billing | Automatic retries of a declined rebill | Dunning, retry ladder |
| Recycle Failed | Retries ran out | Final payment failure |
| Campaign | Container for products, offers and funnels | Roughly a store or offer |
| Purchase (PurchaseID) | One subscription line | Subscription contract |
| NEW_SALE | First order | First subscription order |
| Postback | Outgoing webhook | Webhook, integration event |
| Autoresponder | Checkout Champ's built-in email | Loop or Recharge notification email |
| Partial order | A visitor who entered details at checkout but did not finish the order; it reaches Klaviyo as Started Checkout | Abandoned checkout |
Book your free Checkout Champ check
A 20-minute call. We look at what your Checkout Champ sends to Klaviyo, whether rebills reach it, which subscription emails are missing and whether Checkout Champ autoresponders double-send.
Book your free Checkout Champ check
Prefer a written review of your whole Klaviyo account? Get a free Klaviyo audit.
