Multi-Location Setup: Run 2–25 Locations from One Dashboard

Multi-location operators run every location from the same admin.eatsyorders.com account. One login, one customer database, one loyalty program — but each location has its own catalog, hours, delivery footprint, and staff. Here's how it works.

Why per-location matters

Different locations sell different things. Different counties have different sales tax. Different neighborhoods have different delivery zones. A "one-size-fits-all" config breaks the moment your second location opens. Eatsy is built per-location from the ground up: every dataset has a location scope.

Adding a new location

This is staff-led. You schedule a 30-minute new-location call with your onboarding manager. We:

1. Create the new Place in the system.
2. Clone the master catalog from another location (admin.eatsyorders.com → Location management → Import catalog).
3. Configure the new location's hours, taxes, delivery footprint, and gateway.
4. Seed the initial staff for that location.

You then walk the cloned catalog in Menu management and tweak per-location overrides — pricing, items not available, location-only specials. Most operators finish in 30–60 minutes.

Brand config: location vs. company

Channels → Brand config → Appearance has two stacked sections:

• Location appearance — applies to a single location.
• Company appearance — fallback for any location that doesn't override.

So your second location can have a different logo or color if it's a different concept (e.g. flagship vs. food-hall stall), or inherit the company default if not.

Per-location menu overrides

The location switcher in the top-left of the dashboard scopes everything you see in Menu management. Switch to Location B, and edits you make there only apply to B. To roll a menu change to all locations, change it on each one (or use Massive upload per location).

Per-location operations

• Hours — staff-configured during the new-location onboarding call. Tell us the hours; we set them.
• Delivery footprint — zones, fees, minimums per zone. Staff-configured.
• Payment gateway — each location has its own Shift4 or NMI account. Staff-configured.
• Tax rates — per location. Staff-configured.

All of these are visible in Account → Settings → ... once configured, but the initial setup is run by your onboarding manager.

Per-location employees

Users → Employees lets you assign each employee to specific locations. A Manager at Location A can be locked out of Location B's data — no "see everything" by default. See Staff Permissions.

The location switcher

Top-left of every page in admin.eatsyorders.com. Switches the entire dashboard's scope. There is no "All Locations" aggregate view in the merchant admin currently — you view one location at a time. For aggregate revenue across locations, your onboarding manager can pull a report.

Pricing

Linear: $89.99/month per location for Microsite, $149.99/month per location for Branded App. No bundle discount — but no penalty either. Add or remove a location any time.