GraphQL API
The storefront talks to the backend through one GraphQL schema. Every commerce engine serves the same schema, so a storefront keeps working when the engine behind it changes. This reference is generated from @evolve-framework/schemas v1.0.0.
Domains
The schema is built from domains. Each domain adds its queries, mutations, and types, and some add fields to another domain's types.
| Domain | Queries | Mutations | Types |
|---|---|---|---|
| Address lookup | 1 | – | 0 |
| Address suggest | 2 | – | 1 |
| Authentication | – | 8 | 22 |
| Back in stock | 1 | 3 | 6 |
| Business units | 2 | 10 | 28 |
| Cart | 2 | 13 | 56 |
| Catalog | 9 | 1 | 59 |
| Checkout | – | 3 | 10 |
| Content | 12 | 1 | 81 |
| Customer | 2 | 10 | 28 |
| Delivery options | 1 | 3 | 22 |
| Gift card | 1 | – | 0 |
| Invoice | 1 | – | 4 |
| Multiple carts | 1 | 4 | 10 |
| Order | 2 | 1 | 12 |
| Order approval | – | 5 | 39 |
| Payment | – | 5 | 23 |
| Product review | – | 2 | 17 |
| Quote | 1 | 4 | 23 |
| Return | 3 | 3 | 32 |
| Shopping lists | 2 | 6 | 18 |
| Vat check | 1 | – | 2 |
| Shared types | – | – | 60 |
126 operations in total.
Engine support
Which commerce engine has a module for each domain. A service gets a domain by composing its module. A module that exists can still leave parts unimplemented; the engine's package page says which.
B2B
A service builds the schema with or without its business-buyer parts. What only exists in the business build is marked B2B, such as a purchase order number on the cart.