Sous Chef API
Sous Chef Onboarding API
Documentation

What "provisioned" means

This API provisions to one specific point: menu-buildable. A location and its stores exist, have a menu copied onto them, and can be built on — and stop there. Read every response with that line in mind, because "provisioned" is easy to over-read as "open for business," and it does not mean that here.

What a provisioned store is

After addBrandsToLocation, a store exists for each delivery platform your organization is connected to. Each one is:

  • not active — it does not accept orders;
  • not integrated — nothing has synced it to the delivery platform yet;
  • not published — no menu is visible to a customer anywhere.

It is, deliberately, inert. Everything needed to take it live is in place; nothing that would actually do so has run.

Why going live is a separate step

Going live on a delivery platform is not purely a technical action — it is a business decision with its own checks: menu review, platform-side merchant setup, and timing the operator actually wants. Folding that into a provisioning call would mean a single API request could put a brand new, unreviewed menu in front of real customers. This API stops one step short of that on purpose, so going live stays a deliberate action taken separately, never a side effect of provisioning.

A provisioned store is visible in the Sous Chef portal from the moment it is created, and the Management API's fetchStores lists it with wentLiveAt set to that moment. That timestamp records when the store was set up, not when it started selling. If your integration needs to know whether a store is open and taking orders, that is a Management API concern — fetchStoreStatuses reports it.

What this API never creates

Two things sit outside this API entirely, even though they sound adjacent to "provisioning":

  • Organizations. Your organization already exists before your first call; this API has no operation that creates one.
  • Brands. fetchProvisionableBrands lists brands that already exist and are not retired in your organization. This API adds an existing brand to a location — it never defines a new one.

Where to look for the technical side of "provisioned"

The mechanics — what gets written for each brand, and why the write is safe to repeat — are in Concepts → The provisioning flow and Concepts → Retries and idempotency. This page is the one to point a non-technical stakeholder at when the question is "what does this API actually do to my restaurant."