Shopify vs WooCommerce

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to WooCommerce
   Shopify~partialprobed6/10

   Shopify has no llms.txt (confirmed 404 via probe), but it does publish agent-oriented docs in markdown form (agents.md, ai-toolkit.md, storefront-mcp.md, order-mcp.md) explicitly designed for AI agents/coding tools to consume, plus an AI Toolkit that connects agents to docs and schemas. missing for 10: a working llms.txt endpoint, and independent confirmation that agents can successfully parse/use these .md docs end-to-end.

   • [probe] “PROBE llms.txt: HTTP 404 at https://shopify.dev/llms.txt”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “The toolkit connects your agent to: Developer docs and API schemas... Code validation: validate GraphQL queries, Liquid templates, and Shopi…”
   • [claimed-docs] “Shopify AI Toolkit gives your AI coding tool a Shopify-aware starting point.”
   • [claimed-docs] “Shopify AI Toolkit connects your AI coding tools to Shopify's developer docs, API schemas, and CLI store management so they can help you bui…”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”

   proof ↗⚑ flag

   WooCommerce✓fullprobed9/10

   A direct probe confirms an llms.txt file is live at developer.woocommerce.com/llms.txt returning HTTP 200 with structured documentation listing, and there's an official MCP server for AI agent interaction with WooCommerce stores, directly supporting agent-oriented discovery. Missing for 10: no independent/community corroboration of agents actually using llms.txt successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.woocommerce.com/llms.txt # WooCommerce Documentation This file contains a list of all documen…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Shopify
   Shopify~partialprobed5/10

   Shopify CLI (shopify-docs-3,17,30,42) and GraphQL Admin/Storefront APIs (shopify-docs-18,31,32) provide command-line and programmatic access that could be scripted, and webhooks (shopify-docs-4,21,43) support event-driven automation, but there is no explicit documentation of running the CLI non-interactively or in a CI pipeline, no CI/CD guide, and no headless-mode flag mentioned. Missing for 10: explicit CI/CD documentation, non-interactive/headless CLI mode, automation pipeline examples.

   • [claimed-docs] “Initialize new apps, themes, and headless storefronts in an instant with the latest Shopify CLI.”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”
   • [claimed-docs] “A single command installs all the dependencies you need, including the CLI itself, so you can dive straight into development.”
   • [claimed-docs] “Run the second command to create a new app. Your app will be added as a new subdirectory.”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [probe] “official CLI documented at https://shopify.dev/docs/api/shopify-cli”

   proof ↗⚑ flag

   WooCommerce~partialprobed4/10

   WooCommerce ships WC-CLI for command-line store management and a REST API for scripted automation, which supports some headless/CI-style operations, but there is no evidence of a documented headless runtime mode, containerized CI test harness, or official guidance for running WooCommerce end-to-end in a CI pipeline. missing for 10: documented headless/CI deployment pattern, official CI/testing pipeline integration, evidence of automated store provisioning without a GUI.

   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [github] “Once you've installed all prerequisites, the following will prepare all of the build outputs necessary for development”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Shopify—none0/10

   All Shopify MCP evidence describes Shopify acting as an MCP *server* provider (Catalog, Cart, Checkout, Order MCP servers) for external AI agents to consume — the opposite direction of this story, which asks whether Shopify itself can plug in external MCP servers to gain new tools. No evidence shows Shopify's admin, Sidekick, or any Shopify-side agent acting as an MCP client that connects to third-party MCP servers. Missing for 10: any documentation of Shopify (or its AI features) consuming/plugging-in external MCP servers as a client.

   • [claimed-docs] “Connect any AI assistant to real-time commerce data from Shopify stores with Model Context Protocol (MCP) servers.”
   • [claimed-docs] “Use the Order MCP server to fetch the current state of an order placed through your agent, including line items, fulfillment events, and pos…”
   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “enables AI agents to build and iterate on a cart before the buyer commits to purchase”
   • [claimed-docs] “enables AI agents to create and manage checkout sessions, convert carts into checkouts, and refer buyers to the merchant storefront to compl…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”

   proof ↗⚑ flag

   WooCommerce—none0/10

   Evidence only shows WooCommerce exposing itself as an MCP *server* so external AI assistants can call its tools (docs-14/29/probe-3), not WooCommerce acting as an MCP *client* that plugs in and consumes tools from other MCP servers. No documentation or feature describes WooCommerce connecting outward to third-party MCP servers.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Shopify
   Shopify✓fullprobed8/10

   Shopify publishes multiple official MCP servers (Storefront MCP, Cart MCP, Checkout MCP, Order MCP, Catalog MCP) explicitly for connecting AI agents to real-time commerce data, with dedicated docs pages for each and a UCP framework for agentic commerce. Missing for 10: independent/hands-on verification that these MCP servers work as documented and details on setup/auth flow for external agent clients.

   • [claimed-docs] “Connect any AI assistant to real-time commerce data from Shopify stores with Model Context Protocol (MCP) servers.”
   • [claimed-docs] “Use the Order MCP server to fetch the current state of an order placed through your agent, including line items, fulfillment events, and pos…”
   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “enables AI agents to build and iterate on a cart before the buyer commits to purchase”
   • [claimed-docs] “enables AI agents to create and manage checkout sessions, convert carts into checkouts, and refer buyers to the merchant storefront to compl…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”

   proof ↗⚑ flag

   WooCommerce✓fullprobed7/10

   WooCommerce documents native MCP support enabling AI assistants to interact directly with stores via a standardized protocol, confirmed by both docs and a probe of the dedicated MCP feature page. Missing for 10: independent/hands-on corroboration of the MCP server working in practice, and details on setup/configuration depth.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Shopify
   Shopify✓fullprobed9/10

   Shopify CLI is well documented as an official command-line tool for generating and managing apps, themes, and headless storefronts, with clear commands (init, dev, deploy) and dev-store integration; it's also positioned as AI-aware via the AI Toolkit that connects AI coding tools to CLI store management. missing for 10: independent/hands-on third-party review specifically validating CLI usability for AI-native workflows.

   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”
   • [claimed-docs] “Initialize new apps, themes, and headless storefronts in an instant with the latest Shopify CLI.”
   • [claimed-docs] “A single command installs all the dependencies you need, including the CLI itself, so you can dive straight into development.”
   • [claimed-docs] “Run the second command to create a new app. Your app will be added as a new subdirectory.”
   • [claimed-docs] “Shopify AI Toolkit connects your AI coding tools to Shopify's developer docs, API schemas, and CLI store management so they can help you bui…”
   • [claimed-docs] “Dev stores are testing environments that you own and control. They let you build and test your apps in a realistic Shopify environment witho…”
   • [probe] “official CLI documented at https://shopify.dev/docs/api/shopify-cli”

   proof ↗⚑ flag

   WooCommerce✓fullprobed8/10

   WooCommerce documents an official WC-CLI for managing stores via command line (woocommerce-docs-13, woocommerce-probe-4), and separately ships native MCP support enabling AI assistants to interact with stores (woocommerce-docs-14/29/probe-3), which together satisfy the 'official CLI for AI-native workflows' story. Missing for 10: independent/hands-on verification of CLI usage in AI-agent workflows, and no explicit documentation tying the CLI itself to AI-native tooling (MCP is separate from CLI).

   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to WooCommerce
   Shopify✓fullprobed8/10

   Shopify ships extensive, well-documented public APIs (Admin GraphQL API, Storefront API, webhooks, scoped OAuth tokens, quarterly-versioned releases, GraphiQL explorer, CLI) that let any external system—including AI agents via UCP/MCP servers—drive the platform programmatically. Community threads confirm the API is usable in practice, though several complain about documentation quality and API design limitations (e.g., no refund endpoint, restrictive access scopes). Missing for 10: a standardized machine-readable OpenAPI/spec file (probe found 404s for openapi.json/llms.txt) and stronger independent hands-on corroboration of ease-of-use to offset the documented developer complaints.

   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “Your code obtains an access token scoped to the permissions it needs.”
   • [claimed-docs] “its access scopes determine what it can access”
   • [claimed-docs] “Shopify releases new API versions on a predictable quarterly schedule, giving you time to adopt changes before older versions are retired. S…”
   • [claimed-docs] “GraphiQL is an in-browser tool for writing, validating, and testing GraphQL queries. When working with Shopify's GraphQL Admin API, GraphiQL…”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”
   • [community] “Shopify is really terrible when it comes to partner support. The documentation is terrible and if you want to use their API, be prepared to …”
   • [community] “App Charges get added to clients bills, you're not getting paid right away (60+ days in some cases) vs getting paid instantly. If someone do…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://shopify.dev/openapi.json, https://shopify.dev/swagger.json, https://shopify.dev/api/openapi.…”

   proof ↗⚑ flag

   WooCommerce✓fullprobed9/10

   WooCommerce documents a full REST API (v3) with authenticated CRUD access to store data, official client libraries in multiple languages, a customer-facing Store API, a CLI, webhooks, and even a native MCP server enabling AI assistants to interact directly with stores — together this is a well-documented public API surface highly suited to AI-native/agentic use. Missing for 10: no published OpenAPI/Swagger spec (probe found 404s) and no independent hands-on developer report confirming ease of programmatic use.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “The Store API provides public Rest API endpoints for the development of customer-facing cart, checkout, and product functionality.”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.woocommerce.com/openapi.json, https://developer.woocommerce.com/swagger.json, http…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to WooCommerce
   Shopify~partialclaimed5/10

   Shopify's general API auth model documents scoped access tokens ("access token scoped to the permissions it needs", "its access scopes determine what it can access") which would apply to any custom app/agent integration, and the agent-specific docs (UCP/MCP) reference authenticating agents, but there's no explicit documentation of an agent-specific credential-issuance flow or least-privilege scope management tailored to AI agents. Missing for 10: agent-specific scoped-credential issuance workflow, examples of narrowing scopes for autonomous agents, independent/hands-on confirmation of this working in agentic contexts.

   • [claimed-docs] “Your code obtains an access token scoped to the permissions it needs.”
   • [claimed-docs] “its access scopes determine what it can access”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”

   proof ↗⚑ flag

   WooCommerce~partialclaimed6/10

   WooCommerce's REST API key generation lets admins choose an access level (Read, Write, or Read/Write) per user, and API access conforms to that WordPress user's roles/capabilities — enabling coarse-grained least-privilege credential issuance for an agent. However, this is role/permission-level scoping, not fine-grained resource- or action-specific scoping, and there's no documented agent-specific provisioning flow, key expiration/rotation, or scope granularity beyond the three access levels. Missing for 10: granular per-resource/per-endpoint scoping, dedicated agent-credential workflow, expiration/rotation controls, and independent corroboration of least-privilege usage in agentic contexts.

   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Shopify✓fullcommunity8/10

   Shopify documents official SDKs/APIs (Admin GraphQL API, Storefront API, CLI, Hydrogen) plus AI-specific tooling like the AI Toolkit and UCP/MCP servers explicitly designed for AI agents and coding tools to build against (shopify-docs-18, shopify-docs-31, shopify-docs-32, shopify-docs-39, shopify-docs-53, shopify-docs-6, shopify-docs-34). Community commentary raises complaints about API design and documentation quality (shopify-comm-8, shopify-comm-12), but doesn't concretely contradict the existence or functioning of the official SDKs. missing for 10: independent hands-on validation of SDK reliability/quality, and a clearer enumerated list of officially supported language SDKs beyond generic claims.

   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [claimed-docs] “Shopify AI Toolkit gives your AI coding tool a Shopify-aware starting point.”
   • [claimed-docs] “Shopify AI Toolkit connects your AI coding tools to Shopify's developer docs, API schemas, and CLI store management so they can help you bui…”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”
   • [community] “Shopify is really terrible when it comes to partner support. The documentation is terrible and if you want to use their API, be prepared to …”
   • [community] “Shopify is a terrible experience overall, and I wouldn't recommend it for anyone looking to start a quick ecom business online... certain ty…”

   proof ↗⚑ flag

   WooCommerce✓fullclaimed8/10

   WooCommerce documents official REST API client libraries in multiple languages (JavaScript, PHP, Python, Ruby), plus a documented REST/Store API and CLI, giving AI-native developers official SDK-level building blocks. Missing for 10: independent/hands-on corroboration of SDK quality and completeness, and no unified 'official SDK' branding beyond the library list.

   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to WooCommerce
   Shopify✓fullclaimed8/10

   Shopify documents webhook subscriptions explicitly, letting apps/agents subscribe to Shopify webhook topics for near-real-time event data, and explains their use for syncing and triggering actions. This is well documented first-party but lacks independent hands-on corroboration or AI-specific webhook integration examples. Missing for 10: independent/hands-on verification, explicit AI-agent-specific webhook consumption examples.

   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”

   proof ↗⚑ flag

   WooCommerce✓fullclaimed9/10

   WooCommerce has native, well-documented webhook support that lets a store send automatic event notifications to any configurable URL, letting an AI-native agent subscribe to store events like order created/updated. Missing for 10: independent hands-on corroboration or examples of AI agents actually consuming these webhooks.

   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “A webhook is an event notification sent to a URL of your choice. You (or your developer) can configure a webhook that is triggered by events…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Shopify—none0/10

   The evidence pack covers agentic commerce (AI agents shopping via UCP/MCP), a developer-facing AI Toolkit for code validation, and AI-assisted theme design, but contains no documentation of Shopify surfacing AI-generated insights or suggestions from a merchant's own store data (e.g., sales/inventory analytics, customer behavior suggestions) inside the admin or product itself.

   ⚑ flag

   WooCommerce—none0/10

   The evidence shows WooCommerce exposes data via REST API, MCP, and CLI for external AI tools to interact with the store, but there is no evidence of native AI-generated insights or suggestions surfaced inside the WooCommerce product itself (e.g., an AI-powered analytics/insights dashboard). MCP support enables external agents to query data but does not itself constitute in-product AI-generated insights.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Shopify~partialclaimed5/10

   Shopify documents building blocks for autonomous behavior — webhooks that trigger actions on events, and MCP/UCP-based AI agent APIs (cart, checkout, order, catalog) that let agents act on a buyer's behalf without a human in the loop — but there is no evidence of a merchant-facing, no-code 'set up an automation that runs in the background' feature (e.g., a Flow-like rules engine) in the pack; the described capability is developer-oriented infrastructure for building agents/apps, not a turnkey automation-setup experience for an AI-native end user. missing for 10: a documented built-in automation/rules engine for non-developers, evidence of scheduling/persistent background execution, and independent confirmation these agent APIs run unattended long-term.

   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”
   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “enables AI agents to build and iterate on a cart before the buyer commits to purchase”
   • [claimed-docs] “enables AI agents to create and manage checkout sessions, convert carts into checkouts, and refer buyers to the merchant storefront to compl…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”

   proof ↗⚑ flag

   WooCommerce~partialprobed5/10

   WooCommerce documents webhooks that automatically fire event notifications in the background (docs-8, docs-26) and now ships native MCP support so AI assistants can programmatically interact with store data (docs-14, docs-29, probe-3), which together provide building blocks for background automation. However there's no evidence of a built-in 'set up an autonomous agent/workflow' feature for AI-native users beyond these primitives — automations still require external tooling or custom code via the REST API/CLI. Missing for 10: a first-party autonomous agent/automation-builder UI, documentation of persistent background AI-driven workflows, and independent confirmation that MCP-driven automations actually run unattended in production.

   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “A webhook is an event notification sent to a URL of your choice. You (or your developer) can configure a webhook that is triggered by events…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Shopify—none0/10

   The evidence pack mentions AI tangentially (e.g., 'Design fast with AI' theme design copy) and extensively covers AI *agents connecting to* Shopify via MCP/UCP for external agents, plus an AI coding toolkit for developers—but there is no evidence of a built-in AI assistant inside Shopify's own product (like an admin chat agent) that a merchant/user can delegate tasks to.

   ⚑ flag

   WooCommerce—none0/10

   Evidence shows WooCommerce supports the Model Context Protocol so external AI assistants/tools can connect to and interact with a store (docs-14, docs-29, probe-3), but this is the reverse of the story — it makes WooCommerce a target for external agents, not a built-in AI assistant inside the product that a user can delegate tasks to. No dashboard-embedded assistant, chat interface, or agentic feature is documented anywhere in the evidence pack.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Shopify~partialprobed6/10

   Shopify documents an agentic/AI layer (UCP, Catalog/Cart/Checkout/Order MCP servers) that lets AI agents search products, build carts, and checkout on behalf of buyers using natural-language driven agent interactions, and an AI Toolkit that lets AI coding tools query docs/schemas. This supports natural-language-driven operation of commerce flows by AI agents, but there's no evidence of a natural-language interface for merchants to operate the admin/store itself (e.g., 'create a discount via chat'), and no independent/hands-on corroboration of these agentic flows working end-to-end. Missing for 10: evidence of NL-driven merchant/admin operation, independent verification of MCP/UCP agent flows in practice.

   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the Universal Commerce Protocol (UCP)”
   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “enables AI agents to build and iterate on a cart before the buyer commits to purchase”
   • [claimed-docs] “enables AI agents to create and manage checkout sessions, convert carts into checkouts, and refer buyers to the merchant storefront to compl…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”
   • [claimed-docs] “Connect any AI assistant to real-time commerce data from Shopify stores with Model Context Protocol (MCP) servers.”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”

   proof ↗⚑ flag

   WooCommerce~partialprobed6/10

   WooCommerce documents native MCP support enabling AI assistants to interact with stores via a standardized protocol, which is the concrete mechanism for natural-language/agentic operation, and a CLI exists for scripted control. However, evidence is limited to first-party docs with no independent hands-on verification of natural-language command execution in practice. Missing for 10: independent/community validation that MCP-driven natural language commands actually work end-to-end, breadth of supported operations via MCP, and any real-world usage reports.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Shopify
   Shopify✓fullclaimed7/10

   Shopify docs describe GraphiQL, an in-browser tool for writing, validating, and executing real GraphQL queries/mutations against the Admin API, which is exactly an interactive API reference with runnable examples. Missing for 10: independent/hands-on confirmation and evidence of similar interactive runnable exploration for other APIs (Storefront, REST) beyond Admin GraphQL.

   • [claimed-docs] “GraphiQL is an in-browser tool for writing, validating, and testing GraphQL queries. When working with Shopify's GraphQL Admin API, GraphiQL…”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”

   proof ↗⚑ flag

   WooCommerce—none0/10

   WooCommerce publishes REST API reference documentation (docs-11, docs-27, docs-44, docs-x1/x2) but there is no evidence of an interactive, runnable API console (e.g., Swagger/OpenAPI explorer); a direct probe for OpenAPI/Swagger specs on the developer site returned 404 on all candidate paths (woocommerce-probe-2), indicating no interactive reference exists.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.woocommerce.com/openapi.json, https://developer.woocommerce.com/swagger.json, http…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Shopify—none0/10

   Shopify's APIs (Admin, Storefront) are GraphQL-based, and while docs describe schemas, versioning, and a GraphiQL explorer, there is no evidence of a downloadable OpenAPI/Swagger spec — a direct probe of common spec endpoints (openapi.json, swagger.json, etc.) returned 404 across all candidates. No vendor claim exists for an OpenAPI-equivalent machine-readable spec download, so this is an unmet capability rather than a disputed claim.

   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [claimed-docs] “GraphiQL is an in-browser tool for writing, validating, and testing GraphQL queries. When working with Shopify's GraphQL Admin API, GraphiQL…”

   proof ↗⚑ flag

   WooCommerce—none0/10

   WooCommerce documents a REST API extensively (woocommerce-docs-11, -27, -44, -x1, -x2) but a direct probe for machine-readable OpenAPI/Swagger specs at expected paths returned 404 across all candidates (woocommerce-probe-2), and no evidence pack item links to a downloadable OpenAPI/Swagger JSON/YAML file. The REST API docs site appears to be human-readable documentation, not a published machine-readable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.woocommerce.com/openapi.json, https://developer.woocommerce.com/swagger.json, http…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Shopify
   Shopify✓fullclaimed8/10

   Shopify docs explicitly describe dev stores as owned testing environments that let developers build and test apps/integrations 'in a realistic Shopify environment without affecting any live store,' directly connectable via `shopify app dev` from the CLI, plus GraphiQL for safely exercising queries/mutations. This directly satisfies the sandbox-without-touching-production story for AI-native/agentic development workflows. Missing for 10: no explicit mention of a dedicated sandbox for the newer agent/UCP/MCP flows specifically, and no independent hands-on confirmation of dev-store isolation.

   • [claimed-docs] “Dev stores are testing environments that you own and control. They let you build and test your apps in a realistic Shopify environment witho…”
   • [claimed-docs] “GraphiQL is an in-browser tool for writing, validating, and testing GraphQL queries. When working with Shopify's GraphQL Admin API, GraphiQL…”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”

   proof ↗⚑ flag

   WooCommerce—none0/10

   No evidence pack item describes a sandbox/staging environment, test-mode API keys, or any mechanism for testing WooCommerce (including its REST API or MCP integration) without affecting production data. The REST API and MCP docs describe live store interaction only, with no mention of a sandbox mode.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Shopify
   Shopify✓fullclaimed7/10

   Shopify documents a quarterly versioned API release schedule with advance notice before retirement and a subscribable changelog, directly matching the story's requirement for versioned APIs with a documented deprecation policy. Missing for 10: independent/hands-on corroboration that deprecation timelines are reliably honored, and a standalone deprecation-policy doc beyond the versioning page.

   • [claimed-docs] “Shopify releases new API versions on a predictable quarterly schedule, giving you time to adopt changes before older versions are retired. S…”

   proof ↗⚑ flag

   WooCommerce~partialclaimed4/10

   WooCommerce's REST API is explicitly versioned (v1/v2/v3 under /wp-json/wc/v3/), satisfying the 'versioned APIs' half of the story, but the evidence pack directly states 'no deprecation-timeline policy is published' for these APIs. Missing for 10: a documented deprecation/sunset timeline or migration guide between API versions, and any changelog specifying when older versions (v1/v2/legacy) will be retired.

   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”

   proof ↗⚑ flag

