Shopify vs Swell

Agent access

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

   weight 2 · round to Shopify
   Shopify~partialprobed6/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   A direct probe of the documented llms.txt path returns 404, and no evidence pack item shows a dedicated agent-oriented docs endpoint (e.g., markdown docs, llms.txt, or similar) that an agent could be pointed at; the swell.is/ai marketing page describes AI-friendly schema/API concepts but not a llms.txt or agent-consumable doc file.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.swell.is/llms.txt”
   • [claimed-docs] “Install once and your agent picks up the file contract, the CLI and the validate-deploy-verify loop.”

   proof ↗⚑ flag

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

   weight 2 · round to Shopify
   Shopify~partialprobed5/10

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

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

   proof ↗⚑ flag

   Swell~partialprobed4/10

   Swell ships an official CLI (`swell app init/push`, switch store) and a REST/webhook API that could in principle be scripted in automation pipelines, and the AI page mentions a 'validate-deploy-verify loop' agents can drive via the CLI, implying non-interactive usage. However, there is no explicit documentation of CI/headless execution, environment variables for non-interactive auth in CI, or any CI/CD integration guide. Missing for 10: explicit CI/CD documentation or examples, non-interactive auth flow guidance, and independent confirmation of headless automation use.

   • [claimed-docs] “Swell CLI is a command-line interface that helps you create and work with apps, themes, and storefronts.”
   • [claimed-docs] “swell app init: initialize an app in the current directory with a default config file and folder structure”
   • [claimed-docs] “swell app push: push configuration files to a development store”
   • [claimed-docs] “Switch your current default store.”
   • [claimed-docs] “Install once and your agent picks up the file contract, the CLI and the validate-deploy-verify loop.”
   • [probe] “official CLI documented at https://developers.swell.is/apps/cli”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Shopify—none0/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   Swell is an e-commerce platform; evidence describes CLI, functions, webhooks, and an AI-assisted schema/model workflow, but nothing indicates Swell can consume external MCP servers or plug in third-party tool sets. Absence of evidence for an applicable capability means 'none'.

   ⚑ flag

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

   weight 3 · round to Shopify
   Shopify✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   Evidence shows a CLI, webhooks, and 'agent'-friendly file-based contract, but no mention of an official MCP server or MCP protocol support anywhere in the docs or probes; probes even show llms.txt and openapi.json as 404, suggesting no structured agent-integration endpoint. Swell is a commerce platform (not itself an agent), so this axis applies, but no evidence confirms it ships an MCP server.

   • [claimed-docs] “Install once and your agent picks up the file contract, the CLI and the validate-deploy-verify loop.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.swell.is/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.swell.is/openapi.json, https://developers.swell.is/swagger.json, https://develope…”
   • [probe] “official CLI documented at https://developers.swell.is/apps/cli”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Shopify
   Shopify✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Swell✓fullprobed7/10

   Swell documents an official CLI (swell app init, push, switch store) and explicitly ties it into an AI-agent workflow ('Install once and your agent picks up the file contract, the CLI and the validate-deploy-verify loop'), showing intent for AI-native usage. Missing for 10: independent/hands-on corroboration of agentic CLI usage, and deeper documentation of AI-specific CLI commands beyond app scaffolding.

   • [claimed-docs] “swell app init: initialize an app in the current directory with a default config file and folder structure”
   • [claimed-docs] “Switch your current default store.”
   • [claimed-docs] “Swell CLI is a command-line interface that helps you create and work with apps, themes, and storefronts.”
   • [claimed-docs] “swell app push: push configuration files to a development store”
   • [claimed-docs] “Install once and your agent picks up the file contract, the CLI and the validate-deploy-verify loop.”
   • [probe] “official CLI documented at https://developers.swell.is/apps/cli”

   proof ↗⚑ flag

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

   weight 3 · round to Shopify
   Shopify✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Swell✓fullprobed7/10

   Swell exposes a documented backend REST API with authentication (basic auth, environment-specific keys), official Node/PHP client libraries, and endpoints for products, stock, purchase links, etc., plus a runtime schema-introspection call and CLI for driving apps/config programmatically. However, no OpenAPI spec or llms.txt was discoverable (probes 404), reducing machine-readability for agentic consumption. Missing for 10: a discoverable OpenAPI/machine-readable spec, independent third-party confirmation of API robustness.

   • [claimed-docs] “Official libraries for the Swell API are available for Node and PHP.”
   • [claimed-docs] “Keys are environment-specific: secret keys prefixed sk_test_ route requests to your store's test environment, while sk_live_ keys target liv…”
   • [claimed-docs] “One call returns a store’s whole schema at runtime: every model—standard, merchant custom and app-installed alike—with field types and relat…”
   • [claimed-docs] “authenticate with basic auth using your store ID as the username and a secret key as the password”
   • [claimed-docs] “Purchase links allow you to configure a pre-selected group of products within a cart and direct a customer to its checkout through a designa…”
   • [claimed-docs] “Stock adjustments are used to keep track of inventory changes over time.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.swell.is/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.swell.is/openapi.json, https://developers.swell.is/swagger.json, https://develope…”

   proof ↗⚑ flag

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

   weight 2 · round to Shopify
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   Swell's API auth docs only show basic auth with a secret key and test/live key environments (sk_test_/sk_live_), not granular, scoped or least-privilege credential issuance for agents; team role/permission assignment (docs-17) applies to dashboard users, not API credentials. No evidence of scoped API tokens, OAuth scopes, or agent-specific credential minting.

   • [claimed-docs] “Keys are environment-specific: secret keys prefixed sk_test_ route requests to your store's test environment, while sk_live_ keys target liv…”
   • [claimed-docs] “authenticate with basic auth using your store ID as the username and a secret key as the password”
   • [claimed-docs] “Assign specific roles and permissions to team members for better control.”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Shopify
   Shopify✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   Swell~partialprobed6/10

   Swell documents official backend API libraries for Node and PHP plus a first-party CLI, which supports building against official SDKs, but coverage is limited to two languages and there's no evidence of broader SDK ecosystem (e.g., Python, Go) or independent corroboration; openapi/llms.txt probes returned 404, suggesting weaker machine-readable API contract support. missing for 10: SDKs beyond Node/PHP, independent/hands-on validation, discoverable OpenAPI spec.

   • [claimed-docs] “Official libraries for the Swell API are available for Node and PHP.”
   • [claimed-docs] “Swell CLI is a command-line interface that helps you create and work with apps, themes, and storefronts.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.swell.is/openapi.json, https://developers.swell.is/swagger.json, https://develope…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.swell.is/llms.txt”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Shopify✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Swell✓fullclaimed8/10

   Swell's docs explicitly describe webhooks that subscribe to model events and call external URLs, enabling event-driven/agentic integrations (swell-docs-5, swell-docs-25). Missing for 10: independent/hands-on corroboration of webhook reliability and a documented list of supported event types/payloads beyond the overview mention.

   • [claimed-docs] “Webhooks can be configured to call a URL when a particular event occurs, enabling outgoing calls to external services.”
   • [claimed-docs] “Webhooks enable real-time communication between the Swell platform and external services, by subscribing to any number of model events.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round drawn
   Shopify—none0/10

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

   ⚑ flag

   Swell—none0/10

   Swell's AI-related docs focus on making its schema/API machine-readable for external agents to build integrations (schema discovery, model generation, CLI loop), not on the product itself surfacing AI-generated insights or suggestions from store data to users. Reporting features (swell-docs-35) are plain analytics with no AI generation mentioned.

   • [claimed-docs] “Drop a JSON file into your app’s models/ directory and Swell generates the REST resource from it—fields, validation, relationships and lifec…”
   • [claimed-docs] “One call returns a store’s whole schema at runtime: every model—standard, merchant custom and app-installed alike—with field types and relat…”
   • [claimed-docs] “Install once and your agent picks up the file contract, the CLI and the validate-deploy-verify loop.”
   • [claimed-docs] “Access detailed reports that aid in tracking and analyzing your store's performance.”

   proof ↗⚑ flag

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

   weight 2 · round to Shopify
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed4/10

   Swell provides webhooks and serverless functions that could be composed into background automations (event-triggered external calls, edge functions with no cold start), but there is no documented dedicated 'automation' or scheduling/workflow engine, and the AI-agent skills content (swell-probe-rt-2) is about coding-time development assistance, not autonomous runtime automations. Missing for 10: a described automation/orchestration feature, scheduling or trigger-based workflow builder, and evidence of autonomous background execution beyond raw webhook/function primitives.

   • [claimed-docs] “Webhooks can be configured to call a URL when a particular event occurs, enabling outgoing calls to external services.”
   • [claimed-docs] “Webhooks enable real-time communication between the Swell platform and external services, by subscribing to any number of model events.”
   • [claimed-docs] “Functions are deployed to edge data centers in 200+ locations and have no cold start time.”
   • [claimed-docs] “Functions have no cold boots and do not require extra time to start up before executing your code.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Shopify—none0/10

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

   ⚑ flag

   Swell—none0/10

   Swell's docs describe making the platform friendly to external AI coding agents (schema discovery endpoint, file-based model generation, CLI hooks) but there is no evidence of a built-in AI assistant embedded in the Swell dashboard/product that a user can delegate tasks to directly.

   • [claimed-docs] “Drop a JSON file into your app’s models/ directory and Swell generates the REST resource from it—fields, validation, relationships and lifec…”
   • [claimed-docs] “One call returns a store’s whole schema at runtime: every model—standard, merchant custom and app-installed alike—with field types and relat…”
   • [claimed-docs] “Install once and your agent picks up the file contract, the CLI and the validate-deploy-verify loop.”
   • [claimed-docs] “One call returns a store's whole schema at runtime: every model—standard, merchant custom and app-installed alike—with field types and relat…”

   proof ↗⚑ flag

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

   weight 2 · round to Shopify
   Shopify~partialprobed6/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   The evidence describes Swell's AI-focused developer tooling (CLI, JSON model files, schema introspection API, webhooks) aimed at letting AI coding agents build integrations, but nothing shows an end user issuing natural-language commands to operate the storefront/admin platform itself — the CLI (swell-docs-4, swell-docs-24, swell-docs-33, swell-docs-44) is a traditional command-line tool, not an NL interface. Missing for 10: any chat/NL command interface, conversational operation of dashboard or storefront, or documentation of natural-language input being parsed/executed by the product.

   • [claimed-docs] “Install once and your agent picks up the file contract, the CLI and the validate-deploy-verify loop.”
   • [claimed-docs] “Swell CLI is a command-line interface that helps you create and work with apps, themes, and storefronts.”
   • [claimed-docs] “swell app init: initialize an app in the current directory with a default config file and folder structure”
   • [claimed-docs] “swell app push: push configuration files to a development store”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Shopify
   Shopify✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   No evidence of an interactive API reference or runnable examples; probes explicitly show no OpenAPI/Swagger spec and no llms.txt found, and none of the docs mention a live/interactive API explorer.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.swell.is/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.swell.is/openapi.json, https://developers.swell.is/swagger.json, https://develope…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Shopify—none0/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   Direct probes for OpenAPI/Swagger files and llms.txt all returned 404, and no documentation item advertises a downloadable machine-readable API spec; the runtime schema endpoint (swell-docs-9/22) describes store data models, not an OpenAPI contract.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.swell.is/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.swell.is/openapi.json, https://developers.swell.is/swagger.json, https://develope…”
   • [claimed-docs] “One call returns a store’s whole schema at runtime: every model—standard, merchant custom and app-installed alike—with field types and relat…”
   • [claimed-docs] “One call returns a store's whole schema at runtime: every model—standard, merchant custom and app-installed alike—with field types and relat…”

   proof ↗⚑ flag

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

   weight 1 · round to Shopify
   Shopify✓fullclaimed8/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed6/10

   Swell provides environment-specific API keys (sk_test_ vs sk_live_) that route to a store's test environment, and CLI commands reference a 'development store' for pushing configs, indicating a sandbox distinct from production data. However, there's no explicit AI-native workflow documentation tying this test environment to agentic testing loops, and the AI-focused docs emphasize schema/model generation rather than sandbox isolation explicitly. Missing for 10: explicit documentation of an AI agent using the test environment in its validate-deploy-verify loop, and independent/hands-on confirmation that sandbox data is fully isolated from production.

   • [claimed-docs] “Keys are environment-specific: secret keys prefixed sk_test_ route requests to your store's test environment, while sk_live_ keys target liv…”
   • [claimed-docs] “swell app push: push configuration files to a development store”
   • [claimed-docs] “Switch your current default store.”
   • [claimed-docs] “Install once and your agent picks up the file contract, the CLI and the validate-deploy-verify loop.”

   proof ↗⚑ flag

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

   weight 2 · round to Shopify
   Shopify✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   No evidence pack item mentions API versioning or a deprecation policy; probes for openapi.json/llms.txt also failed, suggesting no discoverable machine-readable API spec either. This is a fair question for an API-driven commerce platform, but nothing in the evidence supports it.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.swell.is/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.swell.is/openapi.json, https://developers.swell.is/swagger.json, https://develope…”

   proof ↗⚑ flag

