Luminix insights — rule-based exceptions today, ML later

Cross-module exceptions already land in the GM action queue. What is live today is rule-based; machine-learning recommendations are roadmap — not a live AI product.

Restaurant software vendors talk about AI constantly. For a GM, the only question that matters: does it save me time on shift — or add another dashboard?

Luminix answers that with a rule-based exception hub today. Machine-learning recommendations are on the roadmap — we do not sell “AI insights” as a live product you can turn on now.

Built on connected data

Insights only work when modules share records. Luminix already connects scheduling, HR, inventory, vendors, and finance under one organization — the hub reads exceptions across those signals, not a single CSV export.

Examples of rule-based exceptions shipping today (availability varies by tenant and tier):

Labor vs coverage warnings before publish week
Below-par inventory and variance review items
Onboarding and AP items clustered for finance / GM review

Same queue, not a new inbox

Exceptions land as actionable items in the portal — alongside cert expirations and below-par items. GMs do not learn a separate "AI app."

Operator approval, not black box

Luminix is not aiming for unattended changes to schedules, orders, or approvals. Items come with context; your team decides what to act on. That matches how GMs actually run — especially on compliance and labor.

What to ask on a demo

Which exception types are live in the demo tenant today?
How do queue items respect location permissions?
What is rule-based now versus ML roadmap?

Status

Rule-based hub exceptions are live where your modules are enabled. Proactive ML recommendations are roadmap — not every module or tenant has an “AI feed.” Book a demo for current availability and roadmap fit for your group.