Agent discovery

1. ai-native userMy products are discoverable by AI agents and answer engines through a cross-merchant catalog or feed built for agents

   weight 2 · round to Shopify
   Shopify~partialprobed6/10

   Shopify documents a Global Catalog MCP server enabling AI agents to search and discover products 'across the entire Shopify ecosystem' plus UCP for agentic commerce, which directly supports cross-merchant agent discoverability. However, this is developer/agent-integration infrastructure rather than a proven, widely-adopted answer-engine feed, and there's no independent evidence of adoption by major answer engines or of an llms.txt-style universal feed (llms.txt probe returned 404). missing for 10: independent verification that answer engines/agents actually consume this catalog at scale, evidence of a standardized feed format beyond MCP/UCP, and confirmation the llms.txt or similar discovery file exists.

   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”
   • [claimed-docs] “Build agentic shopping experiences powered by Shopify merchants, from product discovery to checkout.”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”
   • [probe] “PROBE llms.txt: HTTP 404 at https://shopify.dev/llms.txt”

   proof ↗⚑ flag

   WooCommerce—none0/10

   Evidence shows only single-store integrations (REST API, MCP server, llms.txt for developer docs) that let an agent interact with one WooCommerce store's own data — there is no evidence of a cross-merchant catalog, aggregated product feed, or answer-engine-oriented discovery layer spanning multiple WooCommerce merchants.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.woocommerce.com/llms.txt # WooCommerce Documentation This file contains a list of all documen…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”

   proof ↗⚑ flag

