How to choose per-location pricing for your restaurant group

If you are an owner evaluating Luminix, you will hear per location per month — because that is how you run: each store has its own schedule, counts, and compliance burden. This guide explains how we think about packaging without locking you into a number before a scoping call.

Why per location fits GMs and owners

• GMs experience value per store — one queue, one schedule, one logbook rhythm
• Owners multiply by location count for budget — three stores, one quote line
• Modules stay connected within the tenant — you are not buying disjoint SKUs per store

Three tiers (structure)

Luminix packages map to how groups actually roll out:

| Tier | Focus | Typical starting point | |------|-------|------------------------| | Core | Portal, daily ops, scheduling, HR | Fix schedule + people chaos first | | Operations | Core + inventory + vendors | Connect counts to POs | | Complete | Operations + finance + compliance + reports | Full BOH command center |

Final dollars depend on location count, employee volume, and contract term. See our Pricing page for current public framing.

Pilot before you commit

Qualified groups run a 60–90 day pilot on the demo tenant — full modules for one to three locations. Use the pilot to answer:

• Do GMs actually live in the portal queue?
• Did scheduling warnings catch cert gaps before publish?
• Is inventory-to-PO worth expanding to all SKUs?

Convert to annual paid when the workflow sticks — not when the calendar says so.

Founding customer terms

Early customers may receive a limited founding discount on annual prepay. Implementation fees are often waived for pilots converting in the first cohort. Details on your Order Form — not buried in marketing footnotes.

Next step

Book a demo for a tailored per-location quote. Internal decision guide for our team lives in business documentation — your rep will walk through tiers on the call.