Platform-specific plans
Implementation guides by commerce platform
Each guide begins with an actual documented platform surface, then gives an implementation and test plan. A guide never treats an API or a brand logo as proof of protocol adoption.
Implementation guide
Shopify
Map product discovery, cart state and checkout handoff to Shopify's documented UCP and MCP surfaces before treating a store as agent-ready.
Implementation guide
WooCommerce
Validate WooCommerce's developer-preview MCP integration against a test store, using its canonical product and order abilities with a dedicated least-privilege WordPress user.
Implementation guide
Adobe Commerce / Magento
Select the Adobe Commerce API surface from the merchant's actual deployment model, then validate catalog, cart and order behavior without treating API access as proof of agent-protocol support.
Implementation guide
BigCommerce
Choose the BigCommerce API according to storefront or server context, then preserve channel, variant and price-list context through checkout without inferring protocol adoption.
Implementation guide
Salesforce Commerce Cloud
Use Salesforce B2C Commerce shopper APIs for the authorized storefront flow, and treat its documented UCP integration as a separate, configuration-dependent capability with explicit regional and platform limits.
Implementation guide
commercetools
Use current product projections and versioned cart resources as the merchant-controlled source of truth, with explicit Store, price and inventory context and conflict-safe mutations.
Need a stack-neutral starting point? Use the failure-mode test plan and the readiness diagnostic.