[ { "productId": "bigcommerce", "storyId": "abandoned-cart-recovery", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions abandoned cart recovery, abandoned checkout emails, or cart recovery links; coverage focuses on APIs, headless architecture, webhooks, B2B, and theming, none of which address this specific merchant capability.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "admin-commerce-api", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "First-party docs confirm REST/GraphQL Admin APIs for managing products, orders, customers and store settings, with scoped API-account credentials and a sandbox for testing (bigcommerce-docs-30, docs-32, docs-38, docs-39) plus webhooks for event-driven workflows (bigcommerce-docs-5). However, the evidence never explicitly names refund or fulfillment-triggering endpoints, and one hands-on account reports the API was unreliable, suffering throttling/dropped connections (bigcommerce-comm-4), which tempers confidence in full lifecycle reliability. Missing for 10: explicit refund/fulfillment API documentation, independent verification of stable high-volume API usage, and third-party confirmation of full CRUD lifecycle beyond vendor docs.", "evidenceIds": [ "bigcommerce-docs-30", "bigcommerce-docs-32", "bigcommerce-docs-38", "bigcommerce-docs-39", "bigcommerce-docs-5", "bigcommerce-comm-4" ] }, { "productId": "bigcommerce", "storyId": "agent-catalog-discovery", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows BigCommerce's developer docs and APIs (REST/GraphQL, headless storefronts, an llms.txt for AI agents to navigate developer docs) but nothing about a cross-merchant product catalog or feed designed to make individual merchants' products discoverable by AI agents/answer engines across the platform. The llms.txt probe is aimed at documentation discovery, not a product feed for agent commerce.", "evidenceIds": [ "bigcommerce-probe-1", "bigcommerce-docs-18", "bigcommerce-docs-25" ] }, { "productId": "bigcommerce", "storyId": "agent-order-lifecycle", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "BigCommerce documents REST/GraphQL APIs for managing orders programmatically and a webhooks system for event-driven integrations, which supports agent-driven order status/fulfillment automation without human admin interaction. However, the evidence never specifically documents returns/RMA endpoints, order-status-change webhook topics, or a fulfillment workflow API, and one community report raises concerns about API reliability/throttling under load. Missing for 10: explicit docs on returns/RMA API, order-status webhook event list, fulfillment API detail, and independent confirmation of reliable agent-driven order lifecycle automation.", "evidenceIds": [ "bigcommerce-docs-30", "bigcommerce-docs-25", "bigcommerce-docs-5", "bigcommerce-docs-34", "bigcommerce-comm-4" ] }, { "productId": "bigcommerce", "storyId": "agent-storefront-commerce", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence shows only general REST/GraphQL APIs, webhooks, Catalyst, and an llms.txt for AI-assisted docs browsing — no documented MCP/UCP agent-commerce endpoint enabling an AI shopping agent to discover products and build carts is mentioned anywhere in the pack.", "evidenceIds": [ "bigcommerce-docs-25", "bigcommerce-docs-18", "bigcommerce-probe-1" ] }, { "productId": "bigcommerce", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "A direct probe confirms developer.bigcommerce.com/llms.txt returns HTTP 200 with structured content including an explicit 'Instructions for AI Agent' section, directly satisfying the story's requirement of agent-discoverable docs. Missing for 10: no independent/community confirmation of agents actually using it, and no broader agent-oriented doc ecosystem (e.g., MCP server, structured API docs for agents) beyond the single llms.txt file.", "evidenceIds": [ "bigcommerce-probe-1" ] }, { "productId": "bigcommerce", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence only shows AI-powered search/chat on the developer documentation portal (bigcommerce-docs-16, bigcommerce-docs-27), not AI-generated insights or suggestions derived from a merchant's actual store/sales data. No mention of AI analytics, product recommendations, or in-product insight generation from BigCommerce's own data.", "evidenceIds": [ "bigcommerce-docs-16", "bigcommerce-docs-27" ] }, { "productId": "bigcommerce", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows BigCommerce offers webhooks and REST/GraphQL APIs for building integrations, but nothing describes a way for an AI-native user to configure autonomous background automations (e.g., scheduled agents, workflow triggers, or persistent background jobs) within the platform itself. Webhooks are reactive event hooks requiring external infrastructure to act on them, not a built-in autonomous automation feature.", "evidenceIds": [ "bigcommerce-docs-5", "bigcommerce-docs-25", "bigcommerce-docs-26" ] }, { "productId": "bigcommerce", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence only shows AI-powered search/chat on the developer docs site and an llms.txt file for AI agents crawling documentation, not a built-in AI assistant inside the BigCommerce product to which a user can delegate store-management tasks. No mention of an in-product agentic assistant capable of taking actions on behalf of the user.", "evidenceIds": [ "bigcommerce-docs-16", "bigcommerce-docs-27", "bigcommerce-probe-1" ] }, { "productId": "bigcommerce", "storyId": "agentic-headless", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "BigCommerce exposes REST/GraphQL APIs with OAuth-based API accounts and sandbox environments explicitly meant for scripted, non-UI automation of store management and headless storefronts, which supports CI-style programmatic use. However there's no dedicated CLI or CI/CD-native tooling, and a community report describes unreliable API connectivity/throttling that undermines confidence in dependable automation. Missing for 10: an official CLI, documented CI/CD pipeline integration, and confirmation the throttling issue is resolved.", "evidenceIds": [ "bigcommerce-docs-30", "bigcommerce-docs-31", "bigcommerce-docs-32", "bigcommerce-docs-38", "bigcommerce-docs-39", "bigcommerce-comm-4" ] }, { "productId": "bigcommerce", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "BigCommerce is an e-commerce SaaS platform; the evidence shows REST/GraphQL APIs, webhooks, apps marketplace, and llms.txt for AI agents reading docs, but no mention of an MCP client/host feature allowing users to plug MCP servers into BigCommerce so it can use their tools.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "BigCommerce is an ecommerce platform (not an agent), so the MCP-server axis applies, but no evidence shows an official MCP server; docs mention REST/GraphQL APIs, webhooks, and an llms.txt file for AI agent guidance, none of which constitute an MCP server implementation. Missing for 10: any mention of an MCP server, MCP endpoint, or MCP-compatible integration.", "evidenceIds": [ "bigcommerce-docs-25", "bigcommerce-docs-30", "bigcommerce-probe-1" ] }, { "productId": "bigcommerce", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 2, "confidence": "low", "rationale": "Docs mention 'AI-powered search and chat' and 'AI-ready page actions' on the developer portal, and an llms.txt file exists with instructions for AI agents, suggesting some agentic/NL tooling around the developer docs, but there is no evidence that a user can actually operate the storefront/store management (products, orders, settings) via natural-language commands. Missing for 10: concrete NL command interface for store operations, evidence of chat-driven catalog/order management, independent hands-on confirmation.", "evidenceIds": [ "bigcommerce-docs-16", "bigcommerce-docs-27", "bigcommerce-probe-1" ] }, { "productId": "bigcommerce", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence covers REST/GraphQL APIs, SDKs, API clients, and an llms.txt AI-agent instructions file, but there is no mention of an official BigCommerce CLI tool anywhere in the pack. missing for 10: an official CLI product/tool, its documentation, install instructions, and any command reference.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "agentic-public-api", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "BigCommerce ships extensive first-party documentation for REST and GraphQL APIs, OAuth-based API accounts (store/app/account-level), webhooks, sandboxes, an in-browser Request Runner, and API client SDKs, explicitly positioned for programmatic/automated store management and headless integration. It even exposes an llms.txt with AI-agent-specific instructions, signaling deliberate AI-native accessibility. Missing for 10: independent/third-party corroboration of large-scale programmatic API reliability (one dated community comment mentions throttling/connection issues, but it's secondhand and not a definitive contradiction of documented capability).", "evidenceIds": [ "bigcommerce-docs-25", "bigcommerce-docs-30", "bigcommerce-docs-39", "bigcommerce-docs-33", "bigcommerce-docs-38", "bigcommerce-docs-18", "bigcommerce-probe-1" ] }, { "productId": "bigcommerce", "storyId": "agentic-scoped-keys", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "BigCommerce docs describe OAuth-based API accounts with configurable scopes (store-level, app-level, account-level) created via Settings > API Accounts, which supports issuing least-privilege credentials, but nothing ties this explicitly to AI-agent use cases or agent-specific scoping/rotation controls. missing for 10: agent-specific credential guidance, fine-grained per-agent scope templates, independent/hands-on verification of scope enforcement.", "evidenceIds": [ "bigcommerce-docs-32", "bigcommerce-docs-39", "bigcommerce-docs-30" ] }, { "productId": "bigcommerce", "storyId": "agentic-sdks", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "BigCommerce documents official SDKs/tools (Checkout SDK, API Clients library, design system SDK) plus REST/GraphQL APIs, sandboxes, and API account setup, giving AI-native builders a well-documented path to build against first-party SDKs. Community reports of API throttling/incomplete ecosystem introduce some quality caveats but don't contradict SDK existence. Missing for 10: independent hands-on corroboration of SDK reliability/quality and AI-specific SDK usage examples.", "evidenceIds": [ "bigcommerce-docs-35", "bigcommerce-docs-36", "bigcommerce-docs-37", "bigcommerce-docs-30", "bigcommerce-docs-38", "bigcommerce-comm-4" ] }, { "productId": "bigcommerce", "storyId": "agentic-webhooks", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "BigCommerce has dedicated Webhooks documentation covering event subscription, including cloud pub/sub webhook delivery, confirming first-party webhook support for external event notification. Missing for 10: independent hands-on confirmation of webhook reliability, full event catalog details, and AI-specific framing of webhook consumption.", "evidenceIds": [ "bigcommerce-docs-5", "bigcommerce-docs-26", "bigcommerce-docs-34" ] }, { "productId": "bigcommerce", "storyId": "api-interactive-docs", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "BigCommerce's developer docs explicitly describe an interactive API Reference with an embedded 'Request Runner' letting developers experiment with REST/GraphQL calls directly in the browser, plus AI-powered search/chat and AI-ready page actions layered on the docs site. This matches the story of an interactive, runnable API reference well. Missing for 10: independent/hands-on user corroboration of the Request Runner experience and no explicit mention of GraphQL runnable examples alongside REST.", "evidenceIds": [ "bigcommerce-docs-33", "bigcommerce-docs-16", "bigcommerce-docs-27", "bigcommerce-docs-25" ] }, { "productId": "bigcommerce", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence pack item mentions an OpenAPI (or equivalent machine-readable) spec file being available for download; references only cover REST/GraphQL usage, API Reference and Request Runner tools, not a downloadable spec artifact.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "api-sandbox", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "BigCommerce's developer docs explicitly describe creating a sandbox store ('Partner Use Sandbox') and a free trial store to 'test API calls and build integrations without affecting live data,' plus an in-browser Request Runner for experimenting with REST calls safely. This directly satisfies the story of testing without touching production data. Missing for 10: independent/hands-on community confirmation that the sandbox behaves identically to production and any AI-agent-specific sandbox tooling.", "evidenceIds": [ "bigcommerce-docs-31", "bigcommerce-docs-38", "bigcommerce-docs-33", "bigcommerce-docs-39" ] }, { "productId": "bigcommerce", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack documents BigCommerce's REST/GraphQL APIs, sandboxes, and API account scopes, but nowhere mentions API versioning schemes or a documented deprecation/sunset policy for endpoints. missing for 10: explicit API version numbering scheme, deprecation notice process, sunset timelines, changelog of breaking changes.", "evidenceIds": [ "bigcommerce-docs-25", "bigcommerce-docs-30", "bigcommerce-docs-39" ] }, { "productId": "bigcommerce", "storyId": "app-extension-marketplace", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "BigCommerce documents an app marketplace ('Over 1,200 apps to help you grow') and developer APIs to build single-click marketplace apps, but there's no detail on vetting/curation processes, and a hands-on community report describes the app ecosystem as 'rather incomplete' with API reliability issues. missing for 10: vetting/curation details, marketplace category breadth evidence, more recent independent corroboration of app quality/coverage.", "evidenceIds": [ "bigcommerce-docs-10", "bigcommerce-docs-3", "bigcommerce-comm-4" ] }, { "productId": "bigcommerce", "storyId": "automation-bulk-operations", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "BigCommerce documents REST and GraphQL APIs for programmatically managing products, orders, and customers (bigcommerce-docs-30, bigcommerce-docs-25), which could technically enable scripted bulk operations, but there is no explicit documentation of batch/bulk endpoints, rate-limit handling, or bulk-import tooling for AI-driven workflows. One community report also notes historical API throttling/reliability issues (bigcommerce-comm-4), suggesting bulk API use may face friction, though this is anecdotal and not a concrete documented failure of a specific bulk feature. Missing for 10: dedicated bulk/batch API documentation, explicit rate-limit or pagination guidance for large-scale operations, and independent verification of reliable bulk throughput.", "evidenceIds": [ "bigcommerce-docs-30", "bigcommerce-docs-25", "bigcommerce-comm-4" ] }, { "productId": "bigcommerce", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "BigCommerce provides webhooks that fire on store events, which can trigger external automation, but there's no evidence of a native rules engine allowing users to define conditional trigger-action automations within the platform itself. missing for 10: native if-this-then-that rules builder, documentation of event-to-action automation configuration, evidence of AI-native or no-code rule definition UI.", "evidenceIds": [ "bigcommerce-docs-5", "bigcommerce-docs-26", "bigcommerce-docs-34" ] }, { "productId": "bigcommerce", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any scheduling, cron, or recurring workflow/job automation capability; evidence only covers APIs, webhooks, theming, and headless commerce features. missing for 10: any scheduler/cron API, workflow automation engine, or documented way to run recurring jobs.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any versioning, review, or rollback mechanism for automations/workflows (e.g., webhooks, scripts, or app configs) in BigCommerce docs; evidence covers APIs, headless storefronts, and webhooks setup but nothing about version history, diffing, or reverting automation changes.", "evidenceIds": [ "bigcommerce-docs-5", "bigcommerce-docs-26", "bigcommerce-docs-34", "bigcommerce-docs-25" ] }, { "productId": "bigcommerce", "storyId": "b2b-wholesale-selling", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "BigCommerce documents a dedicated 'B2B Edition' offering company accounts, quotes, and custom pricing for wholesale/enterprise buyers alongside standard DTC storefronts, directly matching the story's core asks (customer-specific pricing, quotes, B2B accounts). Missing for 10: explicit detail on volume/tiered pricing rules, net-terms invoicing workflow specifics, and independent/hands-on corroboration of B2B Edition in practice.", "evidenceIds": [ "bigcommerce-docs-12", "bigcommerce-docs-20", "bigcommerce-docs-28" ] }, { "productId": "bigcommerce", "storyId": "bulk-catalog-operations", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Docs confirm REST/GraphQL APIs to programmatically manage products, orders, and store settings (bigcommerce-docs-30, bigcommerce-docs-25), which supports bulk catalog operations via API, but there is no explicit documentation of a native CSV bulk import/export tool for the catalog in this evidence pack, and one community report flags historical API reliability/throttling issues (bigcommerce-comm-4). missing for 10: explicit CSV import/export feature docs, UI walkthrough for bulk edit, independent confirmation of reliable bulk operations at scale.", "evidenceIds": [ "bigcommerce-docs-30", "bigcommerce-docs-25", "bigcommerce-docs-32", "bigcommerce-comm-4" ] }, { "productId": "bigcommerce", "storyId": "checkout-customization", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "BigCommerce explicitly advertises the ability to 'extend checkout' via its developer platform and provides a dedicated Checkout SDK (checkout-sdk-js) as a supported extension point rather than requiring a full checkout fork [bigcommerce-docs-3][bigcommerce-docs-36]. However, the evidence pack gives no detail on specific extension points for custom fields, branding theming, discount logic, or validation rules within checkout, nor any independent/hands-on confirmation that these specific capabilities work as described. Missing for 10: documented API/SDK methods for custom checkout fields, branding customization, discount rule injection, and validation logic, plus independent developer corroboration of these specific capabilities.", "evidenceIds": [ "bigcommerce-docs-3", "bigcommerce-docs-36" ] }, { "productId": "bigcommerce", "storyId": "content-pages-blogs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers storefront theming (Stencil), headless APIs, webhooks, and apps, but contains no mention of an admin-side content/blog/pages/media management module for merchants; the only content-adjacent evidence is about theme file structure and API-driven storefront building, not admin content authoring.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "custom-app-development", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "BigCommerce documents a broad developer toolkit — REST/GraphQL APIs, Checkout SDK, API Clients, Catalyst (Next.js) and Stencil (Handlebars) scaffolding, sandbox/trial stores, OAuth API accounts, and a single-click app marketplace for distribution — giving solid first-party coverage of SDKs, scaffolding, and a distribution channel. However, there's no detailed documented app review/certification workflow, and hands-on community reports describe the Stencil theming system as inconsistent and hard to work with and cite unreliable API connections/throttling, undercutting the polish of the developer experience. Missing for 10: an explicit documented app-review/certification process, a dedicated CLI scaffolding tool, and independent corroboration that the SDK/tooling experience is smooth in practice.", "evidenceIds": [ "bigcommerce-docs-3", "bigcommerce-docs-35", "bigcommerce-docs-36", "bigcommerce-docs-37", "bigcommerce-docs-38", "bigcommerce-docs-39", "bigcommerce-docs-6", "bigcommerce-comm-4", "bigcommerce-comm-6" ] }, { "productId": "bigcommerce", "storyId": "express-wallet-checkout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Evidence pack mentions a general payments page (bigcommerce-docs-14/23) but provides no specifics about Apple Pay, Google Pay, PayPal, or one-click wallet checkout support; no documentation or community confirmation of accelerated wallet checkout flows. missing for 10: mention of specific wallet integrations (Apple Pay, Google Pay, PayPal one-click), checkout flow details, or merchant/customer confirmation of wallet usage.", "evidenceIds": [ "bigcommerce-docs-14", "bigcommerce-docs-23" ] }, { "productId": "bigcommerce", "storyId": "gateway-choice-multicurrency", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "BigCommerce has a dedicated payments page referencing multiple payment providers/credit card solutions, implying support for third-party gateways, but there is no explicit documentation confirming a marketplace of alternative gateways or multi-currency charging capability. missing for 10: explicit list/count of supported third-party payment gateways, documentation of multi-currency checkout/settlement support, and independent confirmation of gateway flexibility.", "evidenceIds": [ "bigcommerce-docs-14", "bigcommerce-docs-23" ] }, { "productId": "bigcommerce", "storyId": "headless-storefront-api", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "BigCommerce provides well-documented GraphQL Storefront API and a first-party headless frontend framework (Catalyst, built on Next.js), plus REST/GraphQL management APIs, SDKs, and sandbox tooling for developers to build fully custom storefronts (bigcommerce-docs-1, -2, -7, -18, -25, -29, -36). Community evidence corroborates decent API/dev experience for local development with live data (bigcommerce-comm-1), though older complaints exist about API reliability and Stencil theme complexity that are tangential to the modern headless stack. Missing for 10: recent independent hands-on validation specifically of Catalyst/GraphQL Storefront API at production scale, and clearer confirmation the API throttling issues (from older community reports) have been resolved.", "evidenceIds": [ "bigcommerce-docs-1", "bigcommerce-docs-2", "bigcommerce-docs-7", "bigcommerce-docs-18", "bigcommerce-docs-25", "bigcommerce-docs-29", "bigcommerce-docs-36", "bigcommerce-comm-1" ] }, { "productId": "bigcommerce", "storyId": "international-selling", "verdict": "partial", "quality": 2, "confidence": "low", "rationale": "BigCommerce's 'Multi-Site' solution promotes 'Multiple Brands and Regions' which gestures at localized storefronts, but the evidence pack contains no explicit documentation of multi-currency pricing, storefront translations, or duty/tax handling for international sales. Missing for 10: explicit multi-currency pricing docs, translation/localization tooling, duties/customs handling, and any independent confirmation these features work end-to-end.", "evidenceIds": [ "bigcommerce-docs-11", "bigcommerce-docs-19" ] }, { "productId": "bigcommerce", "storyId": "inventory-multi-location", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Evidence covers headless storefront APIs, theming, B2B, webhooks, and general API tooling, but nothing addresses multi-location inventory tracking, stock adjustments, or location-based fulfillment routing. missing for 10: multi-location inventory API/docs, stock adjustment workflows, warehouse-based fulfillment logic, any first-party or community confirmation of these capabilities.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "marketplace-social-channels", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "BigCommerce's marketing pages reference an 'Omnichannel Ecommerce Software Solution' and a large app marketplace (1,200+ apps) that could include channel-sync apps, but the evidence pack contains no concrete documentation of specific marketplace/social/shopping-feed integrations (e.g., Amazon, Google Shopping, Facebook/Instagram) or a dedicated channel-manager feature. Missing for 10: explicit docs on channel listing/sync workflows, named integrations (Amazon, eBay, Google Shopping, TikTok, Instagram), and any first-party or independent confirmation these work reliably.", "evidenceIds": [ "bigcommerce-docs-13", "bigcommerce-docs-21", "bigcommerce-docs-10" ] }, { "productId": "bigcommerce", "storyId": "native-payment-processing", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Evidence only shows a page title 'Ecommerce Payment Providers & Credit Card Solutions' (BigCommerce Payments) exists, confirming some integrated payments offering, but there is no detail on published card rates, payout schedules, or fraud tooling specifics, nor any independent confirmation it works without a third-party gateway. Missing for 10: documented rate sheet, payout timing details, fraud/chargeback tooling specifics, and hands-on/community corroboration of using it without a third-party gateway.", "evidenceIds": [ "bigcommerce-docs-14", "bigcommerce-docs-23" ] }, { "productId": "bigcommerce", "storyId": "openness-api-parity", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "BigCommerce documents broad REST and GraphQL API coverage for products, orders, customers, store settings, checkout, webhooks, B2B, and multi-store management, suggesting most UI operations have API equivalents, and even provides sandbox/trial environments and an API Request Runner for testing. However, there is no explicit vendor statement guaranteeing 100% UI-to-API parity, and a community report notes historical issues with reliably connecting to the API without throttling. Missing for 10: an explicit parity guarantee/documentation mapping every control-panel action to an API endpoint, and independent hands-on confirmation that all admin UI actions (e.g., full theme/store configuration) are API-accessible without gaps.", "evidenceIds": [ "bigcommerce-docs-25", "bigcommerce-docs-30", "bigcommerce-docs-32", "bigcommerce-docs-33", "bigcommerce-docs-38", "bigcommerce-comm-4" ] }, { "productId": "bigcommerce", "storyId": "openness-full-export", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "BigCommerce exposes REST and GraphQL APIs that can be used to pull products, orders, customers, and settings programmatically (bigcommerce-docs-30, bigcommerce-docs-25), which gives a technical path to extract data in open JSON formats, but there is no documented bulk 'export all my data' feature, data-portability guarantee, or migration-out tooling. missing for 10: explicit full-account data export/download feature, documented data portability/GDPR-style export policy, and evidence of successful full data migration away from BigCommerce.", "evidenceIds": [ "bigcommerce-docs-30", "bigcommerce-docs-25", "bigcommerce-docs-4" ] }, { "productId": "bigcommerce", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "BigCommerce is a proprietary SaaS platform; no evidence indicates its core source code is published under an open license (only design system and SDKs like the Checkout SDK/design system are noted as open source, not the platform itself). missing for 10: any statement that BigCommerce's core product source is open-licensed or publicly viewable.", "evidenceIds": [ "bigcommerce-docs-37" ] }, { "productId": "bigcommerce", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "BigCommerce is a SaaS-hosted ecommerce platform with no self-hosted/on-prem deployment option in evidence; self-hosting the core product is not a category fit for this managed platform.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "pos-in-person-sales", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence covers headless APIs, theming, B2B, multi-store, payments, and webhooks, but there is no mention of a native point-of-sale product or integration that syncs catalog/inventory/customers with a physical retail POS system. Omnichannel page is referenced but no details show POS capability.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of data residency/region selection controls anywhere in the pack; docs only cover APIs, theming, headless commerce, and multi-store branding, none of which address data storage location choice.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack addresses AI-training data opt-out or privacy controls preventing BigCommerce data from being used to train AI models; all evidence concerns APIs, headless commerce, themes, and developer tooling. Missing for 10: any privacy policy, data-use opt-out setting, or AI training exclusion documentation.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence addresses AI-native data retention/deletion controls—nothing about data lifecycle policies, deletion APIs, or retention settings for AI agents or data processed by AI tools; evidence only covers commerce APIs, theming, and app ecosystem.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses telemetry/usage-tracking opt-out controls for AI-native users; all docs and community items concern APIs, theming, and commerce features. missing for 10: any mention of telemetry, analytics opt-out, or privacy/data-collection settings.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "product-variant-modeling", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The axis clearly applies to an ecommerce platform, but the evidence pack contains no documentation or community mentions of product variants, options, custom fields, or metafields — only generic references to REST/GraphQL APIs for 'managing products' and building headless storefronts. Missing for 10: any docs on variant/option modeling, custom fields, or metafield support, and any independent confirmation of catalog flexibility beyond a fixed template.", "evidenceIds": [ "bigcommerce-docs-30", "bigcommerce-docs-25" ] }, { "productId": "bigcommerce", "storyId": "serverless-commerce-functions", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows only webhooks (event notifications), REST/GraphQL APIs, and third-party app integrations — none of which are serverless functions or hooks that execute custom backend logic (discounts, shipping, validation) inside the platform itself. Missing for 10: any documentation of a functions/hooks runtime, script execution environment, or in-platform custom logic injection comparable to Shopify Functions.", "evidenceIds": [ "bigcommerce-docs-5", "bigcommerce-docs-26", "bigcommerce-docs-34", "bigcommerce-docs-3", "bigcommerce-docs-25" ] }, { "productId": "bigcommerce", "storyId": "shipping-rates-labels", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items reference live carrier rate shopping, label purchasing, or shipment tracking within BigCommerce checkout; the evidence focuses on APIs, theming, headless commerce, and marketplace apps, not shipping/carrier integration. This is a fair axis for an ecommerce platform (shipping apps and carrier integrations are common in the category), but nothing shows BigCommerce natively delivers it.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "tax-calculation-automation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items mention tax/VAT calculation, jurisdiction-based rates, rate updates, or tax filing/reporting features; the evidence covers APIs, theming, headless commerce, and B2B/webhooks instead.", "evidenceIds": [] }, { "productId": "bigcommerce", "storyId": "theme-code-customization", "verdict": "disputed", "quality": 5, "confidence": "medium", "rationale": "BigCommerce documents a Handlebars-based theme engine (Stencil) as its templating layer, and a hands-on HN comment confirms local development with live product data. However another hands-on account describes the same theme system as having 'hundreds of theme files' and a 'maddeningly incomplete and inconsistent templating tag system,' directly contradicting the claim that customization is well-documented and smooth. Missing for 10: no dedicated docs on Stencil CLI local preview workflow, no explicit version-controlled/git-based theme deploy pipeline evidence, and no independent corroboration resolving the conflicting community reports.", "evidenceIds": [ "bigcommerce-docs-6", "bigcommerce-docs-24", "bigcommerce-comm-1", "bigcommerce-comm-6" ] }, { "productId": "bigcommerce", "storyId": "theme-storefront-launch", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "BigCommerce docs confirm a Stencil theme engine for hosted storefronts and marketing copy stating stores can be built 'with or without code,' implying pre-designed themes plus customization options, alongside marketplace apps for extending functionality (bigcommerce-docs-6, bigcommerce-docs-8, bigcommerce-docs-10). However, a hands-on community account explicitly describes BigCommerce theme customization as one of the worst web-dev experiences due to 'hundreds of theme files' and an 'inconsistent templating tag system' (bigcommerce-comm-6), undercutting the no-code simplicity claim for anything beyond basic use. Missing for 10: explicit documentation of a visual drag-and-drop page builder/section editor for non-technical merchants, a gallery of professionally designed themes, and independent praise confirming ease of no-code branding/layout changes.", "evidenceIds": [ "bigcommerce-docs-6", "bigcommerce-docs-8", "bigcommerce-docs-10", "bigcommerce-comm-6" ] }, { "productId": "medusa", "storyId": "abandoned-cart-recovery", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Medusa's evidence pack covers cart, order, payment modules and general commerce architecture, but there is no mention of abandoned cart detection, recovery email triggers, or checkout-recovery links/workflows anywhere in the docs, GitHub, or community sources. This is a plausible axis for a commerce platform (notification/workflow modules could support it), but no evidence shows it shipping.", "evidenceIds": [ "medusa-docs-22", "medusa-docs-24", "medusa-gh-1" ] }, { "productId": "medusa", "storyId": "admin-commerce-api", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Medusa documents commerce modules (Product, Order, Cart, Payment, Fulfillment, Tax) and maintains OpenAPI specs powering Admin/Store REST APIs, confirming programmatic control over products, orders, refunds, and fulfillment via the admin API. However, the evidence pack lacks a direct hands-on example of issuing a refund or triggering fulfillment through the API, and the openapi.json probe for the admin spec 404s despite the store spec being confirmed. missing for 10: direct admin API refund/fulfillment usage examples, independent developer corroboration of admin API completeness, working openapi.json endpoint discovery.", "evidenceIds": [ "medusa-docs-21", "medusa-docs-22", "medusa-docs-23", "medusa-docs-24", "medusa-docs-26", "medusa-gh-x1", "medusa-probe-2" ] }, { "productId": "medusa", "storyId": "agent-catalog-discovery", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Medusa's MCP server only exposes its own developer documentation to AI tools like Cursor (medusa-docs-4, medusa-docs-33/37, medusa-probe-3), not merchant product catalogs. There is no evidence of a cross-merchant catalog, agent-facing product feed, or discoverability mechanism for storefront products by AI agents/answer engines — the OpenAPI probe for a public product feed also failed (medusa-probe-2).", "evidenceIds": [ "medusa-docs-4", "medusa-docs-33", "medusa-docs-37", "medusa-probe-2", "medusa-probe-3" ] }, { "productId": "medusa", "storyId": "agent-order-lifecycle", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Medusa documents dedicated Order, Fulfillment, and Payment modules and publishes a machine-readable OpenAPI 3.0 spec for its Store/Admin REST APIs (medusa-docs-23, medusa-docs-26, medusa-gh-x1), and a community comment confirms built-in returns/exchange ('swap') handling (medusa-comm-10) — together suggesting an agent could programmatically track and update post-purchase order states. However, the pack has no explicit documentation of a returns/RMA API endpoint, no concrete webhook payload/event schema (Webhook Events appears only as a Cloud pricing bullet, medusa-docs-16), and no example flow showing an agent completing status→fulfillment→return without touching the admin UI. Missing for 10: explicit returns/RMA API docs, concrete webhook event schema/trigger docs, and an end-to-end agent-without-admin example.", "evidenceIds": [ "medusa-docs-23", "medusa-docs-26", "medusa-gh-x1", "medusa-comm-10", "medusa-docs-16" ] }, { "productId": "medusa", "storyId": "agent-storefront-commerce", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Medusa's documented MCP server (medusa-docs-4/33/37, probe-3) is scoped to searching Medusa's documentation for IDEs/AI coding tools, not a storefront-facing agent-commerce endpoint for product discovery or cart building; the Store REST/OpenAPI (medusa-gh-x1) exists but is a generic commerce API, not a documented MCP/UCP agent-commerce interface. No evidence of any UCP or dedicated shopping-agent MCP endpoint on the storefront itself.", "evidenceIds": [ "medusa-docs-4", "medusa-docs-33", "medusa-docs-37", "medusa-probe-3", "medusa-gh-x1", "medusa-docs-22" ] }, { "productId": "medusa", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Medusa has a verified live llms.txt file (HTTP 200) describing the platform for AI agents, plus a documented official MCP server for querying docs directly from AI tools/IDEs like Cursor, confirming agent-oriented documentation access is a first-class supported pathway. Missing for 10: independent third-party confirmation of agents successfully using llms.txt in practice beyond the probe check.", "evidenceIds": [ "medusa-probe-1", "medusa-docs-4", "medusa-docs-37", "medusa-probe-3" ] }, { "productId": "medusa", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence only shows an MCP server for querying Medusa's documentation (medusa-docs-4, medusa-docs-33/37) and generic 'guardrails for agents to build customizations' marketing copy — nothing shows Medusa surfacing AI-generated insights or suggestions derived from a merchant's own commerce data (orders, inventory, sales trends). missing for 10: any feature generating insights/recommendations from store data, admin dashboard AI analytics, or product evidence of in-app AI suggestions.", "evidenceIds": [ "medusa-docs-4", "medusa-docs-33", "medusa-docs-37", "medusa-docs-13" ] }, { "productId": "medusa", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "The pricing/docs evidence mentions 'Background workers' and 'Webhook Events' as platform features that could underpin autonomous background automations, and a 'Cloud Development Agent' is referenced, but none of the evidence describes an actual workflow/scheduler/automation-builder interface an AI-native user would configure. Missing for 10: documented workflow/scheduled-job engine, concrete setup instructions for autonomous background automations, and independent confirmation these run unattended.", "evidenceIds": [ "medusa-docs-30", "medusa-docs-16", "medusa-docs-15" ] }, { "productId": "medusa", "storyId": "agentic-builtin-assistant", "verdict": "partial", "quality": 2, "confidence": "low", "rationale": "Medusa's pricing page lists a 'Cloud Development Agent' as an enterprise feature, hinting at some built-in AI assistant capability, but there's no documentation describing what it does, how a user delegates tasks to it, or how it's used within the product UI. The rest of the AI-related evidence (MCP server, 'guardrails for agents') is about external AI coding agents building customizations or IDE tools connecting to docs, not a built-in in-product assistant for end users. Missing for 10: documentation/screenshots of the Cloud Development Agent's actual task-delegation workflow, independent/hands-on confirmation it exists and works, and clarity on how it differs from the developer-facing MCP/CLI tooling.", "evidenceIds": [ "medusa-docs-15", "medusa-docs-29", "medusa-docs-13", "medusa-docs-34" ] }, { "productId": "medusa", "storyId": "agentic-headless", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Medusa is explicitly described as a headless commerce platform with an installable open-source npm package and CLI (medusa-comm-3, medusa-gh-2, medusa-probe-4, medusa-docs-29), and cloud tooling references PR previews and background workers suggesting CI/automation support (medusa-docs-11, medusa-docs-30). However there is no explicit documentation of running Medusa in a CI pipeline or automated test/build scripts, and community notes flag unresolved serverless/background-job execution concerns (medusa-comm-2). Missing for 10: dedicated CI/automation guide, evidence of headless test execution, and independent confirmation of serverless/CI deployment working smoothly.", "evidenceIds": [ "medusa-comm-3", "medusa-gh-2", "medusa-probe-4", "medusa-docs-29", "medusa-docs-11", "medusa-docs-30", "medusa-comm-2" ] }, { "productId": "medusa", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence only shows Medusa hosting an MCP server (docs.medusajs.com/mcp) that external AI tools like Cursor can connect to for documentation lookup — this is Medusa acting as an MCP server provider, not evidence that Medusa itself can consume/plug in external MCP servers to use their tools. No documentation or community evidence describes Medusa (or its Cloud Development Agent) connecting to external MCP servers as a client.", "evidenceIds": [ "medusa-docs-4", "medusa-docs-33", "medusa-docs-37", "medusa-probe-3", "medusa-docs-15" ] }, { "productId": "medusa", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Medusa officially hosts a Streamable HTTP MCP server at docs.medusajs.com/mcp that can be added to MCP-compatible AI agents/tools like Cursor, confirmed by both docs and an independent probe. Missing for 10: independent hands-on report of connecting an agent to it and details on tool/resource coverage beyond documentation lookup.", "evidenceIds": [ "medusa-docs-4", "medusa-docs-33", "medusa-docs-37", "medusa-probe-3" ] }, { "productId": "medusa", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Medusa exposes an official MCP server, but it is scoped to searching documentation for AI tools/IDEs, not to operating the commerce platform itself (products, orders, carts) via natural language. Marketing mentions of a 'Cloud Development Agent' and 'guardrails for agents to build customizations' hint at broader agentic operation but are never elaborated with concrete NL-command examples or independent corroboration. Missing for 10: evidence of natural-language commands actually driving store/admin operations, hands-on examples of agentic customization via the guardrails feature, and independent confirmation of the Cloud Development Agent's capabilities.", "evidenceIds": [ "medusa-docs-4", "medusa-docs-33", "medusa-docs-37", "medusa-docs-15", "medusa-docs-13", "medusa-docs-29", "medusa-probe-3" ] }, { "productId": "medusa", "storyId": "agentic-official-cli", "verdict": "full", "quality": 6, "confidence": "medium", "rationale": "Medusa ships an official CLI (documented at docs.medusajs.com/resources/medusa-cli) and a separate Cloud CLI referenced in pricing, giving developers and agentic tooling a scriptable interface to manage Medusa projects. Missing for 10: detailed command reference/usage examples, evidence of AI-agent-specific CLI features (e.g., non-interactive/JSON output modes), and independent hands-on confirmation of the CLI beyond doc links.", "evidenceIds": [ "medusa-probe-4", "medusa-docs-29" ] }, { "productId": "medusa", "storyId": "agentic-public-api", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Medusa maintains a full OpenAPI 3.0 spec for its Store and Admin REST APIs (medusa-gh-x1), which powers extensive public documentation for commerce modules (product, cart, order, payment, tax, fulfillment, inventory, sales channel), giving AI-native users a documented, machine-readable API surface to drive the platform programmatically. Missing for 10: independent hands-on confirmation of API usability, and standard discovery endpoints (openapi.json/swagger.json) 404 at the docs root per probe, meaning the spec is only reachable via GitHub rather than a conventional self-describing endpoint.", "evidenceIds": [ "medusa-gh-x1", "medusa-docs-21", "medusa-docs-22", "medusa-docs-23", "medusa-docs-24", "medusa-docs-25", "medusa-docs-26", "medusa-probe-2" ] }, { "productId": "medusa", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows only generic RBAC/SSO/Audit Logs mentions in pricing tiers, with no documentation of issuing scoped or least-privilege API credentials specifically for AI agents, nor any agent-specific token/key scoping mechanism.", "evidenceIds": [ "medusa-docs-3" ] }, { "productId": "medusa", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack shows Medusa exposes a machine-readable OpenAPI 3.0 spec and various module docs, plus an MCP server and CLI for AI tooling, but there is no citation of an official client SDK (e.g., a maintained JS/TypeScript SDK package) that an AI-native developer could build against. missing for 10: explicit official SDK documentation/package reference, examples of SDK usage, language coverage beyond REST spec.", "evidenceIds": [ "medusa-gh-x1", "medusa-docs-4", "medusa-probe-2" ] }, { "productId": "medusa", "storyId": "agentic-webhooks", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Medusa's pricing page lists 'Webhook Events' as a feature, indicating webhook-based event subscription exists, but no documentation details the subscription mechanism, event catalog, or setup process, and no independent/hands-on confirmation is present. Missing for 10: detailed webhook docs, event type catalog, hands-on verification, independent corroboration.", "evidenceIds": [ "medusa-docs-16" ] }, { "productId": "medusa", "storyId": "api-interactive-docs", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Medusa maintains full OpenAPI 3.0 specs for its Store/Admin REST APIs that power a hosted docs.medusajs.com/api reference, indicating a structured, machine-readable API reference exists, but the evidence pack has no confirmation of 'try it out' style runnable request execution in that reference, and a direct openapi.json endpoint probe returned 404s. missing for 10: explicit documentation/screenshot of an interactive 'run this request' feature in the API reference, independent confirmation of a Swagger/Redoc-style try-it-out UI.", "evidenceIds": [ "medusa-gh-x1", "medusa-probe-2" ] }, { "productId": "medusa", "storyId": "api-machine-spec", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "Medusa maintains a full OpenAPI 3.0 spec for its Store and Admin REST APIs in the medusajs/medusa GitHub repo, which powers docs.medusajs.com/api and is directly downloadable as a raw YAML file (medusa-gh-x1). However, a runtime probe found no discoverable/conventional endpoint like openapi.json or swagger.json on the docs domain itself (medusa-probe-2), meaning users must know to fetch it from GitHub rather than a standard machine-readable discovery path. Missing for 10: a documented, directly-linked download endpoint on the docs site itself, and confirmation the spec is kept in sync/versioned for consumers outside the repo.", "evidenceIds": [ "medusa-gh-x1", "medusa-probe-2" ] }, { "productId": "medusa", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "While Medusa's self-hosted architecture and 'Instant previews on PRs' (medusa-docs-11) suggest general dev/staging capabilities, there is no evidence of a dedicated sandbox environment specifically for AI-native testing against non-production data (e.g., a test mode for the MCP server or API keys scoped to sandbox data). missing for 10: explicit sandbox/test environment documentation, AI-agent-specific test mode, isolation guarantees separating sandbox from production data.", "evidenceIds": [ "medusa-docs-11", "medusa-docs-4" ] }, { "productId": "medusa", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "There's an OpenAPI spec for the Store/Admin APIs, but no evidence of API versioning scheme or a documented deprecation policy anywhere in the docs; probe for openapi.json even 404s at the docs root. Missing for 10: any mention of API version numbers, changelog of breaking changes, or a stated deprecation/support timeline.", "evidenceIds": [ "medusa-gh-x1", "medusa-probe-2" ] }, { "productId": "medusa", "storyId": "app-extension-marketplace", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Medusa's evidence covers its open-source core modules, framework, and integrations documentation, but there is no mention of a curated or vetted marketplace/app store of third-party extensions comparable to Shopify's App Store. The story specifically requires a vetted marketplace covering long-tail features, which is unevidenced here.", "evidenceIds": [] }, { "productId": "medusa", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "While Medusa's commerce modules (Product, Inventory, Order, etc.) and REST/OpenAPI API surface could plausibly support batch operations, no evidence in the pack documents bulk-update, bulk-import/export, or batch-processing endpoints/workflows for AI-driven mass operations across items.", "evidenceIds": [] }, { "productId": "medusa", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Medusa's pricing page lists 'Webhook Events' as a feature, and its framework/workflow architecture (implied by 'Framework - Guardrails for agents to build customizations') suggests event-driven automation capability, but the evidence pack contains no documentation of a rule-definition system, event subscribers, or trigger-action configuration mechanism. Missing for 10: dedicated docs on defining custom event subscribers/rules, examples of trigger-condition-action automation, and independent confirmation the feature works as described beyond a single bullet point.", "evidenceIds": [ "medusa-docs-16", "medusa-docs-13", "medusa-docs-34" ] }, { "productId": "medusa", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Evidence mentions only generic 'background workers' and workflow/framework capabilities, with no documentation of a scheduling API, cron syntax, or recurring-job/workflow trigger mechanism. Missing for 10: explicit scheduled-job/cron API docs, recurring workflow trigger examples, any first-party or community confirmation of a scheduler feature.", "evidenceIds": [ "medusa-docs-30", "medusa-gh-1" ] }, { "productId": "medusa", "storyId": "automation-versioned-workflows", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Medusa's evidence only shows generic infrastructure features—GitHub-based deployment, PR previews, and automatic backups—that imply some git-based versioning and rollback for the whole application, but nothing specifically documents versioning, reviewing, or rolling back 'automations' (e.g., workflow definitions) as a distinct AI-native capability. missing for 10: explicit automation/workflow version history, a review/approval flow for automation changes, and a dedicated rollback mechanism for automations themselves.", "evidenceIds": [ "medusa-docs-1", "medusa-docs-2", "medusa-docs-11", "medusa-docs-17", "medusa-docs-35" ] }, { "productId": "medusa", "storyId": "b2b-wholesale-selling", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Medusa has a documented B2B Recipe and related commerce modules (Product, Cart, Order, Pricing infrastructure implied) plus GitHub confirmation that the framework supports 'advanced B2B or DTC commerce stores,' showing the platform is architected to support B2B use cases alongside DTC. However, the evidence never details specific features like customer-specific price lists, volume/tiered pricing, quote workflows, or net-terms invoicing — these are not named in any docs excerpt. missing for 10: explicit documentation of customer-specific price lists, volume pricing rules, quote/RFQ workflow, net-terms invoicing support, and independent/hands-on confirmation these B2B features work in practice.", "evidenceIds": [ "medusa-docs-6", "medusa-gh-3", "medusa-docs-8", "medusa-docs-21" ] }, { "productId": "medusa", "storyId": "bulk-catalog-operations", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Medusa exposes a Product Module and REST/Admin API (medusa-docs-21, medusa-gh-x1) that could support programmatic catalog edits, but there is no direct evidence of a bulk CSV import/export feature or bulk-edit UI for operations leads. missing for 10: explicit CSV import/export tooling, bulk-edit admin UI documentation, and any hands-on confirmation that bulk catalog operations work without per-product edits.", "evidenceIds": [ "medusa-docs-21", "medusa-gh-x1", "medusa-docs-9" ] }, { "productId": "medusa", "storyId": "checkout-customization", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Medusa's modular architecture (Cart, Payment, Tax, Fulfillment, Order modules) and documented 'Framework for customization' let developers extend commerce logic without forking core code, and Storefront Development Guides imply building custom checkout UIs on top of these modules. However, no evidence specifically documents checkout-page extension points for fields, branding, or discount/validation logic — no Promotion/discount module or checkout-specific customization guide is cited. missing for 10: dedicated checkout customization docs, discount/promotion module evidence, branding/field-level extension points, independent developer confirmation of checkout customization.", "evidenceIds": [ "medusa-docs-22", "medusa-docs-24", "medusa-docs-25", "medusa-docs-5", "medusa-gh-1", "medusa-gh-4", "medusa-docs-36" ] }, { "productId": "medusa", "storyId": "content-pages-blogs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Medusa's documented modules cover commerce entities (Product, Cart, Order, Payment, Tax, Fulfillment, Inventory, Sales Channel) but no evidence shows a content/pages/blog/media module or CMS capability in the admin; Admin Injection Zones only allow UI customization, not content authoring.", "evidenceIds": [ "medusa-docs-21", "medusa-docs-22", "medusa-docs-23", "medusa-docs-18", "medusa-docs-14" ] }, { "productId": "medusa", "storyId": "custom-app-development", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Medusa provides a documented Framework and commerce modules for building custom apps, an official CLI (medusa-cli), OpenAPI specs for Store/Admin APIs, starter kits (Next.js/Gatsby storefronts per community feedback), and extension points like Admin Injection Zones and Medusa UI — a reasonably strong extensibility story for a commerce platform. However, there is no clear evidence of a formal marketplace/app-review process or distribution path (e.g., a plugin submission/certification pipeline), and no independent verification of SDK completeness beyond docs. missing for 10: documented app review/certification/distribution marketplace process, independent hands-on verification of scaffolding tooling and SDKs beyond first-party docs.", "evidenceIds": [ "medusa-gh-1", "medusa-gh-4", "medusa-docs-13", "medusa-docs-18", "medusa-docs-19", "medusa-probe-4", "medusa-gh-x1", "medusa-comm-9" ] }, { "productId": "medusa", "storyId": "express-wallet-checkout", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence only shows a generic 'Payment Module' doc entry with no mention of Apple Pay, Google Pay, PayPal, or any accelerated/one-click wallet checkout capability; nothing describes wallet-specific integrations or a one-click experience for buyers. This axis clearly applies to a commerce platform, but there is no evidence it delivers accelerated wallet payments.", "evidenceIds": [ "medusa-docs-24" ] }, { "productId": "medusa", "storyId": "gateway-choice-multicurrency", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "The evidence pack only shows a doc-page title for a 'Payment Module' (medusa-docs-24) with no description of supporting multiple third-party gateways or multi-currency charging; there's no mention of Stripe/PayPal/other providers, currency configuration, or a plugin marketplace for payment providers. missing for 10: explicit description of pluggable third-party payment providers, evidence of multi-currency charge support, and any merchant-facing docs/community confirmation of switching or combining payment gateways.", "evidenceIds": [ "medusa-docs-24" ] }, { "productId": "medusa", "storyId": "headless-storefront-api", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Medusa provides documented Storefront Development Guides, first-party Next.js starter storefronts, commerce modules (product, cart, order, payment, tax, fulfillment), and a documented Store REST/OpenAPI API (openapi.full.yaml) that developers can build fully custom headless storefronts against, corroborated by community feedback praising the Next.js/Gatsby starter kits and headless architecture. Missing for 10: independent hands-on report building a production custom storefront end-to-end and a live OpenAPI endpoint (probe found 404s on some openapi paths despite the spec existing in-repo).", "evidenceIds": [ "medusa-docs-5", "medusa-gh-1", "medusa-gh-4", "medusa-docs-21", "medusa-docs-22", "medusa-docs-23", "medusa-docs-24", "medusa-gh-x1", "medusa-comm-9", "medusa-comm-3" ] }, { "productId": "medusa", "storyId": "international-selling", "verdict": "disputed", "quality": 4, "confidence": "medium", "rationale": "Medusa's Tax Module doc suggests some duties/tax handling capability, but there is no evidence in the pack of multi-currency pricing, localized storefronts, or translation tooling — and a hands-on HN reviewer explicitly flags that 'internationalization... every product has a single string for description/title, with no easy way to localize text across regions,' directly contradicting the translations/localization part of this story. missing for 10: multi-currency pricing docs, region/locale storefront docs, translation/i18n module evidence, duties/customs handling detail beyond a generic Tax Module link.", "evidenceIds": [ "medusa-docs-25", "medusa-comm-4", "medusa-comm-3" ] }, { "productId": "medusa", "storyId": "inventory-multi-location", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "Medusa's documented commerce modules explicitly include an Inventory Module and a Fulfillment Module, which per Medusa's architecture support multi-location stock levels and location-aware fulfillment, and the Sales Channel module ties fulfillment sets to channels — the core building blocks operations leads need. However, the evidence pack only lists module names/titles rather than detailed workflows (e.g., stock adjustment audit trails, warehouse-selection logic in fulfillment), and no independent/hands-on report specifically validates multi-location behavior. Missing for 10: independent corroboration of multi-location stock adjustments and warehouse-based fulfillment routing, and detailed docs excerpts beyond module titles.", "evidenceIds": [ "medusa-docs-8", "medusa-docs-26", "medusa-docs-7", "medusa-comm-3" ] }, { "productId": "medusa", "storyId": "marketplace-social-channels", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Medusa's Sales Channel Module lets merchants manage a single product catalog across multiple defined sales channels, which is the underlying architecture needed for multi-channel selling, but there is no evidence of built-in connectors or sync tooling for actual external marketplaces, social commerce platforms, or shopping feeds (e.g., Amazon, Instagram, Google Shopping). Missing for 10: documented integrations/apps for external marketplaces or feed syncing, evidence of feed export formats, and any hands-on confirmation that products actually sync outward rather than just being logically grouped by channel.", "evidenceIds": [ "medusa-docs-7", "medusa-gh-3" ] }, { "productId": "medusa", "storyId": "native-payment-processing", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Medusa's Payment Module (medusa-docs-24) is documented as an integration layer for third-party payment providers (e.g., Stripe, PayPal), not a first-party processor with its own published card rates, payouts, or fraud tooling. No evidence in the pack shows Medusa acting as the payment processor of record — the architecture is built around 'wiring' external gateways, which is the opposite of this story's ask.", "evidenceIds": [ "medusa-docs-24", "medusa-gh-1" ] }, { "productId": "medusa", "storyId": "openness-api-parity", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Medusa is architected API-first: its Admin dashboard is itself a client of the documented Admin REST API, and Medusa publishes complete OpenAPI 3.0 specs for both Store and Admin APIs, implying the UI's functionality is API-backed. However, no evidence explicitly confirms full feature parity (e.g., every admin UI action having a documented API equivalent) or independent verification of this claim. Missing for 10: explicit parity documentation/statement, independent hands-on confirmation that all UI actions map to API endpoints, and no gaps noted (e.g., some UI-only settings).", "evidenceIds": [ "medusa-gh-x1", "medusa-gh-1", "medusa-docs-14" ] }, { "productId": "medusa", "storyId": "openness-full-export", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Medusa's core is open-source and self-hostable, and vendor messaging emphasizes 'you own the project' and full source-code control, plus documented REST/OpenAPI specs (medusa-gh-x1) that could be used to pull data out programmatically. However there is no explicit documented 'export all data' feature, bulk data-export tool, or standardized open-format export (CSV/JSON dump) for leaving the platform — ownership is implied via self-hosting rather than a first-class export capability.\n\nmissing for 10: explicit bulk data-export tooling, documented open-format export (CSV/JSON), migration/exit guide confirming full data portability.", "evidenceIds": [ "medusa-gh-2", "medusa-docs-2", "medusa-docs-10", "medusa-docs-20", "medusa-gh-x1" ] }, { "productId": "medusa", "storyId": "openness-open-license", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Medusa's core is confirmed open-source on GitHub, with modules 'open-source and freely available on npm,' and community commentary independently confirms the repo is MIT-licensed. This directly satisfies an AI-native user's ability to read the source under an open license. Missing for 10: an explicit first-party license statement/citation (e.g., LICENSE file text) rather than inference from a community comment, and clarity on whether the entire platform vs. just certain modules is MIT-licensed.", "evidenceIds": [ "medusa-gh-1", "medusa-gh-2", "medusa-comm-11", "medusa-comm-14" ] }, { "productId": "medusa", "storyId": "openness-self-host", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Medusa's core commerce modules are open-source (MIT-licensed) and published on npm/GitHub, and community discussion independently confirms the MIT licensing model, supporting fully self-hosted deployment separate from the optional paid Cloud hosting. Docs also reinforce 'own your source-code, we handle infra' as an optional add-on rather than a requirement.\n\nmissing for 10: a first-party self-hosting/installation guide citation and independent hands-on report of successfully running a self-hosted instance.", "evidenceIds": [ "medusa-gh-1", "medusa-gh-2", "medusa-comm-11", "medusa-docs-2", "medusa-docs-10" ] }, { "productId": "medusa", "storyId": "pos-in-person-sales", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Medusa's evidence covers its Sales Channel, Inventory, and Product modules which theoretically enable multi-channel selling, but there is no mention of an actual point-of-sale product/app or in-person checkout capability anywhere in the pack. Missing for 10: any POS application/device support, in-store checkout flow, or documentation of a POS integration syncing catalog/inventory/customers in real time.", "evidenceIds": [ "medusa-docs-7", "medusa-docs-8", "medusa-gh-3" ] }, { "productId": "medusa", "storyId": "privacy-data-residency", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Medusa's open-source/self-hosted architecture (BYOC, 'You own the project, we handle the infra') inherently lets users deploy in any region they choose, and the Enterprise pricing tier explicitly lists 'Data sovereignty, SOC2, custom DPA' as a feature, implying some data-residency control for cloud customers. However, there is no documentation of specific supported regions, a UI/API for selecting storage location, or details on how data sovereignty is technically enforced. Missing for 10: explicit region-selection mechanism/UI, list of supported regions, technical details on how residency is guaranteed, independent confirmation of the enterprise feature in practice.", "evidenceIds": [ "medusa-docs-27", "medusa-docs-10", "medusa-docs-32", "medusa-gh-2" ] }, { "productId": "medusa", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Medusa is a self-hosted/owned commerce platform, not an AI model vendor consuming user data for training; the 'prevent data being used for AI training' axis is a category error for this product type, not something evidenced or unevidenced.", "evidenceIds": [] }, { "productId": "medusa", "storyId": "privacy-retention-controls", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Medusa is self-hosted/open-source (you own your infra and database) and Cloud tier mentions 'Data sovereignty, SOC2, custom DPA' and 'Automatic backups', implying some control over where and how data is stored, but there is no explicit documentation of data retention policies, deletion APIs, or GDPR-style erasure workflows for commerce/customer data. Missing for 10: explicit data retention/deletion tooling or docs, GDPR/right-to-erasure endpoints, and independent confirmation of these controls in practice.", "evidenceIds": [ "medusa-docs-2", "medusa-docs-27", "medusa-docs-17" ] }, { "productId": "medusa", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses telemetry collection or an opt-out mechanism for Medusa; the axis is applicable to a self-hosted commerce platform but no documentation, GitHub, or community source confirms or denies telemetry practices.", "evidenceIds": [] }, { "productId": "medusa", "storyId": "product-variant-modeling", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Medusa's open-source Product Module (variants/options) and broader commerce-module architecture support building custom product data structures (medusa-docs-21, medusa-gh-2, medusa-gh-4), but the evidence pack gives no detailed confirmation of a general metafields/custom-fields system for products — and an early hands-on community review explicitly noted that metadata support existed for orders but not products at the time (medusa-comm-9), raising doubt about full custom-field flexibility on the catalog side. Missing for 10: current first-party documentation/screenshots showing per-product custom fields or metafields UI, independent confirmation that this limitation has been resolved, and detail on how option/variant modeling handles non-standard catalog structures.", "evidenceIds": [ "medusa-docs-21", "medusa-gh-2", "medusa-gh-4", "medusa-comm-9" ] }, { "productId": "medusa", "storyId": "serverless-commerce-functions", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Medusa's GitHub and marketing docs confirm a 'built-in framework for customization' that lets developers 'extend, customize, and own every commerce workflow' and includes commerce modules (Fulfillment, Tax, Cart, Order) that could house custom logic, supporting the general concept of injecting backend logic. However, the evidence pack lacks concrete documentation of the specific hook/subscriber/workflow mechanisms, discount or promotion customization, or serverless function deployment model that would show how validation/shipping/discount logic actually gets injected. Missing for 10: explicit workflow/subscriber/hook API docs, a discount-module customization example, and confirmation of serverless execution model.", "evidenceIds": [ "medusa-gh-1", "medusa-docs-13", "medusa-docs-34", "medusa-docs-36", "medusa-docs-26", "medusa-docs-25" ] }, { "productId": "medusa", "storyId": "shipping-rates-labels", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence only shows a generic 'Fulfillment Module' doc title (medusa-docs-26); there is no evidence of live carrier rate shopping at checkout, label purchasing, or shipment tracking integration. Missing for 10: carrier rate-shopping integration details, label purchase workflow, tracking/status sync evidence.", "evidenceIds": [ "medusa-docs-26" ] }, { "productId": "medusa", "storyId": "tax-calculation-automation", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Medusa ships a dedicated Tax Module in its commerce modules, implying built-in tax configuration, but the evidence pack gives no detail on automatic per-jurisdiction rate calculation, rate updates/currency, or generating filing-ready tax reports. missing for 10: documentation of jurisdiction-based automatic tax calculation, rate update/maintenance mechanism, tax report generation/export for filing, and any third-party tax provider integrations (e.g., Avalara/TaxJar).", "evidenceIds": [ "medusa-docs-25" ] }, { "productId": "medusa", "storyId": "theme-code-customization", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Medusa provides storefront development guides and Next.js/Gatsby starter kits (medusa-docs-5, medusa-comm-9) plus GitHub-based deploys and PR preview environments (medusa-docs-1, medusa-docs-11, medusa-docs-35), which cover part of the version-controlled-deploy and preview aspects of the story. However, Medusa is headless — there is no documented 'templating layer' or theme system (it's a full custom React/Next.js app, not theme templates), and no explicit local-preview workflow documentation is cited. Missing for 10: a documented templating/theme abstraction layer, explicit local-preview tooling docs, and independent hands-on confirmation of the PR-preview/deploy flow.", "evidenceIds": [ "medusa-docs-5", "medusa-comm-9", "medusa-docs-1", "medusa-docs-11", "medusa-docs-35" ] }, { "productId": "medusa", "storyId": "theme-storefront-launch", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Medusa is explicitly a headless, developer-first commerce platform — its storefront resources are 'Storefront Development Guides' requiring coding (medusa-docs-5), not a no-code theme/section editor. Community feedback explicitly notes headless means 'I have to write my own interfaces,' the opposite of a no-code polished-theme experience (medusa-comm-6). No evidence anywhere in the pack of a theme marketplace, visual page builder, or no-code branding/layout editor for merchants.", "evidenceIds": [ "medusa-docs-5", "medusa-comm-6", "medusa-gh-1" ] }, { "productId": "shopify", "storyId": "abandoned-cart-recovery", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "admin-commerce-api", "verdict": "disputed", "quality": 4, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-31", "shopify-docs-5", "shopify-docs-48", "shopify-docs-43", "shopify-comm-9", "shopify-comm-8" ] }, { "productId": "shopify", "storyId": "agent-catalog-discovery", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-49", "shopify-docs-6", "shopify-docs-34", "shopify-docs-38", "shopify-probe-3", "shopify-probe-1" ] }, { "productId": "shopify", "storyId": "agent-order-lifecycle", "verdict": "disputed", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-45", "shopify-docs-52", "shopify-docs-4", "shopify-docs-21", "shopify-docs-43", "shopify-docs-31", "shopify-comm-9" ] }, { "productId": "shopify", "storyId": "agent-storefront-commerce", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "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).", "evidenceIds": [ "shopify-docs-6", "shopify-docs-7", "shopify-docs-34", "shopify-docs-44", "shopify-docs-49", "shopify-docs-50", "shopify-docs-51", "shopify-docs-52", "shopify-probe-3" ] }, { "productId": "shopify", "storyId": "agentic-agent-docs", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-probe-1", "shopify-docs-6", "shopify-docs-35", "shopify-docs-39", "shopify-docs-53", "shopify-probe-3" ] }, { "productId": "shopify", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "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.", "evidenceIds": [ "shopify-docs-4", "shopify-docs-21", "shopify-docs-43", "shopify-docs-6", "shopify-docs-34", "shopify-docs-49", "shopify-docs-50", "shopify-docs-51", "shopify-docs-52" ] }, { "productId": "shopify", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "agentic-headless", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-3", "shopify-docs-17", "shopify-docs-30", "shopify-docs-42", "shopify-docs-18", "shopify-docs-31", "shopify-docs-32", "shopify-docs-4", "shopify-docs-43", "shopify-probe-4" ] }, { "productId": "shopify", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-7", "shopify-docs-45", "shopify-docs-49", "shopify-docs-50", "shopify-docs-51", "shopify-docs-52", "shopify-probe-3" ] }, { "productId": "shopify", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "shopify-docs-7", "shopify-docs-45", "shopify-docs-49", "shopify-docs-50", "shopify-docs-51", "shopify-docs-52", "shopify-docs-6", "shopify-probe-3" ] }, { "productId": "shopify", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-6", "shopify-docs-34", "shopify-docs-44", "shopify-docs-49", "shopify-docs-50", "shopify-docs-51", "shopify-docs-52", "shopify-docs-7", "shopify-probe-3" ] }, { "productId": "shopify", "storyId": "agentic-official-cli", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "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.", "evidenceIds": [ "shopify-docs-17", "shopify-docs-3", "shopify-docs-30", "shopify-docs-42", "shopify-docs-53", "shopify-docs-x2", "shopify-probe-4" ] }, { "productId": "shopify", "storyId": "agentic-public-api", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "shopify-docs-31", "shopify-docs-32", "shopify-docs-4", "shopify-docs-5", "shopify-docs-48", "shopify-docs-x1", "shopify-docs-x3", "shopify-docs-17", "shopify-comm-8", "shopify-comm-9", "shopify-probe-2" ] }, { "productId": "shopify", "storyId": "agentic-scoped-keys", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-5", "shopify-docs-48", "shopify-docs-6", "shopify-docs-34" ] }, { "productId": "shopify", "storyId": "agentic-sdks", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-18", "shopify-docs-31", "shopify-docs-32", "shopify-docs-39", "shopify-docs-53", "shopify-docs-6", "shopify-docs-34", "shopify-comm-8", "shopify-comm-12" ] }, { "productId": "shopify", "storyId": "agentic-webhooks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "shopify-docs-4", "shopify-docs-21", "shopify-docs-43" ] }, { "productId": "shopify", "storyId": "api-interactive-docs", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-x3", "shopify-docs-18", "shopify-docs-31" ] }, { "productId": "shopify", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "shopify-probe-3", "shopify-docs-18", "shopify-docs-x3" ] }, { "productId": "shopify", "storyId": "api-sandbox", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "shopify-docs-x2", "shopify-docs-x3", "shopify-docs-17" ] }, { "productId": "shopify", "storyId": "api-versioning-policy", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-x1" ] }, { "productId": "shopify", "storyId": "app-extension-marketplace", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "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).", "evidenceIds": [ "shopify-docs-1", "shopify-docs-15", "shopify-docs-23", "shopify-docs-54", "shopify-comm-7", "shopify-comm-8", "shopify-comm-12" ] }, { "productId": "shopify", "storyId": "automation-bulk-operations", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "shopify-docs-12", "shopify-docs-31", "shopify-docs-18" ] }, { "productId": "shopify", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-4", "shopify-docs-21", "shopify-docs-43", "shopify-docs-5" ] }, { "productId": "shopify", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [ "shopify-docs-4", "shopify-docs-43", "shopify-docs-21" ] }, { "productId": "shopify", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "b2b-wholesale-selling", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-13", "shopify-docs-58" ] }, { "productId": "shopify", "storyId": "bulk-catalog-operations", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "shopify-docs-31", "shopify-docs-18", "shopify-comm-12" ] }, { "productId": "shopify", "storyId": "checkout-customization", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-1", "shopify-docs-25", "shopify-docs-40", "shopify-docs-8", "shopify-docs-35" ] }, { "productId": "shopify", "storyId": "content-pages-blogs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "custom-app-development", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-3", "shopify-docs-17", "shopify-docs-18", "shopify-docs-31", "shopify-docs-32", "shopify-docs-42", "shopify-docs-x2", "shopify-comm-7", "shopify-comm-8" ] }, { "productId": "shopify", "storyId": "express-wallet-checkout", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-14", "shopify-docs-25", "shopify-docs-40" ] }, { "productId": "shopify", "storyId": "gateway-choice-multicurrency", "verdict": "disputed", "quality": 4, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-14", "shopify-docs-10", "shopify-docs-16", "shopify-docs-37", "shopify-comm-6", "shopify-comm-11" ] }, { "productId": "shopify", "storyId": "headless-storefront-api", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "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).", "evidenceIds": [ "shopify-docs-2", "shopify-docs-19", "shopify-docs-32", "shopify-docs-33", "shopify-docs-36", "shopify-docs-x1", "shopify-docs-x2", "shopify-docs-17" ] }, { "productId": "shopify", "storyId": "international-selling", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.\n\nmissing for 10: explicit evidence of translation/localization tooling, explicit duties/customs handling documentation, independent/hands-on confirmation of multi-currency and localized storefront experience.", "evidenceIds": [ "shopify-docs-10", "shopify-docs-16", "shopify-docs-37", "shopify-docs-46", "shopify-docs-11", "shopify-docs-27", "shopify-docs-56", "shopify-docs-12", "shopify-docs-57" ] }, { "productId": "shopify", "storyId": "inventory-multi-location", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "marketplace-social-channels", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "shopify-docs-57", "shopify-docs-55" ] }, { "productId": "shopify", "storyId": "native-payment-processing", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-14", "shopify-docs-25", "shopify-docs-40", "shopify-comm-4", "shopify-comm-6" ] }, { "productId": "shopify", "storyId": "openness-api-parity", "verdict": "disputed", "quality": 4, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-31", "shopify-docs-19", "shopify-docs-32", "shopify-comm-9", "shopify-comm-12", "shopify-comm-10" ] }, { "productId": "shopify", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-comm-7", "shopify-comm-12" ] }, { "productId": "shopify", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Shopify is a proprietary closed-source commerce SaaS platform; there is no evidence, nor is it a reasonable expectation, that its core source code is published under an open license. Openness axis applies to open-source products, not to a hosted SaaS platform of this kind.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "openness-self-host", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Shopify is a fully hosted, proprietary commerce SaaS platform; even its 'headless' storefront option explicitly advertises 'Hosting included' (shopify-docs-33), meaning there is no way to run the core Shopify platform on your own infrastructure. No evidence anywhere in the pack shows an open-source or self-hostable core product, unlike competitor platforms in this category that do offer that option.", "evidenceIds": [ "shopify-docs-33", "shopify-docs-20", "shopify-docs-2" ] }, { "productId": "shopify", "storyId": "pos-in-person-sales", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-9", "shopify-docs-26", "shopify-docs-55", "shopify-docs-57" ] }, { "productId": "shopify", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack item addresses AI-training data opt-out or data-privacy controls for merchant/customer data; all citations concern APIs, CLI, agents/MCP, commerce features, or unrelated community complaints.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Shopify is an e-commerce platform, not an AI dev tool/agent whose telemetry collection an 'AI-native user' would opt out of; this privacy-posture axis about telemetry/usage-tracking opt-out doesn't apply to this product category.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "product-variant-modeling", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "shopify", "storyId": "serverless-commerce-functions", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-4", "shopify-docs-21", "shopify-docs-43", "shopify-docs-8", "shopify-docs-22", "shopify-docs-35" ] }, { "productId": "shopify", "storyId": "shipping-rates-labels", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-12", "shopify-docs-57" ] }, { "productId": "shopify", "storyId": "tax-calculation-automation", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-11", "shopify-docs-27", "shopify-docs-56" ] }, { "productId": "shopify", "storyId": "theme-code-customization", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-3", "shopify-docs-17", "shopify-docs-15", "shopify-docs-23", "shopify-docs-8", "shopify-docs-22", "shopify-docs-x2" ] }, { "productId": "shopify", "storyId": "theme-storefront-launch", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "shopify-docs-15", "shopify-docs-23", "shopify-docs-24", "shopify-docs-54", "shopify-comm-3" ] }, { "productId": "swell", "storyId": "abandoned-cart-recovery", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "swell", "storyId": "admin-commerce-api", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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).\n\nmissing for 10: explicit refund/fulfillment endpoint documentation, OpenAPI reference, independent/hands-on verification of order-edit and refund calls.", "evidenceIds": [ "swell-docs-7", "swell-docs-8", "swell-docs-26", "swell-docs-27", "swell-docs-28", "swell-docs-39", "swell-probe-2" ] }, { "productId": "swell", "storyId": "agent-catalog-discovery", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-9", "swell-docs-22", "swell-docs-3", "swell-docs-23" ] }, { "productId": "swell", "storyId": "agent-order-lifecycle", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [ "swell-docs-25", "swell-docs-28", "swell-docs-5" ] }, { "productId": "swell", "storyId": "agent-storefront-commerce", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-9", "swell-docs-21", "swell-probe-1", "swell-probe-2" ] }, { "productId": "swell", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "swell-probe-1", "swell-docs-21" ] }, { "productId": "swell", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-3", "swell-docs-9", "swell-docs-21", "swell-docs-35" ] }, { "productId": "swell", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "swell-docs-5", "swell-docs-25", "swell-docs-6", "swell-docs-34" ] }, { "productId": "swell", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-3", "swell-docs-9", "swell-docs-21", "swell-docs-22" ] }, { "productId": "swell", "storyId": "agentic-headless", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "swell-docs-33", "swell-docs-4", "swell-docs-44", "swell-docs-24", "swell-docs-21", "swell-probe-3" ] }, { "productId": "swell", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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'.", "evidenceIds": [] }, { "productId": "swell", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "swell-docs-21", "swell-probe-1", "swell-probe-2", "swell-probe-3" ] }, { "productId": "swell", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-21", "swell-docs-33", "swell-docs-4", "swell-docs-44" ] }, { "productId": "swell", "storyId": "agentic-official-cli", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-4", "swell-docs-24", "swell-docs-33", "swell-docs-44", "swell-docs-21", "swell-probe-3" ] }, { "productId": "swell", "storyId": "agentic-public-api", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-7", "swell-docs-8", "swell-docs-9", "swell-docs-39", "swell-docs-26", "swell-docs-28", "swell-probe-1", "swell-probe-2" ] }, { "productId": "swell", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-8", "swell-docs-39", "swell-docs-17" ] }, { "productId": "swell", "storyId": "agentic-sdks", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-7", "swell-docs-33", "swell-probe-2", "swell-probe-1" ] }, { "productId": "swell", "storyId": "agentic-webhooks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "swell-docs-5", "swell-docs-25" ] }, { "productId": "swell", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-probe-1", "swell-probe-2" ] }, { "productId": "swell", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "swell-probe-1", "swell-probe-2", "swell-docs-9", "swell-docs-22" ] }, { "productId": "swell", "storyId": "api-sandbox", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-8", "swell-docs-44", "swell-docs-24", "swell-docs-21" ] }, { "productId": "swell", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "swell-probe-1", "swell-probe-2" ] }, { "productId": "swell", "storyId": "app-extension-marketplace", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-4", "swell-docs-13", "swell-docs-21", "swell-docs-33", "swell-docs-40", "swell-docs-45" ] }, { "productId": "swell", "storyId": "automation-bulk-operations", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "swell-docs-14", "swell-docs-15", "swell-docs-28" ] }, { "productId": "swell", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-5", "swell-docs-25", "swell-docs-31", "swell-docs-2", "swell-docs-6" ] }, { "productId": "swell", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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).", "evidenceIds": [] }, { "productId": "swell", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "swell", "storyId": "b2b-wholesale-selling", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-16", "swell-docs-30", "swell-docs-17" ] }, { "productId": "swell", "storyId": "bulk-catalog-operations", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-14", "swell-docs-7", "swell-docs-39" ] }, { "productId": "swell", "storyId": "checkout-customization", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "swell-docs-2", "swell-docs-6", "swell-docs-19", "swell-docs-25", "swell-docs-32", "swell-docs-36", "swell-docs-10" ] }, { "productId": "swell", "storyId": "content-pages-blogs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "swell", "storyId": "custom-app-development", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-4", "swell-docs-33", "swell-docs-44", "swell-docs-7", "swell-docs-31", "swell-docs-32", "swell-docs-40", "swell-docs-45", "swell-probe-3", "swell-probe-1", "swell-probe-2" ] }, { "productId": "swell", "storyId": "express-wallet-checkout", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "swell-docs-20", "swell-docs-37" ] }, { "productId": "swell", "storyId": "gateway-choice-multicurrency", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-20", "swell-docs-37", "swell-docs-43" ] }, { "productId": "swell", "storyId": "headless-storefront-api", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-1", "swell-docs-2", "swell-docs-7", "swell-docs-8", "swell-docs-33", "swell-docs-39", "swell-probe-2" ] }, { "productId": "swell", "storyId": "international-selling", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "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.", "evidenceIds": [ "swell-docs-43" ] }, { "productId": "swell", "storyId": "inventory-multi-location", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "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.", "evidenceIds": [ "swell-docs-28", "swell-docs-15" ] }, { "productId": "swell", "storyId": "marketplace-social-channels", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-14", "swell-docs-25", "swell-docs-5" ] }, { "productId": "swell", "storyId": "native-payment-processing", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-20", "swell-docs-37" ] }, { "productId": "swell", "storyId": "openness-api-parity", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-1", "swell-docs-9", "swell-docs-31", "swell-docs-33", "swell-probe-2" ] }, { "productId": "swell", "storyId": "openness-full-export", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "swell-docs-14" ] }, { "productId": "swell", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Swell is a closed commercial SaaS platform; no evidence of any open-source license or public source repository is present in the evidence pack, and probes for open API/spec artifacts returned 404s.", "evidenceIds": [ "swell-probe-1", "swell-probe-2" ] }, { "productId": "swell", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Swell is a hosted commerce SaaS platform (functions deployed to Swell's edge, environment-specific API keys, dashboard/backend API) with no evidence of a self-hostable core server; self-hosting is not a fair axis for this managed cloud product's category.", "evidenceIds": [] }, { "productId": "swell", "storyId": "pos-in-person-sales", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "swell", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "swell", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Swell is an e-commerce/headless-commerce platform, not an AI model provider or a service that trains AI models on user data; the axis of preventing data use for AI model training is not a fair question for this product category, and no evidence pack items address such a policy.", "evidenceIds": [] }, { "productId": "swell", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "swell", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses telemetry, usage tracking, or opt-out mechanisms for Swell's CLI, apps, or AI tooling; the pack covers commerce features and developer tooling but never mentions data collection or privacy settings.", "evidenceIds": [] }, { "productId": "swell", "storyId": "product-variant-modeling", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "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.", "evidenceIds": [ "swell-docs-15", "swell-docs-19", "swell-docs-31", "swell-docs-32", "swell-docs-9" ] }, { "productId": "swell", "storyId": "serverless-commerce-functions", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "swell-docs-2", "swell-docs-6", "swell-docs-25", "swell-docs-31", "swell-docs-32", "swell-docs-33", "swell-docs-34" ] }, { "productId": "swell", "storyId": "shipping-rates-labels", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "swell", "storyId": "tax-calculation-automation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "swell", "storyId": "theme-code-customization", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-10", "swell-docs-13", "swell-docs-33", "swell-docs-4", "swell-docs-44", "swell-docs-40" ] }, { "productId": "swell", "storyId": "theme-storefront-launch", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "swell-docs-10", "swell-docs-11", "swell-docs-12", "swell-docs-13", "swell-docs-40", "swell-docs-45" ] }, { "productId": "woocommerce", "storyId": "abandoned-cart-recovery", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions abandoned cart recovery, cart abandonment tracking, or automated recovery emails/links; core WooCommerce docs cover payments, shipping, taxes, APIs, and product management but nothing about cart-abandonment recovery workflows (this is typically only available via third-party plugins/extensions not evidenced here).", "evidenceIds": [] }, { "productId": "woocommerce", "storyId": "admin-commerce-api", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "WooCommerce's REST API (v3, versioned under /wp-json/wc/v3/) supports full CRUD on products, orders, and refunds via standard HTTP verbs and JSON, with official client libraries in multiple languages and role-based key scoping; docs explicitly cover refunds and order/fulfillment management, and webhooks allow event-driven triggering. Missing for 10: no independent/hands-on developer corroboration of complex workflows (e.g., fulfillment triggers) beyond vendor docs, and no published OpenAPI spec or deprecation policy for versioning.", "evidenceIds": [ "woocommerce-docs-11", "woocommerce-docs-27", "woocommerce-docs-40", "woocommerce-docs-44", "woocommerce-docs-x1", "woocommerce-docs-x2", "woocommerce-docs-24", "woocommerce-docs-8", "woocommerce-probe-2" ] }, { "productId": "woocommerce", "storyId": "agent-catalog-discovery", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows only single-store integrations (REST API, MCP server, llms.txt for developer docs) that let an agent interact with one WooCommerce store's own data — there is no evidence of a cross-merchant catalog, aggregated product feed, or answer-engine-oriented discovery layer spanning multiple WooCommerce merchants.", "evidenceIds": [ "woocommerce-docs-14", "woocommerce-docs-29", "woocommerce-probe-3", "woocommerce-probe-1", "woocommerce-docs-11" ] }, { "productId": "woocommerce", "storyId": "agent-order-lifecycle", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "WooCommerce's REST API (v3) documents CRUD access to WC data and webhooks for automatic event notifications, which could plausibly cover order status changes, and the Managing Money guide mentions issuing refunds — giving a technical path for agent-driven order lifecycle actions. However, there is no explicit documentation of an orders/returns endpoint, no RMA/returns workflow, and fulfillment is described only via the human-facing dashboard/shipping-label workflow, not an API a fully autonomous agent could drive end-to-end. Missing for 10: explicit order-status/fulfillment REST endpoints, a documented returns/RMA API, and evidence that refunds/fulfillment can be completed via API+webhooks without any admin UI step.", "evidenceIds": [ "woocommerce-docs-11", "woocommerce-docs-27", "woocommerce-docs-44", "woocommerce-docs-8", "woocommerce-docs-26", "woocommerce-docs-5", "woocommerce-docs-24", "woocommerce-docs-37", "woocommerce-docs-7", "woocommerce-docs-25" ] }, { "productId": "woocommerce", "storyId": "agent-storefront-commerce", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "WooCommerce documents native MCP support enabling AI assistants/tools to interact directly with stores via a standardized protocol, and separately exposes Store API endpoints for product listing, search, and cart-to-order conversion — together matching the story of a documented agent-commerce endpoint rather than scraping. Missing for 10: explicit documentation of which MCP tools/endpoints cover product discovery and cart-building specifically, no UCP mention, and no independent/hands-on validation that the MCP server works as described.", "evidenceIds": [ "woocommerce-docs-14", "woocommerce-docs-29", "woocommerce-probe-3", "woocommerce-docs-12", "woocommerce-docs-28" ] }, { "productId": "woocommerce", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "A direct probe confirms an llms.txt file is live at developer.woocommerce.com/llms.txt returning HTTP 200 with structured documentation listing, and there's an official MCP server for AI agent interaction with WooCommerce stores, directly supporting agent-oriented discovery. Missing for 10: no independent/community corroboration of agents actually using llms.txt successfully.", "evidenceIds": [ "woocommerce-probe-1", "woocommerce-docs-14", "woocommerce-probe-3" ] }, { "productId": "woocommerce", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence shows WooCommerce exposes data via REST API, MCP, and CLI for external AI tools to interact with the store, but there is no evidence of native AI-generated insights or suggestions surfaced inside the WooCommerce product itself (e.g., an AI-powered analytics/insights dashboard). MCP support enables external agents to query data but does not itself constitute in-product AI-generated insights.", "evidenceIds": [ "woocommerce-docs-14", "woocommerce-docs-29", "woocommerce-probe-3" ] }, { "productId": "woocommerce", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "WooCommerce documents webhooks that automatically fire event notifications in the background (docs-8, docs-26) and now ships native MCP support so AI assistants can programmatically interact with store data (docs-14, docs-29, probe-3), which together provide building blocks for background automation. However there's no evidence of a built-in 'set up an autonomous agent/workflow' feature for AI-native users beyond these primitives — automations still require external tooling or custom code via the REST API/CLI. Missing for 10: a first-party autonomous agent/automation-builder UI, documentation of persistent background AI-driven workflows, and independent confirmation that MCP-driven automations actually run unattended in production.", "evidenceIds": [ "woocommerce-docs-8", "woocommerce-docs-26", "woocommerce-docs-14", "woocommerce-docs-29", "woocommerce-probe-3", "woocommerce-docs-11" ] }, { "productId": "woocommerce", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows WooCommerce supports the Model Context Protocol so external AI assistants/tools can connect to and interact with a store (docs-14, docs-29, probe-3), but this is the reverse of the story — it makes WooCommerce a target for external agents, not a built-in AI assistant inside the product that a user can delegate tasks to. No dashboard-embedded assistant, chat interface, or agentic feature is documented anywhere in the evidence pack.", "evidenceIds": [ "woocommerce-docs-14", "woocommerce-docs-29", "woocommerce-probe-3" ] }, { "productId": "woocommerce", "storyId": "agentic-headless", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "WooCommerce ships WC-CLI for command-line store management and a REST API for scripted automation, which supports some headless/CI-style operations, but there is no evidence of a documented headless runtime mode, containerized CI test harness, or official guidance for running WooCommerce end-to-end in a CI pipeline. missing for 10: documented headless/CI deployment pattern, official CI/testing pipeline integration, evidence of automated store provisioning without a GUI.", "evidenceIds": [ "woocommerce-docs-13", "woocommerce-probe-4", "woocommerce-docs-11", "woocommerce-docs-27", "woocommerce-gh-1" ] }, { "productId": "woocommerce", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence only shows WooCommerce exposing itself as an MCP *server* so external AI assistants can call its tools (docs-14/29/probe-3), not WooCommerce acting as an MCP *client* that plugs in and consumes tools from other MCP servers. No documentation or feature describes WooCommerce connecting outward to third-party MCP servers.", "evidenceIds": [ "woocommerce-docs-14", "woocommerce-docs-29", "woocommerce-probe-3" ] }, { "productId": "woocommerce", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "WooCommerce documents native MCP support enabling AI assistants to interact directly with stores via a standardized protocol, confirmed by both docs and a probe of the dedicated MCP feature page. Missing for 10: independent/hands-on corroboration of the MCP server working in practice, and details on setup/configuration depth.", "evidenceIds": [ "woocommerce-docs-14", "woocommerce-docs-29", "woocommerce-probe-3" ] }, { "productId": "woocommerce", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "WooCommerce documents native MCP support enabling AI assistants to interact with stores via a standardized protocol, which is the concrete mechanism for natural-language/agentic operation, and a CLI exists for scripted control. However, evidence is limited to first-party docs with no independent hands-on verification of natural-language command execution in practice. Missing for 10: independent/community validation that MCP-driven natural language commands actually work end-to-end, breadth of supported operations via MCP, and any real-world usage reports.", "evidenceIds": [ "woocommerce-docs-14", "woocommerce-docs-29", "woocommerce-probe-3", "woocommerce-docs-13" ] }, { "productId": "woocommerce", "storyId": "agentic-official-cli", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "WooCommerce documents an official WC-CLI for managing stores via command line (woocommerce-docs-13, woocommerce-probe-4), and separately ships native MCP support enabling AI assistants to interact with stores (woocommerce-docs-14/29/probe-3), which together satisfy the 'official CLI for AI-native workflows' story. Missing for 10: independent/hands-on verification of CLI usage in AI-agent workflows, and no explicit documentation tying the CLI itself to AI-native tooling (MCP is separate from CLI).", "evidenceIds": [ "woocommerce-docs-13", "woocommerce-probe-4", "woocommerce-docs-14", "woocommerce-probe-3" ] }, { "productId": "woocommerce", "storyId": "agentic-public-api", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "WooCommerce documents a full REST API (v3) with authenticated CRUD access to store data, official client libraries in multiple languages, a customer-facing Store API, a CLI, webhooks, and even a native MCP server enabling AI assistants to interact directly with stores — together this is a well-documented public API surface highly suited to AI-native/agentic use. Missing for 10: no published OpenAPI/Swagger spec (probe found 404s) and no independent hands-on developer report confirming ease of programmatic use.", "evidenceIds": [ "woocommerce-docs-11", "woocommerce-docs-27", "woocommerce-docs-40", "woocommerce-docs-44", "woocommerce-docs-12", "woocommerce-docs-13", "woocommerce-docs-8", "woocommerce-docs-14", "woocommerce-docs-29", "woocommerce-docs-x1", "woocommerce-docs-x2", "woocommerce-probe-2", "woocommerce-probe-3", "woocommerce-probe-4" ] }, { "productId": "woocommerce", "storyId": "agentic-scoped-keys", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "WooCommerce's REST API key generation lets admins choose an access level (Read, Write, or Read/Write) per user, and API access conforms to that WordPress user's roles/capabilities — enabling coarse-grained least-privilege credential issuance for an agent. However, this is role/permission-level scoping, not fine-grained resource- or action-specific scoping, and there's no documented agent-specific provisioning flow, key expiration/rotation, or scope granularity beyond the three access levels. Missing for 10: granular per-resource/per-endpoint scoping, dedicated agent-credential workflow, expiration/rotation controls, and independent corroboration of least-privilege usage in agentic contexts.", "evidenceIds": [ "woocommerce-docs-x1", "woocommerce-docs-11", "woocommerce-docs-27" ] }, { "productId": "woocommerce", "storyId": "agentic-sdks", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "WooCommerce documents official REST API client libraries in multiple languages (JavaScript, PHP, Python, Ruby), plus a documented REST/Store API and CLI, giving AI-native developers official SDK-level building blocks. Missing for 10: independent/hands-on corroboration of SDK quality and completeness, and no unified 'official SDK' branding beyond the library list.", "evidenceIds": [ "woocommerce-docs-40", "woocommerce-docs-11", "woocommerce-docs-27", "woocommerce-docs-44", "woocommerce-docs-x1", "woocommerce-docs-x2" ] }, { "productId": "woocommerce", "storyId": "agentic-webhooks", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "WooCommerce has native, well-documented webhook support that lets a store send automatic event notifications to any configurable URL, letting an AI-native agent subscribe to store events like order created/updated. Missing for 10: independent hands-on corroboration or examples of AI agents actually consuming these webhooks.", "evidenceIds": [ "woocommerce-docs-8", "woocommerce-docs-26" ] }, { "productId": "woocommerce", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "WooCommerce publishes REST API reference documentation (docs-11, docs-27, docs-44, docs-x1/x2) but there is no evidence of an interactive, runnable API console (e.g., Swagger/OpenAPI explorer); a direct probe for OpenAPI/Swagger specs on the developer site returned 404 on all candidate paths (woocommerce-probe-2), indicating no interactive reference exists.", "evidenceIds": [ "woocommerce-docs-11", "woocommerce-docs-27", "woocommerce-docs-44", "woocommerce-docs-x1", "woocommerce-docs-x2", "woocommerce-probe-2" ] }, { "productId": "woocommerce", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "WooCommerce documents a REST API extensively (woocommerce-docs-11, -27, -44, -x1, -x2) but a direct probe for machine-readable OpenAPI/Swagger specs at expected paths returned 404 across all candidates (woocommerce-probe-2), and no evidence pack item links to a downloadable OpenAPI/Swagger JSON/YAML file. The REST API docs site appears to be human-readable documentation, not a published machine-readable spec.", "evidenceIds": [ "woocommerce-probe-2", "woocommerce-docs-11", "woocommerce-docs-x2" ] }, { "productId": "woocommerce", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence pack item describes a sandbox/staging environment, test-mode API keys, or any mechanism for testing WooCommerce (including its REST API or MCP integration) without affecting production data. The REST API and MCP docs describe live store interaction only, with no mention of a sandbox mode.", "evidenceIds": [] }, { "productId": "woocommerce", "storyId": "api-versioning-policy", "verdict": "partial", "quality": 4, "confidence": "high", "rationale": "WooCommerce's REST API is explicitly versioned (v1/v2/v3 under /wp-json/wc/v3/), satisfying the 'versioned APIs' half of the story, but the evidence pack directly states 'no deprecation-timeline policy is published' for these APIs. Missing for 10: a documented deprecation/sunset timeline or migration guide between API versions, and any changelog specifying when older versions (v1/v2/legacy) will be retired.", "evidenceIds": [ "woocommerce-docs-x2", "woocommerce-docs-11", "woocommerce-docs-44" ] }, { "productId": "woocommerce", "storyId": "app-extension-marketplace", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "WooCommerce's official marketplace explicitly offers 'hundreds of free and paid extensions' plus 140 region-specific payment gateways, covering long-tail feature needs, and this is corroborated by hands-on positive community sentiment. Missing for 10: independent third-party vetting/curation quality analysis and marketplace app review/rating transparency details.", "evidenceIds": [ "woocommerce-docs-10", "woocommerce-docs-22", "woocommerce-docs-36", "woocommerce-docs-18", "woocommerce-comm-1" ] }, { "productId": "woocommerce", "storyId": "automation-bulk-operations", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "WooCommerce exposes a REST API (CRUD via JSON), a CLI (WC-CLI) for command-line store management, and a native MCP server for AI assistants — all of which could be scripted to perform bulk operations across many items — but no evidence explicitly documents batch/bulk endpoints or bulk-processing workflows for AI-native automation. missing for 10: explicit batch/bulk API endpoint documentation, evidence of MCP or CLI actually performing multi-item bulk actions, and any hands-on confirmation of bulk operation performance at scale.", "evidenceIds": [ "woocommerce-docs-11", "woocommerce-docs-13", "woocommerce-docs-14", "woocommerce-probe-3", "woocommerce-probe-4" ] }, { "productId": "woocommerce", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "WooCommerce documents webhooks that fire automatic event notifications to a URL when store events occur, which is a form of event-triggered automation, but there is no native in-product rules engine to define conditional actions (if X then Y) — the actual 'action' logic must live in an external receiver, not within WooCommerce itself. missing for 10: a built-in rules/automation engine for defining conditional actions, first-party workflow/automation tooling beyond webhooks, and independent confirmation of AI-driven rule creation.", "evidenceIds": [ "woocommerce-docs-8", "woocommerce-docs-26" ] }, { "productId": "woocommerce", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "WooCommerce offers webhooks, REST API, subscriptions/renewals, and a CLI, but there is no evidence of a scheduler or job orchestration feature for recurring automated workflows in an AI-native sense; nothing in the docs describes cron-like job scheduling or workflow automation.", "evidenceIds": [] }, { "productId": "woocommerce", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack shows WooCommerce's REST API, webhooks, and MCP server integration for AI assistants to interact with store data, but nothing about versioning, reviewing, or rolling back automations or workflows. There's no changelog, audit trail, or rollback mechanism described for any automation actions taken via MCP, API, or webhooks.", "evidenceIds": [ "woocommerce-docs-14", "woocommerce-docs-29", "woocommerce-docs-8", "woocommerce-docs-26", "woocommerce-docs-27" ] }, { "productId": "woocommerce", "storyId": "b2b-wholesale-selling", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack has no mention of B2B-specific capabilities like customer-specific price lists, volume/tiered pricing, quote requests, or net-terms invoicing; only generic marketplace/extension mentions and general product variation features are cited, none of which address wholesale/B2B commerce specifically.", "evidenceIds": [] }, { "productId": "woocommerce", "storyId": "bulk-catalog-operations", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "WooCommerce's REST API (docs-11, docs-27, docs-44) supports bulk create/read/update/delete of product data via JSON, and WC-CLI (docs-13, probe-4) lets operations staff manage the store from the command line — both enabling bulk catalog operations without per-product UI clicks. However, the evidence pack never cites WooCommerce's native CSV product importer/exporter (a well-known core feature) or any documentation of CSV-based bulk edit workflows, so the 'CSV' half of the story is unevidenced here. Missing for 10: explicit CSV import/export documentation, evidence of bulk-edit UI/tools beyond API/CLI, and independent confirmation of large-catalog performance.", "evidenceIds": [ "woocommerce-docs-11", "woocommerce-docs-27", "woocommerce-docs-44", "woocommerce-docs-13", "woocommerce-probe-4" ] }, { "productId": "woocommerce", "storyId": "checkout-customization", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "WooCommerce documents a general hook system (add_action/filter extension points for templates) and a dedicated Store API for building customer-facing cart/checkout functionality, plus a REST API and marketplace of extensions, all of which support extending checkout without forking core code. However, the evidence pack lacks specifics on checkout-field-level hooks (e.g., field customization/validation filters), discount/coupon extension points, or branding customization guidance specific to checkout — missing for 10: checkout field customization hooks, discount/validation extension documentation, and independent developer corroboration that these extension points suffice for real-world checkout customization.", "evidenceIds": [ "woocommerce-docs-12", "woocommerce-docs-28", "woocommerce-docs-9", "woocommerce-docs-45", "woocommerce-docs-11", "woocommerce-docs-10" ] }, { "productId": "woocommerce", "storyId": "content-pages-blogs", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "WooCommerce is built as a plugin on top of WordPress, and docs confirm this tight integration (\"open-source commerce platform for WordPress,\" \"If you have a WordPress site, adding Woo takes just minutes\"), which implies the WordPress admin (with its native Pages, Posts/blog, and Media Library) is shared with product management. Storefront theme docs also show content can be inserted into store templates via hooks. However, no evidence explicitly describes a unified admin workflow for managing blog posts, pages, and media alongside products, or shows this in a hands-on merchant walkthrough. Missing for 10: explicit documentation or screenshots of managing WordPress pages/posts/media from the same dashboard as products, and independent confirmation of this workflow.", "evidenceIds": [ "woocommerce-docs-16", "woocommerce-docs-53", "woocommerce-docs-9", "woocommerce-docs-45" ] }, { "productId": "woocommerce", "storyId": "custom-app-development", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "WooCommerce provides official developer resources: a REST API with official JS/PHP/Python/Ruby libraries, a WC-CLI tool, Storefront theme hook system, Storybook integration for UX development, and a public GitHub repo for building extensions, plus a Marketplace for distributing extensions (docs-11, docs-40, docs-13, docs-9, docs-55, woocommerce-gh-1, docs-10). However, there is no documented formal extension review/approval process or dedicated scaffolding/generator tool (e.g., a 'create-extension' CLI) beyond WC-CLI for store management, so the 'scaffolding' and 'review' parts of the story are only thinly evidenced. Missing for 10: explicit extension review/approval criteria, a dedicated project scaffolding generator, and independent developer corroboration of the distribution pipeline.", "evidenceIds": [ "woocommerce-docs-11", "woocommerce-docs-40", "woocommerce-docs-13", "woocommerce-docs-9", "woocommerce-docs-55", "woocommerce-gh-1", "woocommerce-docs-10", "woocommerce-probe-4" ] }, { "productId": "woocommerce", "storyId": "express-wallet-checkout", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Docs confirm WooCommerce integrates with 140 region-specific gateways including WooPayments, Stripe, PayPal, Square, and Amazon Pay, which in practice enable wallet-based accelerated checkouts, but no evidence explicitly names Apple Pay or Google Pay support or describes a one-click/no-re-entry checkout experience. missing for 10: explicit documentation of Apple Pay/Google Pay support, description of accelerated/one-click checkout UX, and any hands-on confirmation that details aren't re-entered.", "evidenceIds": [ "woocommerce-docs-1", "woocommerce-docs-18", "woocommerce-docs-41", "woocommerce-docs-47" ] }, { "productId": "woocommerce", "storyId": "gateway-choice-multicurrency", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docs confirm WooCommerce bundles basic payment methods (cards, BACS, checks, COD) plus access to 140 region-specific third-party gateways (WooPayments, Stripe, PayPal, Square, Amazon Pay), showing strong third-party gateway choice. However, evidence does not explicitly document multi-currency charging/checkout support (this typically requires separate extensions), so the 'charge in multiple currencies' half of the story is unevidenced. Missing for 10: explicit multi-currency checkout/gateway documentation, independent/hands-on confirmation of gateway switching working smoothly.", "evidenceIds": [ "woocommerce-docs-1", "woocommerce-docs-18", "woocommerce-docs-41", "woocommerce-docs-47", "woocommerce-docs-33" ] }, { "productId": "woocommerce", "storyId": "headless-storefront-api", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "WooCommerce documents both a full REST API (v3, with official JS/PHP/Python/Ruby libraries) and a dedicated Store API purpose-built for headless cart/checkout/product frontends, enabling a fully custom headless storefront to be built against documented, versioned endpoints. Missing for 10: no first-party official headless frontend framework/starter kit evidenced, and no independent hands-on report confirming a production headless build.", "evidenceIds": [ "woocommerce-docs-11", "woocommerce-docs-12", "woocommerce-docs-28", "woocommerce-docs-40", "woocommerce-docs-x2", "woocommerce-probe-2" ] }, { "productId": "woocommerce", "storyId": "international-selling", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack shows tax setup, shipping, and payment gateway docs, but contains no mention of multi-currency pricing, localized/translated storefronts, or international duties/customs handling — the core elements of this story are absent. This is a fair question for an e-commerce platform (many competitors ship native multi-currency/localization), so it applies, but no supporting evidence exists.", "evidenceIds": [] }, { "productId": "woocommerce", "storyId": "inventory-multi-location", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers products, payments, shipping labels, taxes, APIs, and marketplace extensions, but contains no mention of multi-location/warehouse inventory tracking, per-location stock adjustments, or fulfillment routing logic. WooCommerce's core inventory model (docs-4, docs-23, docs-50) is single-stock-count per product/variation with no multi-warehouse concept documented.", "evidenceIds": [ "woocommerce-docs-4", "woocommerce-docs-23", "woocommerce-docs-50" ] }, { "productId": "woocommerce", "storyId": "marketplace-social-channels", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack mentions a general extensions marketplace and REST/Store APIs, but nothing documents native or extension-based syncing of a single catalog to external marketplaces, social commerce channels, or shopping feeds (e.g., Google Shopping, Facebook/Instagram, Amazon). Missing for 10: any documentation of channel-sync extensions or feed integrations, evidence of catalog export/sync workflows, or hands-on confirmation of multi-channel listing.", "evidenceIds": [ "woocommerce-docs-10", "woocommerce-docs-22", "woocommerce-docs-36" ] }, { "productId": "woocommerce", "storyId": "native-payment-processing", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "WooPayments is documented as Woo's own integrated payment solution with transaction listing, payouts, and refunds handled directly in the dashboard (woocommerce-docs-5/24/37/43/52), which supports the 'no third-party gateway' framing. However, the evidence never publishes concrete card processing rates or documents dedicated fraud-prevention/chargeback tooling — the docs only gesture at 'managing money' generally, and WooCommerce's broader payments story explicitly leans on 140 external gateways (docs-1/18/41/47) rather than emphasizing WooPayments exclusivity. Missing for 10: published card rate sheet, explicit fraud/dispute tooling documentation, and confirmation WooPayments avoids third-party processor plumbing entirely.", "evidenceIds": [ "woocommerce-docs-5", "woocommerce-docs-24", "woocommerce-docs-37", "woocommerce-docs-43", "woocommerce-docs-52", "woocommerce-docs-1", "woocommerce-docs-18" ] }, { "productId": "woocommerce", "storyId": "openness-api-parity", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "WooCommerce documents a broad, versioned REST API (products, orders, customers, refunds, webhooks, coupons), a separate Store API for cart/checkout, an official WC-CLI, and even native MCP support for AI agents — strong evidence of API-driven parity with the UI. However, the docs don't confirm 1:1 coverage for every admin UI action (e.g., full store-setup wizard, extension marketplace management, granular tax/shipping configuration screens), and there's no independent hands-on test confirming complete UI/API parity. Missing for 10: explicit documentation or independent verification that every admin-UI setting/workflow (not just core commerce objects) is exposed via API, and confirmation of parity for extension-specific UI features.", "evidenceIds": [ "woocommerce-docs-11", "woocommerce-docs-12", "woocommerce-docs-13", "woocommerce-docs-14", "woocommerce-docs-27", "woocommerce-docs-40", "woocommerce-docs-x1", "woocommerce-docs-x2", "woocommerce-probe-3", "woocommerce-probe-4" ] }, { "productId": "woocommerce", "storyId": "openness-full-export", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "WooCommerce is self-hosted and open-source, with explicit messaging about 'full control of your data' and a REST API (JSON, versioned, documented) that allows programmatic export of products, orders, and customer data. However, evidence shows migration guides only for moving data *into* WooCommerce, not exporting/leaving, and no explicit CSV/data-portability export tool or 'leave the platform' guide is documented. Missing for 10: explicit data-export/portability documentation for leaving the platform, evidence of built-in CSV/data dump tools, and independent confirmation that a full data export actually works in open non-proprietary formats.", "evidenceIds": [ "woocommerce-docs-16", "woocommerce-docs-11", "woocommerce-docs-27", "woocommerce-docs-44", "woocommerce-docs-30", "woocommerce-docs-38", "woocommerce-docs-x2" ] }, { "productId": "woocommerce", "storyId": "openness-open-license", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "WooCommerce is explicitly open-source (GPL-licensed WordPress plugin) with its source publicly hosted on GitHub, and its own site states it 'gives you full control: of your checkout, your data, your costs' as an open-source commerce platform. missing for 10: no explicit citation of the license file/terms text itself, only general open-source claims and the GitHub repo link.", "evidenceIds": [ "woocommerce-docs-16", "woocommerce-gh-1" ] }, { "productId": "woocommerce", "storyId": "openness-self-host", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "WooCommerce is explicitly described as an open-source commerce platform giving 'full control of your checkout, your data, your costs,' and the GitHub repo shows the buildable source code (self-hosted on WordPress), plus migration guides for moving your store confirm self-hosting is core to the product's design. Missing for 10: no independent hands-on report confirming a full self-hosted deployment walkthrough.", "evidenceIds": [ "woocommerce-docs-16", "woocommerce-gh-1", "woocommerce-docs-30", "woocommerce-docs-53" ] }, { "productId": "woocommerce", "storyId": "pos-in-person-sales", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack contains no mention of a point-of-sale product, in-person selling, or POS-catalog sync capability for WooCommerce; all evidence covers online store features (payments, shipping, taxes, APIs, mobile app for managing the online store). This is a fair axis for an ecommerce platform, but no evidence shows WooCommerce delivers it, so it is 'none' rather than 'na'.", "evidenceIds": [] }, { "productId": "woocommerce", "storyId": "privacy-data-residency", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "WooCommerce is self-hosted on WordPress, so by nature the store owner controls the hosting infrastructure and therefore the physical location of data — docs-16 states WooCommerce gives 'full control of your data.' However, there is no explicit first-party documentation of region-selection controls, data-residency settings, or compliance tooling addressing where data is stored. missing for 10: explicit data-residency/region-selection documentation, compliance certifications (e.g., GDPR data location controls), and any admin-facing region config feature.", "evidenceIds": [ "woocommerce-docs-16" ] }, { "productId": "woocommerce", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "WooCommerce is an e-commerce platform, not an AI model provider or chatbot; there is no mechanism by which user data would be used to train AI models, and no evidence pack item addresses AI-training opt-out or data usage policy for model training. This axis is a category error for the product type.", "evidenceIds": [] }, { "productId": "woocommerce", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack items address data retention policies, deletion controls, GDPR-style export/erasure tools, or AI-specific data lifecycle controls; REST API docs describe generic CRUD capability but not a data retention/deletion governance feature. This axis applies to an e-commerce platform handling customer PII, but no documentation demonstrates such controls.", "evidenceIds": [] }, { "productId": "woocommerce", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "low", "rationale": "WooCommerce is a self-hosted, open-source e-commerce plugin, not an AI tool or SaaS with its own telemetry pipeline to opt into/out of; the story about opting out of AI-native telemetry doesn't map onto this product's role. No evidence pack items address telemetry settings at all.", "evidenceIds": [] }, { "productId": "woocommerce", "storyId": "product-variant-modeling", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "WooCommerce docs confirm product variations/attributes (e.g., variable products with color/size attributes), subscriptions, bundles, and simple products with just name/price, plus recent 'variation galleries' improvements, supporting flexible catalog modeling. However, evidence lacks explicit mention of custom fields/metafields support (WooCommerce does support custom product meta natively via WordPress custom fields, but no doc here confirms this) or detail on how flexible/extensible attribute schemas are beyond basic variations. Missing for 10: explicit metafields/custom-fields documentation, evidence of unlimited custom attribute sets beyond simple variations, and independent/hands-on confirmation of complex catalog modeling in practice.", "evidenceIds": [ "woocommerce-docs-3", "woocommerce-docs-4", "woocommerce-docs-23", "woocommerce-docs-50", "woocommerce-docs-21", "woocommerce-docs-49", "woocommerce-docs-32", "woocommerce-docs-46", "woocommerce-docs-51" ] }, { "productId": "woocommerce", "storyId": "serverless-commerce-functions", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "WooCommerce's architecture is documented as extensible via PHP hooks (add_action/add_filter) that plugins/extensions use to insert custom logic into templates and core flows, and the Marketplace/extensions ecosystem confirms third-party logic can run inside the platform. However, the evidence pack only shows generic Storefront theme hooks and marketplace extension mentions — it does not document WooCommerce's core action/filter hooks specifically for discounts, shipping rules, or validation, nor any serverless/function-as-a-service execution model. Missing for 10: concrete documentation of cart/checkout/shipping filter hooks (e.g., woocommerce_calculate_totals, woocommerce_package_rates) or a serverless functions feature, and independent developer corroboration of using hooks for discount/shipping/validation logic.", "evidenceIds": [ "woocommerce-docs-9", "woocommerce-docs-45", "woocommerce-docs-54", "woocommerce-docs-10", "woocommerce-docs-22" ] }, { "productId": "woocommerce", "storyId": "shipping-rates-labels", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "WooCommerce marketing docs claim 'live shipping rates from leading carriers' and 'options to print labels at home' bundled with the platform, but the shipping doc itself only discusses label cost verification, not a live-rate/checkout integration or tracking dashboard, and label printing/live rates in practice typically require third-party extensions (e.g., WooCommerce Shipping) not detailed here. Missing for 10: concrete documentation of the checkout carrier-rate integration flow, label purchase workflow details, and shipment tracking UI, plus independent/hands-on confirmation this works out-of-the-box.", "evidenceIds": [ "woocommerce-docs-20", "woocommerce-docs-34", "woocommerce-docs-48", "woocommerce-docs-7", "woocommerce-docs-25" ] }, { "productId": "woocommerce", "storyId": "tax-calculation-automation", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "WooCommerce docs mention 'automated tax calculations' as a marketing feature and a core guide for enabling/configuring taxes and adding tax rates, but the evidence pack shows only manual tax-rate table setup, not per-jurisdiction automatic rate updates, VAT-specific handling, or built-in filing-ready tax reports. Missing for 10: evidence of automatic jurisdiction rate updates (e.g. via a tax service integration), VAT-specific compliance handling, and generation of filing-ready tax reports.", "evidenceIds": [ "woocommerce-docs-6", "woocommerce-docs-20", "woocommerce-docs-34" ] }, { "productId": "woocommerce", "storyId": "theme-code-customization", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "WooCommerce/Storefront documents a genuine templating layer (add_action hooks for HTML/PHP/JS insertion into core templates) and the GitHub repo shows a local build process plus Storybook integration for developing/testing in isolation, giving developers a documented customization and local-preview path. However there is no explicit documentation of a version-controlled theme deployment workflow (e.g., CI/CD, staging-to-production theme push) — that relies on generic WordPress/Git practices not directly evidenced here. Missing for 10: documented deployment/versioning workflow for themes, explicit local preview tooling beyond Storybook, end-to-end example of a version-controlled theme release.", "evidenceIds": [ "woocommerce-docs-9", "woocommerce-docs-45", "woocommerce-docs-54", "woocommerce-docs-55", "woocommerce-gh-1", "woocommerce-docs-57" ] }, { "productId": "woocommerce", "storyId": "theme-storefront-launch", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "WooCommerce offers designed themes (Storefront, and the new block theme 'Purple' with 'extensive customization options and modern templates') and initial setup guidance around homepage design, menus, and site structure, suggesting a storefront can be launched and styled. However, the core documented customization mechanism for Storefront explicitly requires inserting HTML/PHP/JavaScript via add_action() hooks, which is code-based rather than no-code, and evidence for genuine no-code block-editor customization (drag-and-drop sections, branding controls) is thin and limited to a single beta announcement. Missing for 10: detailed no-code section/layout editor documentation, evidence of drag-and-drop branding tools, and independent hands-on confirmation that non-developers can fully customize without code.", "evidenceIds": [ "woocommerce-docs-9", "woocommerce-docs-45", "woocommerce-docs-54", "woocommerce-docs-57", "woocommerce-docs-31", "woocommerce-docs-39" ] } ]