Agent ops

1. ai-native userAn agent can take an order through its post-purchase lifecycle — status, fulfillment, returns — via documented APIs and webhooks without a human in the admin

   weight 2 · round to WooCommerce
   Shopify!disputedcontradicted5/10

   Shopify documents an Order MCP server and Admin/webhooks stack that let an agent fetch order status and fulfillment events ('line items, fulfillment events, and post-purchase adjustments') without human intervention (shopify-docs-45/52, shopify-docs-4/21/43, shopify-docs-31), which covers the status/fulfillment portions of the story well. However, community hands-on reports specifically contradict the returns/refunds piece: 'Want to do refunds? Too bad there's no way to do it via the API' (shopify-comm-9), directly undercutting the vendor's vague 'post-purchase adjustments' claim for the returns lifecycle stage. Missing for 10: an explicit, documented Returns/Refund API or MCP action, and independent confirmation that returns can actually be completed agent-side without admin involvement.

   • [claimed-docs] “Use the Order MCP server to fetch the current state of an order placed through your agent, including line items, fulfillment events, and pos…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [community] “App Charges get added to clients bills, you're not getting paid right away (60+ days in some cases) vs getting paid instantly. If someone do…”

   proof ↗⚑ flag

   WooCommerce~partialclaimed4/10

   WooCommerce's REST API (v3) documents CRUD access to WC data and webhooks for automatic event notifications, which could plausibly cover order status changes, and the Managing Money guide mentions issuing refunds — giving a technical path for agent-driven order lifecycle actions. However, there is no explicit documentation of an orders/returns endpoint, no RMA/returns workflow, and fulfillment is described only via the human-facing dashboard/shipping-label workflow, not an API a fully autonomous agent could drive end-to-end. Missing for 10: explicit order-status/fulfillment REST endpoints, a documented returns/RMA API, and evidence that refunds/fulfillment can be completed via API+webhooks without any admin UI step.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “A webhook is an event notification sent to a URL of your choice. You (or your developer) can configure a webhook that is triggered by events…”
   • [claimed-docs] “This includes topics such as listing transactions, viewing your payouts, issuing refunds to customers, and so on.”
   • [claimed-docs] “our Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing y…”
   • [claimed-docs] “our Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing y…”
   • [claimed-docs] “Carriers verify shipment information during the delivery process and compare the cost paid for the shipping label to the actual cost to ship…”
   • [claimed-docs] “If the amount paid for the label is incorrect, it can result in an adjustment.”

   proof ↗⚑ flag

Agentic checkout

1. ai-native userA shopping agent can discover my store's products and build carts through a documented agent-commerce endpoint on the store (MCP/UCP), not by scraping

   weight 3 · round to Shopify
   Shopify✓fullprobed9/10

   Shopify has documented, first-party agent-commerce endpoints: UCP for agents to authenticate, search catalog, build carts/checkouts, and monitor orders, plus explicit MCP servers for Storefront/Catalog discovery, Cart, Checkout, and Order state — exactly matching the discover-products-and-build-carts-via-documented-endpoint story. This is corroborated by a dedicated probe confirming the official MCP server docs exist. Missing for 10: independent/hands-on third-party validation that an agent successfully used these endpoints in production (only vendor docs and a docs-existence probe, no real-world agent integration report).

   • [claimed-docs] “Build AI agents that authenticate with Shopify, search the Catalog, build carts and checkouts, and monitor orders using the Universal Commer…”
   • [claimed-docs] “Connect any AI assistant to real-time commerce data from Shopify stores with Model Context Protocol (MCP) servers.”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the [Universal Commerce Protocol (UCP)]”
   • [claimed-docs] “Build unified agentic experiences that securely act on behalf of buyers with the Universal Commerce Protocol (UCP)”
   • [claimed-docs] “enables AI agents to search and discover products across the entire Shopify ecosystem”
   • [claimed-docs] “enables AI agents to build and iterate on a cart before the buyer commits to purchase”
   • [claimed-docs] “enables AI agents to create and manage checkout sessions, convert carts into checkouts, and refer buyers to the merchant storefront to compl…”
   • [claimed-docs] “enables AI agents to fetch the current state of an order placed through their agent, including line items, fulfillment events, and post-purc…”
   • [probe] “official MCP server documented at https://shopify.dev/docs/agents”

   proof ↗⚑ flag

   WooCommerce✓fullprobed7/10

   WooCommerce documents native MCP support enabling AI assistants/tools to interact directly with stores via a standardized protocol, and separately exposes Store API endpoints for product listing, search, and cart-to-order conversion — together matching the story of a documented agent-commerce endpoint rather than scraping. Missing for 10: explicit documentation of which MCP tools/endpoints cover product discovery and cart-building specifically, no UCP mention, and no independent/hands-on validation that the MCP server works as described.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [claimed-docs] “The Store API provides public Rest API endpoints for the development of customer-facing cart, checkout, and product functionality.”
   • [claimed-docs] “Obtaining a list of products to display that can be searched or filtered... Converting a customer’s cart to an Order, collecting addresses, …”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to WooCommerce
   Shopify~partialclaimed3/10

   Evidence shows only a narrow bulk capability (creating up to 250 shipping labels at once) and general Admin/GraphQL APIs that could support scripted bulk edits, but there is no documentation of a dedicated bulk-operations API (e.g., bulk product/order import-export) or AI-agent-driven bulk actions across many items. Missing for 10: explicit bulk GraphQL/REST operation endpoints for products/orders/inventory, AI-agent tooling that performs multi-item batch actions, and any hands-on confirmation of bulk automation at scale.

   • [claimed-docs] “Create up to 250 labels at once to process at scale”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”

   proof ↗⚑ flag

   WooCommerce~partialprobed5/10

   WooCommerce exposes a REST API (CRUD via JSON), a CLI (WC-CLI) for command-line store management, and a native MCP server for AI assistants — all of which could be scripted to perform bulk operations across many items — but no evidence explicitly documents batch/bulk endpoints or bulk-processing workflows for AI-native automation. missing for 10: explicit batch/bulk API endpoint documentation, evidence of MCP or CLI actually performing multi-item bulk actions, and any hands-on confirmation of bulk operation performance at scale.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Shopify
   Shopify~partialclaimed5/10

   Shopify's webhook system lets developers subscribe to events and trigger custom actions ('a trigger to perform an additional action after that event has occurred'), which supports event-driven automation, but this requires writing app/webhook code rather than a declarative 'define rules' interface accessible to an AI-native (non-developer) user. Missing for 10: evidence of a native no-code rule builder (e.g., Shopify Flow) with trigger-condition-action UI, and any AI-specific mechanism for autonomously defining such rules.

   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [claimed-docs] “Your code obtains an access token scoped to the permissions it needs.”

   proof ↗⚑ flag

   WooCommerce~partialclaimed4/10

   WooCommerce documents webhooks that fire automatic event notifications to a URL when store events occur, which is a form of event-triggered automation, but there is no native in-product rules engine to define conditional actions (if X then Y) — the actual 'action' logic must live in an external receiver, not within WooCommerce itself. missing for 10: a built-in rules/automation engine for defining conditional actions, first-party workflow/automation tooling beyond webhooks, and independent confirmation of AI-driven rule creation.

   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “A webhook is an event notification sent to a URL of your choice. You (or your developer) can configure a webhook that is triggered by events…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Shopify—none0/10

   Shopify's evidence covers webhooks (event-driven triggers), APIs, MCP/agent tooling, and CLI, but nothing describes scheduling recurring jobs or workflows (e.g., cron-like scheduling, recurring task automation) — webhooks are reactive to events, not time-based recurring schedules. missing for 10: any documentation of a scheduler, recurring job/task API, or workflow automation with time-based triggers.

   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”

   proof ↗⚑ flag

   WooCommerce—none0/10

   WooCommerce offers webhooks, REST API, subscriptions/renewals, and a CLI, but there is no evidence of a scheduler or job orchestration feature for recurring automated workflows in an AI-native sense; nothing in the docs describes cron-like job scheduling or workflow automation.

   ⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Shopify—none0/10

   No evidence in the pack shows Shopify offering versioning, review workflows, or rollback capabilities for automations (e.g., Shopify Flow or similar). The evidence covers CLI, webhooks, APIs, MCP/agent tooling, and themes, but nothing addresses version history, diffing, review/approval, or reverting automation changes.

   ⚑ flag

   WooCommerce—none0/10

   The evidence pack shows WooCommerce's REST API, webhooks, and MCP server integration for AI assistants to interact with store data, but nothing about versioning, reviewing, or rolling back automations or workflows. There's no changelog, audit trail, or rollback mechanism described for any automation actions taken via MCP, API, or webhooks.

   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [claimed-docs] “A webhook is an event notification sent to a URL of your choice. You (or your developer) can configure a webhook that is triggered by events…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”

   proof ↗⚑ flag

