Small merchants need a reliable way to let AI shopping agents help customers purchase products without rebuilding their entire online store. The agentic commerce protocol specification for small merchants provides a technical framework for connecting an AI agent to a merchant’s checkout system while keeping order processing and payment responsibilities on the merchant’s side.
The Agentic Commerce Protocol (ACP) defines how buyer agents and merchant systems exchange checkout information. It supports a structured process for creating a cart session, updating order details, completing a purchase, and keeping order information synchronized.
For a small US retailer using Shopify, WooCommerce, or a custom storefront, the main decision is whether direct protocol integration is necessary or whether an existing commerce platform or payment provider can handle the work more efficiently.
The 5 Points That Matter Most About ACP Today
- ACP is an open standard that defines how AI agents interact with businesses to complete purchases for buyers
- Most small merchants do not need to build anything because platforms and payment processors now handle the technical layer
- OpenAI ended Instant Checkout on March 24 2026 so the main value of ACP today is product discovery in AI shopping.
- Clean and accurate product data matters more than checkout code
- Your platform or payment processor should decide your path before any developer does
What the Agentic Commerce Protocol Does
Traditional online shopping usually requires customers to browse a website, add products to a cart, enter shipping details, and complete checkout. Agentic commerce allows supported AI shopping experiences to coordinate more of this process through structured software interfaces.
ACP gives the agent and merchant a defined way to communicate instead of relying entirely on browser automation.
The merchant remains responsible for important business operations, including:
- Maintaining accurate product prices and inventory.
- Calculating applicable taxes, discounts, and shipping costs.
- Validating orders and processing payments.
- Managing fulfillment, cancellations, and refunds.
- Keeping the merchant’s order management system accurate.
For example, a customer might ask an AI shopping assistant to purchase a particular kitchen appliance under $150. The assistant can help identify a suitable item and initiate a supported checkout flow. The merchant’s system must still confirm the actual price, availability, shipping charges, and final order status.
ACP does not automatically make every product discoverable through every AI assistant. Product discovery, platform eligibility, and checkout integration are separate requirements.
Agentic Commerce Protocol Specification at a Glance
The protocol’s checkout specification defines the API interactions needed to manage a purchase. The exact implementation should follow the current version of the specification being adopted.
| Specification detail | What it means for a small merchant |
|---|---|
| Communication format | HTTPS requests and JSON responses |
| Checkout session | A unique session tracks the purchase in progress |
| Product and cart data | The merchant returns authoritative line items and calculated costs |
| Fulfillment | Available shipping or other supported fulfillment options are returned |
| Payment processing | The merchant uses its payment provider and supported payment integration |
| Order management | The merchant creates and maintains the actual order record |
| Request safety | Authentication, idempotency, and request validation protect checkout operations |
| Order synchronization | Supported event notifications help keep order status current |
| Platform access | Availability of a particular in-chat checkout experience may require approval |
The specification is an integration contract rather than a storefront builder. It does not replace product pages, inventory management, payment processing, or customer service.
The Five Checkout Endpoints Small Merchants Need to Understand
ACP checkout uses REST API endpoints to manage the purchase lifecycle. Each endpoint handles a specific operation.
1. Create a checkout session
POST /checkout_sessions
The agent submits the requested items. The merchant creates a session and returns current product details, line items, pricing, available fulfillment options, and the session status.
2. Retrieve the current session
GET /checkout_sessions/{id}
The agent can retrieve the latest state of an existing checkout session. This helps recover the current state when a request is interrupted or needs verification.
3. Update the checkout session
POST /checkout_sessions/{id}
The merchant recalculates the cart when the customer changes quantities, shipping details, fulfillment options, or supported discounts.
4. Complete the checkout
POST /checkout_sessions/{id}/complete
The merchant validates the payment information, processes the transaction through the supported payment flow, creates the order, and returns its final state.
5. Cancel the checkout session
POST /checkout_sessions/{id}/cancel
The merchant cancels an eligible session and releases any inventory reservation associated with it. A completed order may require a separate cancellation or refund process.
These endpoints are not interchangeable. Creating a session does not mean an order has been placed, and a successful payment request should not be treated as confirmation until the merchant’s system verifies the transaction and order creation.
What Data Must a Merchant Return?
A checkout integration needs more than a product name and a price. The agent must receive enough information to display the correct purchase details and determine whether the checkout is ready for payment.
Product and line-item information
Each item should have a stable identifier that maps to the merchant’s product or variant record. The merchant should also return the quantity, applicable unit price, item description, and relevant adjustments required by the selected schema.
For a small retailer selling clothing, for example, a shirt in a medium size may have a different inventory record from the same shirt in a large size. The integration must preserve that distinction instead of treating both products as interchangeable.
Pricing, taxes, and discounts
The merchant’s system should calculate the authoritative checkout total. Depending on the order, that total may include:
- Product prices and quantities.
- Applied discounts and coupon adjustments.
- Shipping or other applicable fulfillment charges.
- Sales tax calculated using the relevant order details.
- The final amount due.
For US businesses, tax calculations may depend on the delivery address, product taxability, and applicable state or local rules. The merchant should use its established tax calculation process rather than relying on an AI agent to estimate the amount.
Fulfillment options
The response should describe the fulfillment options the merchant actually supports, including their identifiers and costs. Depending on the business, these might include standard shipping, expedited shipping, or local pickup.
The system should not offer an unavailable shipping method or promise a delivery date it cannot support. Changes to the delivery address can affect both tax and shipping calculations, so the checkout must be recalculated when relevant details change.
Session status and customer messages
The response communicates whether checkout is ready for payment or requires additional information. It should also return appropriate messages and errors so the agent can explain the next step to the customer.
For example, an out-of-stock item should produce a clear response that prevents an unavailable product from proceeding to payment.
How a Small Merchant Can Implement ACP
A practical implementation starts with the existing commerce system rather than a complete rebuild.
- Audit the existing storeIdentify where product data, inventory, taxes, shipping rules, discounts, orders, and payment processing currently live.
- Choose the integration routeCheck whether the current ecommerce platform or payment provider offers a supported implementation. If not, assess the effort required to build and maintain a custom adapter.
- Build the checkout API layerImplement the required endpoints against the current version of the specification. Map incoming item identifiers to real products and return complete, accurate checkout state.
- Connect the payment workflowUse a supported payment handler and the existing payment service provider. Validate credentials and payment outcomes before confirming an order.
- Test normal and failure scenariosTest quantity changes, invalid addresses, expired inventory, discounts, failed payments, retries, cancellations, and interrupted requests.
- Verify eligibility and launch readinessConfirm platform access requirements, complete the required conformance testing, and monitor order consistency after deployment.
A merchant that already has reliable ecommerce infrastructure may need an adapter and API integration rather than an entirely new store. However, the work can be substantial if its inventory, pricing, and order records are fragmented across multiple systems.
Security Requirements That Protect Small Businesses
A checkout API can create financial and operational risks if it trusts incoming requests or processes repeated requests incorrectly.
Authenticate requests and verify signatures
Use HTTPS for all checkout communication. Validate the authentication credentials and request signatures required by the chosen protocol version. Where timestamps are included, apply the specified freshness checks to reduce the risk of replayed requests.
Secrets should be stored in a protected server-side environment rather than exposed in browser code, public repositories, or client-side configuration.
Make requests idempotent
Idempotency helps ensure that retrying the same operation does not accidentally create a second order or charge a customer twice.
For example, a network timeout might occur after the payment provider has processed a transaction but before the merchant receives the response. The merchant should be able to reconcile the original attempt instead of blindly charging again.
Use the protocol’s idempotency mechanism together with the payment provider’s own safeguards and a durable record of transaction attempts.
Validate prices and inventory on the server
Never assume that an item price, discount, or availability supplied by a client is authoritative. Resolve product identifiers against the merchant’s own catalog and validate inventory and pricing when creating or updating the checkout.
The final purchase should use the verified cart state and selected fulfillment option.
Keep payment data and order records consistent
Use the supported payment flow and limit access to payment credentials. Do not log raw payment secrets or expose them in error messages.
If payment succeeds but order creation fails, the system needs a recovery procedure. Depending on the payment provider and transaction state, that may involve reconciling the payment, retrying a safe order operation, or initiating an appropriate reversal.
A reliable integration must handle these failure cases before it processes live customer orders.
Practical Example: A Small US Online Store
Consider a family-owned retailer selling coffee equipment through its existing ecommerce website.
A customer asks an AI shopping agent to purchase a grinder priced at $89. The merchant has ten units in stock and offers standard and expedited shipping.
The agent initiates a checkout session, and the merchant verifies the product identifier and quantity. Its system calculates the applicable shipping costs and sales tax based on the order details.
The customer then selects expedited shipping. The agent sends an update request, and the merchant recalculates the total before returning the updated checkout state.
Once the customer confirms the purchase, the supported payment flow is processed. The merchant creates the order and returns its identifier and status. Subsequent order updates keep the supported checkout experience aligned with the merchant’s actual order record.
The important detail is that the AI agent coordinates the interaction, but the retailer’s systems remain responsible for prices, inventory, payment processing, and fulfillment.
What Does ACP Integration Cost a Small Merchant?
There is no single reliable cost for implementing ACP across all small businesses. The expense depends on the existing platform, payment setup, technical requirements, and amount of custom development.
A merchant with a supported integration may have less engineering work than a business that must build its own API layer and payment workflow.
| Cost factor | What affects the cost |
|---|---|
| Existing platform | Availability of supported integrations and APIs |
| Custom development | Number of endpoints, system mappings, and custom business rules |
| Payment integration | Supported handlers, payment-provider compatibility, and testing |
| Security | Authentication, signature verification, idempotency, and access controls |
| Testing | Error handling, checkout conformance, payment retries, and order reconciliation |
| Ongoing maintenance | API version changes, monitoring, bug fixes, and operational support |
Which costs should be estimated first?
Start by checking whether the store’s current platform or payment provider already supports the required checkout flow. This can substantially change the amount of custom engineering required.
Next, estimate the work needed to synchronize inventory, calculate accurate totals, process payments, and recover from failed requests. These operational requirements are more important than simply counting API endpoints.
Do not assume that an open specification means every integration, transaction, or platform feature is free. Hosting, development, payment processing, and third-party services may still carry costs.
Should You Build a Custom ACP Integration or Use Your Existing Platform?
For small merchants, the main decision is whether direct integration provides enough business value to justify its technical and maintenance costs.
| Option | Best fit | Main trade-off |
|---|---|---|
| Existing platform integration | Stores with supported native or partner integrations | Less control over implementation details |
| Payment provider integration | Merchants whose payment provider supports the required workflow | Depends on provider capabilities and eligibility |
| Custom API integration | Businesses with specific requirements and developer resources | Higher development and maintenance responsibility |
| Continue with traditional checkout | Stores without a clear need for agent-driven transactions | Customers may need to leave the AI experience to complete purchases |
Use this decision framework
Choose an existing integration when your ecommerce platform already supports the required functionality. This is usually the first route worth investigating because it may reduce custom development.
Consider a payment provider’s implementation when your current provider can support the relevant checkout and payment requirements. Confirm that its integration supports your platform and intended AI commerce experience.
Build a custom integration when you need more control over checkout behavior and have the resources to maintain secure APIs, payment reconciliation, and order synchronization.
Delay implementation when product data is unreliable, inventory is frequently inaccurate, or your checkout already creates unresolved payment and fulfillment issues. Fixing those problems first reduces the risk of carrying them into an AI-driven sales channel.
For merchants evaluating the agentic commerce protocol specification for small merchants, the deciding factor should be the total cost of reliable operation rather than the initial cost of writing the endpoints.
Implementation Checklist Before Accepting Live Orders
Use this checklist to assess whether your store is ready for a production integration.
Production readiness
0 of 10Product and variant identifiers map to real catalog recordsPrices and inventory are validated by the merchant systemTaxes discounts and shipping are recalculated when requiredAll required checkout endpoints follow the selected specification versionPayment handlers and credentials are configured securelyRepeated requests cannot create duplicate charges or ordersFailed payments and interrupted requests have recovery proceduresCancellation and refund workflows are testedOrder status updates remain consistent across systemsPlatform eligibility and conformance requirements are confirmed
Reset checklist
Completing this checklist does not certify an integration. It helps identify operational gaps that should be addressed before real customers use the checkout.
Frequently Asked Questions
What is the agentic commerce protocol specification for small merchants?
It is a technical framework for connecting merchant checkout systems with AI agents. It defines how supported systems create and update checkout sessions, exchange pricing and fulfillment information, process purchases, and return order status.
Does a small business need to rebuild its website to support agentic commerce?
No. A merchant may be able to retain its existing website, catalog, inventory system, and payment provider. The required work depends on whether the current platform supports the protocol or needs a custom integration.
Can ACP work with WooCommerce or Shopify?
Compatibility depends on the available platform integrations, extensions, and supported implementation routes. Merchants should verify current compatibility with their platform and the intended AI shopping service rather than assume that installing a plugin automatically enables ACP checkout.
Does the protocol process payments directly?
The protocol coordinates the checkout interaction, but the merchant remains responsible for the applicable payment workflow. The merchant must use a supported payment integration and validate the resulting transaction before confirming the order.
Is agentic commerce free for small merchants?
The specification itself is openly available, but implementation is not necessarily free. Development, hosting, security testing, payment processing, and ongoing maintenance can create costs. Any platform-specific fees or eligibility requirements should be verified separately.
What happens if an item becomes unavailable during checkout?
The merchant should revalidate inventory when the checkout changes and return an updated session state with an appropriate message or error. The unavailable item should not proceed to payment as though stock were still available.
How should a merchant choose an ACP integration approach?
Start with the existing ecommerce platform and payment provider. If a supported integration meets the store’s requirements, compare its costs and limitations with custom development. Build directly only when the additional control justifies the engineering and maintenance effort.
Does implementing ACP guarantee more sales through AI shopping agents?
No. Technical integration does not guarantee product visibility, customer demand, platform access, or sales. Results depend on factors such as product relevance, pricing, inventory, customer preferences, and the availability of supported shopping experiences.