Agent discovery

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

   weight 2 · round to Shopify
   Shopify~partialprobed6/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   Swell's AI-related docs focus on making a single store's own schema/API programmatically accessible to developers/agents building on Swell (schema endpoint, JSON model generation, CLI), not on a cross-merchant catalog or feed that lets external AI agents or answer engines discover products across multiple Swell merchants. No evidence of a shared product feed, marketplace-wide index, or agent-facing discovery layer spanning stores.

   • [claimed-docs] “One call returns a store’s whole schema at runtime: every model—standard, merchant custom and app-installed alike—with field types and relat…”
   • [claimed-docs] “One call returns a store's whole schema at runtime: every model—standard, merchant custom and app-installed alike—with field types and relat…”
   • [claimed-docs] “Drop a JSON file into your app’s models/ directory and Swell generates the REST resource from it—fields, validation, relationships and lifec…”
   • [claimed-docs] “Drop a JSON file into your app's models/ directory and Swell generates the REST resource from it—fields, validation, relationships and lifec…”

   proof ↗⚑ flag

Agent ops

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

   weight 2 · round to Shopify
   Shopify!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   The evidence pack shows Swell has a backend API, webhooks for model events, and stock/inventory adjustment endpoints, but nothing documents order status tracking, fulfillment workflows, or returns/RMA processes exposed via API or webhook events. Without concrete evidence of order-lifecycle endpoints (status changes, fulfillment triggers, return creation/processing), there's no basis to say an agent can manage the full post-purchase lifecycle without human intervention in admin.

   • [claimed-docs] “Webhooks enable real-time communication between the Swell platform and external services, by subscribing to any number of model events.”
   • [claimed-docs] “Stock adjustments are used to keep track of inventory changes over time.”
   • [claimed-docs] “Webhooks can be configured to call a URL when a particular event occurs, enabling outgoing calls to external services.”

   proof ↗⚑ flag

