A shopping assistant can find a relevant product and build a useful cart without completing a purchase. That distinction matters when a commerce team evaluates an agentic shopping pilot. If every successful handoff is reported as a sale, the dashboard can look healthy while buyers still struggle with delivery choices, payment or an unfinished checkout.
Shopify's current developer documentation describes separate cart and checkout capabilities. Carts support exploration and estimated totals; checkout sessions represent an active purchase and expose a status. Depending on eligibility and the required review, completion can involve a merchant storefront handoff. These are Shopify-specific capabilities, not evidence that every agent or merchant supports the same flow. The operating framework below is Aeris editorial analysis.
Name the customer state
Start with language that the customer can understand. A product has been found. An item has been selected. A cart has been prepared. Checkout needs attention. An order has been confirmed. Each statement should correspond to evidence available to the system.
Avoid using a reassuring phrase such as “all done” when the buyer still needs to act. A friendly answer can still be precise about the next step. If payment must happen on the merchant's website, explain that handoff and provide the relevant destination.
Keep the internal reporting vocabulary aligned with these customer states. Otherwise, a team may count an operational response as a commercial outcome simply because both events carry a success label.
Preserve the selected offer
The handoff should carry the item the buyer actually chose. Check the variant, quantity and market before treating a prepared cart as ready for review. A product family name alone may not identify the intended size or color.
Show which commercial details remain estimates and which have been resolved. A subtotal does not necessarily answer the buyer's question about the amount payable after fulfillment choices and other applicable conditions. When information changes, make the change visible before requesting the next decision.
Use a small set of representative products for the pilot. Include ordinary items alongside cases involving variants or multiple quantities. A demonstration based only on the easiest item tells the team little about the quality of the broader journey.
Make the handoff observable
Record the transition into checkout separately from the transition out of it. A buyer opening a checkout destination demonstrates progress, but it does not establish that an order exists. Give each stage a clear evidence requirement.
When an authoritative order confirmation is available through an authorized integration, use it to support the completed-purchase state. Where the integration cannot observe completion, label that limitation instead of guessing from a click or elapsed time.
Keep the evidence record proportionate. The operating team needs a reference, a timestamp and a state it can investigate. It does not need to copy private payment information into a general marketing report.
Test interrupted journeys
Include a buyer who leaves checkout and returns later. Test a changed quantity, an unavailable variant and a handoff that cannot be opened. These cases help reveal whether the assistant explains the current state or repeats an earlier answer that is no longer useful.
For an uncertain response, check the existing state before repeating a consequential action. The desired outcome is a single clear journey, with unresolved situations assigned to an accountable owner. A retry that merely makes the interface look responsive can create confusion downstream.
Review the customer-facing language in these cases. “We could not confirm completion” is a different claim from “your purchase failed.” The evidence should determine which statement the assistant can support.
Report the transition that needs work
Show discovery, cart preparation, checkout entry and confirmed purchases as distinct stages. Define the population and observation period for each comparison. Keep unobserved outcomes visible so that missing data does not become an apparent conversion improvement.
Use the pilot review to choose one specific repair. Perhaps buyers need clearer delivery information before the handoff. Perhaps the selected variant is lost. Perhaps the integration needs a better way to reconcile an existing order after an interruption.
An effective agentic commerce pilot makes the next customer action clearer and the result easier to verify. A prepared cart is valuable progress. A confirmed order is a separate outcome that deserves its own evidence.
Source
Shopify developer documentation: Carts and checkout for agents, reviewed September 18, 2026. The pilot framework is Aeris editorial analysis.
