[AI shopping & agentic commerce]() / [Use cases]() / [Checkout routes]() [How it works]() [What you get]() [Scope]() [Start a review]() [AI shopping & agentic commerce]()[Orders that complete]() # Keep AI-referred sales whole, from answer to order. Every AI route gets a checkout or a handoff, chosen by what the basket needs, so bundles, promotions and promises survive the trip. [Start with an AI shopping review]() [How it works]() Route parity · native checkout in the assistant Tested on real baskets Basket feature Native route Decision Single jacket Carried Native Discount code Carried Native Jacket + Care Kit bundle Not supported Hand off Care Kit subscription Not supported Hand off Pixel events Don’t fire Server events The parity matrix: what a route carries, and what to do with the rest. ## Sound familiar? - You switched on a channel, and bundles, subscriptions or promotions quietly stopped working. - Nobody has run a real basket through each route. - Your pixels and analytics don’t fire inside an assistant’s checkout, so you can’t see what it earned. A shorter checkout that drops the Care Kit, the discount or the delivery date costs the sale. A Walmart executive said in March 2026 that products in its early ChatGPT checkout converted three times worse than click-out. ## What changes. ShowTodayWith the engine Routes One checkout for everything A checkout or a handoff, route by route Testing Assumed to match your store A real basket run through every route Bundles and subscriptions Dropped without a warning Handed to your checkout with the basket intact Measurement Pixels that never fire Server events and one reconciled record The decision Because the channel is available Because completed profitable orders beat the handoff, net of fees ## How it works. 4 steps, 4 stages. - AI**1** - Rules and automation**2** - Your team**1** - Approval 1. 1 Map 1. Rules and automation ### Map what each route can carry A parity matrix per route: products, discounts, bundles, subscriptions, shipping, tax, tracking and returns. - Shopify - ChatGPT - Merchant Center - Microsoft Copilot 2. 2 Test 1. AI ### Run real baskets Builds test baskets from your actual orders, runs them through each route and flags what drops out. 3. 3 Route 1. Rules and automation ### Send each basket the right way Single items use native checkout where it’s on. Anything the route can’t carry hands off to your checkout with the basket intact. - Shopify 4. 4 Review 1. Your team Approval ### Decide where native is worth it Your commerce and finance leads compare completed profitable orders and fees against the handoff, route by route. New route features re-run the matrix ## What you get. Real work, every week. Route decisions Reviewed quarterly - ChatGPT via ShopifyBuyers land on Fernway’s checkout **Handoff**Keep - Copilot, single itemsNative checkout, for single items only **Native**Validate - PerplexityNo merchant route confirmed **None**Defer One line per route: what happens there, and the verdict your commerce lead signs. Basket · INT-104 **2 of 2**basket lines kept at Fernway’s checkout - Canvas field jacket · Navy M · $168 The native route can carry it - Care Kit bundle · $28 Not supported on the native route - Handed off to Fernway’s checkout Basket and promise intact - Delivery promise · Thursday Carried to the order A basket the native route can’t carry, followed to the handoff. Nothing drops out on the way. ## How you’ll know it’s working. 1. Completed profitable orders against the handoff Net of channel fees, payment costs, refunds and support, not the checkout steps saved. 2. Baskets that lose a feature on a route Every bundle, subscription or promotion that doesn’t survive, found before a shopper finds it. 3. Eligible attempts completed The denominator that tells a payment from a finished purchase. Baselines agreed before we build. ## Works with what you have. Commerce - Shopify Search & AI - ChatGPT - Merchant Center - Microsoft Copilot Payments - Stripe Measurement - Google Analytics We configure first Shopify’s ChatGPT, Copilot and Google channels, and your payment processor’s own agent tools, cover much of the plumbing. We switch on what fits, then test it with real baskets. We build when Your baskets carry bundles, subscriptions or account rules a native route can’t, and the handoff and the records need to hold together. ## What a first build includes. Built in your accounts, around your team. Scope, fee and baseline agreed before we start. 1. 1 Design 2. 2 Build 3. 3 Run it, or hand it over [Start with a review]() [Scope this build]() ### We build - A parity matrix for every route you sell through - Test baskets built from your real orders - Handoff rules that keep the basket intact - A route review that compares native checkout with the handoff ### We start from - Order history and basket types - Channel, storefront and payment access - Promotion, tax and shipping rules ### From your team Owner Head of ecommerce, with payments Involves - Ecommerce - Payments - Operations - Finance ## Questions teams ask. Do we have to turn on native checkout everywhere? No. A handoff to your own checkout is a legitimate design, and often the better one when a route can’t carry your basket. We recommend native checkout only where it earns more profit than the handoff. Is Shopify’s ChatGPT route native checkout? As of October 2026, it sends buyers to your own checkout. OpenAI also documents a separate route for selected merchants and a plugin beta for approved partners, so we check which applies to your account before promising anything. Do we need to support every agent protocol? No. The protocols solve different jobs, and a payment credential is only one dependency in a completed purchase. We build for the routes you’re approved for and have demand on. Who owns it once it’s running? You do. It’s built in your accounts, documented, with training for the people who run it. Ownership usually sits with your head of ecommerce, with payments. We can keep running it with you, or step back. How do we start? Usually with an AI shopping review: two to four weeks, a fixed fee credited to the build, and a plan that’s yours. If the job is already clear, we can scope the build directly. ## Part of your AI shopping engine. One of 13 use cases, in 5 parts. [See the whole AI shopping engine]() 1. [Found & right **3**]() 2. [Help choosing **3**]() 3. [Orders that complete **3**]() 4. [Buying on account **1**]() 5. [Proof & route **3**]() In orders that complete - **Checkout routes**You’re here - [**Order reconciliation**Reconcile AI-placed orders from payment to fulfillment]() - [**Service handoff**Hand AI-sold orders to service with the context]() Works with - [**AI answer accuracy**Find and fix what AI assistants say about your products]() See it at work - [**In Fernway’s launch week, through AI**Day 6: the basket handed off whole]() - [**Also in**Digital commerce & conversion]() ## Keep the sale whole. Start with an AI shopping review. [Start with an AI shopping review]() [**Talk it through first**15 minutes]() We reply within one business day. --- Source: [https://www.thekeating.co/use-cases/ai-checkout-routes/]() [Contact Keating & Co](mailto:nelson@thekeating.co) · [Agent guidance](https://www.thekeating.co/llms.txt)