Agentic checkout

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

   weight 3 · round to Shopify
   Shopify✓fullprobed9/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   The evidence shows Swell's AI features target developers building on Swell (schema-introspection API for building resources, CLI tooling) rather than a documented agent-commerce endpoint (MCP/UCP) for external shopping agents to discover products or build carts. No mention of MCP, UCP, or a shopping-agent-facing commerce protocol appears anywhere in the pack, and probes for llms.txt/openapi discovery endpoints return 404.

   • [claimed-docs] “One call returns a store’s whole schema at runtime: every model—standard, merchant custom and app-installed alike—with field types and relat…”
   • [claimed-docs] “Install once and your agent picks up the file contract, the CLI and the validate-deploy-verify loop.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.swell.is/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.swell.is/openapi.json, https://developers.swell.is/swagger.json, https://develope…”

   proof ↗⚑ flag

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

   weight 2 · round to Swell
   Shopify~partialclaimed3/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed4/10

   Swell supports bulk product import/export via CSV (swell-docs-14) and bulk stock tracking (swell-docs-15, swell-docs-28), which are bulk-style operations, but there is no evidence of an AI-native bulk API (e.g., batch create/update/delete endpoints) or agent-driven bulk automation across arbitrary item sets. Missing for 10: documented bulk REST/GraphQL endpoints, agent-callable batch operations, and evidence of scale/performance guarantees for bulk actions.

   • [claimed-docs] “Seamlessly import or export products from CSV files, including product categories.”
   • [claimed-docs] “Create unique product variations with unlimited options and attributes. Track inventory of each variant in real-time.”
   • [claimed-docs] “Stock adjustments are used to keep track of inventory changes over time.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed5/10

   Swell provides webhooks that subscribe to model lifecycle events and trigger calls to external services, plus serverless functions to run custom logic in response to those events, which together enable event-driven automation. However, there is no evidence of a dedicated no-code 'rules engine' or conditional trigger-action UI — automation requires writing webhook handlers/functions rather than defining declarative rules. Missing for 10: a visual/declarative rules builder, conditional logic beyond simple event subscription, and independent evidence of real-world automation use.

   • [claimed-docs] “Webhooks can be configured to call a URL when a particular event occurs, enabling outgoing calls to external services.”
   • [claimed-docs] “Webhooks enable real-time communication between the Swell platform and external services, by subscribing to any number of model events.”
   • [claimed-docs] “Data models can alter a store's database schema, either by adding fields to existing models (like products and orders) or creating completel…”
   • [claimed-docs] “Deploy serverless functions to customize logic and connect to external APIs.”
   • [claimed-docs] “Functions are deployed to edge data centers in 200+ locations and have no cold start time.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Shopify—none0/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   Swell is an e-commerce platform with webhooks, functions, and a CLI, but no evidence describes any scheduling capability for recurring jobs or workflows (cron-like triggers, scheduled functions, or workflow automation timers).

   ⚑ flag

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

   weight 1 · round drawn
   Shopify—none0/10

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

   ⚑ flag

   Swell—none0/10

   Swell is an e-commerce platform; there's no evidence of version control, review workflows, or rollback capability for automations/workflows—CLI push and app config exist but no versioning/review/rollback of automation logic is documented.

   ⚑ flag

