A thing I kept running into while building StoreFlux (a multi-tenant commerce backend): the moment you add enough optional features, you start wanting some way to gate them per tenant. The usual answer is a feature-flag system or a plan-tier check scattered across controllers. I didn't want either, so here's what we actually built instead.
The rule we set first
Core commerce β products, orders, customers, payments, inventory β is never behind a flag, a plan, or a tier. If a tenant can sign up, they get all of that, full stop. Everything else lives in a short, closed list of optional modules: realtime, AI, loyalty, referrals, B2B, coupons, gift cards, banners, SEO, social ads, carriers, API keys, webhooks. Thirteen of them right now.
Every module ships off by default for every tenant. A SuperAdmin turns one on for a specific tenant β there's no self-serve upgrade flow yet, it's deliberate and manual.β¦