Feature flags

Feature flags turn storefront and admin features on or off per store, as data — no rebuild. They live in the tenant config as a JSON map, feature_flags, that the storefront and admin read at runtime.

Where they’re set

Deep-ops console → Core → Tenant configs → Feature flags (the feature_flags field). It’s a plain JSON object of flag: true|false:

{
  "wishlist": true,
  "collections": true,
  "reviews": false,
  "loyalty": false
}

The storefront and admin read known keys; a flag that’s absent falls back to its safe built-in default. So you only need to list the flags you’re changing.

The flags

These are the flags the storefront and admin recognise. The default column is the safe posture a store ships with (also what the reference BellTex seed sets).

Flag	Purpose	Default
wishlist	Customer wishlists / save-for-later	on
collections	Curated product collections on the storefront	on
completeTheLook	“Complete the look” cross-sell on product pages	on
oto	One-time-offer / one-tap-order upsell flow	on
reviews	Product reviews & ratings	off
loyalty	Loyalty / points program	off

Reviews and loyalty are off by default

reviews and loyalty ship off. Turn them on deliberately once you’re ready to moderate reviews or run a points program — set "reviews": true / "loyalty": true in the tenant config’s feature_flags. Leaving them off is the safe default, not an oversight.

Flags are a store-shaped map

feature_flags is a free-form JSON object, so a store (or a theme) can carry its own keys — the reference BellTex store, for example, adds catalog-specific flags like boysSection. Unknown keys are simply ignored by features that don’t look for them. The model default is an empty map {}; the frontends apply their built-in default for any flag you don’t set.

How a flag reaches the apps

Flags are published in the public runtime config the frontends read (GET /api/v1/config/ → features), so a change takes effect when the frontends refresh (~5 minutes) or immediately after docker compose restart storefront admin. No image rebuild — see Store settings & branding.

Tip

There’s also a separate Feature Flags admin section (named on/off toggles with descriptions, per company) for operational flags outside the storefront’s runtime map. For buyer-facing storefront/admin features, TenantConfig.feature_flags above is the surface you want.