Restaurant AI FAQ
TL;DR
Multi-location restaurants need four things: isolated data per location, an owner-wide rollup dashboard, the ability to run each location on a different plan tier, and flexible payment routing (one entity vs separate LLCs). Aedan Rose ships all four — one owner login switches between restaurants in a single click, each on its own independent plan tier.
Why isolation matters
Cross-location data leaks are how multi-location software breaks. An employee at location A should never see location B's schedule, customers, or analytics unless they have an explicit role at B.
Aedan Rose enforces isolation at the database layer across both PostgreSQL and Firestore. Every query is scoped to the active restaurant; permissions are checked server-side, not just in the UI.
Per-location plan flexibility
Most multi-location platforms force you onto one plan for all sites. That breaks the math: your flagship needs Enterprise, your café needs Free, your pop-up needs Starter.
Aedan Rose lets each restaurant run an independent plan tier (Free / Starter / Pro / Growth / Business / Enterprise) under one owner login. Move a site up or down mid-cycle with prorated billing.
Payment routing for groups
Some groups are one legal entity with shared payouts. Others are separate LLCs per location. Aedan Rose supports both: owner-default Stripe Connect account, or per-restaurant separate accounts.
CFO MRR queries dedupe shared subscriptions so analytics don't double-count an owner who paid once.
The owner rollup
Group Overview dashboard rolls up every restaurant — plan tier, employee count, last activity, orders/reservations in the last 24h — sortable, searchable, one screen.
Read more on Aedan Rose
Try it free — no credit card
Free plan supports 25 conversations per month. Cancel anytime, no contract.
Start Free See Pricing