B2b

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

   weight 2 · round drawn
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed5/10

   Swell documents customer-group price rules for wholesale/VIP accounts, tiered-price breaks, and running wholesale and retail from a single catalog/dashboard, covering price-list and volume-pricing needs. However, there is no evidence of quote generation or net-terms invoicing functionality anywhere in the pack. missing for 10: quote workflows, net-terms invoicing support, independent/hands-on corroboration of B2B pricing in practice.

   • [claimed-docs] “Use price rules for specific customer groups like wholesale accounts/VIPs, and offer tiered-price breaks.”
   • [claimed-docs] “Run your wholesale and retail operations from a single catalog and dashboard.”
   • [claimed-docs] “Assign specific roles and permissions to team members for better control.”

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

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

   ⚑ flag

   Swell✓fullclaimed9/10

   Strong first-party documentation covers variants/options, custom fields, and extensible data models, but lacks independent/hands-on corroboration. missing for 10: independent verification or hands-on demonstration of custom field/metafield modeling in practice.

   • [claimed-docs] “Create unique product variations with unlimited options and attributes. Track inventory of each variant in real-time.”
   • [claimed-docs] “Integrate business data and custom content with your catalog using custom models and fields.”
   • [claimed-docs] “Data models can alter a store's database schema, either by adding fields to existing models (like products and orders) or creating completel…”
   • [claimed-docs] “Add functionality to the dashboard and backend API with custom models.”
   • [claimed-docs] “One call returns a store’s whole schema at runtime: every model—standard, merchant custom and app-installed alike—with field types and relat…”

   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 Swell
   Shopify~partialcommunity4/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed6/10

   Swell explicitly documents CSV import/export for products and categories, plus a full backend API (with official Node/PHP libraries) that could support bulk editing programmatically. However, there's no direct evidence of a bulk edit UI or batch-update API endpoint distinct from one-at-a-time product edits, and no independent/hands-on corroboration of CSV import/export reliability at scale. Missing for 10: documented bulk-edit UI or batch API endpoint, independent verification of CSV import/export at scale.

   • [claimed-docs] “Seamlessly import or export products from CSV files, including product categories.”
   • [claimed-docs] “Official libraries for the Swell API are available for Node and PHP.”
   • [claimed-docs] “authenticate with basic auth using your store ID as the username and a secret key as the password”

   proof ↗⚑ flag

