[AI shopping & agentic commerce]() / [Use cases]() / [Order reconciliation]() [How it works]() [What you get]() [Scope]() [Start a review]() [AI shopping & agentic commerce]()[Orders that complete]() # Reconcile AI-placed orders from payment to fulfillment. Every AI-placed order joined from intent to payment to shipment, so a payment with no order, or an order with no promise, reaches a person fast. [Start with an AI shopping review]() [How it works]() Event timeline · INT-104 Event Record Result Shopper intent INT-104 Jacket + Care Kit, $196 Checkout CK-104 Payment authorized Order ORD-8512 Created and matched Same event again CK-104 Updated ORD-8512, no new order One purchase, event by event. A repeated confirmation updates the order instead of creating a second one. ## Sound familiar? - A payment went through and nobody can find the order. - The same confirmation arrived twice, and now there are two orders. - Finance, support and the warehouse each see a different version of the purchase. A payment confirmation and an order are separate records. When they drift apart, customers pay for nothing or get charged twice, and finance finds out at month end. ## What changes. ShowTodayWith the engine Records Intent, payment and order in separate tools One record, joined by a shared id Duplicates Found by the customer The same event updates the same order, every time Mismatches Found at month end Opened as a case within minutes Totals Whatever the channel sent Checked against the final price, tax and shipping ## How it works. 5 steps, 4 stages. - AI**1** - Rules and automation**3** - Your team**1** - Approval 1. 1 Capture 1. Rules and automation ### Capture every event Intent, checkout, payment, order and fulfillment events are stored with one shared id. - Shopify - Stripe - ShipBob 2. 2 Join 1. Rules and automation ### Join them on one record Repeated or out-of-order events update the same order instead of creating a new one. 3. 3 Check 1. Rules and automation ### Check totals and promises The final price, tax, shipping and delivery date are matched against what the shopper was shown. - NetSuite 2. AI ### Explain what’s off Reads a mismatch and writes the case: what arrived, what didn’t and the likely cause. 4. 4 Resolve 1. Your team Approval ### Resolve the exceptions Your operations lead decides every payment with no order, refund or reship. Nothing retries a purchase on its own. Each exception becomes a test ## What you get. Real work, every week. Mismatch queue Today - CK-109Paid $168, no order after 20 minutes **$168**Open - CK-111The same payment event delivered twice **1 order**Merged - CK-114Order total $9 under the checkout total **$9**Review The mismatch queue: each case has a cause, an owner and a clock. ## How you’ll know it’s working. 1. Eligible attempts completed Intent to order, so a payment that never became a purchase shows up. 2. Payments with no order The failure that costs customers money and costs you trust. 3. Time to resolve a mismatch From the first sign to a refund, a reship or a merged order. Baselines agreed before we build. ## Works with what you have. Commerce - Shopify - NetSuite Payments - Stripe Fulfillment - ShipBob Support - Gorgias We configure first Shopify’s order events and your payment processor’s agent tools can send signed completion events where the route supports it. We use them, and keep order ingestion and fulfillment with you. We build when Orders arrive from more than one route, or finance and support can’t see one record for each purchase. ## 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 - An event store keyed by one shared id - Duplicate and out-of-order handling - A mismatch queue with an owner and a clock - A daily reconciliation report for finance and support ### We start from - Payment, order and fulfillment events - Shopify, processor and 3PL access - Your refund and reship rules ### From your team Owner Head of ecommerce, with finance Involves - Ecommerce - Finance - Operations - Customer service ## Questions teams ask. Doesn’t the payment processor handle this? It confirms the payment. It doesn’t know whether your order exists, was picked, or matches what the shopper saw. Reconciling is the merchant’s job, and the processor’s tools are an input to it. Does a valid payment signature prove the right thing was bought? No. A signature proves authority to pay. It says nothing about whether the right product, size or price was selected. We test that untrusted product content can’t change what’s paid for. 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 finance. 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**Keep AI-referred sales whole, from answer to order]() - **Order reconciliation**You’re here - [**Service handoff**Hand AI-sold orders to service with the context]() Works with - [**Order status**Resolve “where is my order” with a status customers can trust]() See it at work - [**In Fernway’s launch week, through AI**Day 7: the order reconciled]() ## Know where every AI order stands. 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/agent-order-reconciliation/]() [Contact Keating & Co](mailto:nelson@thekeating.co) · [Agent guidance](https://www.thekeating.co/llms.txt)