Fabric vs Vendure

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.

Vendure

Full cart, coupon, shipping and payment flow in the GraphQL Shop API, with ErrorResult types an agent can branch on. No vendor-hosted API. Vendure Cloud is only partly available.

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

Vendure

1. Keep the session token from the first Shop API response and send it on every call. It holds the active order
2. Check each mutation result's __typename and errorCode. Expected failures return 200 with an ErrorResult
3. Don't retry addItemToOrder blindly. Read the active order first, since a repeat adds the quantity again
4. For server-side work, enable api-key in authOptions.tokenMethod and give the key one role in one channel
5. Run 3.7.3 or later, and purge old job records, which may still hold session tokens