Medusa vs BigCommerce

Agent access

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

   weight 2 · round to Medusa
   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

   BigCommerce✓fullprobed8/10

   A direct probe confirms developer.bigcommerce.com/llms.txt returns HTTP 200 with structured content including an explicit 'Instructions for AI Agent' section, directly satisfying the story's requirement of agent-discoverable docs. Missing for 10: no independent/community confirmation of agents actually using it, and no broader agent-oriented doc ecosystem (e.g., MCP server, structured API docs for agents) beyond the single llms.txt file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   BigCommerce~partialcommunity6/10

   BigCommerce exposes REST/GraphQL APIs with OAuth-based API accounts and sandbox environments explicitly meant for scripted, non-UI automation of store management and headless storefronts, which supports CI-style programmatic use. However there's no dedicated CLI or CI/CD-native tooling, and a community report describes unreliable API connectivity/throttling that undermines confidence in dependable automation. Missing for 10: an official CLI, documented CI/CD pipeline integration, and confirmation the throttling issue is resolved.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “Sign up for a free BigCommerce trial store to test API calls and build integrations without affecting live data.”
   • [claimed-docs] “Navigate to **Settings > API Accounts** in your store control panel. Create credentials with the scopes you need.”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Medusa—none0/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   BigCommerce is an e-commerce SaaS platform; the evidence shows REST/GraphQL APIs, webhooks, apps marketplace, and llms.txt for AI agents reading docs, but no mention of an MCP client/host feature allowing users to plug MCP servers into BigCommerce so it can use their tools.

   ⚑ flag

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

   weight 3 · round to Medusa
   Medusa✓fullprobed8/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   BigCommerce is an ecommerce platform (not an agent), so the MCP-server axis applies, but no evidence shows an official MCP server; docs mention REST/GraphQL APIs, webhooks, and an llms.txt file for AI agent guidance, none of which constitute an MCP server implementation. Missing for 10: any mention of an MCP server, MCP endpoint, or MCP-compatible integration.

   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Medusa
   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

   BigCommerce—none0/10

   Evidence covers REST/GraphQL APIs, SDKs, API clients, and an llms.txt AI-agent instructions file, but there is no mention of an official BigCommerce CLI tool anywhere in the pack. missing for 10: an official CLI product/tool, its documentation, install instructions, and any command reference.

   ⚑ flag

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

   weight 3 · round to BigCommerce
   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

   BigCommerce✓fullprobed9/10

   BigCommerce ships extensive first-party documentation for REST and GraphQL APIs, OAuth-based API accounts (store/app/account-level), webhooks, sandboxes, an in-browser Request Runner, and API client SDKs, explicitly positioned for programmatic/automated store management and headless integration. It even exposes an llms.txt with AI-agent-specific instructions, signaling deliberate AI-native accessibility. Missing for 10: independent/third-party corroboration of large-scale programmatic API reliability (one dated community comment mentions throttling/connection issues, but it's secondhand and not a definitive contradiction of documented capability).

   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”
   • [claimed-docs] “You can experiment with our REST Management APIs using the **Request Runner**, which is built in to the [API Reference]”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [claimed-docs] “GraphQL Storefront API overview”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

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

   weight 2 · round to BigCommerce
   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

   BigCommerce~partialclaimed6/10

   BigCommerce docs describe OAuth-based API accounts with configurable scopes (store-level, app-level, account-level) created via Settings > API Accounts, which supports issuing least-privilege credentials, but nothing ties this explicitly to AI-agent use cases or agent-specific scoping/rotation controls. missing for 10: agent-specific credential guidance, fine-grained per-agent scope templates, independent/hands-on verification of scope enforcement.

   • [claimed-docs] “Navigate to **Settings > API Accounts** in your store control panel. Create credentials with the scopes you need.”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to BigCommerce
   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

   BigCommerce✓fullcommunity7/10

   BigCommerce documents official SDKs/tools (Checkout SDK, API Clients library, design system SDK) plus REST/GraphQL APIs, sandboxes, and API account setup, giving AI-native builders a well-documented path to build against first-party SDKs. Community reports of API throttling/incomplete ecosystem introduce some quality caveats but don't contradict SDK existence. Missing for 10: independent hands-on corroboration of SDK reliability/quality and AI-specific SDK usage examples.

   • [claimed-docs] “Accelerate your app development. Get started making API requests in the language of your choice with our API Clients.”
   • [claimed-docs] “Checkout SDK | SDK | [checkout-sdk-js]”
   • [claimed-docs] “Our open source design system. Use to build BigCommerce Apps that feel native inside the control panel.”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to BigCommerce
   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

   BigCommerce✓fullclaimed7/10

   BigCommerce has dedicated Webhooks documentation covering event subscription, including cloud pub/sub webhook delivery, confirming first-party webhook support for external event notification. Missing for 10: independent hands-on confirmation of webhook reliability, full event catalog details, and AI-specific framing of webhook consumption.

   • [claimed-docs] “Webhooks”
   • [claimed-docs] “Google Cloud Platform Pub/Sub Webhooks”
   • [claimed-docs] “Overview | BigCommerce Docs”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   Medusa—none0/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence only shows AI-powered search/chat on the developer documentation portal (bigcommerce-docs-16, bigcommerce-docs-27), not AI-generated insights or suggestions derived from a merchant's actual store/sales data. No mention of AI analytics, product recommendations, or in-product insight generation from BigCommerce's own data.

   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog, and richer feedback tools.”
   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog”

   proof ↗⚑ flag

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

   weight 2 · round to Medusa
   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

   BigCommerce—none0/10

   Evidence shows BigCommerce offers webhooks and REST/GraphQL APIs for building integrations, but nothing describes a way for an AI-native user to configure autonomous background automations (e.g., scheduled agents, workflow triggers, or persistent background jobs) within the platform itself. Webhooks are reactive event hooks requiring external infrastructure to act on them, not a built-in autonomous automation feature.

   • [claimed-docs] “Webhooks”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Google Cloud Platform Pub/Sub Webhooks”

   proof ↗⚑ flag

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

   weight 3 · round to Medusa
   Medusa~partialclaimed2/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence only shows AI-powered search/chat on the developer docs site and an llms.txt file for AI agents crawling documentation, not a built-in AI assistant inside the BigCommerce product to which a user can delegate store-management tasks. No mention of an in-product agentic assistant capable of taking actions on behalf of the user.

   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog, and richer feedback tools.”
   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

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

   weight 2 · round to Medusa
   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

   BigCommerce~partialprobed2/10

   Docs mention 'AI-powered search and chat' and 'AI-ready page actions' on the developer portal, and an llms.txt file exists with instructions for AI agents, suggesting some agentic/NL tooling around the developer docs, but there is no evidence that a user can actually operate the storefront/store management (products, orders, settings) via natural-language commands. Missing for 10: concrete NL command interface for store operations, evidence of chat-driven catalog/order management, independent hands-on confirmation.

   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog, and richer feedback tools.”
   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to BigCommerce
   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

   BigCommerce✓fullclaimed8/10

   BigCommerce's developer docs explicitly describe an interactive API Reference with an embedded 'Request Runner' letting developers experiment with REST/GraphQL calls directly in the browser, plus AI-powered search/chat and AI-ready page actions layered on the docs site. This matches the story of an interactive, runnable API reference well. Missing for 10: independent/hands-on user corroboration of the Request Runner experience and no explicit mention of GraphQL runnable examples alongside REST.

   • [claimed-docs] “You can experiment with our REST Management APIs using the **Request Runner**, which is built in to the [API Reference]”
   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog, and richer feedback tools.”
   • [claimed-docs] “AI-powered search and chat, AI-ready page actions, an in-browser API Request Runner, a redesigned changelog”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”

   proof ↗⚑ flag

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

   weight 2 · round to Medusa
   Medusa~partialprobed7/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   No evidence pack item mentions an OpenAPI (or equivalent machine-readable) spec file being available for download; references only cover REST/GraphQL usage, API Reference and Request Runner tools, not a downloadable spec artifact.

   ⚑ flag

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

   weight 1 · round to BigCommerce
   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

   BigCommerce✓fullclaimed8/10

   BigCommerce's developer docs explicitly describe creating a sandbox store ('Partner Use Sandbox') and a free trial store to 'test API calls and build integrations without affecting live data,' plus an in-browser Request Runner for experimenting with REST calls safely. This directly satisfies the story of testing without touching production data. Missing for 10: independent/hands-on community confirmation that the sandbox behaves identically to production and any AI-agent-specific sandbox tooling.

   • [claimed-docs] “Sign up for a free BigCommerce trial store to test API calls and build integrations without affecting live data.”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [claimed-docs] “You can experiment with our REST Management APIs using the **Request Runner**, which is built in to the [API Reference]”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   BigCommerce—none0/10

   The evidence pack documents BigCommerce's REST/GraphQL APIs, sandboxes, and API account scopes, but nowhere mentions API versioning schemes or a documented deprecation/sunset policy for endpoints. missing for 10: explicit API version numbering scheme, deprecation notice process, sunset timelines, changelog of breaking changes.

   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”

   proof ↗⚑ flag

Agent discovery

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

   weight 2 · round drawn
   Medusa—none0/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence shows BigCommerce's developer docs and APIs (REST/GraphQL, headless storefronts, an llms.txt for AI agents to navigate developer docs) but nothing about a cross-merchant product catalog or feed designed to make individual merchants' products discoverable by AI agents/answer engines across the platform. The llms.txt probe is aimed at documentation discovery, not a product feed for agent commerce.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”
   • [claimed-docs] “GraphQL Storefront API overview”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”

   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 drawn
   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

   BigCommerce~partialcommunity5/10

   BigCommerce documents REST/GraphQL APIs for managing orders programmatically and a webhooks system for event-driven integrations, which supports agent-driven order status/fulfillment automation without human admin interaction. However, the evidence never specifically documents returns/RMA endpoints, order-status-change webhook topics, or a fulfillment workflow API, and one community report raises concerns about API reliability/throttling under load. Missing for 10: explicit docs on returns/RMA API, order-status webhook event list, fulfillment API detail, and independent confirmation of reliable agent-driven order lifecycle automation.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Webhooks”
   • [claimed-docs] “Overview | BigCommerce Docs”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   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 drawn
   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

   BigCommerce—none0/10

   Evidence shows only general REST/GraphQL APIs, webhooks, Catalyst, and an llms.txt for AI-assisted docs browsing — no documented MCP/UCP agent-commerce endpoint enabling an AI shopping agent to discover products and build carts is mentioned anywhere in the pack.

   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “GraphQL Storefront API overview”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.bigcommerce.com/llms.txt # BigCommerce Docs > Build amazing commerce solutions powered by the…”

   proof ↗⚑ flag

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

   weight 2 · round to BigCommerce
   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

   BigCommerce~partialcommunity3/10

   BigCommerce documents REST and GraphQL APIs for programmatically managing products, orders, and customers (bigcommerce-docs-30, bigcommerce-docs-25), which could technically enable scripted bulk operations, but there is no explicit documentation of batch/bulk endpoints, rate-limit handling, or bulk-import tooling for AI-driven workflows. One community report also notes historical API throttling/reliability issues (bigcommerce-comm-4), suggesting bulk API use may face friction, though this is anecdotal and not a concrete documented failure of a specific bulk feature. Missing for 10: dedicated bulk/batch API documentation, explicit rate-limit or pagination guidance for large-scale operations, and independent verification of reliable bulk throughput.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Medusa~partialclaimed4/10

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

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

   proof ↗⚑ flag

   BigCommerce~partialclaimed4/10

   BigCommerce provides webhooks that fire on store events, which can trigger external automation, but there's no evidence of a native rules engine allowing users to define conditional trigger-action automations within the platform itself. missing for 10: native if-this-then-that rules builder, documentation of event-to-action automation configuration, evidence of AI-native or no-code rule definition UI.

   • [claimed-docs] “Webhooks”
   • [claimed-docs] “Google Cloud Platform Pub/Sub Webhooks”
   • [claimed-docs] “Overview | BigCommerce Docs”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Medusa—none0/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   No evidence of any scheduling, cron, or recurring workflow/job automation capability; evidence only covers APIs, webhooks, theming, and headless commerce features. missing for 10: any scheduler/cron API, workflow automation engine, or documented way to run recurring jobs.

   ⚑ flag

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

   weight 1 · round to Medusa
   Medusa~partialclaimed3/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   No evidence of any versioning, review, or rollback mechanism for automations/workflows (e.g., webhooks, scripts, or app configs) in BigCommerce docs; evidence covers APIs, headless storefronts, and webhooks setup but nothing about version history, diffing, or reverting automation changes.

   • [claimed-docs] “Webhooks”
   • [claimed-docs] “Google Cloud Platform Pub/Sub Webhooks”
   • [claimed-docs] “Overview | BigCommerce Docs”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”

   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 BigCommerce
   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

   BigCommerce✓fullclaimed7/10

   BigCommerce documents a dedicated 'B2B Edition' offering company accounts, quotes, and custom pricing for wholesale/enterprise buyers alongside standard DTC storefronts, directly matching the story's core asks (customer-specific pricing, quotes, B2B accounts). Missing for 10: explicit detail on volume/tiered pricing rules, net-terms invoicing workflow specifics, and independent/hands-on corroboration of B2B Edition in practice.

   • [claimed-docs] “B2B ecommerce built for how business buyers actually buy”
   • [claimed-docs] “B2B ecommerce built for how business buyers actually buy | BigCommerce”
   • [claimed-docs] “Set up B2B Edition for wholesale and enterprise buyers with company accounts, quotes, and custom pricing.”

   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
   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

   BigCommerce—none0/10

   The axis clearly applies to an ecommerce platform, but the evidence pack contains no documentation or community mentions of product variants, options, custom fields, or metafields — only generic references to REST/GraphQL APIs for 'managing products' and building headless storefronts. Missing for 10: any docs on variant/option modeling, custom fields, or metafield support, and any independent confirmation of catalog flexibility beyond a fixed template.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”

   proof ↗⚑ flag

Catalog ops

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

   weight 2 · round to BigCommerce
   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

   BigCommerce~partialcommunity5/10

   Docs confirm REST/GraphQL APIs to programmatically manage products, orders, and store settings (bigcommerce-docs-30, bigcommerce-docs-25), which supports bulk catalog operations via API, but there is no explicit documentation of a native CSV bulk import/export tool for the catalog in this evidence pack, and one community report flags historical API reliability/throttling issues (bigcommerce-comm-4). missing for 10: explicit CSV import/export feature docs, UI walkthrough for bulk edit, independent confirmation of reliable bulk operations at scale.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Navigate to **Settings > API Accounts** in your store control panel. Create credentials with the scopes you need.”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

Inventory

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

   weight 2 · round to Medusa
   Medusa~partialcommunity7/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence covers headless storefront APIs, theming, B2B, webhooks, and general API tooling, but nothing addresses multi-location inventory tracking, stock adjustments, or location-based fulfillment routing. missing for 10: multi-location inventory API/docs, stock adjustment workflows, warehouse-based fulfillment logic, any first-party or community confirmation of these capabilities.

   ⚑ flag

Checkout

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

   weight 3 · round drawn
   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

   BigCommerce~partialclaimed5/10

   BigCommerce explicitly advertises the ability to 'extend checkout' via its developer platform and provides a dedicated Checkout SDK (checkout-sdk-js) as a supported extension point rather than requiring a full checkout fork [bigcommerce-docs-3][bigcommerce-docs-36]. However, the evidence pack gives no detail on specific extension points for custom fields, branding theming, discount logic, or validation rules within checkout, nor any independent/hands-on confirmation that these specific capabilities work as described. Missing for 10: documented API/SDK methods for custom checkout fields, branding customization, discount rule injection, and validation logic, plus independent developer corroboration of these specific capabilities.

   • [claimed-docs] “Create single-click apps for the BigCommerce marketplace, build custom integrations, or extend checkout.”
   • [claimed-docs] “Checkout SDK | SDK | [checkout-sdk-js]”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   BigCommerce—none0/10

   Evidence pack mentions a general payments page (bigcommerce-docs-14/23) but provides no specifics about Apple Pay, Google Pay, PayPal, or one-click wallet checkout support; no documentation or community confirmation of accelerated wallet checkout flows. missing for 10: mention of specific wallet integrations (Apple Pay, Google Pay, PayPal one-click), checkout flow details, or merchant/customer confirmation of wallet usage.

   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions”
   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions | BigCommerce”

   proof ↗⚑ flag

Conversion

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

   weight 1 · round drawn
   Medusa—none0/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   No evidence pack item mentions abandoned cart recovery, abandoned checkout emails, or cart recovery links; coverage focuses on APIs, headless architecture, webhooks, B2B, and theming, none of which address this specific merchant capability.

   ⚑ flag

App dev

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

   weight 2 · round drawn
   Medusa~partialprobed6/10

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

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

   proof ↗⚑ flag

   BigCommerce~partialcommunity6/10

   BigCommerce documents a broad developer toolkit — REST/GraphQL APIs, Checkout SDK, API Clients, Catalyst (Next.js) and Stencil (Handlebars) scaffolding, sandbox/trial stores, OAuth API accounts, and a single-click app marketplace for distribution — giving solid first-party coverage of SDKs, scaffolding, and a distribution channel. However, there's no detailed documented app review/certification workflow, and hands-on community reports describe the Stencil theming system as inconsistent and hard to work with and cite unreliable API connections/throttling, undercutting the polish of the developer experience. Missing for 10: an explicit documented app-review/certification process, a dedicated CLI scaffolding tool, and independent corroboration that the SDK/tooling experience is smooth in practice.

   • [claimed-docs] “Create single-click apps for the BigCommerce marketplace, build custom integrations, or extend checkout.”
   • [claimed-docs] “Accelerate your app development. Get started making API requests in the language of your choice with our API Clients.”
   • [claimed-docs] “Checkout SDK | SDK | [checkout-sdk-js]”
   • [claimed-docs] “Our open source design system. Use to build BigCommerce Apps that feel native inside the control panel.”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”
   • [claimed-docs] “BigCommerce's Handlebars-based theme engine for building hosted storefronts.”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”
   • [community] “I've never had a worse webdev experience than attempting to create a BigCommerce theme. There are hundreds of theme files, and a maddeningly…”

   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 BigCommerce
   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

   BigCommerce~partialcommunity5/10

   BigCommerce documents an app marketplace ('Over 1,200 apps to help you grow') and developer APIs to build single-click marketplace apps, but there's no detail on vetting/curation processes, and a hands-on community report describes the app ecosystem as 'rather incomplete' with API reliability issues. missing for 10: vetting/curation details, marketplace category breadth evidence, more recent independent corroboration of app quality/coverage.

   • [claimed-docs] “Over 1,200 apps to help you grow.”
   • [claimed-docs] “Create single-click apps for the BigCommerce marketplace, build custom integrations, or extend checkout.”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

Functions

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

   weight 2 · round to Medusa
   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

   BigCommerce—none0/10

   Evidence shows only webhooks (event notifications), REST/GraphQL APIs, and third-party app integrations — none of which are serverless functions or hooks that execute custom backend logic (discounts, shipping, validation) inside the platform itself. Missing for 10: any documentation of a functions/hooks runtime, script execution environment, or in-platform custom logic injection comparable to Shopify Functions.

   • [claimed-docs] “Webhooks”
   • [claimed-docs] “Google Cloud Platform Pub/Sub Webhooks”
   • [claimed-docs] “Overview | BigCommerce Docs”
   • [claimed-docs] “Create single-click apps for the BigCommerce marketplace, build custom integrations, or extend checkout.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”

   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
   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

   BigCommerce~partialcommunity6/10

   First-party docs confirm REST/GraphQL Admin APIs for managing products, orders, customers and store settings, with scoped API-account credentials and a sandbox for testing (bigcommerce-docs-30, docs-32, docs-38, docs-39) plus webhooks for event-driven workflows (bigcommerce-docs-5). However, the evidence never explicitly names refund or fulfillment-triggering endpoints, and one hands-on account reports the API was unreliable, suffering throttling/dropped connections (bigcommerce-comm-4), which tempers confidence in full lifecycle reliability. Missing for 10: explicit refund/fulfillment API documentation, independent verification of stable high-volume API usage, and third-party confirmation of full CRUD lifecycle beyond vendor docs.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “Navigate to **Settings > API Accounts** in your store control panel. Create credentials with the scopes you need.”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [claimed-docs] “BigCommerce offers three types of OAuth-based API accounts to developers who wish to use BigCommerce's REST APIs: store-level credentials, a…”
   • [claimed-docs] “Webhooks”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

Headless

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

   weight 3 · round to Medusa
   Medusa✓fullcommunity9/10

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

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

   proof ↗⚑ flag

   BigCommerce✓fullcommunity8/10

   BigCommerce provides well-documented GraphQL Storefront API and a first-party headless frontend framework (Catalyst, built on Next.js), plus REST/GraphQL management APIs, SDKs, and sandbox tooling for developers to build fully custom storefronts (bigcommerce-docs-1, -2, -7, -18, -25, -29, -36). Community evidence corroborates decent API/dev experience for local development with live data (bigcommerce-comm-1), though older complaints exist about API reliability and Stencil theme complexity that are tangential to the modern headless stack. Missing for 10: recent independent hands-on validation specifically of Catalyst/GraphQL Storefront API at production scale, and clearer confirmation the API throttling issues (from older community reports) have been resolved.

   • [claimed-docs] “go fully headless with the GraphQL Storefront API”
   • [claimed-docs] “Build with Catalyst (Next.js), customize Stencil themes, or go fully headless”
   • [claimed-docs] “Catalyst: Headless Storefronts Made Easy”
   • [claimed-docs] “GraphQL Storefront API overview”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “or go fully headless with the GraphQL Storefront API.”
   • [claimed-docs] “Checkout SDK | SDK | [checkout-sdk-js]”
   • [community] “I actually helped my previous company migrate from Magento to BigCommerce, and found their offering incredibly compelling compared to Shopif…”

   proof ↗⚑ flag

Channels

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

   weight 2 · round drawn
   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

   BigCommerce~partialclaimed3/10

   BigCommerce's marketing pages reference an 'Omnichannel Ecommerce Software Solution' and a large app marketplace (1,200+ apps) that could include channel-sync apps, but the evidence pack contains no concrete documentation of specific marketplace/social/shopping-feed integrations (e.g., Amazon, Google Shopping, Facebook/Instagram) or a dedicated channel-manager feature. Missing for 10: explicit docs on channel listing/sync workflows, named integrations (Amazon, eBay, Google Shopping, TikTok, Instagram), and any first-party or independent confirmation these work reliably.

   • [claimed-docs] “Omnichannel Ecommerce Software Solution”
   • [claimed-docs] “Omnichannel Ecommerce Software Solution | BigCommerce”
   • [claimed-docs] “Over 1,200 apps to help you grow.”

   proof ↗⚑ flag

Global

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

   weight 2 · round drawn
   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

   BigCommerce~partialclaimed2/10

   BigCommerce's 'Multi-Site' solution promotes 'Multiple Brands and Regions' which gestures at localized storefronts, but the evidence pack contains no explicit documentation of multi-currency pricing, storefront translations, or duty/tax handling for international sales. Missing for 10: explicit multi-currency pricing docs, translation/localization tooling, duties/customs handling, and any independent confirmation these features work end-to-end.

   • [claimed-docs] “Multi-Site: One Platform, Multiple Brands and Regions”
   • [claimed-docs] “Multi-Site: One Platform, Multiple Brands and Regions | BigCommerce”

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

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   Evidence covers headless APIs, theming, B2B, multi-store, payments, and webhooks, but there is no mention of a native point-of-sale product or integration that syncs catalog/inventory/customers with a physical retail POS system. Omnichannel page is referenced but no details show POS capability.

   ⚑ flag

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

   weight 2 · round drawn
   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

   BigCommerce~partialcommunity6/10

   BigCommerce documents broad REST and GraphQL API coverage for products, orders, customers, store settings, checkout, webhooks, B2B, and multi-store management, suggesting most UI operations have API equivalents, and even provides sandbox/trial environments and an API Request Runner for testing. However, there is no explicit vendor statement guaranteeing 100% UI-to-API parity, and a community report notes historical issues with reliably connecting to the API without throttling. Missing for 10: an explicit parity guarantee/documentation mapping every control-panel action to an API endpoint, and independent hands-on confirmation that all admin UI actions (e.g., full theme/store configuration) are API-accessible without gaps.

   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “Navigate to **Settings > API Accounts** in your store control panel. Create credentials with the scopes you need.”
   • [claimed-docs] “You can experiment with our REST Management APIs using the **Request Runner**, which is built in to the [API Reference]”
   • [claimed-docs] “To create a sandbox for your own general use, select **Partner Use Sandbox**”
   • [community] “I did try BigCommerce, but there were many issue with them. The software was very slow, and the app ecosystem was rather incomplete. From wh…”

   proof ↗⚑ flag

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

   weight 3 · round to Medusa
   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

   BigCommerce~partialclaimed4/10

   BigCommerce exposes REST and GraphQL APIs that can be used to pull products, orders, customers, and settings programmatically (bigcommerce-docs-30, bigcommerce-docs-25), which gives a technical path to extract data in open JSON formats, but there is no documented bulk 'export all my data' feature, data-portability guarantee, or migration-out tooling. missing for 10: explicit full-account data export/download feature, documented data portability/GDPR-style export policy, and evidence of successful full data migration away from BigCommerce.

   • [claimed-docs] “Use REST and GraphQL APIs to manage products, orders, customers, and store settings programmatically.”
   • [claimed-docs] “The BigCommerce suite of APIs empowers you to create apps, automate store processes, and build headless ecommerce solutions.”
   • [claimed-docs] “Use REST and Gra”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Medusa
   Medusa✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   BigCommerce is a proprietary SaaS platform; no evidence indicates its core source code is published under an open license (only design system and SDKs like the Checkout SDK/design system are noted as open source, not the platform itself). missing for 10: any statement that BigCommerce's core product source is open-licensed or publicly viewable.

   • [claimed-docs] “Our open source design system. Use to build BigCommerce Apps that feel native inside the control panel.”

   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 drawn
   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

   BigCommerce~partialclaimed3/10

   BigCommerce has a dedicated payments page referencing multiple payment providers/credit card solutions, implying support for third-party gateways, but there is no explicit documentation confirming a marketplace of alternative gateways or multi-currency charging capability. missing for 10: explicit list/count of supported third-party payment gateways, documentation of multi-currency checkout/settlement support, and independent confirmation of gateway flexibility.

   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions”
   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions | BigCommerce”

   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 BigCommerce
   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

   BigCommerce~partialclaimed3/10

   Evidence only shows a page title 'Ecommerce Payment Providers & Credit Card Solutions' (BigCommerce Payments) exists, confirming some integrated payments offering, but there is no detail on published card rates, payout schedules, or fraud tooling specifics, nor any independent confirmation it works without a third-party gateway. Missing for 10: documented rate sheet, payout timing details, fraud/chargeback tooling specifics, and hands-on/community corroboration of using it without a third-party gateway.

   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions”
   • [claimed-docs] “Ecommerce Payment Providers & Credit Card Solutions | BigCommerce”

   proof ↗⚑ flag

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

   weight 2 · round to Medusa
   Medusa~partialclaimed5/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   No evidence of data residency/region selection controls anywhere in the pack; docs only cover APIs, theming, headless commerce, and multi-store branding, none of which address data storage location choice.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round to Medusa
   Medusa~partialclaimed3/10

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

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

   proof ↗⚑ flag

   BigCommerce—none0/10

   No evidence addresses AI-native data retention/deletion controls—nothing about data lifecycle policies, deletion APIs, or retention settings for AI agents or data processed by AI tools; evidence only covers commerce APIs, theming, and app ecosystem.

   ⚑ flag

3. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Medusa—none0/10

   No evidence in the pack addresses telemetry collection or an opt-out mechanism for Medusa; the axis is applicable to a self-hosted commerce platform but no documentation, GitHub, or community source confirms or denies telemetry practices.

   ⚑ flag

   BigCommerce—none0/10

   No evidence in the pack addresses telemetry/usage-tracking opt-out controls for AI-native users; all docs and community items concern APIs, theming, and commerce features. missing for 10: any mention of telemetry, analytics opt-out, or privacy/data-collection settings.

   ⚑ flag

Content

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

   weight 1 · round drawn
   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

   BigCommerce—none0/10

   The evidence pack covers storefront theming (Stencil), headless APIs, webhooks, and apps, but contains no mention of an admin-side content/blog/pages/media management module for merchants; the only content-adjacent evidence is about theme file structure and API-driven storefront building, not admin content authoring.

   ⚑ flag

Theme dev

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

   weight 2 · round to Medusa
   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

   BigCommerce!disputedcontradicted5/10

   BigCommerce documents a Handlebars-based theme engine (Stencil) as its templating layer, and a hands-on HN comment confirms local development with live product data. However another hands-on account describes the same theme system as having 'hundreds of theme files' and a 'maddeningly incomplete and inconsistent templating tag system,' directly contradicting the claim that customization is well-documented and smooth. Missing for 10: no dedicated docs on Stencil CLI local preview workflow, no explicit version-controlled/git-based theme deploy pipeline evidence, and no independent corroboration resolving the conflicting community reports.

   • [claimed-docs] “BigCommerce's Handlebars-based theme engine for building hosted storefronts.”
   • [claimed-docs] “BigCommerce’s Handlebars-based theme engine for building hosted storefronts.”
   • [community] “I actually helped my previous company migrate from Magento to BigCommerce, and found their offering incredibly compelling compared to Shopif…”
   • [community] “I've never had a worse webdev experience than attempting to create a BigCommerce theme. There are hundreds of theme files, and a maddeningly…”

   proof ↗⚑ flag

Themes

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

   weight 3 · round to BigCommerce
   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

   BigCommerce~partialcommunity6/10

   BigCommerce docs confirm a Stencil theme engine for hosted storefronts and marketing copy stating stores can be built 'with or without code,' implying pre-designed themes plus customization options, alongside marketplace apps for extending functionality (bigcommerce-docs-6, bigcommerce-docs-8, bigcommerce-docs-10). However, a hands-on community account explicitly describes BigCommerce theme customization as one of the worst web-dev experiences due to 'hundreds of theme files' and an 'inconsistent templating tag system' (bigcommerce-comm-6), undercutting the no-code simplicity claim for anything beyond basic use. Missing for 10: explicit documentation of a visual drag-and-drop page builder/section editor for non-technical merchants, a gallery of professionally designed themes, and independent praise confirming ease of no-code branding/layout changes.

   • [claimed-docs] “BigCommerce's Handlebars-based theme engine for building hosted storefronts.”
   • [claimed-docs] “Build your store with or without code.”
   • [claimed-docs] “Over 1,200 apps to help you grow.”
   • [community] “I've never had a worse webdev experience than attempting to create a BigCommerce theme. There are hundreds of theme files, and a maddeningly…”

   proof ↗⚑ flag

Shipping

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

   weight 2 · round drawn
   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

   BigCommerce—none0/10

   No evidence pack items reference live carrier rate shopping, label purchasing, or shipment tracking within BigCommerce checkout; the evidence focuses on APIs, theming, headless commerce, and marketplace apps, not shipping/carrier integration. This is a fair axis for an ecommerce platform (shipping apps and carrier integrations are common in the category), but nothing shows BigCommerce natively delivers it.

   ⚑ 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 Medusa
   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

   BigCommerce—none0/10

   No evidence pack items mention tax/VAT calculation, jurisdiction-based rates, rate updates, or tax filing/reporting features; the evidence covers APIs, theming, headless commerce, and B2B/webhooks instead.

   ⚑ flag