menu-MENAmenu-MENA
HomePricingBlogContact UsGet Started
Map of Cairo and Alexandria pinned with multiple restaurant branch locations

Manage Multiple Restaurant Branches from One Account

By menu-MENA Team

Published on May 4, 2026

Branches are not copies of each other

A koshary chain with one location in Maadi and one in Zamalek does not run the same menu at both. The Maadi branch might sell a takeaway-heavy lineup with smaller portions and a delivery-friendly price ladder. The Zamalek branch might run a sit-down operation with combo plates and a different beverage selection. They share a brand and an owner, but the menu, the photos, the pricing, and even the WhatsApp number are different.

Most digital menu tools either force you to run separate accounts (separate logins, separate billing, no cross-branch reporting) or force you to share a single menu across every location (which is wrong). menu-MENA is built for the middle case, which is the actual case.

A QR menu system built for chains, not single locations

A QR menu for restaurants with one location is straightforward. A QR menu system for a chain has to handle separate menus per branch, separate WhatsApp numbers, and aggregated reporting without forcing the owner to log in five times. That is the multi-branch model below.

How multi-branch works on menu-MENA

The data model is a parent tenant with child branches. The parent owns billing, the global brand, the design templates, and the catalog overlays that should be shared. Each child branch has its own slug, its own menu, its own pricing, its own opening hours, its own WhatsApp number, and its own QR code.

When you create a new branch from the dashboard, it inherits the parent's catalog and overlays at creation. From that moment forward it can drift independently. If your Zamalek branch wants to charge 5 EGP more for the special koshary, it does, without affecting Maadi.

Owner dashboard showing three branches with separate menus and aggregate analytics

One login, separate storefronts

The owner logs in once and switches between branches with a dropdown. Each branch's storefront URL is distinct, for example menus.mena-x.com/koshary-maadi and menus.mena-x.com/koshary-zamalek. Guests scan the QR specific to where they are sitting. The parent owner sees aggregated stats across all branches plus drill-downs into each.

Per-branch QR codes

Generated client-side at any size from 128 to 512 pixels, downloadable as PNG. A common pattern is a printed QR at the entrance, a smaller QR on each table, and a delivery-page QR on the takeaway bag, all pointing at the right branch.

The pricing math

The base subscription is 3 EGP per day, 90 EGP per month, or 1,000 EGP per year. Every additional branch is 50% off the base. The math is straightforward:

  • 1 branch: 1.0x base (3 EGP/day, 90 EGP/month, 1,000 EGP/year)
  • 2 branches: 1.5x base (4.5 EGP/day, 135 EGP/month, 1,500 EGP/year)
  • 3 branches: 2.0x base (6 EGP/day, 180 EGP/month, 2,000 EGP/year)
  • 4 branches: 2.5x base (7.5 EGP/day, 225 EGP/month, 2,500 EGP/year)
  • 5 branches: 3.0x base (9 EGP/day, 270 EGP/month, 3,000 EGP/year)

A five-branch chain pays roughly 3,000 EGP per year for fully separate menus, separate analytics, separate QR codes, and shared admin. Compare that to printing five sets of laminated bilingual menus every time a single ingredient cost moves.

The 14-day free trial covers the parent account and all branches you create during the trial period.

What happens when you open a new branch

A practical flow. You open a third branch in Heliopolis. From the parent dashboard you click "Add branch", give it a slug, pick whether to start from a clone of an existing branch or from the bare catalog, and set its WhatsApp number and opening hours. The branch goes live immediately with its own URL. You print QRs, deploy stickers, and the next billing cycle picks up the new 2.0x rate.

If the branch underperforms and you close it six months later, you archive it from the dashboard. The next billing cycle drops back to 1.5x. You do not have to delete data; archived branches stay queryable for historical reporting.

Side-by-side menu comparison showing the same dish at different prices across two branches

Per-branch features that actually matter

A few things that come up constantly with multi-branch operators in Egypt:

Different WhatsApp numbers

Each branch has its own WhatsApp Business number wired into the WhatsApp FAB. A guest dining in Alexandria reaches the Alexandria branch when they tap to order, not the Cairo HQ.

Different operating hours

A branch inside a mall has mall hours. A branch on a corso has late-night hours. The storefront grays out items outside the branch's serving window for that section, so a guest does not order breakfast at midnight from a branch that does not serve it.

Different dietary realities

A branch attached to a hotel might run a fully vegan section. A branch on a beachfront might lean seafood-heavy. The dietary labels (vegetarian, vegan, dairy, nuts, spicy, popular, new) are per-item, per-branch, so the filtering on the storefront reflects what each branch actually sells.

Key takeaways

  • Each branch has its own menu, URL, QR code, WhatsApp number, and pricing
  • Owner account ties everything together for billing and aggregated reporting
  • 50% off every additional branch: 2 branches at 1.5x, 3 at 2x, 5 at 3x the base
  • Branches inherit the parent catalog at creation, then drift independently
  • Closing a branch reduces your bill at the next cycle automatically

A chain that runs three branches in Cairo on menu-MENA pays roughly 2,000 EGP per year and gets three independent storefronts with shared admin. That is less than the cost of one decent night of staffing.

Frequently Asked Questions

Branch one pays the base — pick your flavor: 3 EGP/day, 90 EGP/month, or 1,000 EGP/year. Branches two through five each ride at half the base, so a five-branch chain runs at 3.0x: 270 EGP/month or 3,000 EGP/year for all five locations together.

No. Each branch has its own menu, its own pricing, its own opening hours, and its own WhatsApp number. The owner account ties them together for billing and admin, but the storefronts are independent.

Yes. Branches inherit the parent tenant's catalog and overlays by default at creation, then drift independently. You can also push selective updates from one branch to another from the admin dashboard.

Yes. Each branch is a separate slug on the platform, for example menus.mena-x.com/koshary-maadi and menus.mena-x.com/koshary-zamalek. Guests scan a QR specific to the branch they are dining at.

The owner account has access to all branches. Per-branch staff roles let you give a manager edit access to only their location while keeping the parent account in control of billing and global settings.

The owner dashboard aggregates view counts, popular items, and WhatsApp click-throughs across all branches and lets you drill into any single branch. You can compare which dishes sell best where.

Billing recalculates at the next cycle based on the active branch count. If you go from three branches back to two, your bill drops back to 1.5x the base on the next renewal.

They do. The whole platform is a Progressive Web App that runs inside any modern browser, so iOS guests, Android guests, and desktop browsers all hit identical menus with no install required. Multi-branch owners typically pin the dashboard to their home screen so flipping between locations is one tap.

No hard limit. Chains with ten or more branches use the same multi-branch model, and the 50% off rule applies to every additional branch beyond the first regardless of count.