Subscription FAQ
Does Dineax already support subscriptions?
Yes, as a foundation. Dineax has plan, tenant subscription, entitlement, usage-counter, trial, lifecycle, Admin, Console visibility, audit, and focused test foundations.
Can customers currently buy individual modules?
Not yet. Commercial module packaging, module add-ons, subscription items, and pricing are not production-ready.
Does a user role control the subscription?
No. A user role controls what a user may do. A subscription controls what the tenant is entitled to use. These are separate concepts.
What is an entitlement?
An entitlement is the tenant-level right to use a capability. A user still needs the relevant permission to perform actions inside that capability.
Are outlet and device limits supported?
Limit foundations exist in parts of the product, and usage counters exist. Commercial outlet and device pricing is not active yet.
Can customers upgrade plans themselves?
Self-service paid upgrades are not production-ready. Plan changes require an approved workflow and commercial policy.
Does Dineax generate subscription invoices?
No. Dineax SaaS subscription invoices are not currently production-ready.
Why do I see "No plans found" in Dineax Console?
The page loaded, but the connected environment has no visible subscription plan records for your user. This can be normal in development, test, or newly configured environments. It does not mean commercial billing is ready or that approved public plans exist.
Who should change a tenant's subscription?
Commercially sensitive changes should go through the approved platform/support process until self-service subscription billing is implemented and validated. Restaurant outlet staff should not manage SaaS subscription plans.
Can I add another outlet or device from the subscription page?
Not as a production billing workflow today. Outlet and device allowances are planned commercial concepts, but outlet-based and device-based subscription pricing are not active.
Are restaurant payments the same as subscription payments?
No. Restaurant payments are customer payments inside the POS. Subscription payments are future SaaS billing records between a tenant and Dineax.
What happens when a trial expires?
The foundation can record expiry. Final customer behavior depends on approved trial policy, entitlement enforcement, data retention, and support workflow.
Why can a module be unavailable even if a user has permission?
Because permission is user-level access. A future commercial module can still be unavailable if the tenant is not entitled to it or if the feature is not released for the tenant's operating model.
Will menu management wait for subscription commercialization?
No. Core product and pilot work can continue. Subscription commercialization is needed before selling differentiated modules or broadly enforcing paid-module access.
Is subscription commercialization a pilot blocker?
Not by itself. It becomes a blocker only if the pilot contract requires paid module packaging, paid add-ons, entitlement-aware navigation, subscription invoicing, or subscription payment collection.