Store Management

Manage your stores' availability and metadata through the Commerce API.

For full endpoint documentation — including pause/resume operations, metadata updates, and store listing — see the Commerce API Reference.

Fulfillment Capability

Every store advertises which fulfillment types it supports via two booleans:

• deliveryAllowed — true if this store accepts delivery orders.
• pickupAllowed — true if this store accepts pickup orders.

At least one of these must be true. A catalog push that declares both as false will be rejected.

Fulfillment capability is a store-level property — it is not carried in the CatalogSet payload and does not change per menu. Set it once per store via the store management endpoints (or via the admin portal) and update it only when the store's real-world capability changes.

What the consumer app does with these flags

• Discovery: stores are filtered by the selected fulfillment mode. A delivery-only store will not surface for pickup-mode users, and vice versa.
• Restaurant cards: render a "Delivery", "Pickup", or "Delivery · Pickup" badge from these flags. Mode-incompatible stores are greyed out with an explanation rather than hidden.
• Cart gate: the Add-to-Cart button is disabled on mode-incompatible stores with copy that prompts the user to switch mode.
• Order placement: the backend re-validates the combination; a delivery order for a pickup-only store is rejected with a typed error.

Recommendation

If you integrate a provider whose store operating model only supports one fulfillment type, set the other flag to false on all your stores explicitly. The system defaults both to true — declaring your capability prevents surprising the end user mid-checkout.