Admin & Feature Flags
Change behavior without a deploy
Most-specific scope wins — same precedence philosophy as pricing
Feature flags resolve globally, by business tier, or by region, with the more specific scope always winning. They're served through a short-TTL read-through cache, busted instantly by a FeatureFlagChanged event, so admins see changes take effect in seconds.
Resolution example
Same flag, three contexts
| Context | Winning scope | rfq_enabled |
|---|---|---|
| Global default | GLOBAL | On |
| Small-tier buyers | TIER | Off |
| Small-tier buyers in the EU | REGION | On |
Guardrails
Caught before it ships
Contradiction warnings
If a business tier is configured as RFQ-only checkout but its
rfq_enabledflag resolves false, the admin save handler surfaces a warning before it's persisted — not after a buyer hits a dead end.Graceful in-flight handling
A flag disabled mid-session doesn't hard-cut a buyer who's already mid-checkout — money-in-flight flags allow completion; purely cosmetic ones cut off immediately.