B2b

1. merchantSell B2B and wholesale — customer-specific price lists, volume pricing, quotes or net-terms invoicing — alongside DTC

   weight 2 · round to Shopify
   Shopify~partialclaimed5/10

   Shopify explicitly markets a B2B feature set ("Sell to businesses and consumers from one platform... you get all the B2B features you need") but the evidence pack gives no detail on customer-specific price lists, volume/tiered pricing, quoting, or net-terms invoicing — only high-level marketing copy. missing for 10: specifics on price lists, volume pricing tiers, quote workflows, net-terms/invoicing support, and any independent/hands-on confirmation these B2B features work as advertised.

   • [claimed-docs] “Sell to businesses and consumers from one platform. Your business buyers get modern self-serve, and you get all the B2B features you need.”
   • [claimed-docs] “Sell to businesses and consumers from one platform. Your business buyers get modern self-serve”

   proof ↗⚑ flag

   WooCommerce—none0/10

   The evidence pack has no mention of B2B-specific capabilities like customer-specific price lists, volume/tiered pricing, quote requests, or net-terms invoicing; only generic marketplace/extension mentions and general product variation features are cited, none of which address wholesale/B2B commerce specifically.

   ⚑ flag

Catalog

1. merchantModel products with variants, options, and custom fields/metafields that fit my catalog, not a fixed template

   weight 3 · round to WooCommerce
   Shopify—none0/10

   The evidence pack contains no mention of product variants, options, or metafields—core Shopify catalog-modeling features—despite this being a natural axis for an e-commerce platform to be judged on. Only generic API/CLI/theme references are present, none tied to flexible product data modeling.

   ⚑ flag

   WooCommerce~partialclaimed6/10

   WooCommerce docs confirm product variations/attributes (e.g., variable products with color/size attributes), subscriptions, bundles, and simple products with just name/price, plus recent 'variation galleries' improvements, supporting flexible catalog modeling. However, evidence lacks explicit mention of custom fields/metafields support (WooCommerce does support custom product meta natively via WordPress custom fields, but no doc here confirms this) or detail on how flexible/extensible attribute schemas are beyond basic variations. Missing for 10: explicit metafields/custom-fields documentation, evidence of unlimited custom attribute sets beyond simple variations, and independent/hands-on confirmation of complex catalog modeling in practice.

   • [claimed-docs] “Let customers choose from endless product variations, subscription options, single items, or bundles.”
   • [claimed-docs] “In WooCommerce, you can add a product with just a name and a price.”
   • [claimed-docs] “You’ll need to decide which categories to use for organizing and displaying your products... How will you handle products with variations, l…”
   • [claimed-docs] “How will you handle products with variations, like a shirt that comes in different colors? What attributes will you need for these products?”
   • [claimed-docs] “you can sell anything with Woo. Let customers choose from endless product variations, subscription options, single items, or bundles”
   • [claimed-docs] “you can sell anything with Woo. Let customers choose from endless product variations, subscription options, single items, or bundles.”
   • [claimed-docs] “Variation galleries now on for every store, product collection grids alignment improvements, virtual orders drop shipping…”
   • [claimed-docs] “WooCommerce 11.1 is here! Variation galleries now on for every store”
   • [claimed-docs] “WooCommerce 11.1 is here! Variation galleries now on for every store, product collection grids alignment improvements, virtual orders drop s…”

   proof ↗⚑ flag

Catalog ops

1. operations leadBulk import, export, and edit the catalog — CSV or API — without touching products one at a time

   weight 2 · round to WooCommerce
   Shopify~partialcommunity4/10

   The evidence pack has no first-party documentation describing a native CSV import/export or bulk-edit catalog tool; the only support is the general-purpose Admin API (GraphQL) that could be used to build bulk operations (shopify-docs-31, shopify-docs-18) plus a community mention confirming CSV parsing exists but with account-tier restrictions and limited data (shopify-comm-12). This shows the capability likely exists but is thin/gated rather than a clearly documented, frictionless bulk tool. Missing for 10: dedicated first-party docs on native CSV import/export UI, bulk edit tooling, or a specific bulk-catalog API endpoint, and independent hands-on confirmation of smooth large-scale editing.

   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [community] “Shopify is a terrible experience overall, and I wouldn't recommend it for anyone looking to start a quick ecom business online... certain ty…”

   proof ↗⚑ flag

   WooCommerce~partialprobed5/10

   WooCommerce's REST API (docs-11, docs-27, docs-44) supports bulk create/read/update/delete of product data via JSON, and WC-CLI (docs-13, probe-4) lets operations staff manage the store from the command line — both enabling bulk catalog operations without per-product UI clicks. However, the evidence pack never cites WooCommerce's native CSV product importer/exporter (a well-known core feature) or any documentation of CSV-based bulk edit workflows, so the 'CSV' half of the story is unevidenced here. Missing for 10: explicit CSV import/export documentation, evidence of bulk-edit UI/tools beyond API/CLI, and independent confirmation of large-catalog performance.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”

   proof ↗⚑ flag

Inventory

1. operations leadInventory tracks across multiple locations with stock adjustments and fulfillment from the right warehouse

   weight 2 · round drawn
   Shopify—none0/10

   The evidence pack covers apps, APIs, headless storefronts, AI agents/MCP, POS, markets, tax, shipping, B2B, payments, themes and CLI, but contains no mention of multi-location inventory tracking, stock adjustments, or fulfillment routing/warehouse selection logic. Missing for 10: multi-location inventory management docs, stock adjustment workflows, fulfillment-from-nearest-warehouse logic, and any community/hands-on confirmation of these features working.

   ⚑ flag

   WooCommerce—none0/10

   The evidence pack covers products, payments, shipping labels, taxes, APIs, and marketplace extensions, but contains no mention of multi-location/warehouse inventory tracking, per-location stock adjustments, or fulfillment routing logic. WooCommerce's core inventory model (docs-4, docs-23, docs-50) is single-stock-count per product/variation with no multi-warehouse concept documented.

   • [claimed-docs] “In WooCommerce, you can add a product with just a name and a price.”
   • [claimed-docs] “You’ll need to decide which categories to use for organizing and displaying your products... How will you handle products with variations, l…”
   • [claimed-docs] “How will you handle products with variations, like a shirt that comes in different colors? What attributes will you need for these products?”

   proof ↗⚑ flag

Checkout

1. developerCustomize checkout — fields, branding, discounts, and validation logic — through supported extension points rather than forking checkout

   weight 3 · round to WooCommerce
   Shopify~partialclaimed5/10

   Shopify's docs confirm apps can extend checkout ('apps that integrate into...checkout') and market the checkout as 'customizable', and the AI toolkit validates 'Shopify Extensions' against schemas, implying supported checkout extension points exist. However, the evidence pack never names concrete extension mechanisms like checkout UI extensions, checkout branding API, or Shopify Functions for discounts/validation logic that a developer would actually use. Missing for 10: explicit documentation of checkout UI extension APIs, checkout branding/customization API, and Shopify Functions for discount and validation logic, plus independent hands-on confirmation these work without forking checkout.

   • [claimed-docs] “Extend Shopify's core functionality with apps that integrate into Shopify's admin, online store, checkout and more.”
   • [claimed-docs] “The world's highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”
   • [claimed-docs] “The world’s highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”
   • [claimed-docs] “validate GraphQL queries, Liquid templates, and Shopify Extensions against Shopify schemas to catch issues earlier”
   • [claimed-docs] “The toolkit connects your agent to: Developer docs and API schemas... Code validation: validate GraphQL queries, Liquid templates, and Shopi…”

   proof ↗⚑ flag

   WooCommerce~partialclaimed6/10

   WooCommerce documents a general hook system (add_action/filter extension points for templates) and a dedicated Store API for building customer-facing cart/checkout functionality, plus a REST API and marketplace of extensions, all of which support extending checkout without forking core code. However, the evidence pack lacks specifics on checkout-field-level hooks (e.g., field customization/validation filters), discount/coupon extension points, or branding customization guidance specific to checkout — missing for 10: checkout field customization hooks, discount/validation extension documentation, and independent developer corroboration that these extension points suffice for real-world checkout customization.

   • [claimed-docs] “The Store API provides public Rest API endpoints for the development of customer-facing cart, checkout, and product functionality.”
   • [claimed-docs] “Obtaining a list of products to display that can be searched or filtered... Converting a customer’s cart to an Order, collecting addresses, …”
   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “Storefront has a lot of `add_action()` functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core …”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “Grow your business with hundreds of free and paid extensions”

   proof ↗⚑ flag

2. merchantBuyers can pay with accelerated wallets — Apple Pay, Google Pay, PayPal, platform one-click — without re-entering details

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

   Shopify Payments docs claim support for cards, wallets, installments, and crypto, and Shopify Checkout is marketed as a high-converting one-click checkout, implying accelerated wallet support, but no evidence explicitly names Apple Pay, Google Pay, or PayPal integration details or confirms seamless one-click behavior across all wallets. missing for 10: explicit documentation naming Apple Pay/Google Pay/PayPal support, evidence of no re-entry of details, independent/hands-on confirmation of accelerated checkout wallets working as advertised.

   • [claimed-docs] “Accept cards, wallets, installments, and crypto—from day one.”
   • [claimed-docs] “The world's highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”
   • [claimed-docs] “The world’s highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”

   proof ↗⚑ flag

   WooCommerce~partialclaimed4/10

   Docs confirm WooCommerce integrates with 140 region-specific gateways including WooPayments, Stripe, PayPal, Square, and Amazon Pay, which in practice enable wallet-based accelerated checkouts, but no evidence explicitly names Apple Pay or Google Pay support or describes a one-click/no-re-entry checkout experience. missing for 10: explicit documentation of Apple Pay/Google Pay support, description of accelerated/one-click checkout UX, and any hands-on confirmation that details aren't re-entered.

   • [claimed-docs] “there are 140 region-specific gateways to choose from and integrate with, including WooPayments, Stripe, PayPal, Square, and Amazon Pay”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery... there are 140 region…”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery. Beyond the basics, the…”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery. Beyond the basics, the…”

   proof ↗⚑ flag