Inventory

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

   weight 2 · round to Swell
   Shopify—none0/10

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

   ⚑ flag

   Swell~partialclaimed5/10

   Swell documents stock adjustments (swell-docs-28) and real-time variant inventory tracking (swell-docs-15), but there is no explicit evidence of multi-location/multi-warehouse inventory tracking or location-based fulfillment routing. missing for 10: multi-location inventory data model, per-location stock levels, warehouse/location-based fulfillment routing logic, and any hands-on confirmation of these features.

   • [claimed-docs] “Stock adjustments are used to keep track of inventory changes over time.”
   • [claimed-docs] “Create unique product variations with unlimited options and attributes. Track inventory of each variant in real-time.”

   proof ↗⚑ flag

Checkout

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

   weight 3 · round to Shopify
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed4/10

   Swell offers general extension mechanisms—serverless functions for custom logic, webhooks, custom models/fields, and Liquid theme customization—that could plausibly be applied to checkout, and cross-sell/upsell at checkout is mentioned, but there is no documentation specifically describing checkout page field customization, checkout branding controls, or checkout-specific validation hooks as a supported extension point. Missing for 10: explicit checkout page/field customization API or theme section, checkout-specific validation hook docs, discount/promo configuration tied to checkout flow, and any hands-on example of extending checkout without forking.

   • [claimed-docs] “Deploy serverless functions to customize logic and connect to external APIs.”
   • [claimed-docs] “Functions are deployed to edge data centers in 200+ locations and have no cold start time.”
   • [claimed-docs] “Integrate business data and custom content with your catalog using custom models and fields.”
   • [claimed-docs] “Webhooks enable real-time communication between the Swell platform and external services, by subscribing to any number of model events.”
   • [claimed-docs] “Add functionality to the dashboard and backend API with custom models.”
   • [claimed-docs] “Increase sales with cross-sells and upsells on product pages and at checkout.”
   • [claimed-docs] “Create themes using Liquid, with compatibility for Shopify theme tags, filters and objects, supported by our visual theme editor.”

   proof ↗⚑ flag

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

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed4/10

   Changelog entries confirm Apple Pay support for subscriptions via Braintree and a PayPal gateway integration, showing some accelerated-wallet capability, but there's no evidence of Google Pay, platform one-click checkout, or broad (non-subscription) Apple Pay support at general checkout. missing for 10: Google Pay support, platform one-click checkout evidence, confirmation Apple Pay works for all order types (not just subscriptions), independent/hands-on verification of wallet checkout flow.

   • [claimed-docs] “Added Apple Pay support for subscriptions via Braintree.”
   • [claimed-docs] “Implemented PayPal gateway for direct card payments”

   proof ↗⚑ flag

Conversion

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

   weight 1 · round drawn
   Shopify—none0/10

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

   ⚑ flag

   Swell—none0/10

   The evidence pack contains no mention of abandoned cart recovery, cart reminder emails, or checkout recovery links anywhere in Swell's documented features, changelog, or API docs; klaviyo and other marketing integrations are noted only for unrelated SMS opt-in.

   ⚑ flag

App dev

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

   weight 2 · round to Shopify
   Shopify~partialcommunity7/10

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

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

   proof ↗⚑ flag

   Swell~partialprobed6/10

   Swell provides a real developer toolkit: official Node/PHP SDKs, a CLI (`swell app init`, `push`) for scaffolding apps/themes, custom models/functions/webhooks for extending the platform, and theme distribution/upgrade/duplicate features tied to storefront apps like Proxima. However, evidence for a formal app review or marketplace submission/distribution process (beyond theme distribution) is thin, and probes show no discoverable OpenAPI/llms.txt for programmatic SDK generation. Missing for 10: explicit third-party app marketplace/review workflow, broader language SDK coverage, and independent verification of the CLI/SDK experience.

   • [claimed-docs] “swell app init: initialize an app in the current directory with a default config file and folder structure”
   • [claimed-docs] “Swell CLI is a command-line interface that helps you create and work with apps, themes, and storefronts.”
   • [claimed-docs] “swell app push: push configuration files to a development store”
   • [claimed-docs] “Official libraries for the Swell API are available for Node and PHP.”
   • [claimed-docs] “Data models can alter a store's database schema, either by adding fields to existing models (like products and orders) or creating completel…”
   • [claimed-docs] “Add functionality to the dashboard and backend API with custom models.”
   • [claimed-docs] “A storefront app, such as Proxima, may implement themes and thereby support the Swell Theme Editor as well as a number of storefront feature…”
   • [claimed-docs] “may implement themes and thereby support the Swell Theme Editor as well as a number of storefront features such as the ability to upgrade, d…”
   • [probe] “official CLI documented at https://developers.swell.is/apps/cli”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.swell.is/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.swell.is/openapi.json, https://developers.swell.is/swagger.json, https://develope…”

   proof ↗⚑ flag

