Medusa vs WooCommerce

Agent access

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

   weight 2 · round drawn
   Medusa✓fullprobed9/10

   Medusa has a verified live llms.txt file (HTTP 200) describing the platform for AI agents, plus a documented official MCP server for querying docs directly from AI tools/IDEs like Cursor, confirming agent-oriented documentation access is a first-class supported pathway. Missing for 10: independent third-party confirmation of agents successfully using llms.txt in practice beyond the probe check.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.medusajs.com/llms.txt # Medusa > Medusa is a digital commerce platform with a built-in Framework f…”
   • [claimed-docs] “Medusa hosts a Streamable HTTP MCP server at `https://docs.medusajs.com/mcp` that you can add to AI agents supporting MCP server connections…”
   • [claimed-docs] “The Medusa documentation provides a remote Model Context Protocol (MCP) server that allows you to find information from the Medusa documenta…”
   • [probe] “official MCP server documented at https://docs.medusajs.com/learn/introduction/build-with-llms-ai/mcp-server”

   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 Medusa
   Medusa~partialprobed6/10

   Medusa is explicitly described as a headless commerce platform with an installable open-source npm package and CLI (medusa-comm-3, medusa-gh-2, medusa-probe-4, medusa-docs-29), and cloud tooling references PR previews and background workers suggesting CI/automation support (medusa-docs-11, medusa-docs-30). However there is no explicit documentation of running Medusa in a CI pipeline or automated test/build scripts, and community notes flag unresolved serverless/background-job execution concerns (medusa-comm-2). Missing for 10: dedicated CI/automation guide, evidence of headless test execution, and independent confirmation of serverless/CI deployment working smoothly.

   • [community] “I love the idea of a headless ecommerce platform, especially one that comes with a nice backend GUI for managing inventory. Pleasantly surpr…”
   • [github] “Medusa's core commerce modules are open-source and freely available on npm.”
   • [probe] “official CLI documented at https://docs.medusajs.com/resources/medusa-cli”
   • [claimed-docs] “Medusa MCP and Cloud CLI”
   • [claimed-docs] “Instant previews on PRs”
   • [claimed-docs] “Background workers”
   • [community] “Haven't investigated deploying Medusa to a serverless environment yet. We use background workers to process jobs from a Bull queue that may …”

   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
   Medusa—none0/10

   The evidence only shows Medusa hosting an MCP server (docs.medusajs.com/mcp) that external AI tools like Cursor can connect to for documentation lookup — this is Medusa acting as an MCP server provider, not evidence that Medusa itself can consume/plug in external MCP servers to use their tools. No documentation or community evidence describes Medusa (or its Cloud Development Agent) connecting to external MCP servers as a client.

   • [claimed-docs] “Medusa hosts a Streamable HTTP MCP server at `https://docs.medusajs.com/mcp` that you can add to AI agents supporting MCP server connections…”
   • [claimed-docs] “allows you to find information from the Medusa documentation right in your IDEs or AI tools, such as Cursor”
   • [claimed-docs] “The Medusa documentation provides a remote Model Context Protocol (MCP) server that allows you to find information from the Medusa documenta…”
   • [probe] “official MCP server documented at https://docs.medusajs.com/learn/introduction/build-with-llms-ai/mcp-server”
   • [claimed-docs] “Cloud Development Agent”

   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 Medusa
   Medusa✓fullprobed8/10

   Medusa officially hosts a Streamable HTTP MCP server at docs.medusajs.com/mcp that can be added to MCP-compatible AI agents/tools like Cursor, confirmed by both docs and an independent probe. Missing for 10: independent hands-on report of connecting an agent to it and details on tool/resource coverage beyond documentation lookup.

   • [claimed-docs] “Medusa hosts a Streamable HTTP MCP server at `https://docs.medusajs.com/mcp` that you can add to AI agents supporting MCP server connections…”
   • [claimed-docs] “allows you to find information from the Medusa documentation right in your IDEs or AI tools, such as Cursor”
   • [claimed-docs] “The Medusa documentation provides a remote Model Context Protocol (MCP) server that allows you to find information from the Medusa documenta…”
   • [probe] “official MCP server documented at https://docs.medusajs.com/learn/introduction/build-with-llms-ai/mcp-server”

   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 WooCommerce
   Medusa✓fullprobed6/10

   Medusa ships an official CLI (documented at docs.medusajs.com/resources/medusa-cli) and a separate Cloud CLI referenced in pricing, giving developers and agentic tooling a scriptable interface to manage Medusa projects. Missing for 10: detailed command reference/usage examples, evidence of AI-agent-specific CLI features (e.g., non-interactive/JSON output modes), and independent hands-on confirmation of the CLI beyond doc links.

   • [probe] “official CLI documented at https://docs.medusajs.com/resources/medusa-cli”
   • [claimed-docs] “Medusa MCP and Cloud 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
   Medusa✓fullprobed8/10

   Medusa maintains a full OpenAPI 3.0 spec for its Store and Admin REST APIs (medusa-gh-x1), which powers extensive public documentation for commerce modules (product, cart, order, payment, tax, fulfillment, inventory, sales channel), giving AI-native users a documented, machine-readable API surface to drive the platform programmatically. Missing for 10: independent hands-on confirmation of API usability, and standard discovery endpoints (openapi.json/swagger.json) 404 at the docs root per probe, meaning the spec is only reachable via GitHub rather than a conventional self-describing endpoint.

   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [claimed-docs] “Product Module - Medusa Documentation”
   • [claimed-docs] “Cart Module - Medusa Documentation”
   • [claimed-docs] “Order Module - Medusa Documentation”
   • [claimed-docs] “Payment Module - Medusa Documentation”
   • [claimed-docs] “Tax Module - Medusa Documentation”
   • [claimed-docs] “Fulfillment Module - Medusa Documentation”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.medusajs.com/openapi.json, https://docs.medusajs.com/swagger.json, https://docs.medusaj…”

   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
   Medusa—none0/10

   Evidence shows only generic RBAC/SSO/Audit Logs mentions in pricing tiers, with no documentation of issuing scoped or least-privilege API credentials specifically for AI agents, nor any agent-specific token/key scoping mechanism.

   • [claimed-docs] “RBAC, SSO, Audit Logs”

   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 to WooCommerce
   Medusa—none0/10

   The evidence pack shows Medusa exposes a machine-readable OpenAPI 3.0 spec and various module docs, plus an MCP server and CLI for AI tooling, but there is no citation of an official client SDK (e.g., a maintained JS/TypeScript SDK package) that an AI-native developer could build against. missing for 10: explicit official SDK documentation/package reference, examples of SDK usage, language coverage beyond REST spec.

   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [claimed-docs] “Medusa hosts a Streamable HTTP MCP server at `https://docs.medusajs.com/mcp` that you can add to AI agents supporting MCP server connections…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.medusajs.com/openapi.json, https://docs.medusajs.com/swagger.json, https://docs.medusaj…”

   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
   Medusa~partialclaimed3/10

   Medusa's pricing page lists 'Webhook Events' as a feature, indicating webhook-based event subscription exists, but no documentation details the subscription mechanism, event catalog, or setup process, and no independent/hands-on confirmation is present. Missing for 10: detailed webhook docs, event type catalog, hands-on verification, independent corroboration.

   • [claimed-docs] “Webhook Events”

   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
   Medusa—none0/10

   Evidence only shows an MCP server for querying Medusa's documentation (medusa-docs-4, medusa-docs-33/37) and generic 'guardrails for agents to build customizations' marketing copy — nothing shows Medusa surfacing AI-generated insights or suggestions derived from a merchant's own commerce data (orders, inventory, sales trends). missing for 10: any feature generating insights/recommendations from store data, admin dashboard AI analytics, or product evidence of in-app AI suggestions.

   • [claimed-docs] “Medusa hosts a Streamable HTTP MCP server at `https://docs.medusajs.com/mcp` that you can add to AI agents supporting MCP server connections…”
   • [claimed-docs] “allows you to find information from the Medusa documentation right in your IDEs or AI tools, such as Cursor”
   • [claimed-docs] “The Medusa documentation provides a remote Model Context Protocol (MCP) server that allows you to find information from the Medusa documenta…”
   • [claimed-docs] “Framework - Guardrails for agents to build customizations.”

   proof ↗⚑ 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 to WooCommerce
   Medusa~partialclaimed4/10

   The pricing/docs evidence mentions 'Background workers' and 'Webhook Events' as platform features that could underpin autonomous background automations, and a 'Cloud Development Agent' is referenced, but none of the evidence describes an actual workflow/scheduler/automation-builder interface an AI-native user would configure. Missing for 10: documented workflow/scheduled-job engine, concrete setup instructions for autonomous background automations, and independent confirmation these run unattended.

   • [claimed-docs] “Background workers”
   • [claimed-docs] “Webhook Events”
   • [claimed-docs] “Cloud Development Agent”

   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 to Medusa
   Medusa~partialclaimed2/10

   Medusa's pricing page lists a 'Cloud Development Agent' as an enterprise feature, hinting at some built-in AI assistant capability, but there's no documentation describing what it does, how a user delegates tasks to it, or how it's used within the product UI. The rest of the AI-related evidence (MCP server, 'guardrails for agents') is about external AI coding agents building customizations or IDE tools connecting to docs, not a built-in in-product assistant for end users. Missing for 10: documentation/screenshots of the Cloud Development Agent's actual task-delegation workflow, independent/hands-on confirmation it exists and works, and clarity on how it differs from the developer-facing MCP/CLI tooling.

   • [claimed-docs] “Cloud Development Agent”
   • [claimed-docs] “Medusa MCP and Cloud CLI”
   • [claimed-docs] “Framework - Guardrails for agents to build customizations.”
   • [claimed-docs] “Guardrails for agents to build customizations.”

   proof ↗⚑ 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 to WooCommerce
   Medusa~partialprobed4/10

   Medusa exposes an official MCP server, but it is scoped to searching documentation for AI tools/IDEs, not to operating the commerce platform itself (products, orders, carts) via natural language. Marketing mentions of a 'Cloud Development Agent' and 'guardrails for agents to build customizations' hint at broader agentic operation but are never elaborated with concrete NL-command examples or independent corroboration. Missing for 10: evidence of natural-language commands actually driving store/admin operations, hands-on examples of agentic customization via the guardrails feature, and independent confirmation of the Cloud Development Agent's capabilities.

   • [claimed-docs] “Medusa hosts a Streamable HTTP MCP server at `https://docs.medusajs.com/mcp` that you can add to AI agents supporting MCP server connections…”
   • [claimed-docs] “allows you to find information from the Medusa documentation right in your IDEs or AI tools, such as Cursor”
   • [claimed-docs] “The Medusa documentation provides a remote Model Context Protocol (MCP) server that allows you to find information from the Medusa documenta…”
   • [claimed-docs] “Cloud Development Agent”
   • [claimed-docs] “Framework - Guardrails for agents to build customizations.”
   • [claimed-docs] “Medusa MCP and Cloud CLI”
   • [probe] “official MCP server documented at https://docs.medusajs.com/learn/introduction/build-with-llms-ai/mcp-server”

   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 Medusa
   Medusa~partialprobed5/10

   Medusa maintains full OpenAPI 3.0 specs for its Store/Admin REST APIs that power a hosted docs.medusajs.com/api reference, indicating a structured, machine-readable API reference exists, but the evidence pack has no confirmation of 'try it out' style runnable request execution in that reference, and a direct openapi.json endpoint probe returned 404s. missing for 10: explicit documentation/screenshot of an interactive 'run this request' feature in the API reference, independent confirmation of a Swagger/Redoc-style try-it-out UI.

   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.medusajs.com/openapi.json, https://docs.medusajs.com/swagger.json, https://docs.medusaj…”

   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 to Medusa
   Medusa~partialprobed7/10

   Medusa maintains a full OpenAPI 3.0 spec for its Store and Admin REST APIs in the medusajs/medusa GitHub repo, which powers docs.medusajs.com/api and is directly downloadable as a raw YAML file (medusa-gh-x1). However, a runtime probe found no discoverable/conventional endpoint like openapi.json or swagger.json on the docs domain itself (medusa-probe-2), meaning users must know to fetch it from GitHub rather than a standard machine-readable discovery path. Missing for 10: a documented, directly-linked download endpoint on the docs site itself, and confirmation the spec is kept in sync/versioned for consumers outside the repo.

   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.medusajs.com/openapi.json, https://docs.medusajs.com/swagger.json, https://docs.medusaj…”

   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 drawn
   Medusa—none0/10

   While Medusa's self-hosted architecture and 'Instant previews on PRs' (medusa-docs-11) suggest general dev/staging capabilities, there is no evidence of a dedicated sandbox environment specifically for AI-native testing against non-production data (e.g., a test mode for the MCP server or API keys scoped to sandbox data). missing for 10: explicit sandbox/test environment documentation, AI-agent-specific test mode, isolation guarantees separating sandbox from production data.

   • [claimed-docs] “Instant previews on PRs”
   • [claimed-docs] “Medusa hosts a Streamable HTTP MCP server at `https://docs.medusajs.com/mcp` that you can add to AI agents supporting MCP server connections…”

   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 WooCommerce
   Medusa—none0/10

   There's an OpenAPI spec for the Store/Admin APIs, but no evidence of API versioning scheme or a documented deprecation policy anywhere in the docs; probe for openapi.json even 404s at the docs root. Missing for 10: any mention of API version numbers, changelog of breaking changes, or a stated deprecation/support timeline.

   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.medusajs.com/openapi.json, https://docs.medusajs.com/swagger.json, https://docs.medusaj…”

   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 drawn
   Medusa—none0/10

   Evidence shows Medusa's MCP server only exposes its own developer documentation to AI tools like Cursor (medusa-docs-4, medusa-docs-33/37, medusa-probe-3), not merchant product catalogs. There is no evidence of a cross-merchant catalog, agent-facing product feed, or discoverability mechanism for storefront products by AI agents/answer engines — the OpenAPI probe for a public product feed also failed (medusa-probe-2).

   • [claimed-docs] “Medusa hosts a Streamable HTTP MCP server at `https://docs.medusajs.com/mcp` that you can add to AI agents supporting MCP server connections…”
   • [claimed-docs] “allows you to find information from the Medusa documentation right in your IDEs or AI tools, such as Cursor”
   • [claimed-docs] “The Medusa documentation provides a remote Model Context Protocol (MCP) server that allows you to find information from the Medusa documenta…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.medusajs.com/openapi.json, https://docs.medusajs.com/swagger.json, https://docs.medusaj…”
   • [probe] “official MCP server documented at https://docs.medusajs.com/learn/introduction/build-with-llms-ai/mcp-server”

   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 Medusa
   Medusa~partialcommunity5/10

   Medusa documents dedicated Order, Fulfillment, and Payment modules and publishes a machine-readable OpenAPI 3.0 spec for its Store/Admin REST APIs (medusa-docs-23, medusa-docs-26, medusa-gh-x1), and a community comment confirms built-in returns/exchange ('swap') handling (medusa-comm-10) — together suggesting an agent could programmatically track and update post-purchase order states. However, the pack has no explicit documentation of a returns/RMA API endpoint, no concrete webhook payload/event schema (Webhook Events appears only as a Cloud pricing bullet, medusa-docs-16), and no example flow showing an agent completing status→fulfillment→return without touching the admin UI. Missing for 10: explicit returns/RMA API docs, concrete webhook event schema/trigger docs, and an end-to-end agent-without-admin example.

   • [claimed-docs] “Order Module - Medusa Documentation”
   • [claimed-docs] “Fulfillment Module - Medusa Documentation”
   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [community] “Swap Difference - love that you have this out of the box. Many e-commerce companies use 3rd party returns/exchange services because Shopify …”
   • [claimed-docs] “Webhook Events”

   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 WooCommerce
   Medusa—none0/10

   Medusa's documented MCP server (medusa-docs-4/33/37, probe-3) is scoped to searching Medusa's documentation for IDEs/AI coding tools, not a storefront-facing agent-commerce endpoint for product discovery or cart building; the Store REST/OpenAPI (medusa-gh-x1) exists but is a generic commerce API, not a documented MCP/UCP agent-commerce interface. No evidence of any UCP or dedicated shopping-agent MCP endpoint on the storefront itself.

   • [claimed-docs] “Medusa hosts a Streamable HTTP MCP server at `https://docs.medusajs.com/mcp` that you can add to AI agents supporting MCP server connections…”
   • [claimed-docs] “allows you to find information from the Medusa documentation right in your IDEs or AI tools, such as Cursor”
   • [claimed-docs] “The Medusa documentation provides a remote Model Context Protocol (MCP) server that allows you to find information from the Medusa documenta…”
   • [probe] “official MCP server documented at https://docs.medusajs.com/learn/introduction/build-with-llms-ai/mcp-server”
   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [claimed-docs] “Cart Module - Medusa Documentation”

   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
   Medusa—none0/10

   While Medusa's commerce modules (Product, Inventory, Order, etc.) and REST/OpenAPI API surface could plausibly support batch operations, no evidence in the pack documents bulk-update, bulk-import/export, or batch-processing endpoints/workflows for AI-driven mass operations across items.

   ⚑ 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 drawn
   Medusa~partialclaimed4/10

   Medusa's pricing page lists 'Webhook Events' as a feature, and its framework/workflow architecture (implied by 'Framework - Guardrails for agents to build customizations') suggests event-driven automation capability, but the evidence pack contains no documentation of a rule-definition system, event subscribers, or trigger-action configuration mechanism. Missing for 10: dedicated docs on defining custom event subscribers/rules, examples of trigger-condition-action automation, and independent confirmation the feature works as described beyond a single bullet point.

   • [claimed-docs] “Webhook Events”
   • [claimed-docs] “Framework - Guardrails for agents to build customizations.”
   • [claimed-docs] “Guardrails for agents to build customizations.”

   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
   Medusa—none0/10

   Evidence mentions only generic 'background workers' and workflow/framework capabilities, with no documentation of a scheduling API, cron syntax, or recurring-job/workflow trigger mechanism. Missing for 10: explicit scheduled-job/cron API docs, recurring workflow trigger examples, any first-party or community confirmation of a scheduler feature.

   • [claimed-docs] “Background workers”
   • [github] “Medusa is a commerce platform with a built-in framework for customization that allows you to build custom commerce applications without rein…”

   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 to Medusa
   Medusa~partialclaimed3/10

   Medusa's evidence only shows generic infrastructure features—GitHub-based deployment, PR previews, and automatic backups—that imply some git-based versioning and rollback for the whole application, but nothing specifically documents versioning, reviewing, or rolling back 'automations' (e.g., workflow definitions) as a distinct AI-native capability. missing for 10: explicit automation/workflow version history, a review/approval flow for automation changes, and a dedicated rollback mechanism for automations themselves.

   • [claimed-docs] “Deploy from GitHub”
   • [claimed-docs] “Own and control all your source-code, while we handle your infrastructure.”
   • [claimed-docs] “Instant previews on PRs”
   • [claimed-docs] “Automatic backups”
   • [claimed-docs] “Push from GitHub to the fastest infrastructure.”

   proof ↗⚑ 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 Medusa
   Medusa~partialclaimed4/10

   Medusa has a documented B2B Recipe and related commerce modules (Product, Cart, Order, Pricing infrastructure implied) plus GitHub confirmation that the framework supports 'advanced B2B or DTC commerce stores,' showing the platform is architected to support B2B use cases alongside DTC. However, the evidence never details specific features like customer-specific price lists, volume/tiered pricing, quote workflows, or net-terms invoicing — these are not named in any docs excerpt. missing for 10: explicit documentation of customer-specific price lists, volume pricing rules, quote/RFQ workflow, net-terms invoicing support, and independent/hands-on confirmation these B2B features work in practice.

   • [claimed-docs] “B2B Recipe - Medusa Documentation”
   • [github] “The framework and modules can be used to support advanced B2B or DTC commerce stores, marketplaces, distributor platforms, PoS systems, serv…”
   • [claimed-docs] “Inventory Module - Medusa Documentation”
   • [claimed-docs] “Product Module - Medusa Documentation”

   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
   Medusa~partialcommunity5/10

   Medusa's open-source Product Module (variants/options) and broader commerce-module architecture support building custom product data structures (medusa-docs-21, medusa-gh-2, medusa-gh-4), but the evidence pack gives no detailed confirmation of a general metafields/custom-fields system for products — and an early hands-on community review explicitly noted that metadata support existed for orders but not products at the time (medusa-comm-9), raising doubt about full custom-field flexibility on the catalog side. Missing for 10: current first-party documentation/screenshots showing per-product custom fields or metafields UI, independent confirmation that this limitation has been resolved, and detail on how option/variant modeling handles non-standard catalog structures.

   • [claimed-docs] “Product Module - Medusa Documentation”
   • [github] “Medusa's core commerce modules are open-source and freely available on npm.”
   • [github] “build custom commerce applications without reinventing core commerce logic”
   • [community] “Really love that you have starter kits for both Gatsby and Nextjs... Metadata is a killer feature but I only see it for orders and not produ…”

   proof ↗⚑ 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
   Medusa~partialclaimed4/10

   Medusa exposes a Product Module and REST/Admin API (medusa-docs-21, medusa-gh-x1) that could support programmatic catalog edits, but there is no direct evidence of a bulk CSV import/export feature or bulk-edit UI for operations leads. missing for 10: explicit CSV import/export tooling, bulk-edit admin UI documentation, and any hands-on confirmation that bulk catalog operations work without per-product edits.

   • [claimed-docs] “Product Module - Medusa Documentation”
   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [claimed-docs] “Customizable dashboard for your commerce.”

   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 to Medusa
   Medusa~partialcommunity7/10

   Medusa's documented commerce modules explicitly include an Inventory Module and a Fulfillment Module, which per Medusa's architecture support multi-location stock levels and location-aware fulfillment, and the Sales Channel module ties fulfillment sets to channels — the core building blocks operations leads need. However, the evidence pack only lists module names/titles rather than detailed workflows (e.g., stock adjustment audit trails, warehouse-selection logic in fulfillment), and no independent/hands-on report specifically validates multi-location behavior. Missing for 10: independent corroboration of multi-location stock adjustments and warehouse-based fulfillment routing, and detailed docs excerpts beyond module titles.

   • [claimed-docs] “Inventory Module - Medusa Documentation”
   • [claimed-docs] “Fulfillment Module - Medusa Documentation”
   • [claimed-docs] “Sales Channel Module - Medusa Documentation”
   • [community] “I love the idea of a headless ecommerce platform, especially one that comes with a nice backend GUI for managing inventory. Pleasantly surpr…”

   proof ↗⚑ 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
   Medusa~partialclaimed5/10

   Medusa's modular architecture (Cart, Payment, Tax, Fulfillment, Order modules) and documented 'Framework for customization' let developers extend commerce logic without forking core code, and Storefront Development Guides imply building custom checkout UIs on top of these modules. However, no evidence specifically documents checkout-page extension points for fields, branding, or discount/validation logic — no Promotion/discount module or checkout-specific customization guide is cited. missing for 10: dedicated checkout customization docs, discount/promotion module evidence, branding/field-level extension points, independent developer confirmation of checkout customization.

   • [claimed-docs] “Cart Module - Medusa Documentation”
   • [claimed-docs] “Payment Module - Medusa Documentation”
   • [claimed-docs] “Tax Module - Medusa Documentation”
   • [claimed-docs] “Storefront Development Guides - Medusa Documentation”
   • [github] “Medusa is a commerce platform with a built-in framework for customization that allows you to build custom commerce applications without rein…”
   • [github] “build custom commerce applications without reinventing core commerce logic”
   • [claimed-docs] “Extend, customize, and own every commerce workflow.”

   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 WooCommerce
   Medusa—none0/10

   The evidence only shows a generic 'Payment Module' doc entry with no mention of Apple Pay, Google Pay, PayPal, or any accelerated/one-click wallet checkout capability; nothing describes wallet-specific integrations or a one-click experience for buyers. This axis clearly applies to a commerce platform, but there is no evidence it delivers accelerated wallet payments.

   • [claimed-docs] “Payment Module - Medusa Documentation”

   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
   Medusa—none0/10

   Medusa's evidence pack covers cart, order, payment modules and general commerce architecture, but there is no mention of abandoned cart detection, recovery email triggers, or checkout-recovery links/workflows anywhere in the docs, GitHub, or community sources. This is a plausible axis for a commerce platform (notification/workflow modules could support it), but no evidence shows it shipping.

   • [claimed-docs] “Cart Module - Medusa Documentation”
   • [claimed-docs] “Payment Module - Medusa Documentation”
   • [github] “Medusa is a commerce platform with a built-in framework for customization that allows you to build custom commerce applications without rein…”

   proof ↗⚑ 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 drawn
   Medusa~partialprobed6/10

   Medusa provides a documented Framework and commerce modules for building custom apps, an official CLI (medusa-cli), OpenAPI specs for Store/Admin APIs, starter kits (Next.js/Gatsby storefronts per community feedback), and extension points like Admin Injection Zones and Medusa UI — a reasonably strong extensibility story for a commerce platform. However, there is no clear evidence of a formal marketplace/app-review process or distribution path (e.g., a plugin submission/certification pipeline), and no independent verification of SDK completeness beyond docs. missing for 10: documented app review/certification/distribution marketplace process, independent hands-on verification of scaffolding tooling and SDKs beyond first-party docs.

   • [github] “Medusa is a commerce platform with a built-in framework for customization that allows you to build custom commerce applications without rein…”
   • [github] “build custom commerce applications without reinventing core commerce logic”
   • [claimed-docs] “Framework - Guardrails for agents to build customizations.”
   • [claimed-docs] “Admin Injection Zones”
   • [claimed-docs] “Medusa UI”
   • [probe] “official CLI documented at https://docs.medusajs.com/resources/medusa-cli”
   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [community] “Really love that you have starter kits for both Gatsby and Nextjs... Metadata is a killer feature but I only see it for orders and not produ…”

   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
   Medusa—none0/10

   Medusa's evidence covers its open-source core modules, framework, and integrations documentation, but there is no mention of a curated or vetted marketplace/app store of third-party extensions comparable to Shopify's App Store. The story specifically requires a vetted marketplace covering long-tail features, which is unevidenced here.

   ⚑ 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 drawn
   Medusa~partialclaimed5/10

   Medusa's GitHub and marketing docs confirm a 'built-in framework for customization' that lets developers 'extend, customize, and own every commerce workflow' and includes commerce modules (Fulfillment, Tax, Cart, Order) that could house custom logic, supporting the general concept of injecting backend logic. However, the evidence pack lacks concrete documentation of the specific hook/subscriber/workflow mechanisms, discount or promotion customization, or serverless function deployment model that would show how validation/shipping/discount logic actually gets injected. Missing for 10: explicit workflow/subscriber/hook API docs, a discount-module customization example, and confirmation of serverless execution model.

   • [github] “Medusa is a commerce platform with a built-in framework for customization that allows you to build custom commerce applications without rein…”
   • [claimed-docs] “Framework - Guardrails for agents to build customizations.”
   • [claimed-docs] “Guardrails for agents to build customizations.”
   • [claimed-docs] “Extend, customize, and own every commerce workflow.”
   • [claimed-docs] “Fulfillment Module - Medusa Documentation”
   • [claimed-docs] “Tax Module - Medusa Documentation”

   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
   Medusa✓fullprobed7/10

   Medusa documents commerce modules (Product, Order, Cart, Payment, Fulfillment, Tax) and maintains OpenAPI specs powering Admin/Store REST APIs, confirming programmatic control over products, orders, refunds, and fulfillment via the admin API. However, the evidence pack lacks a direct hands-on example of issuing a refund or triggering fulfillment through the API, and the openapi.json probe for the admin spec 404s despite the store spec being confirmed. missing for 10: direct admin API refund/fulfillment usage examples, independent developer corroboration of admin API completeness, working openapi.json endpoint discovery.

   • [claimed-docs] “Product Module - Medusa Documentation”
   • [claimed-docs] “Cart Module - Medusa Documentation”
   • [claimed-docs] “Order Module - Medusa Documentation”
   • [claimed-docs] “Payment Module - Medusa Documentation”
   • [claimed-docs] “Fulfillment Module - Medusa Documentation”
   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.medusajs.com/openapi.json, https://docs.medusajs.com/swagger.json, https://docs.medusaj…”

   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 Medusa
   Medusa✓fullcommunity9/10

   Medusa provides documented Storefront Development Guides, first-party Next.js starter storefronts, commerce modules (product, cart, order, payment, tax, fulfillment), and a documented Store REST/OpenAPI API (openapi.full.yaml) that developers can build fully custom headless storefronts against, corroborated by community feedback praising the Next.js/Gatsby starter kits and headless architecture. Missing for 10: independent hands-on report building a production custom storefront end-to-end and a live OpenAPI endpoint (probe found 404s on some openapi paths despite the spec existing in-repo).

   • [claimed-docs] “Storefront Development Guides - Medusa Documentation”
   • [github] “Medusa is a commerce platform with a built-in framework for customization that allows you to build custom commerce applications without rein…”
   • [github] “build custom commerce applications without reinventing core commerce logic”
   • [claimed-docs] “Product Module - Medusa Documentation”
   • [claimed-docs] “Cart Module - Medusa Documentation”
   • [claimed-docs] “Order Module - Medusa Documentation”
   • [claimed-docs] “Payment Module - Medusa Documentation”
   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [community] “Really love that you have starter kits for both Gatsby and Nextjs... Metadata is a killer feature but I only see it for orders and not produ…”
   • [community] “I love the idea of a headless ecommerce platform, especially one that comes with a nice backend GUI for managing inventory. Pleasantly surpr…”

   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 Medusa
   Medusa~partialclaimed3/10

   Medusa's Sales Channel Module lets merchants manage a single product catalog across multiple defined sales channels, which is the underlying architecture needed for multi-channel selling, but there is no evidence of built-in connectors or sync tooling for actual external marketplaces, social commerce platforms, or shopping feeds (e.g., Amazon, Instagram, Google Shopping). Missing for 10: documented integrations/apps for external marketplaces or feed syncing, evidence of feed export formats, and any hands-on confirmation that products actually sync outward rather than just being logically grouped by channel.

   • [claimed-docs] “Sales Channel Module - Medusa Documentation”
   • [github] “The framework and modules can be used to support advanced B2B or DTC commerce stores, marketplaces, distributor platforms, PoS systems, serv…”

   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 Medusa
   Medusa!disputedcontradicted4/10

   Medusa's Tax Module doc suggests some duties/tax handling capability, but there is no evidence in the pack of multi-currency pricing, localized storefronts, or translation tooling — and a hands-on HN reviewer explicitly flags that 'internationalization... every product has a single string for description/title, with no easy way to localize text across regions,' directly contradicting the translations/localization part of this story. missing for 10: multi-currency pricing docs, region/locale storefront docs, translation/i18n module evidence, duties/customs handling detail beyond a generic Tax Module link.

   • [claimed-docs] “Tax Module - Medusa Documentation”
   • [community] “One area I do think could be improved is internationalization; every product has a single string for description/title, with no easy way to …”
   • [community] “I love the idea of a headless ecommerce platform, especially one that comes with a nice backend GUI for managing inventory. Pleasantly surpr…”

   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 drawn
   Medusa—none0/10

   Medusa's evidence covers its Sales Channel, Inventory, and Product modules which theoretically enable multi-channel selling, but there is no mention of an actual point-of-sale product/app or in-person checkout capability anywhere in the pack. Missing for 10: any POS application/device support, in-store checkout flow, or documentation of a POS integration syncing catalog/inventory/customers in real time.

   • [claimed-docs] “Sales Channel Module - Medusa Documentation”
   • [claimed-docs] “Inventory Module - Medusa Documentation”
   • [github] “The framework and modules can be used to support advanced B2B or DTC commerce stores, marketplaces, distributor platforms, PoS systems, serv…”

   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
   Medusa~partialclaimed6/10

   Medusa is architected API-first: its Admin dashboard is itself a client of the documented Admin REST API, and Medusa publishes complete OpenAPI 3.0 specs for both Store and Admin APIs, implying the UI's functionality is API-backed. However, no evidence explicitly confirms full feature parity (e.g., every admin UI action having a documented API equivalent) or independent verification of this claim. Missing for 10: explicit parity documentation/statement, independent hands-on confirmation that all UI actions map to API endpoints, and no gaps noted (e.g., some UI-only settings).

   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”
   • [github] “Medusa is a commerce platform with a built-in framework for customization that allows you to build custom commerce applications without rein…”
   • [claimed-docs] “Admin - Customizable dashboard for your commerce.”

   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
   Medusa~partialclaimed5/10

   Medusa's core is open-source and self-hostable, and vendor messaging emphasizes 'you own the project' and full source-code control, plus documented REST/OpenAPI specs (medusa-gh-x1) that could be used to pull data out programmatically. However there is no explicit documented 'export all data' feature, bulk data-export tool, or standardized open-format export (CSV/JSON dump) for leaving the platform — ownership is implied via self-hosting rather than a first-class export capability. missing for 10: explicit bulk data-export tooling, documented open-format export (CSV/JSON), migration/exit guide confirming full data portability.

   • [github] “Medusa's core commerce modules are open-source and freely available on npm.”
   • [claimed-docs] “Own and control all your source-code, while we handle your infrastructure.”
   • [claimed-docs] “You own the project, we handle the infra.”
   • [claimed-docs] “You own the project, we handle the infra. No GMV-tax or special licenses.”
   • [github] “openapi: 3.0.0 / info: title: Medusa Storefront API, license: MIT — Medusa maintains complete machine-readable OpenAPI 3.0 specifications fo…”

   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 userRead the product's source under an open license

   weight 2 · round to WooCommerce
   Medusa✓fullcommunity8/10

   Medusa's core is confirmed open-source on GitHub, with modules 'open-source and freely available on npm,' and community commentary independently confirms the repo is MIT-licensed. This directly satisfies an AI-native user's ability to read the source under an open license. Missing for 10: an explicit first-party license statement/citation (e.g., LICENSE file text) rather than inference from a community comment, and clarity on whether the entire platform vs. just certain modules is MIT-licensed.

   • [github] “Medusa is a commerce platform with a built-in framework for customization that allows you to build custom commerce applications without rein…”
   • [github] “Medusa's core commerce modules are open-source and freely available on npm.”
   • [community] “The landing page looks like it's trying to sell me a product, but the Github says it's MIT licensed... is there some component that costs mo…”
   • [community] “Listed among open-source SaaS alternatives: 'Shopify -> MedusaJS'.”

   proof ↗⚑ flag

   WooCommerce✓fullclaimed9/10

   WooCommerce is explicitly open-source (GPL-licensed WordPress plugin) with its source publicly hosted on GitHub, and its own site states it 'gives you full control: of your checkout, your data, your costs' as an open-source commerce platform. missing for 10: no explicit citation of the license file/terms text itself, only general open-source claims and the GitHub repo link.

   • [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”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to WooCommerce
   Medusa✓fullcommunity8/10

   Medusa's core commerce modules are open-source (MIT-licensed) and published on npm/GitHub, and community discussion independently confirms the MIT licensing model, supporting fully self-hosted deployment separate from the optional paid Cloud hosting. Docs also reinforce 'own your source-code, we handle infra' as an optional add-on rather than a requirement. missing for 10: a first-party self-hosting/installation guide citation and independent hands-on report of successfully running a self-hosted instance.

   • [github] “Medusa is a commerce platform with a built-in framework for customization that allows you to build custom commerce applications without rein…”
   • [github] “Medusa's core commerce modules are open-source and freely available on npm.”
   • [community] “The landing page looks like it's trying to sell me a product, but the Github says it's MIT licensed... is there some component that costs mo…”
   • [claimed-docs] “Own and control all your source-code, while we handle your infrastructure.”
   • [claimed-docs] “You own the project, we handle the infra.”

   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
   Medusa~partialclaimed3/10

   The evidence pack only shows a doc-page title for a 'Payment Module' (medusa-docs-24) with no description of supporting multiple third-party gateways or multi-currency charging; there's no mention of Stripe/PayPal/other providers, currency configuration, or a plugin marketplace for payment providers. missing for 10: explicit description of pluggable third-party payment providers, evidence of multi-currency charge support, and any merchant-facing docs/community confirmation of switching or combining payment gateways.

   • [claimed-docs] “Payment Module - Medusa Documentation”

   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 WooCommerce
   Medusa—none0/10

   Medusa's Payment Module (medusa-docs-24) is documented as an integration layer for third-party payment providers (e.g., Stripe, PayPal), not a first-party processor with its own published card rates, payouts, or fraud tooling. No evidence in the pack shows Medusa acting as the payment processor of record — the architecture is built around 'wiring' external gateways, which is the opposite of this story's ask.

   • [claimed-docs] “Payment Module - Medusa Documentation”
   • [github] “Medusa is a commerce platform with a built-in framework for customization that allows you to build custom commerce applications without rein…”

   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 Medusa
   Medusa~partialclaimed5/10

   Medusa's open-source/self-hosted architecture (BYOC, 'You own the project, we handle the infra') inherently lets users deploy in any region they choose, and the Enterprise pricing tier explicitly lists 'Data sovereignty, SOC2, custom DPA' as a feature, implying some data-residency control for cloud customers. However, there is no documentation of specific supported regions, a UI/API for selecting storage location, or details on how data sovereignty is technically enforced. Missing for 10: explicit region-selection mechanism/UI, list of supported regions, technical details on how residency is guaranteed, independent confirmation of the enterprise feature in practice.

   • [claimed-docs] “Data sovereignty, SOC2, custom DPA”
   • [claimed-docs] “You own the project, we handle the infra.”
   • [claimed-docs] “BYOC with Enterprise License”
   • [github] “Medusa's core commerce modules are open-source and freely available on npm.”

   proof ↗⚑ 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 to Medusa
   Medusa~partialclaimed3/10

   Medusa is self-hosted/open-source (you own your infra and database) and Cloud tier mentions 'Data sovereignty, SOC2, custom DPA' and 'Automatic backups', implying some control over where and how data is stored, but there is no explicit documentation of data retention policies, deletion APIs, or GDPR-style erasure workflows for commerce/customer data. Missing for 10: explicit data retention/deletion tooling or docs, GDPR/right-to-erasure endpoints, and independent confirmation of these controls in practice.

   • [claimed-docs] “Own and control all your source-code, while we handle your infrastructure.”
   • [claimed-docs] “Data sovereignty, SOC2, custom DPA”
   • [claimed-docs] “Automatic backups”

   proof ↗⚑ 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
   Medusa—none0/10

   Medusa's documented modules cover commerce entities (Product, Cart, Order, Payment, Tax, Fulfillment, Inventory, Sales Channel) but no evidence shows a content/pages/blog/media module or CMS capability in the admin; Admin Injection Zones only allow UI customization, not content authoring.

   • [claimed-docs] “Product Module - Medusa Documentation”
   • [claimed-docs] “Cart Module - Medusa Documentation”
   • [claimed-docs] “Order Module - Medusa Documentation”
   • [claimed-docs] “Admin Injection Zones”
   • [claimed-docs] “Admin - Customizable dashboard for your commerce.”

   proof ↗⚑ 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
   Medusa~partialcommunity4/10

   Medusa provides storefront development guides and Next.js/Gatsby starter kits (medusa-docs-5, medusa-comm-9) plus GitHub-based deploys and PR preview environments (medusa-docs-1, medusa-docs-11, medusa-docs-35), which cover part of the version-controlled-deploy and preview aspects of the story. However, Medusa is headless — there is no documented 'templating layer' or theme system (it's a full custom React/Next.js app, not theme templates), and no explicit local-preview workflow documentation is cited. Missing for 10: a documented templating/theme abstraction layer, explicit local-preview tooling docs, and independent hands-on confirmation of the PR-preview/deploy flow.

   • [claimed-docs] “Storefront Development Guides - Medusa Documentation”
   • [community] “Really love that you have starter kits for both Gatsby and Nextjs... Metadata is a killer feature but I only see it for orders and not produ…”
   • [claimed-docs] “Deploy from GitHub”
   • [claimed-docs] “Instant previews on PRs”
   • [claimed-docs] “Push from GitHub to the fastest infrastructure.”

   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 WooCommerce
   Medusa—none0/10

   Medusa is explicitly a headless, developer-first commerce platform — its storefront resources are 'Storefront Development Guides' requiring coding (medusa-docs-5), not a no-code theme/section editor. Community feedback explicitly notes headless means 'I have to write my own interfaces,' the opposite of a no-code polished-theme experience (medusa-comm-6). No evidence anywhere in the pack of a theme marketplace, visual page builder, or no-code branding/layout editor for merchants.

   • [claimed-docs] “Storefront Development Guides - Medusa Documentation”
   • [community] “Looks nice but to be a Shopify alternative, headless is not the way... Headless makes me think I have to write my own interfaces which then …”
   • [github] “Medusa is a commerce platform with a built-in framework for customization that allows you to build custom commerce applications without rein…”

   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 WooCommerce
   Medusa—none0/10

   Evidence only shows a generic 'Fulfillment Module' doc title (medusa-docs-26); there is no evidence of live carrier rate shopping at checkout, label purchasing, or shipment tracking integration. Missing for 10: carrier rate-shopping integration details, label purchase workflow, tracking/status sync evidence.

   • [claimed-docs] “Fulfillment Module - Medusa Documentation”

   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 WooCommerce
   Medusa~partialclaimed3/10

   Medusa ships a dedicated Tax Module in its commerce modules, implying built-in tax configuration, but the evidence pack gives no detail on automatic per-jurisdiction rate calculation, rate updates/currency, or generating filing-ready tax reports. missing for 10: documentation of jurisdiction-based automatic tax calculation, rate update/maintenance mechanism, tax report generation/export for filing, and any third-party tax provider integrations (e.g., Avalara/TaxJar).

   • [claimed-docs] “Tax Module - Medusa Documentation”

   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