BoxNCase Platform
Draft
This page is a stub. It captures the intended structure of the BoxNCase Platform documentation; the details are being written as the platform ships. Questions: [email protected].
BoxNCase Commerce is built on Saleor Core. The BoxNCase Platform is the layer around it that provisions and operates commerce stacks for BoxNCase vendors and partners: a control plane, a provisioning worker, wildcard storefront hosting and a Shopify-compatibility gateway.
Everything documented in the rest of this site (the GraphQL API, dashboard, apps, webhooks) applies to each vendor stack. This section documents what is specific to BoxNCase.
What the platform adds
| Capability | Summary |
|---|---|
| Vendor provisioning | Each external vendor gets an isolated Saleor Core stack (API, database, media, dashboard); internal vendors share BoxNCase's main stack behind channel and permission boundaries. |
| Gated B2B storefronts | Storefronts that require an approved wholesale account before prices, catalog or checkout are exposed. |
| Marketplace opt-in and sync | Vendors choose which products are listed on the BoxNCase marketplace; the platform syncs catalog, stock and orders both ways. |
| Order privacy | Self-fulfilling vendors keep customer and order data inside their own stack. |
| Webhooks and auth | How platform services authenticate against vendor stacks and which webhooks the platform subscribes to. |
| WMS operational APIs | Warehouse operations (receiving, picking, packing, split-box shipping) that are not part of the GraphQL schema yet. |
Environments
- BoxNCase main - the production stack for BoxNCase's own catalog (
https://api-production-38d7.up.railway.app/graphql/). Try it in the Playground. - Vendor stacks - one per external vendor, provisioned on demand.
- Sandbox - a disposable stack for integration testing (endpoint provided on request).
Where to go next
- New to the API? Start with the API walkthrough and the API reference.
- Building an integration? Read Building Apps and Webhooks.