Apps

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

   weight 3 · round to Shopify
   Shopify~partialcommunity7/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed4/10

   Swell provides a developer framework for building apps/extensions (CLI, functions, webhooks, custom models, themes) and ships one official storefront app (Proxima), but the evidence never describes a merchant-facing marketplace of vetted third-party apps that a merchant can browse and one-click install to cover long-tail features. This story's core—a marketplace ecosystem for merchants—is only implied by the developer app-building tooling, not demonstrated. Missing for 10: evidence of an actual app marketplace/directory, listing of third-party vetted apps, and a merchant-facing install flow beyond the single first-party Proxima app.

   • [claimed-docs] “swell app init: initialize an app in the current directory with a default config file and folder structure”
   • [claimed-docs] “Proxima is Swell's first official storefront app intended to help merchants get started quickly by supporting compatibility with the well-kn…”
   • [claimed-docs] “Install once and your agent picks up the file contract, the CLI and the validate-deploy-verify loop.”
   • [claimed-docs] “Swell CLI is a command-line interface that helps you create and work with apps, themes, and storefronts.”
   • [claimed-docs] “A storefront app, such as Proxima, may implement themes and thereby support the Swell Theme Editor as well as a number of storefront feature…”
   • [claimed-docs] “may implement themes and thereby support the Swell Theme Editor as well as a number of storefront features such as the ability to upgrade, d…”

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

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

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

   proof ↗⚑ flag

   Swell✓fullclaimed8/10

   Swell explicitly supports deploying serverless 'functions' to customize logic and connect to external APIs, deployed at edge locations with no cold start, plus webhooks that subscribe to model events for custom validation/business logic, and custom models/data schema extension via the CLI/app framework — directly matching the story's discounts/shipping/validation-as-hooks use case. Missing for 10: no concrete first-party example of a discount/shipping-specific function, and no independent/hands-on corroboration beyond vendor docs.

   • [claimed-docs] “Deploy serverless functions to customize logic and connect to external APIs.”
   • [claimed-docs] “Functions are deployed to edge data centers in 200+ locations and have no cold start time.”
   • [claimed-docs] “Webhooks enable real-time communication between the Swell platform and external services, by subscribing to any number of model events.”
   • [claimed-docs] “Data models can alter a store's database schema, either by adding fields to existing models (like products and orders) or creating completel…”
   • [claimed-docs] “Add functionality to the dashboard and backend API with custom models.”
   • [claimed-docs] “Swell CLI is a command-line interface that helps you create and work with apps, themes, and storefronts.”
   • [claimed-docs] “Functions have no cold boots and do not require extra time to start up before executing your code.”

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

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

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

   proof ↗⚑ flag

   Swell✓fullprobed7/10

   Docs confirm a backend API with authentication (secret keys), stock adjustments, purchase links, product purchase options, official Node/PHP client libraries, and admin/backend workflows covering products, orders, stock, and purchase configuration — indicating broad programmatic control of commerce entities. However, explicit admin-API endpoints for issuing refunds and triggering fulfillments are not directly cited, and no OpenAPI spec or independent hands-on test of order/refund/fulfillment flows is available (openapi probes 404). missing for 10: explicit refund/fulfillment endpoint documentation, OpenAPI reference, independent/hands-on verification of order-edit and refund calls.

   • [claimed-docs] “Official libraries for the Swell API are available for Node and PHP.”
   • [claimed-docs] “Keys are environment-specific: secret keys prefixed sk_test_ route requests to your store's test environment, while sk_live_ keys target liv…”
   • [claimed-docs] “Purchase links allow you to configure a pre-selected group of products within a cart and direct a customer to its checkout through a designa…”
   • [claimed-docs] “Products can support both purchase options simultaneously.”
   • [claimed-docs] “Stock adjustments are used to keep track of inventory changes over time.”
   • [claimed-docs] “authenticate with basic auth using your store ID as the username and a secret key as the password”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.swell.is/openapi.json, https://developers.swell.is/swagger.json, https://develope…”

   proof ↗⚑ flag

Headless

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

   weight 3 · round to Shopify
   Shopify✓fullclaimed9/10

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

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

   proof ↗⚑ flag

   Swell✓fullprobed8/10

   Swell provides a documented backend REST API with authentication, official Node/PHP libraries, and explicit support for building frontends 'with any framework,' plus a CLI and serverless functions for custom logic — all core pieces needed for a fully custom headless storefront (swell-docs-1,7,8,33,39). missing for 10: a discoverable OpenAPI/machine-readable spec (probe hits 404) and independent/hands-on developer corroboration beyond first-party docs.

   • [claimed-docs] “Build frontends for storefronts and admin workflows with any framework.”
   • [claimed-docs] “Deploy serverless functions to customize logic and connect to external APIs.”
   • [claimed-docs] “Official libraries for the Swell API are available for Node and PHP.”
   • [claimed-docs] “Keys are environment-specific: secret keys prefixed sk_test_ route requests to your store's test environment, while sk_live_ keys target liv…”
   • [claimed-docs] “Swell CLI is a command-line interface that helps you create and work with apps, themes, and storefronts.”
   • [claimed-docs] “authenticate with basic auth using your store ID as the username and a secret key as the password”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.swell.is/openapi.json, https://developers.swell.is/swagger.json, https://develope…”

   proof ↗⚑ flag

