Shopify vs Medusa

Agent access

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

   weight 2 · round to Medusa
   Shopify~partialprobed6/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Medusa
   Shopify~partialprobed5/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Shopify—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Shopify✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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

5. ai-native userUse an official CLI

   weight 2 · round to Shopify
   Shopify✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Shopify✓fullprobed8/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Shopify
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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

8. ai-native userBuild against official SDKs

   weight 2 · round to Shopify
   Shopify✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   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

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Shopify
   Shopify✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round drawn
   Shopify—none0/10

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

   ⚑ flag

   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

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

   weight 2 · round to Shopify
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Medusa
   Shopify—none0/10

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

   ⚑ flag

   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

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

   weight 2 · round to Shopify
   Shopify~partialprobed6/10

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

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

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round to Shopify
   Shopify✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Medusa
   Shopify—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 1 · round to Shopify
   Shopify✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Shopify
   Shopify✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   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

Agent discovery

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

   weight 2 · round to Shopify
   Shopify~partialprobed6/10

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

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

   proof ↗⚑ flag

   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

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
   Shopify!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

   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

Agentic checkout

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

   weight 3 · round to Shopify
   Shopify✓fullprobed9/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Shopify
   Shopify~partialclaimed3/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Shopify
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Shopify—none0/10

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

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

   proof ↗⚑ flag

   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

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

   weight 1 · round to Medusa
   Shopify—none0/10

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

   ⚑ flag

   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

B2b

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

   weight 2 · round to Shopify
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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

Catalog

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

   weight 3 · round to Medusa
   Shopify—none0/10

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

   ⚑ flag

   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

Catalog ops

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

   weight 2 · round drawn
   Shopify~partialcommunity4/10

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

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

   proof ↗⚑ flag

   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

Inventory

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

   weight 2 · round to Medusa
   Shopify—none0/10

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

   ⚑ flag

   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

Checkout

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

   weight 3 · round drawn
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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

Conversion

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

   weight 1 · round drawn
   Shopify—none0/10

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

   ⚑ flag

   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

App dev

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

   weight 2 · round to Shopify
   Shopify~partialcommunity7/10

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

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

   proof ↗⚑ flag

   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

Apps

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

   weight 3 · round to Shopify
   Shopify~partialcommunity7/10

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

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

   proof ↗⚑ flag

   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

Functions

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

   weight 2 · round to Medusa
   Shopify—none0/10

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

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

   proof ↗⚑ flag

   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

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

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

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

   proof ↗⚑ flag

   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

Headless

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

   weight 3 · round drawn
   Shopify✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   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

Channels

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

   weight 2 · round drawn
   Shopify~partialclaimed3/10

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

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

   proof ↗⚑ flag

   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

Global

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

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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

Pos

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

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Medusa
   Shopify!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Medusa
   Shopify—none0/10

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

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

   proof ↗⚑ flag

   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

3. ai-native userSelf-host the core product

   weight 3 · round to Medusa
   Shopify—none0/10

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

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

   proof ↗⚑ flag

   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

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

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

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

   proof ↗⚑ flag

   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

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

   weight 3 · round to Shopify
   Shopify~partialcommunity6/10

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

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

   proof ↗⚑ flag

   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

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

   weight 2 · round to Medusa
   Shopify—none0/10

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

   ⚑ flag

   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

2. ai-native userControl data retention and deletion

   weight 2 · round to Medusa
   Shopify—none0/10

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

   ⚑ flag

   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

Content

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

   weight 1 · round drawn
   Shopify—none0/10

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

   ⚑ flag

   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

Theme dev

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

   weight 2 · round to Shopify
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   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

Themes

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

   weight 3 · round to Shopify
   Shopify✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   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

Shipping

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

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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

Taxes

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

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   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