Conversion

1. merchantAbandoned carts and checkouts trigger recovery emails or links so I can win the sale back

   weight 1 · round drawn
   Shopify—none0/10

   No evidence in the pack mentions abandoned cart/checkout recovery emails or links; the evidence covers APIs, CLI, themes, POS, tax, agents/MCP, and unrelated community complaints, none of which address this specific merchant capability.

   ⚑ flag

   WooCommerce—none0/10

   No evidence pack item mentions abandoned cart recovery, cart abandonment tracking, or automated recovery emails/links; core WooCommerce docs cover payments, shipping, taxes, APIs, and product management but nothing about cart-abandonment recovery workflows (this is typically only available via third-party plugins/extensions not evidenced here).

   ⚑ flag

App dev

1. developerBuild custom apps and extensions with official SDKs, scaffolding tooling, and a documented review/distribution path

   weight 2 · round to Shopify
   Shopify~partialcommunity7/10

   Shopify provides official SDKs (Admin/Storefront GraphQL APIs, officially supported libraries), a CLI for scaffolding apps/themes/headless storefronts, dev stores for testing, webhooks, and auth scopes — solidly documented in shopify.dev evidence. However, the evidence pack lacks explicit documentation of the app review/certification and App Store distribution process, and community reports (a developer's app being banned with vague reasons, terrible partner support/docs) raise real friction around that path. missing for 10: explicit docs on app review criteria/submission process, independent corroboration that the distribution path works smoothly.

   • [claimed-docs] “Initialize new apps, themes, and headless storefronts in an instant with the latest Shopify CLI.”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”
   • [claimed-docs] “Use Shopify's officially supported libraries to build fast, reliable apps with the programming languages and frameworks you already know.”
   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [claimed-docs] “Run the second command to create a new app. Your app will be added as a new subdirectory.”
   • [claimed-docs] “Dev stores are testing environments that you own and control. They let you build and test your apps in a realistic Shopify environment witho…”
   • [community] “For developers this is potentially even worse than it is for merchants, as many Shopify apps simply cannot be migrated to another platform. …”
   • [community] “Shopify is really terrible when it comes to partner support. The documentation is terrible and if you want to use their API, be prepared to …”

   proof ↗⚑ flag

   WooCommerce~partialprobed6/10

   WooCommerce provides official developer resources: a REST API with official JS/PHP/Python/Ruby libraries, a WC-CLI tool, Storefront theme hook system, Storybook integration for UX development, and a public GitHub repo for building extensions, plus a Marketplace for distributing extensions (docs-11, docs-40, docs-13, docs-9, docs-55, woocommerce-gh-1, docs-10). However, there is no documented formal extension review/approval process or dedicated scaffolding/generator tool (e.g., a 'create-extension' CLI) beyond WC-CLI for store management, so the 'scaffolding' and 'review' parts of the story are only thinly evidenced. Missing for 10: explicit extension review/approval criteria, a dedicated project scaffolding generator, and independent developer corroboration of the distribution pipeline.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “The WooCommerce repository also includes Storybook integration that allows testing and developing in a WooCommerce-agnostic context.”
   • [github] “Once you've installed all prerequisites, the following will prepare all of the build outputs necessary for development”
   • [claimed-docs] “Grow your business with hundreds of free and paid extensions”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”

   proof ↗⚑ flag

Apps

1. merchantExtend my store from a marketplace of vetted apps and extensions covering the long tail of features

   weight 3 · round to WooCommerce
   Shopify~partialcommunity7/10

   Shopify documents a robust apps ecosystem (apps.shopify.dev integrating admin/storefront/checkout) and a separate themes marketplace (themes.shopify.com) covering long-tail customization, giving merchants a clear path to extend functionality without custom dev. However, independent community reports raise real friction in this ecosystem — poor partner/API documentation, apps being banned/unmigratable, and API limitations affecting third-party app reliability (shopify-comm-7, shopify-comm-8, shopify-comm-12) — which tempers the 'vetted, frictionless' framing of the story. Missing for 10: first-party data on app review/vetting process, quantified app store size/quality, and independent merchant reviews of app marketplace satisfaction (vs partner-side complaints).

   • [claimed-docs] “Extend Shopify's core functionality with apps that integrate into Shopify's admin, online store, checkout and more.”
   • [claimed-docs] “Fully flexible and regularly updated with Shopify’s latest features”
   • [claimed-docs] “Look for a design with the features you need most, then customize from there”
   • [claimed-docs] “All the essentials —product recommendations, reviews, discounts, and much more”
   • [community] “For developers this is potentially even worse than it is for merchants, as many Shopify apps simply cannot be migrated to another platform. …”
   • [community] “Shopify is really terrible when it comes to partner support. The documentation is terrible and if you want to use their API, be prepared to …”
   • [community] “Shopify is a terrible experience overall, and I wouldn't recommend it for anyone looking to start a quick ecom business online... certain ty…”

   proof ↗⚑ flag

   WooCommerce✓fullcommunity9/10

   WooCommerce's official marketplace explicitly offers 'hundreds of free and paid extensions' plus 140 region-specific payment gateways, covering long-tail feature needs, and this is corroborated by hands-on positive community sentiment. Missing for 10: independent third-party vetting/curation quality analysis and marketplace app review/rating transparency details.

   • [claimed-docs] “Grow your business with hundreds of free and paid extensions”
   • [claimed-docs] “The Woo Marketplace has hundreds of free and paid extensions that add features and functionality to your store”
   • [claimed-docs] “The Woo Marketplace has hundreds of free and paid extensions that add features and functionality to your store.”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery... there are 140 region…”
   • [community] “I have had a lot of fun using woo and I look forward to using it more.”

   proof ↗⚑ flag

Functions

1. developerInject custom backend logic — discounts, shipping rules, validation — as serverless functions or hooks that run inside the platform

   weight 2 · round to WooCommerce
   Shopify—none0/10

   The evidence pack covers Shopify's general app/extension platform (Admin & Storefront APIs, webhooks, extensions validation, UCP/MCP agent tooling) but never mentions Shopify Functions or any serverless-function/hook mechanism specifically for injecting custom discount, shipping, or validation logic that runs inline within checkout or platform processing — webhooks here are explicitly async/near-real-time, not synchronous business-logic hooks. Missing for 10: any documentation of Shopify Functions, function extension points for discounts/shipping/validation, or evidence of in-platform serverless logic execution.

   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events”
   • [claimed-docs] “it can subscribe to Shopify webhook topics as a mechanism for receiving near-real-time data about these events.”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [claimed-docs] “validate GraphQL queries, Liquid templates, and Shopify Extensions against Shopify schemas to catch issues earlier”
   • [claimed-docs] “validate GraphQL queries, Liquid templates, and Shopify Extensions against Shopify schemas to catch issues earlier.”
   • [claimed-docs] “The toolkit connects your agent to: Developer docs and API schemas... Code validation: validate GraphQL queries, Liquid templates, and Shopi…”

   proof ↗⚑ flag

   WooCommerce~partialclaimed5/10

   WooCommerce's architecture is documented as extensible via PHP hooks (add_action/add_filter) that plugins/extensions use to insert custom logic into templates and core flows, and the Marketplace/extensions ecosystem confirms third-party logic can run inside the platform. However, the evidence pack only shows generic Storefront theme hooks and marketplace extension mentions — it does not document WooCommerce's core action/filter hooks specifically for discounts, shipping rules, or validation, nor any serverless/function-as-a-service execution model. Missing for 10: concrete documentation of cart/checkout/shipping filter hooks (e.g., woocommerce_calculate_totals, woocommerce_package_rates) or a serverless functions feature, and independent developer corroboration of using hooks for discount/shipping/validation logic.

   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “Storefront has a lot of `add_action()` functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core …”
   • [claimed-docs] “Storefront has a lot of add_action() functions ... These allow you to insert sections of content using HTML, PHP, Javascript into its core t…”
   • [claimed-docs] “Grow your business with hundreds of free and paid extensions”
   • [claimed-docs] “The Woo Marketplace has hundreds of free and paid extensions that add features and functionality to your store”

   proof ↗⚑ flag

Admin api

1. developerManage the full commerce lifecycle programmatically — create products, edit orders, issue refunds, trigger fulfillments — through the admin API

   weight 3 · round to WooCommerce
   Shopify!disputedcontradicted4/10

   Shopify's Admin API is documented as the mechanism for apps to 'extend and enhance the Shopify admin' with scoped access tokens and webhook triggers for order/fulfillment events (shopify-docs-31, shopify-docs-5, shopify-docs-48, shopify-docs-43), suggesting broad programmatic control over products, orders, and fulfillments. However, a specific hands-on developer report states 'Want to do refunds? Too bad there's no way to do it via the API' (shopify-comm-9), directly contradicting the refund-issuance claim in this story, and other community reports describe partner/API friction and poor documentation (shopify-comm-8, shopify-comm-12). Missing for 10: explicit documentation citing product-creation, order-editing, refund, and fulfillment-trigger endpoints, and independent confirmation resolving the refund-API contradiction.

   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “Your code obtains an access token scoped to the permissions it needs.”
   • [claimed-docs] “its access scopes determine what it can access”
   • [claimed-docs] “Shopify webhooks are useful for keeping your app in sync with Shopify data, or as a trigger to perform an additional action after that event…”
   • [community] “App Charges get added to clients bills, you're not getting paid right away (60+ days in some cases) vs getting paid instantly. If someone do…”
   • [community] “Shopify is really terrible when it comes to partner support. The documentation is terrible and if you want to use their API, be prepared to …”

   proof ↗⚑ flag

   WooCommerce✓fullprobed9/10

   WooCommerce's REST API (v3, versioned under /wp-json/wc/v3/) supports full CRUD on products, orders, and refunds via standard HTTP verbs and JSON, with official client libraries in multiple languages and role-based key scoping; docs explicitly cover refunds and order/fulfillment management, and webhooks allow event-driven triggering. Missing for 10: no independent/hands-on developer corroboration of complex workflows (e.g., fulfillment triggers) beyond vendor docs, and no published OpenAPI spec or deprecation policy for versioning.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [claimed-docs] “our Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing y…”
   • [claimed-docs] “Webhooks let your WooCommerce store send automatic event notifications to a URL of your choice.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.woocommerce.com/openapi.json, https://developer.woocommerce.com/swagger.json, http…”

   proof ↗⚑ flag

Headless

1. developerBuild a fully custom headless storefront on a documented storefront API or first-party frontend framework

   weight 3 · round to Shopify
   Shopify✓fullclaimed9/10

   Shopify offers a documented Storefront GraphQL API for building custom experiences on any platform (web, apps, games) plus Hydrogen, a first-party React-based headless commerce framework with hosting via Oxygen, and CLI tooling to scaffold headless storefronts. This is well-documented first-party capability with quarterly-versioned APIs and dev-store testing support. Missing for 10: independent hands-on developer report specifically validating headless/Hydrogen storefront build experience (community evidence present is about general API/app dev friction, not headless storefronts specifically).

   • [claimed-docs] “Get all the power of Shopify under the hood, with complete control over the frontend. Start building quickly with Hydrogen”
   • [claimed-docs] “The API offers a full range of commerce options making it possible for customers to view products and collections, add products to a cart, a…”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [claimed-docs] “Build fast with Shopify's all-in-one solution for custom commerce. Hosting included.”
   • [claimed-docs] “Help merchants express their unique brand by building a custom theme or Hydrogen storefront.”
   • [claimed-docs] “Shopify releases new API versions on a predictable quarterly schedule, giving you time to adopt changes before older versions are retired. S…”
   • [claimed-docs] “Dev stores are testing environments that you own and control. They let you build and test your apps in a realistic Shopify environment witho…”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”

   proof ↗⚑ flag

   WooCommerce✓fullprobed8/10

   WooCommerce documents both a full REST API (v3, with official JS/PHP/Python/Ruby libraries) and a dedicated Store API purpose-built for headless cart/checkout/product frontends, enabling a fully custom headless storefront to be built against documented, versioned endpoints. Missing for 10: no first-party official headless frontend framework/starter kit evidenced, and no independent hands-on report confirming a production headless build.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “The Store API provides public Rest API endpoints for the development of customer-facing cart, checkout, and product functionality.”
   • [claimed-docs] “Obtaining a list of products to display that can be searched or filtered... Converting a customer’s cart to an Order, collecting addresses, …”
   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.woocommerce.com/openapi.json, https://developer.woocommerce.com/swagger.json, http…”

   proof ↗⚑ flag

Channels

1. merchantList and sync products to external channels — marketplaces, social commerce, shopping feeds — from one catalog

   weight 2 · round to Shopify
   Shopify~partialclaimed3/10

   Evidence only hints at multi-channel capability ('Orders from all your sales channels in one place', 'Sell online, in person, and in AI chats') without explicitly documenting catalog sync to marketplaces, social commerce platforms, or shopping feeds. Missing for 10: explicit docs on Facebook/Instagram/TikTok/Google Shopping/Amazon channel apps, product feed sync mechanics, and any independent confirmation of catalog consistency across channels.

   • [claimed-docs] “Orders from all your sales channels in one place”
   • [claimed-docs] “Sell online, in person, and in AI chats”

   proof ↗⚑ flag

   WooCommerce—none0/10

   The evidence pack mentions a general extensions marketplace and REST/Store APIs, but nothing documents native or extension-based syncing of a single catalog to external marketplaces, social commerce channels, or shopping feeds (e.g., Google Shopping, Facebook/Instagram, Amazon). Missing for 10: any documentation of channel-sync extensions or feed integrations, evidence of catalog export/sync workflows, or hands-on confirmation of multi-channel listing.

   • [claimed-docs] “Grow your business with hundreds of free and paid extensions”
   • [claimed-docs] “The Woo Marketplace has hundreds of free and paid extensions that add features and functionality to your store”
   • [claimed-docs] “The Woo Marketplace has hundreds of free and paid extensions that add features and functionality to your store.”

   proof ↗⚑ flag

Global

1. merchantSell internationally with localized storefronts, multi-currency pricing, translations, and duties handled

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

   Shopify Markets docs explicitly support selling to multiple markets from one store, market-specific pricing previews, and automated tax/duty-style compliance (sales tax automation, filing) plus shipping label bulk creation, all first-party. However, the evidence pack never explicitly mentions storefront translation tooling or international duties/customs handling by name, only tax automation for US sales tax. missing for 10: explicit evidence of translation/localization tooling, explicit duties/customs handling documentation, independent/hands-on confirmation of multi-currency and localized storefront experience.

   • [claimed-docs] “Sell to multiple markets, all from a single store”
   • [claimed-docs] “Preview what people in your different markets see and confirm they're getting the right products and pricing.”
   • [claimed-docs] “Get a holistic overview of all your markets, zoom in for details, and make updates—all in one place.”
   • [claimed-docs] ““View as” customers in each market - Preview what people in your different markets see and confirm they're getting the right products and pr…”
   • [claimed-docs] “Take the stress out of sales tax in the United States with automated calculations, liability insights, and filing—right in your admin.”
   • [claimed-docs] “Automate filing and remittance in just a few steps”
   • [claimed-docs] “automated calculations, liability insights, and filing—right in your admin”
   • [claimed-docs] “Create up to 250 labels at once to process at scale”
   • [claimed-docs] “Orders from all your sales channels in one place”

   proof ↗⚑ flag

   WooCommerce—none0/10

   The evidence pack shows tax setup, shipping, and payment gateway docs, but contains no mention of multi-currency pricing, localized/translated storefronts, or international duties/customs handling — the core elements of this story are absent. This is a fair question for an e-commerce platform (many competitors ship native multi-currency/localization), so it applies, but no supporting evidence exists.

   ⚑ flag

Pos

1. merchantSell in person with a point-of-sale that shares the same catalog, inventory, and customers as my online store

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

   Shopify explicitly markets POS (shopify-docs-9, shopify-docs-26) as unifying sales channels, backed by 'Sell online, in person, and in AI chats' (shopify-docs-55) and 'orders from all your sales channels in one place' (shopify-docs-57), implying a shared catalog/order backend across online and in-person selling. However, there's no specific evidence detailing shared inventory sync mechanics, shared customer profiles across channels, or hands-on/independent confirmation that POS and online store data stay unified in practice. Missing for 10: explicit documentation of shared inventory sync, unified customer records across POS and online store, and independent/hands-on verification of this multi-channel consistency.

   • [claimed-docs] “From first sale to full scale, today’s best brands run on Shopify’s POS system.”
   • [claimed-docs] “From first sale to full scale, today's best brands run on Shopify's POS system.”
   • [claimed-docs] “Sell online, in person, and in AI chats”
   • [claimed-docs] “Orders from all your sales channels in one place”

   proof ↗⚑ flag

   WooCommerce—none0/10

   The evidence pack contains no mention of a point-of-sale product, in-person selling, or POS-catalog sync capability for WooCommerce; all evidence covers online store features (payments, shipping, taxes, APIs, mobile app for managing the online store). This is a fair axis for an ecommerce platform, but no evidence shows WooCommerce delivers it, so it is 'none' rather than 'na'.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to WooCommerce
   Shopify!disputedcontradicted4/10

   Shopify's docs describe broad Admin/Storefront/GraphQL APIs claimed to cover apps, storefronts, checkout, and even agentic commerce (UCP/MCP) — suggesting near-full UI parity via API. However, concrete hands-on community reports contradict full parity: one developer states 'Want to do refunds? Too bad there's no way to do it via the API,' and another reports that 'certain types of accounts are required to access certain parts of the API,' forcing merchants into limited CSV workarounds, plus reports that Shopify has killed features 'with no alternative way to achieve the removed functionality' via API. missing for 10: independent verification of full UI-API parity, resolution of the refund-API gap, and confirmation that account-tier API restrictions have been lifted.

   • [claimed-docs] “The Admin API lets you build apps and integrations that extend and enhance the Shopify admin.”
   • [claimed-docs] “The API offers a full range of commerce options making it possible for customers to view products and collections, add products to a cart, a…”
   • [claimed-docs] “Create unique customer experiences with the Storefront API on any platform, including the web, apps, and games.”
   • [community] “App Charges get added to clients bills, you're not getting paid right away (60+ days in some cases) vs getting paid instantly. If someone do…”
   • [community] “Shopify is a terrible experience overall, and I wouldn't recommend it for anyone looking to start a quick ecom business online... certain ty…”
   • [community] “If you're not American, you will be forced to hand over 3% of your 80% revenue cut to PayPal (unless your MRR cut is >$30k). Sometimes Shopi…”

   proof ↗⚑ flag

   WooCommerce~partialprobed7/10

   WooCommerce documents a broad, versioned REST API (products, orders, customers, refunds, webhooks, coupons), a separate Store API for cart/checkout, an official WC-CLI, and even native MCP support for AI agents — strong evidence of API-driven parity with the UI. However, the docs don't confirm 1:1 coverage for every admin UI action (e.g., full store-setup wizard, extension marketplace management, granular tax/shipping configuration screens), and there's no independent hands-on test confirming complete UI/API parity. Missing for 10: explicit documentation or independent verification that every admin-UI setting/workflow (not just core commerce objects) is exposed via API, and confirmation of parity for extension-specific UI features.

   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “The Store API provides public Rest API endpoints for the development of customer-facing cart, checkout, and product functionality.”
   • [claimed-docs] “WooCommerce CLI (WC-CLI) offers an efficient way to manage WooCommerce (WC) stores via the command line.”
   • [claimed-docs] “WooCommerce includes native support for the Model Context Protocol (MCP), enabling AI assistants and tools to interact directly with WooComm…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “Official libraries: JavaScript Library, PHP Library, Python Library, Ruby Library”
   • [claimed-docs] “Use of the REST API with the generated keys will conform to that user's WordPress roles and capabilities. Choose the level of access for thi…”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”
   • [probe] “official MCP server documented at https://developer.woocommerce.com/docs/features/mcp/”
   • [probe] “official CLI documented at https://developer.woocommerce.com/docs/category/wc-cli/”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to WooCommerce
   Shopify—none0/10

   Shopify's evidence pack contains no documentation of a comprehensive data-export feature in open/standard formats, and community reports (shopify-comm-7, shopify-comm-12) describe migration friction — apps that can't be ported to other platforms and merchants limited to CSV exports 'with limited amount of information.' There is no first-party claim of full open-format export, so the axis applies but is unmet.

   • [community] “For developers this is potentially even worse than it is for merchants, as many Shopify apps simply cannot be migrated to another platform. …”
   • [community] “Shopify is a terrible experience overall, and I wouldn't recommend it for anyone looking to start a quick ecom business online... certain ty…”

   proof ↗⚑ flag

   WooCommerce~partialclaimed6/10

   WooCommerce is self-hosted and open-source, with explicit messaging about 'full control of your data' and a REST API (JSON, versioned, documented) that allows programmatic export of products, orders, and customer data. However, evidence shows migration guides only for moving data *into* WooCommerce, not exporting/leaving, and no explicit CSV/data-portability export tool or 'leave the platform' guide is documented. Missing for 10: explicit data-export/portability documentation for leaving the platform, evidence of built-in CSV/data dump tools, and independent confirmation that a full data export actually works in open non-proprietary formats.

   • [claimed-docs] “WooCommerce is the open-source commerce platform for WordPress that gives you full control: of your checkout, your data, your costs.”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “This allows WC data to be created, read, updated, and deleted using requests in JSON format and using WordPress REST API Authentication meth…”
   • [claimed-docs] “WooCommerce (WC) 2.6+ is fully integrated with the WordPress REST API. This allows WC data to be created, read, updated, and deleted using r…”
   • [claimed-docs] “Ready to switch platforms? Our migration guides help you confidently move your store to WooCommerce... transfer your data, and unlock the fl…”
   • [claimed-docs] “Ready to switch platforms? Our migration guides help you confidently move your store to WooCommerce.”
   • [claimed-docs] “WooCommerce REST API Documentation - WP REST API v3 — all endpoints are versioned under the /wp-json/wc/v3/ prefix (e.g. GET /wp-json/wc/v3/…”

   proof ↗⚑ flag

3. ai-native userSelf-host the core product

   weight 3 · round to WooCommerce
   Shopify—none0/10

   Shopify is a fully hosted, proprietary commerce SaaS platform; even its 'headless' storefront option explicitly advertises 'Hosting included' (shopify-docs-33), meaning there is no way to run the core Shopify platform on your own infrastructure. No evidence anywhere in the pack shows an open-source or self-hostable core product, unlike competitor platforms in this category that do offer that option.

   • [claimed-docs] “Build fast with Shopify's all-in-one solution for custom commerce. Hosting included.”
   • [claimed-docs] “Get all the power of Shopify under the hood, with complete control over the frontend.”
   • [claimed-docs] “Get all the power of Shopify under the hood, with complete control over the frontend. Start building quickly with Hydrogen”

   proof ↗⚑ flag

   WooCommerce✓fullclaimed9/10

   WooCommerce is explicitly described as an open-source commerce platform giving 'full control of your checkout, your data, your costs,' and the GitHub repo shows the buildable source code (self-hosted on WordPress), plus migration guides for moving your store confirm self-hosting is core to the product's design. Missing for 10: no independent hands-on report confirming a full self-hosted deployment walkthrough.

   • [claimed-docs] “WooCommerce is the open-source commerce platform for WordPress that gives you full control: of your checkout, your data, your costs.”
   • [github] “Once you've installed all prerequisites, the following will prepare all of the build outputs necessary for development”
   • [claimed-docs] “Ready to switch platforms? Our migration guides help you confidently move your store to WooCommerce... transfer your data, and unlock the fl…”
   • [claimed-docs] “If you have a WordPress site, adding Woo takes just minutes!”

   proof ↗⚑ flag

Processing

1. merchantChoose among third-party payment gateways and charge in multiple currencies when the built-in option doesn't fit

   weight 2 · round to WooCommerce
   Shopify!disputedcontradicted4/10

   Shopify docs confirm multi-currency selling via Markets (shopify-docs-10, shopify-docs-16, shopify-docs-37) and payment flexibility (shopify-docs-14), implying third-party gateway support exists, but concrete community evidence shows real friction: Shopify charges an extra 1% fee for using third-party payment gateways instead of Shopify Payments (shopify-comm-6), and merchants report Shopify's own Payment module overrides and disables standalone third-party integrations like Stripe without clear warning (shopify-comm-11), directly undercutting the 'freely choose a third-party gateway' promise. missing for 10: first-party documentation of specific supported third-party gateways and fee structure, independent confirmation that third-party gateways work without penalty on standard plans.

   • [claimed-docs] “Accept cards, wallets, installments, and crypto—from day one.”
   • [claimed-docs] “Sell to multiple markets, all from a single store”
   • [claimed-docs] “Preview what people in your different markets see and confirm they're getting the right products and pricing.”
   • [claimed-docs] “Get a holistic overview of all your markets, zoom in for details, and make updates—all in one place.”
   • [community] “Shopify charges additional 1% per transaction for 3rd party payment integrations. Weird.”
   • [community] “Worth mentioning Shopify uses Stripe. A few months back they introduced their Shopify Payment Module which runs on Stripe, which then overri…”

   proof ↗⚑ flag

   WooCommerce~partialclaimed6/10

   Docs confirm WooCommerce bundles basic payment methods (cards, BACS, checks, COD) plus access to 140 region-specific third-party gateways (WooPayments, Stripe, PayPal, Square, Amazon Pay), showing strong third-party gateway choice. However, evidence does not explicitly document multi-currency charging/checkout support (this typically requires separate extensions), so the 'charge in multiple currencies' half of the story is unevidenced. Missing for 10: explicit multi-currency checkout/gateway documentation, independent/hands-on confirmation of gateway switching working smoothly.

   • [claimed-docs] “there are 140 region-specific gateways to choose from and integrate with, including WooPayments, Stripe, PayPal, Square, and Amazon Pay”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery... there are 140 region…”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery. Beyond the basics, the…”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery. Beyond the basics, the…”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery.”

   proof ↗⚑ flag

2. merchantTake payments with the platform's integrated processing — published card rates, payouts, and fraud tooling — without wiring a third-party gateway

   weight 3 · round to Shopify
   Shopify~partialcommunity6/10

   Shopify Payments is documented as the native, no-third-party-gateway option ('Accept cards, wallets, installments, and crypto—from day one' — shopify-docs-14) and the checkout it powers is highlighted as high-converting (shopify-docs-25/40), but the evidence pack contains no first-party page on published card-processing rates or dedicated fraud-tooling (e.g. Shopify Fraud Filter) documentation. Community reports also surface real friction with the payouts side of the integrated system (random payout freezes over address verification — shopify-comm-4; extra 1% fee if you opt for a 3rd-party gateway instead — shopify-comm-6), which are caveats rather than proof the native processing doesn't work. Missing for 10: explicit published rate-card documentation, dedicated fraud-detection tooling docs, and independent corroboration of payout reliability.

   • [claimed-docs] “Accept cards, wallets, installments, and crypto—from day one.”
   • [claimed-docs] “The world's highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”
   • [claimed-docs] “The world’s highest-converting, customizable, one-click checkout powers 12% of US ecommerce and is trusted by the biggest brands.”
   • [community] “Shopify would randomly stop payouts every 3-4 months or so because they needed to re-verify our owner address information. Apparently, most …”
   • [community] “Shopify charges additional 1% per transaction for 3rd party payment integrations. Weird.”

   proof ↗⚑ flag

   WooCommerce~partialclaimed5/10

   WooPayments is documented as Woo's own integrated payment solution with transaction listing, payouts, and refunds handled directly in the dashboard (woocommerce-docs-5/24/37/43/52), which supports the 'no third-party gateway' framing. However, the evidence never publishes concrete card processing rates or documents dedicated fraud-prevention/chargeback tooling — the docs only gesture at 'managing money' generally, and WooCommerce's broader payments story explicitly leans on 140 external gateways (docs-1/18/41/47) rather than emphasizing WooPayments exclusivity. Missing for 10: published card rate sheet, explicit fraud/dispute tooling documentation, and confirmation WooPayments avoids third-party processor plumbing entirely.

   • [claimed-docs] “This includes topics such as listing transactions, viewing your payouts, issuing refunds to customers, and so on.”
   • [claimed-docs] “our Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing y…”
   • [claimed-docs] “our Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing y…”
   • [claimed-docs] “Managing Money guide explains how money can flow into and out of your site. This includes topics such as listing transactions, viewing your …”
   • [claimed-docs] “Once WooPayments is up and running, our Managing Money guide explains how money can flow into and out of your site.”
   • [claimed-docs] “there are 140 region-specific gateways to choose from and integrate with, including WooPayments, Stripe, PayPal, Square, and Amazon Pay”
   • [claimed-docs] “Woo comes bundled with the ability to accept major credit cards, bank transfers (BACS), checks, and cash on delivery... there are 140 region…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to WooCommerce
   Shopify—none0/10

   No evidence in the pack addresses data residency, regional storage choice, or data sovereignty controls for merchant/store data; the 'markets' features refer to selling regions, not data storage location. Missing for 10: any documentation of data center/region selection, residency guarantees, or compliance controls (e.g. GDPR data localization) for AI-native users.

   ⚑ flag

   WooCommerce~partialclaimed4/10

   WooCommerce is self-hosted on WordPress, so by nature the store owner controls the hosting infrastructure and therefore the physical location of data — docs-16 states WooCommerce gives 'full control of your data.' However, there is no explicit first-party documentation of region-selection controls, data-residency settings, or compliance tooling addressing where data is stored. missing for 10: explicit data-residency/region-selection documentation, compliance certifications (e.g., GDPR data location controls), and any admin-facing region config feature.

   • [claimed-docs] “WooCommerce is the open-source commerce platform for WordPress that gives you full control: of your checkout, your data, your costs.”

   proof ↗⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Shopify—none0/10

   No evidence in the pack addresses data retention or deletion controls for merchants, developers, or AI agents interacting with Shopify data; the documentation excerpts focus on APIs, commerce features, and agent/MCP integrations but never mention data retention policies, deletion requests, or privacy controls.

   ⚑ flag

   WooCommerce—none0/10

   No evidence pack items address data retention policies, deletion controls, GDPR-style export/erasure tools, or AI-specific data lifecycle controls; REST API docs describe generic CRUD capability but not a data retention/deletion governance feature. This axis applies to an e-commerce platform handling customer PII, but no documentation demonstrates such controls.

   ⚑ flag

Content

1. merchantManage content — pages, blogs, media — alongside my products from the same admin

   weight 1 · round to WooCommerce
   Shopify—none0/10

   The evidence pack covers apps, APIs, headless storefronts, themes, POS, tax, shipping, B2B, payments, and AI/MCP tooling, but contains no mention of built-in admin features for managing pages, blog posts, or media content alongside products. No citation supports this specific content-management-in-admin capability.

   ⚑ flag

   WooCommerce~partialclaimed5/10

   WooCommerce is built as a plugin on top of WordPress, and docs confirm this tight integration ("open-source commerce platform for WordPress," "If you have a WordPress site, adding Woo takes just minutes"), which implies the WordPress admin (with its native Pages, Posts/blog, and Media Library) is shared with product management. Storefront theme docs also show content can be inserted into store templates via hooks. However, no evidence explicitly describes a unified admin workflow for managing blog posts, pages, and media alongside products, or shows this in a hands-on merchant walkthrough. Missing for 10: explicit documentation or screenshots of managing WordPress pages/posts/media from the same dashboard as products, and independent confirmation of this workflow.

   • [claimed-docs] “WooCommerce is the open-source commerce platform for WordPress that gives you full control: of your checkout, your data, your costs.”
   • [claimed-docs] “If you have a WordPress site, adding Woo takes just minutes!”
   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “Storefront has a lot of `add_action()` functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core …”

   proof ↗⚑ flag

Theme dev

1. developerCustomize storefront code with a documented templating layer, local preview, and version-controlled theme deploys

   weight 2 · round to WooCommerce
   Shopify~partialclaimed5/10

   Shopify's CLI documentation confirms it can initialize and work with themes (shopify-docs-3, shopify-docs-17, shopify-docs-30) and Liquid is referenced as the templating layer validated by tooling (shopify-docs-8, shopify-docs-22, shopify-docs-35), plus a theme marketplace for customization (shopify-docs-15, shopify-docs-23). However, the evidence never explicitly documents a 'theme dev' local preview server, git-based/version-controlled theme deploy workflow, or push/pull staging process — dev-store evidence (shopify-docs-x2) only covers app dev, not theme dev specifically. Missing for 10: explicit local theme preview command documentation, explicit version-controlled/staged theme deployment workflow, and independent hands-on confirmation of the theme dev loop.

   • [claimed-docs] “Initialize new apps, themes, and headless storefronts in an instant with the latest Shopify CLI.”
   • [claimed-docs] “Shopify CLI is a command-line interface tool that helps you generate and work with Shopify apps, themes and custom storefronts.”
   • [claimed-docs] “Fully flexible and regularly updated with Shopify’s latest features”
   • [claimed-docs] “Look for a design with the features you need most, then customize from there”
   • [claimed-docs] “validate GraphQL queries, Liquid templates, and Shopify Extensions against Shopify schemas to catch issues earlier”
   • [claimed-docs] “validate GraphQL queries, Liquid templates, and Shopify Extensions against Shopify schemas to catch issues earlier.”
   • [claimed-docs] “Dev stores are testing environments that you own and control. They let you build and test your apps in a realistic Shopify environment witho…”

   proof ↗⚑ flag

   WooCommerce~partialclaimed6/10

   WooCommerce/Storefront documents a genuine templating layer (add_action hooks for HTML/PHP/JS insertion into core templates) and the GitHub repo shows a local build process plus Storybook integration for developing/testing in isolation, giving developers a documented customization and local-preview path. However there is no explicit documentation of a version-controlled theme deployment workflow (e.g., CI/CD, staging-to-production theme push) — that relies on generic WordPress/Git practices not directly evidenced here. Missing for 10: documented deployment/versioning workflow for themes, explicit local preview tooling beyond Storybook, end-to-end example of a version-controlled theme release.

   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “Storefront has a lot of `add_action()` functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core …”
   • [claimed-docs] “Storefront has a lot of add_action() functions ... These allow you to insert sections of content using HTML, PHP, Javascript into its core t…”
   • [claimed-docs] “The WooCommerce repository also includes Storybook integration that allows testing and developing in a WooCommerce-agnostic context.”
   • [github] “Once you've installed all prerequisites, the following will prepare all of the build outputs necessary for development”
   • [claimed-docs] “WooCommerce introduces Purple, its first official block theme for beta testing, offering extensive customization options and modern template…”

   proof ↗⚑ flag

Themes

1. merchantLaunch a polished storefront from professionally designed themes and customize layout, sections, and branding without code

   weight 3 · round to Shopify
   Shopify✓fullcommunity8/10

   Shopify provides a theme store with professionally designed, customizable themes (docs-15, docs-23, docs-24, docs-54) explicitly aimed at no-code branding/layout customization ('Design fast with AI. Pick a prebuilt theme... customize from there'), backed by scale-tested credibility from long-time users (shopify-comm-3). missing for 10: hands-on/independent review specifically validating the theme editor's no-code UX (customizer drag-drop experience), and some community commentary criticizes overall dev experience/documentation quality which slightly tempers confidence.

   • [claimed-docs] “Fully flexible and regularly updated with Shopify’s latest features”
   • [claimed-docs] “Look for a design with the features you need most, then customize from there”
   • [claimed-docs] “Design fast with AI. Pick a prebuilt theme. Or go totally custom.”
   • [claimed-docs] “All the essentials —product recommendations, reviews, discounts, and much more”
   • [community] “We've been running e-commerce for six years, and have tried everything (woocommerce, open commerce, bigcommerce, magento, prestashop). They …”

   proof ↗⚑ flag

   WooCommerce~partialclaimed5/10

   WooCommerce offers designed themes (Storefront, and the new block theme 'Purple' with 'extensive customization options and modern templates') and initial setup guidance around homepage design, menus, and site structure, suggesting a storefront can be launched and styled. However, the core documented customization mechanism for Storefront explicitly requires inserting HTML/PHP/JavaScript via add_action() hooks, which is code-based rather than no-code, and evidence for genuine no-code block-editor customization (drag-and-drop sections, branding controls) is thin and limited to a single beta announcement. Missing for 10: detailed no-code section/layout editor documentation, evidence of drag-and-drop branding tools, and independent hands-on confirmation that non-developers can fully customize without code.

   • [claimed-docs] “Storefront has a lot of add_action() functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core te…”
   • [claimed-docs] “Storefront has a lot of `add_action()` functions... These allow you to insert sections of content using HTML, PHP, Javascript into its core …”
   • [claimed-docs] “Storefront has a lot of add_action() functions ... These allow you to insert sections of content using HTML, PHP, Javascript into its core t…”
   • [claimed-docs] “WooCommerce introduces Purple, its first official block theme for beta testing, offering extensive customization options and modern template…”
   • [claimed-docs] “The first decisions you need to make when setting up a store are about homepage design, menus, site structure... If you have a WordPress sit…”
   • [claimed-docs] “The first decisions you need to make when setting up a store are about homepage design, menus, site structure, and payment and shipping opti…”

   proof ↗⚑ flag

Shipping

1. operations leadCheckout shows live carrier rates and I can buy labels and track shipments from the platform

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

   Shopify Shipping docs confirm label creation at scale (up to 250 labels) and order aggregation across sales channels, which implies carrier rate access and label purchasing, but the evidence doesn't explicitly confirm live carrier rate display at checkout or in-platform shipment tracking. Missing for 10: explicit documentation of live carrier rate calculation shown at checkout, and dedicated tracking/label-purchase workflow details beyond marketing copy.

   • [claimed-docs] “Create up to 250 labels at once to process at scale”
   • [claimed-docs] “Orders from all your sales channels in one place”

   proof ↗⚑ flag

   WooCommerce~partialclaimed5/10

   WooCommerce marketing docs claim 'live shipping rates from leading carriers' and 'options to print labels at home' bundled with the platform, but the shipping doc itself only discusses label cost verification, not a live-rate/checkout integration or tracking dashboard, and label printing/live rates in practice typically require third-party extensions (e.g., WooCommerce Shipping) not detailed here. Missing for 10: concrete documentation of the checkout carrier-rate integration flow, label purchase workflow details, and shipment tracking UI, plus independent/hands-on confirmation this works out-of-the-box.

   • [claimed-docs] “Save time with automated tax calculations, live shipping rates from leading carriers, options to print labels at home”
   • [claimed-docs] “Save time with automated tax calculations, live shipping rates from leading carriers, options to print labels at home, and the mobile app fo…”
   • [claimed-docs] “options to print labels at home, and the mobile app for iOS and Android”
   • [claimed-docs] “Carriers verify shipment information during the delivery process and compare the cost paid for the shipping label to the actual cost to ship…”
   • [claimed-docs] “If the amount paid for the label is incorrect, it can result in an adjustment.”

   proof ↗⚑ flag

Taxes

1. merchantSales tax and VAT are calculated automatically per jurisdiction, with rates kept current and reports I can file from

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

   Shopify Tax provides automated sales tax calculations, liability insights, and automated filing/remittance, explicitly for the United States, positioned as a first-party admin feature. However, evidence does not confirm VAT handling or international jurisdiction coverage, nor independent corroboration of accuracy/reliability of filing. missing for 10: VAT/international tax calculation and filing evidence, rate-currency guarantees, third-party/independent validation of accuracy, and any hands-on confirmation of the filing workflow.

   • [claimed-docs] “Take the stress out of sales tax in the United States with automated calculations, liability insights, and filing—right in your admin.”
   • [claimed-docs] “Automate filing and remittance in just a few steps”
   • [claimed-docs] “automated calculations, liability insights, and filing—right in your admin”

   proof ↗⚑ flag

   WooCommerce~partialclaimed4/10

   WooCommerce docs mention 'automated tax calculations' as a marketing feature and a core guide for enabling/configuring taxes and adding tax rates, but the evidence pack shows only manual tax-rate table setup, not per-jurisdiction automatic rate updates, VAT-specific handling, or built-in filing-ready tax reports. Missing for 10: evidence of automatic jurisdiction rate updates (e.g. via a tax service integration), VAT-specific compliance handling, and generation of filing-ready tax reports.

   • [claimed-docs] “This guide explains how to enable and configure taxes in WooCommerce, add tax rates, and understand each available setting.”
   • [claimed-docs] “Save time with automated tax calculations, live shipping rates from leading carriers, options to print labels at home”
   • [claimed-docs] “Save time with automated tax calculations, live shipping rates from leading carriers, options to print labels at home, and the mobile app fo…”

   proof ↗⚑ flag