Plans and feature gating

The model

A plan is a named bundle of features (for example the inventory or marketing feature keys) plus pricing. Every restaurant sits on one plan. Two separate doors guard every screen:

• Permissions decide what a *person* can do (their role) — see Roles and permissions.
• The plan decides what the *restaurant* has subscribed to.

A module outside the plan does not vanish from the sidebar — it opens to a clear notice: "X isn't in this plan … someone with platform access turns it on in Platform → Plans". Nothing already entered is deleted; the module reappears the moment the plan includes the feature.

Managing plans

1. 1
   Platform → Plans tab — create or edit plans and the feature keys they include.
2. 2
   Platform → Restaurants → a restaurant's row → Plan — move that restaurant to a different plan.

Revenue and health tabs

• Revenue — subscription billing across tenants, with a retry action for failed charges.
• Health — the API's own health view for the platform operator.