Skip to main content

Current UI Behavior

This page describes what users should expect from the current subscription UI.

Dineax Console​

Dineax Console is the intended platform surface for subscription visibility and future commercial operations.

Current Console subscription behavior may include:

  • a Subscriptions navigation item;
  • a plan list area;
  • empty state messaging such as No plans found;
  • read-only tenant subscription diagnostics where tenant detail panels are available;
  • current subscription, entitlement, usage, trial, and lifecycle history visibility where API data exists.

Dineax Admin​

Dineax Admin may show tenant-level subscription administration where the signed in user has the required permissions.

Current Admin behavior may include:

  • plan visibility;
  • tenant subscription lifecycle visibility;
  • entitlement override visibility;
  • usage counter visibility;
  • trial visibility;
  • controlled lifecycle actions where implemented and authorized.

Dineax POS​

Dineax POS is not the place to manage SaaS subscription plans. POS users should focus on restaurant operations.

Examples:

  • order taking;
  • KOT/KDS;
  • bill generation;
  • manual payment recording;
  • receipt and reprint workflows;
  • business day and shift operations.

Customer Ordering​

Customer ordering screens should not expose subscription plan management. Commercial module access may later affect which customer-facing capabilities are enabled for a tenant, but billing and subscription management remain a platform/admin concern.

Current Empty States​

Empty stateUser explanation
No plans foundNo visible plan records exist in this environment.
No active subscriptionThe selected tenant does not have a visible active subscription foundation record.
No usage countersNo tracked usage counters are visible for that tenant yet.
No trialsNo trial records are visible for that tenant.

Current Non-Claims​

  • The UI does not prove production billing readiness.
  • The UI does not prove final commercial plan packaging.
  • The UI does not prove customer self-service upgrade readiness.
  • The UI does not prove subscription invoice generation.
  • The UI does not prove subscription payment collection.