Loop Voice for Checkout Champ: funnel carts and orders, sent by postback

Each Loop Voice workspace holds a single storefront, and Checkout Champ fits in one of two ways. If shoppers browse your Shopify store and pay on a Checkout Champ checkout, connect Shopify as the store and Checkout Champ as the checkout on it. If you sell only through Checkout Champ funnels, connect Checkout Champ as the store. In both cases the shopper checks out on Checkout Champ, so that's where Loop Voice hears about the abandoned cart.

Health and device funnels are a good fit. Three of the four stores with published Loop Voice results sell health-related products, and Modern Hearing's story names the one question that stalls its hearing aid shoppers at checkout: "will this actually work for me?" All four stores run on Shopify, so there are no Checkout Champ results to quote yet. The hearing aids and pain relief devices pages show what those shoppers ask.

Checkout Champ's export list is long: partials (incomplete orders), new sales, upsells, declines, cancels, refunds, chargebacks and fulfillment updates, each picked per route. Loop Voice's connection is for order and cart events. Declined rebills look like an obvious call list, but Loop Voice doesn't receive failed-payment events from store platforms yet; the failed payments page covers the CSV upload and Zapier routes instead.

Campaign IDs decide which funnels can trigger a call. Checkout Champ describes a campaign as a collection of products being sold, and campaigns and funnels are normally one to one, so one ID usually means one funnel (Checkout Champ on campaigns).

Example: you sell the same device through a US campaign and a UK campaign, the campaign-per-country setup Checkout Champ calls a common practice. If you've only set up calling for US shoppers, from consent wording to phone numbers, list only the US campaign's ID.

Checkout Champ's webhook service runs every 15 minutes by default and fires everything triggered since the last run, and an Export Delay adds minutes to that interval (Checkout Champ on export profiles). So a cart event can take up to 15 minutes to reach Loop Voice, and the flow can't call before it arrives.

In Loop Voice's September 2026 benchmark, when the first call landed 5 to 15 minutes after a shopper left checkout, 20.5% picked up; at 15 to 60 minutes, 9.3% did. Like the report's other timing figures, it compares different shoppers and stores and is not a controlled test. Don't add an Export Delay, keep the flow's own wait short, and check the time from abandon to first dial in Insights after the first week.

Two more export behaviors to plan for. Checkout Champ says newly created webhooks grab data from one day before, so the first run can include yesterday's partials; if you don't want those shoppers called, activate the flow after that run. And when a post fails, Checkout Champ keeps retrying until it succeeds, so a short outage delays events instead of losing them.