Channels

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

   weight 2 · round to Shopify
   Shopify~partialclaimed3/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   Swell's evidence covers catalog management, CSV import/export, custom models, and webhooks/APIs for building integrations, but there is no mention of built-in or official connectors for marketplaces (Amazon, eBay), social commerce (Instagram/Facebook Shop), or shopping feeds (Google Shopping). Webhooks and APIs could theoretically be used to build such sync, but no evidence shows this capability shipped or documented as a channel-sync feature.

   • [claimed-docs] “Seamlessly import or export products from CSV files, including product categories.”
   • [claimed-docs] “Webhooks enable real-time communication between the Swell platform and external services, by subscribing to any number of model events.”
   • [claimed-docs] “Webhooks can be configured to call a URL when a particular event occurs, enabling outgoing calls to external services.”

   proof ↗⚑ flag

Global

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

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed5/10

   Swell docs claim multi-language content and dynamic currency conversion with local-currency pricing via supported gateways (swell-docs-43), which covers localized storefronts and multi-currency/translation aspects of the story. However, there is no evidence addressing duties, customs, or cross-border tax handling, and no independent corroboration of the localization features in practice. Missing for 10: duties/customs handling, cross-border tax automation, hands-on/independent verification of translation and currency features.

   • [claimed-docs] “Localize your stores with multiple content languages and dynamic currency conversion, plus pricing in local currencies with supported paymen…”

   proof ↗⚑ flag

Pos

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

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   No evidence pack item mentions a point-of-sale (POS) product, in-person selling, or a POS syncing with online catalog/inventory/customers; only wholesale/retail catalog unification (swell-docs-30) is mentioned, which is not POS. The axis is applicable since e-commerce platforms commonly offer POS integrations, but no evidence shows Swell delivers this.

   ⚑ flag

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

   weight 2 · round to Swell
   Shopify!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

   Swell~partialprobed7/10

   Swell is headless-commerce with a backend API, custom-model/schema introspection, webhooks and CLI, and docs explicitly state you can 'build frontends for storefronts and admin workflows with any framework,' implying API parity for admin-side tasks. However there's no explicit UI-to-API parity guarantee, no OpenAPI spec (404 on probes), and no independent confirmation that every UI action (e.g., theme editing, reporting) has an API equivalent. Missing for 10: explicit parity documentation, discoverable OpenAPI/schema spec, and third-party confirmation that all admin UI actions are API-accessible.

   • [claimed-docs] “Build frontends for storefronts and admin workflows with any framework.”
   • [claimed-docs] “One call returns a store’s whole schema at runtime: every model—standard, merchant custom and app-installed alike—with field types and relat…”
   • [claimed-docs] “Data models can alter a store's database schema, either by adding fields to existing models (like products and orders) or creating completel…”
   • [claimed-docs] “Swell CLI is a command-line interface that helps you create and work with apps, themes, and storefronts.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.swell.is/openapi.json, https://developers.swell.is/swagger.json, https://develope…”

   proof ↗⚑ flag

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

   weight 3 · round to Swell
   Shopify—none0/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed3/10

   Swell only documents CSV import/export for products and categories, not a comprehensive open-format export of all store data (orders, customers, custom models, etc.), and there's no documented full data-portability or account-closure export mechanism. Missing for 10: evidence of full-store data export (all models/entities) in open formats, a documented data portability/export-all endpoint, and any confirmation that a merchant can fully migrate away with all their data.

   • [claimed-docs] “Seamlessly import or export products from CSV files, including product categories.”

   proof ↗⚑ flag

