Head to head · Commerce orders · October 2026 research run

Fabric vs Shopware

Shopware scores 71.4 (BB) on agent readiness against Fabric's 43.7 (E), and leads in every scored category. Both do commerce orders.

Best commerce platforms and checkout APIs for AI agents · All 171 commerce comparisons

Which one, for what

Fabric E

Best for A merchant-side API for retailers already on Fabric's order management, catalogue or dropship products.

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Shopware loses 5 points for them

Watch for

No public price, free tier or self-serve signup. A trial account is arranged with Fabric

Shopware BB

Best for A merchant already on Shopware, or a team that wants an MIT PHP backend with a built-in MCP server for back-office work.

Ahead on

  • Reliability, 83 against 23
  • Schema & documentation, 85 against 79
  • Agent ergonomics, 78 against 57
  • Security & auth, 73 against 62
  • Payments & pricing, 50 against 0
  • Maintenance & community, 87 against 15
  • Transparency & trust, 76 against 55

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

The MCP server is marked experimental until 6.8, and 6.7.14.0 changed what tools/list returns on the Store API endpoint

Score by category

CategoryWeight this runFabricShopwareEdge
Reliability16%202383Shopware +60
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27985Shopware +6
Agent ergonomics13%16.25778Shopware +21
Security & auth14%17.56273Shopware +11
Payments & pricing10%12.5050Shopware +50
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81587Shopware +72
Transparency & trust7%8.85576Shopware +21
Negative events≤150-5
TotalE 43.7/100BB 71.4/100

Facts side by side

FactFabricShopware
KindHTTP APIHTTP API
VendorCommerce Fabric, Inc.shopware AG
Hosted endpointhttps://api.fabric.inc/v3no (local only)
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary SaaS under Fabric's Terms and Conditions (last updated 1 January 2026) and an order formMIT for the Community Edition core. Paid plans add proprietary extensions under shopware AG's general terms
Tools exposednone14
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-10-02
Terms last updated2026-01-012026-06-10
Privacy policy last updated2021-01-14couldn't be read
Customer content may train modelsnot found in the textyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone3.4k stars, 31k npm/wk

Verdicts

Fabric

Public OpenAPI files for about 980 operations, llms.txt, client credentials with role-limited system apps, and a published 99.9 per cent SLA. Access needs a sales contract, with no public price or self-serve trial. The commerce docs are labelled legacy, the newest release notes date from July 2025, and no status page was found.

Shopware

MIT-licensed core with OpenAPI specs for both APIs and a built-in MCP server that advertises three discovery tools, previews writes by default and limits each integration to an allowlist. The MCP server is experimental until 6.8, and 20 security advisories were published between May and September 2026, four of them critical.

Before you call either

Fabric

  1. Get the tenant ID and a System App client ID and secret from the merchant's Copilot admin, with the narrowest role the task needs
  2. Request a new system token from {authURL}/v1/token every 10 minutes, since system apps receive no refresh token
  3. Send x-fabric-tenant-id on every call, and x-fabric-channel-id where the merchant sells in more than one channel
  4. Page order searches with offset and limit, because the default response returns 10 orders
  5. Read errorCode and context.endpoint in Orders and Inventory errors, and check for duplicates before retrying a write

Shopware

  1. Ask the merchant for an integration without --admin, tied to an ACL role and an MCP allowlist. Send sw-access-key and sw-secret-access-key headers to /api/_mcp
  2. Call shopware-tool-search first, then shopware-toolset-enable, and keep the Mcp-Session-Id header. A fresh session lists only three tools
  3. Pass dryRun=false to commit a write. shopware-media-upload has no dry run and uploads at once
  4. For shopping, call the Store API over HTTP with the sales channel's sw-access-key and keep the sw-context-token. The Store API MCP endpoint has no cart tools in core
  5. Send includes in search criteria to cut response size, and read the 429 body for the wait time

Questions

Which is better for AI agents, Fabric or Shopware?

Shopware scores 71.4 (BB) on agent readiness against Fabric's 43.7 (E), and leads in every scored category.

Do Fabric and Shopware need an API key?

Fabric uses an OAuth sign-in. Shopware takes an API key or an OAuth sign-in.

Can an agent call Fabric and Shopware without installing anything?

Fabric has a hosted endpoint at https://api.fabric.inc/v3. No hosted endpoint is listed for Shopware.

Are Fabric and Shopware open source?

No open-source release is listed for Fabric. Shopware is open source (MIT for the Community Edition core. Paid plans add proprietary extensions under shopware AG's general terms).

Other comparisons with Fabric or Shopware

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.