◆ Zayos · Multi-location

Multi-location.
One login.

2-25 locations of one brand. Or 2-10 brands across one location. Same admin, unified customer book, per-location Otter tablet, per-location Stripe account if you need it.

Book a 15-min walkthrough →
Customer book carries across
Customer LTV, history, dietary preference all unified — even when they order from a different location.
Per-location menus
Share a base menu, override at the location level. 86'd items stay scoped.
Reporting that rolls up
Dashboard aggregates + per-location filter. AI shift briefing runs per-location every morning.
Per-location Stripe Connect
Multi-LLC operators keep revenue separate without month-end splits.
FAQ
Can a customer order from any location?+

Yes. The storefront detects the customer's address (or they pick a location). The order routes to that location's Otter tablet. The customer's book record stays the same — order history, LTV, dietary preference all carry across locations.

Can different locations have different menus?+

Yes. Menus are per-location. You can also share base menus and override at the location level (Location A has the brunch menu, Location B doesn't). 86'd items apply only to the location that 86'd them.

How does reporting work across locations?+

Dashboard rolls up across locations by default with a per-location filter. Channel mix (direct vs Uber Eats vs DoorDash) is per-location. Revenue + cohort retention is per-location AND aggregated. AI shift briefing runs per-location every morning.

Can each location have its own Stripe account?+

Yes. Stripe Connect destinations are per-location. Multi-location operators with separate LLC structures don't commingle revenue or do month-end accounting splits.

What about loyalty across locations?+

Loyalty is unified by default — points earned at Location A redeem at Location B. You can scope loyalty per-location if franchise economics require it (franchise A doesn't want to honor franchise B's points).