Processing

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

   weight 2 · round to Swell
   Shopify!disputedcontradicted4/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed5/10

   Evidence shows multiple third-party gateway integrations (PayPal, Braintree/Apple Pay) and multi-currency support via dynamic conversion and localized pricing with supported payment gateways, indicating merchants can use alternate gateways and multi-currency pricing. However, there's no evidence of a general gateway marketplace/plugin system letting merchants freely choose among many third-party gateways, nor detail on how currency charging interacts with each gateway. Missing for 10: comprehensive list/marketplace of supported gateways, clarity on which gateways support multi-currency charging, and independent confirmation of ease of switching gateways.

   • [claimed-docs] “Added Apple Pay support for subscriptions via Braintree.”
   • [claimed-docs] “Implemented PayPal gateway for direct card payments”
   • [claimed-docs] “Localize your stores with multiple content languages and dynamic currency conversion, plus pricing in local currencies with supported paymen…”

   proof ↗⚑ flag

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

   weight 3 · round to Shopify
   Shopify~partialcommunity6/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   Evidence shows Swell relies on third-party gateways (PayPal, Braintree) for payment processing rather than offering its own integrated processing with published card rates, payouts, or fraud tooling. No mention of native rates, payout schedules, or fraud tools is present anywhere in the evidence pack.

   • [claimed-docs] “Added Apple Pay support for subscriptions via Braintree.”
   • [claimed-docs] “Implemented PayPal gateway for direct card payments”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Shopify—none0/10

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

   ⚑ flag

   Swell—none0/10

   No evidence in the pack mentions data residency, region selection, or hosting location choices for stores or data; Swell's docs focus on functions, themes, CLI, and commerce features without addressing data storage location controls.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Shopify—none0/10

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

   ⚑ flag

   Swell—none0/10

   Swell is an e-commerce platform; the evidence pack covers catalog, storefront, apps, and API features but contains no mention of data retention policies, deletion controls, or privacy/data-lifecycle management for AI-native users or otherwise. No evidence exists to support this axis being delivered.

   ⚑ flag

Content

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

   weight 1 · round drawn
   Shopify—none0/10

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

   ⚑ flag

   Swell—none0/10

   The evidence pack shows Swell's admin covers products, categories, pricing, inventory, subscriptions, and custom data models, but there is no mention of built-in pages, blog, or media management features in the admin UI — only vague 'custom content' via custom models (swell-docs-19), which is not the same as a CMS/blog/media library. No documentation of pages, blogs, or media assets being managed alongside products.

   ⚑ flag

Theme dev

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

   weight 2 · round to Swell
   Shopify~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed7/10

   Swell documents a Liquid-based templating layer with Shopify-theme compatibility and a visual theme editor, plus a CLI (`swell app init`, `swell app push`) for creating apps/themes and pushing configs to a development store, which supports a deploy workflow. However there's no explicit mention of a local preview server or git-based version-controlled deploy pipeline beyond pushing to a dev store. missing for 10: explicit local preview/dev-server tooling, explicit version-control (git) integration for theme deploys, independent/hands-on confirmation of the workflow.

   • [claimed-docs] “Create themes using Liquid, with compatibility for Shopify theme tags, filters and objects, supported by our visual theme editor.”
   • [claimed-docs] “Proxima is Swell's first official storefront app intended to help merchants get started quickly by supporting compatibility with the well-kn…”
   • [claimed-docs] “Swell CLI is a command-line interface that helps you create and work with apps, themes, and storefronts.”
   • [claimed-docs] “swell app init: initialize an app in the current directory with a default config file and folder structure”
   • [claimed-docs] “swell app push: push configuration files to a development store”
   • [claimed-docs] “A storefront app, such as Proxima, may implement themes and thereby support the Swell Theme Editor as well as a number of storefront feature…”

   proof ↗⚑ flag

Themes

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

   weight 3 · round to Shopify
   Shopify✓fullcommunity8/10

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

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

   proof ↗⚑ flag

   Swell~partialclaimed5/10

   Swell offers a visual theme editor and Liquid-based themes compatible with Shopify Online Store 2.0 structure, plus a first-party storefront app (Proxima) meant to help merchants get started quickly and customize look/feel, along with no-code drag-and-drop category management. However, the bulk of Swell's documentation frames storefronts as developer-built (custom frontends, CLI, JSON model files, functions), suggesting the 'no-code for merchants' experience is thinner than the theme-editor claim implies, and there's no evidence of a marketplace of multiple professionally designed themes beyond Proxima. Missing for 10: evidence of a broader theme marketplace, hands-on/independent proof the visual editor supports full no-code section/layout customization, and clarity on how much coding is truly unnecessary for typical merchants.

   • [claimed-docs] “Create themes using Liquid, with compatibility for Shopify theme tags, filters and objects, supported by our visual theme editor.”
   • [claimed-docs] “Themes are optionally implemented by storefront apps to make it easier for merchants to customize the look and feel of their store.”
   • [claimed-docs] “Design category trees to help your customers find products. Manage it all with simple drag-and-drop.”
   • [claimed-docs] “Proxima is Swell's first official storefront app intended to help merchants get started quickly by supporting compatibility with the well-kn…”
   • [claimed-docs] “A storefront app, such as Proxima, may implement themes and thereby support the Swell Theme Editor as well as a number of storefront feature…”
   • [claimed-docs] “may implement themes and thereby support the Swell Theme Editor as well as a number of storefront features such as the ability to upgrade, d…”

   proof ↗⚑ flag

Shipping

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

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   No evidence of live carrier rate shopping, label purchasing, or shipment tracking integrations anywhere in the evidence pack; only stock adjustments and general inventory tracking are mentioned, which is unrelated to shipping/carrier functionality.

   ⚑ flag

Taxes

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

   weight 2 · round to Shopify
   Shopify~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Swell—none0/10

   No evidence in the pack mentions automatic sales tax or VAT calculation, jurisdiction-based rate updates, or tax filing/reporting; the pack only covers themes, apps, CLI, catalog, and dev tooling.

   ⚑ flag