Why Ghost Kitchens Are a Different Menu Problem
A ghost kitchen runs delivery-only with no dine-in space. Often runs multiple virtual brands from a single shared kitchen: one production line putting out burgers as “Joe's Diner,” pasta as “Nonna's Kitchen,” and salads as “Greenhouse Bowl,” each with its own menu, its own brand, its own customer-facing voice. The menu problem is structurally different from a traditional restaurant: you have N brands instead of 1, you distribute through several aggregators (DoorDash, Uber Eats, Grubhub, ezCater, sometimes Postmates) plus your own direct channel, and every menu change has to propagate to all of them.
This guide covers the menu architecture for ghost kitchen operators, whether you're running a single virtual brand alongside an existing restaurant, or managing 5-10 virtual brands from a dedicated production kitchen. The wrong setup multiplies every menu update across brands and channels; the right setup lets you make each change once.
The 4-Channel Distribution Reality
Ghost kitchen operators distribute menus through 4 channel categories. Each has its own menu requirements, commission economics, and customer relationship.
1. The aggregators (DoorDash, Uber Eats, Grubhub)
The aggregator takes a commission on each delivery order, from 15-20% on entry plans to 30% on top plans (see the DoorDash, Uber Eats and Grubhub pricing pages). The aggregator owns the customer relationship, the data, and the marketing surface. Your menu lives in their system; you can edit it there but you don't own the page. For a delivery-only kitchen, this is often the highest-volume channel.
2. The first-party direct channel (your own website / app)
Lower cost (payment processing and your ordering platform's fees, no aggregator cut), customer relationship is yours, data is yours, marketing is your responsibility. Volume is typically smaller, but each order keeps far more of its revenue. The strategic case for direct is unit economics, not volume.
3. The corporate / catering channel (ezCater, Foodee, etc.)
Commission similar to aggregators, but order sizes are much larger (a group order for an office versus one person's meal). High-margin per-order despite the commission. Different menu requirements (group sizes, larger portions, allergen-comprehensive disclosure for office settings).
4. The marketplace partnerships (specialty channels)
Specific to your concept: an Indian ghost kitchen might also list on Indian-food-specific apps; a vegan brand on PlantBased apps. Lower volume, higher matched-intent customers.
The strategic question for every ghost-kitchen operator: what mix of these 4 channels delivers the best unit economics? The math is rarely “abandon aggregators” (volume) and rarely “abandon direct” (margin); it's usually a mix of the two, tuned to maximize total margin.
The Multi-Brand Menu Architecture
The ghost kitchen menu problem isn't just “one menu, four channels.” It's “N menus, four channels” where N is the number of virtual brands you operate. The architecture decisions:
Ghost Kitchen Menu Architecture Approaches
Match architecture to brand count and operational maturity
| Architecture | Best for | Setup complexity | Update workflow |
|---|---|---|---|
| One platform, multiple menus per brand | 2-5 brands, simpler operations | Low (single dashboard) | Edit once per brand |
| Per-brand platform instances | Brand-distinct customer voice / domain | Higher (N dashboards) | Edit N times |
| Aggregator-only (no direct) | Low-volume operators | Lowest | Edit per aggregator |
| All-channel direct + aggregators | 5-10+ brands at scale | Highest: needs middleware (Olo, Cuboh, Otter) | Edit once, propagate to all |
The Aggregator Commission Math
Aggregator commission economics are easy to underestimate until you look at the line items. The headline “take rate” is rarely the full picture. Five components stack:
1. Marketplace commission
The aggregator's base take, typically 15-30% depending on whether you're on the marketing/visibility tier or the basic listing tier. Many aggregators offer multiple tiers; the higher-commission tier gets more in-app marketing visibility (top of search, banner placement, sponsored slots).
2. Delivery fee subsidy
Aggregators often subsidize delivery cost to keep customer prices low. The subsidy comes from your margin, not theirs. It can add a further cost on top of the marketplace commission.
3. Payment processing
Card processing fees on the customer side. Some aggregators absorb this in the marketplace commission; others bill it separately. Read your contract.
4. Promotional discounting
Aggregator-driven promotions (“25% off your first order,” free delivery weekends) are typically partially-funded by the operator. The discount comes off your margin during the promo period. Volume often does increase but per-order margin decreases.
5. Marketing and visibility add-ons
Optional sponsored placements, banner ads, search-result boosts. Variable cost, optional but often the difference between a brand getting orders or not on a crowded aggregator.
All-in, the effective cost of an aggregator order is higher than the headline commission once these components stack. This math is what makes direct-channel pickup or delivery, with no aggregator commission, so attractive even at lower volume.
The Direct-Channel Strategy: Why It Matters
The unit economics gap between aggregator commission and direct-channel payment processing means a direct order keeps much more of its revenue than the same order through an aggregator. Three operator patterns that successfully build direct-channel volume:
1. Bag-insert promotion to convert aggregator customers to direct
Every aggregator order goes out with a small flyer or QR code in the bag offering 15% off the next direct order at the brand's own URL. Conversion rate is low, but each conversion is worth far more in margin. Operators who track this consistently can build a meaningful share of direct-channel revenue over time.
2. SMS / email loyalty for direct customers
Customers who order direct opt into SMS or email. Direct-channel marketing (back-end product launches, loyalty discounts, restock alerts) drives repeat orders without aggregator commission. SMS or email tooling is a modest monthly cost compared with the aggregator commission each repeat direct order avoids.
3. Speed advantage on direct vs aggregator
Direct orders can route to your kitchen faster than aggregator orders (no aggregator middleware). For time-sensitive products (hot food, especially anything with crispy elements), the speed advantage shows up in customer satisfaction. Surface this to direct customers as a value prop (“faster than DoorDash”).
Ghost Kitchen Menu Setup in One Day
Audit your brand and channel matrix
List every virtual brand you operate. For each brand, list the channels it's on (DoorDash, Uber Eats, Grubhub, direct, ezCater, etc.). For each cell in the matrix, note the menu (does it match across channels, or do you have inconsistencies?). The audit alone often reveals items that exist on one channel but not another: missed revenue.
Decide on architecture
For 1-3 brands with operational simplicity priority: single platform with multiple menus per brand. For 4+ brands or brand-distinct customer voice: per-brand platform instances. For 5-10+ brands at scale: middleware (Olo, Cuboh, Otter) that publishes to all channels from one source.
Build the canonical menu per brand
For each virtual brand, build the canonical menu in your chosen platform. Include all items, descriptions, prices, photos, allergen tags, modifier groups. This is the source of truth that other channels reference.
Set per-channel pricing strategy
Pricing rarely matches 100% across channels. On aggregators, you can absorb the commission (lower margin) or pass it to the customer (slightly higher menu prices, common practice). Decide your strategy: same prices everywhere (simpler, customer-friendly) or aggregator-priced higher to absorb commission (better unit economics, customer-perceptible).
Configure direct-channel landing
Your direct channel needs its own customer-facing URL (e.g., a Menujo menu at menujo.com/@brand-name, which is display-only) and CTAs that drive customers there, plus a separate ordering platform or a phone number for placing the order. Add the URL to your aggregator bag inserts. Ensure the direct site loads fast on mobile, makes the way to order obvious, and works across iPhone and Android. Test the full direct-order flow at least once before going live.
Set up update propagation
Whether through middleware (Olo, Cuboh, Otter) or manual updates, document the workflow: when a menu changes, who updates which channels in what order. Many ghost kitchens go aggregator-first (where volume is) and direct-second; some go direct-first (canonical) and aggregator-second (synced).
Test cross-channel pricing and items
Order from each channel as a customer. Verify the menu, prices, photos, and allergen tags match (or don't, by design). Verify items are not missing on any channel. Verify the order routes to the kitchen with the right brand attribution (kitchen needs to know which virtual brand the order is for to apply the right packaging and label).
Ghost-Kitchen-Specific Menu Mistakes
Five mistakes that consistently separate well-run ghost kitchens from struggling ones.
1. Identical menus across virtual brands
Some operators run 5 virtual brands but use mostly-identical menus: same items, slightly different naming. Aggregators flag this and customers notice; the “virtual brand” deception is obvious. Fix: each virtual brand needs distinct items, distinct photography, distinct voice. If you can't commit to that level of differentiation, run fewer brands.
2. Aggregator-only with no direct strategy
Pure aggregator operations are at the mercy of the aggregator's commission economics, algorithm changes, and platform shutdowns. Fix: build a direct channel even if volume is small. The direct-channel revenue you build is the highest-margin revenue on the operation.
3. Forgetting to remove items that 86
A ghost kitchen running 5 brands with 6 channels each is 30 menu surfaces to update when an item runs out. Operators forget; customers order; refunds and complaints follow. Fix: middleware (Olo, Cuboh, Otter) that propagates 86'ing across all channels in one click. Worth the cost (Otter lists plans from $79 to $278/month; Olo does not publish pricing) for any operation above 5-channel-brand combinations.
4. Identical pricing absorbing aggregator commission
Some operators absorb the full aggregator commission and price the menu the same on direct and aggregators, resulting in thin margins on aggregator orders. Fix: raise aggregator menu prices to absorb commission, leaving direct prices at the canonical level. Customer-acceptable; commission-economics improving.
5. No bag-insert promotion to direct
Every aggregator order is a paid customer-acquisition event you're not capitalizing on. Fix: include a small flyer or QR code in every aggregator bag offering a discount on the next direct order. Conversion rate is low but each conversion is high-margin.
How Menujo Fits Ghost Kitchen Workflow
Menujo is display-only menu: ideal for the direct-channel customer-facing menu, not the aggregator integration layer. Three ghost-kitchen fits:
1. Direct-channel menu per virtual brand
Give each virtual brand its own Menujo menu with its own URL (menujo.com/@brand-name). Free covers one menu; Pro ($7/mo or $70/yr) covers up to 10 menus in one account, so a multi-brand kitchen does not need a separate account per brand. Customers who scan a bag-insert QR code or click a direct link land on the brand's menu. The menu itself is display-only: it shows a tap-to-call phone number, so the smallest operations can take direct orders by phone, while larger ones point guests to their ordering platform from the same bag insert or brand website.
2. Aggregator-bag QR code linking to Menujo direct
The QR code on the bag insert points at the brand's Menujo URL. Menujo's analytics count menu views (7 days of history on Free, 60 on Pro, 90 on Business) and do not record which aggregator a guest came from, so if you want per-aggregator attribution, print a different discount code on each aggregator's insert and track redemptions in your ordering platform or POS. Over time that tells you which aggregator drives the most direct conversions, which feeds your commission negotiations.
3. SMS / email loyalty around the Menujo menu
Menujo has no SMS or email opt-in and no Klaviyo or Postscript integration. The public menu shows your phone number, Instagram, Facebook, TikTok and Google Maps links, so collect direct customers' contact details at the checkout step of your ordering platform, or through the social profiles the menu links to.
What Menujo doesn't do for ghost kitchens
No aggregator integration. For that, Olo, Cuboh, Otter, or Toast handle the publish-to-DoorDash-and-Uber-Eats workflow. No direct ordering. For that, pair Menujo with Toast Online Ordering, Square's online ordering, or a direct-ordering platform like Owner.com. For many ghost kitchens above 3 brands, the right stack is middleware (Olo or Cuboh for aggregator publishing) + a customer-facing menu (Menujo for direct) + a POS for kitchen integration (Toast or Square).
For broader hub navigation, see where your menu lives across distribution channels and platform comparisons. For other restaurant-type guides, see QSR, food trucks, and cafés.
Related Reading
Practical guides for setting up your menu and getting the most out of QR menus:
- What is a digital menu?: definitions, the four main types, and how QR menus actually work for customers.
- How to create a digital menu: a step-by-step setup walkthrough with photos, dietary tags, and table-tent printing.
- Best digital menu platforms 2026: seven platforms compared (Menujo, MenuTiger, Toast, GloriaFood, FineDine, Square, Menubly).
- Restaurant menu printing costs: the yearly cost math on print menus and where digital wins.
- Menu design that drives orders: DoorDash photo data, decoy pricing, item placement, and dietary tags.
Frequently Asked Questions
What is the best digital menu platform for a ghost kitchen?
Depends on your scale. For 1-3 virtual brands with simple operations, Menujo (Free for one brand menu, or Pro at $7/month for up to 10 brand menus in one account) for the direct customer-facing menu plus aggregator-native menu management on each platform. For 4+ brands or higher complexity, middleware like Olo, Cuboh, or Otter (Otter lists plans from $79 to $278/month; Olo does not publish pricing) that publishes a single source-of-truth menu to all aggregators automatically. For full POS + ordering + kitchen integration, Toast or Square for Restaurants paired with Olo for aggregator publishing.
How do I keep menus in sync across DoorDash, Uber Eats, and Grubhub?
Two paths: (1) manual updates on each aggregator's dashboard, which works for 1-3 brands but becomes operationally expensive above that, (2) menu-management middleware like Olo, Cuboh, or Otter that publishes a single canonical menu to all aggregators automatically. Middleware has a monthly cost (Otter lists plans from $79 to $278/month; Olo does not publish pricing) but cuts repetitive manual updates and prevents the cross-channel pricing drift that erodes customer trust.
What's the typical commission rate on ghost kitchen aggregators?
Headline US delivery rates: DoorDash 15-30%, Uber Eats 20-30% (15% in select cities), Grubhub 5-20% marketing commission plus delivery fees starting at 10%. All-in effective rates including delivery subsidy, payment processing, and promotional discounting run higher than the headline rate. Negotiated enterprise rates can be lower for high-volume operators with annual commitments; independent ghost-kitchen operators rarely qualify for those rates.
How do I build a direct channel from aggregator volume?
Three patterns: (1) bag-insert promotion offering 15% off the next direct order, (2) SMS/email loyalty signup at the direct ordering touchpoint with periodic promos, (3) speed-advantage messaging if your direct channel is faster than aggregator. Conversion rates are low, but each converted order is far more profitable. Track aggregator-to-direct conversion with a distinct discount code on each aggregator's insert.
Can I run multiple virtual brands from one POS?
Often, yes. Many restaurant POS systems (Toast, Square for Restaurants, Lightspeed, Clover) offer multiple revenue centers or multiple menus, allowing virtual brands to run from one kitchen with kitchen tickets attributed to the right brand. Confirm the setup with your provider. The complexity is in the customer-facing menu side: each brand needs its own customer-facing menu and aggregator listings, even though the kitchen is one operation.
What's the difference between a ghost kitchen and a virtual brand?
A ghost kitchen is a delivery-only physical operation with no dine-in space. A virtual brand is a customer-facing brand identity that can be operated from a ghost kitchen, a regular restaurant, or a shared kitchen. One ghost kitchen can run 5 virtual brands; one regular restaurant can also run 1 virtual brand alongside its physical brand.
Should I price the same on direct and aggregators?
Many operators raise aggregator menu prices to absorb the commission, leaving direct prices at the canonical level. This is widely-accepted industry practice and customers expect aggregator menus to be slightly more expensive. The trade-off: it cuts into volume on aggregators if your prices end up too far above local competitors. Test the elasticity carefully; the right markup depends on your local competitive set.
How often should I update ghost kitchen menus?
Daily for out-of-stock toggling (the moment an item runs out across all channels). Weekly for pricing review (commodity costs, competitive positioning, aggregator commission changes). Monthly for menu structural changes (new items, removing dead items, photography refreshes). The faster you can update across all channels, the less revenue you lose to stale menus.
How do I handle allergen disclosure across multiple aggregators?
Each aggregator has its own allergen-tagging system. Maintain consistency: the same item should have the same allergen tags on every channel. Middleware platforms (Olo, Cuboh, Otter) sync menus across channels, but confirm whether allergen tags are included; manual operations need a checklist to verify. For corporate-catering channels, allergen disclosure depth is typically higher than aggregator standards, so budget more time for ezCater listings.
Can I use Menujo for ghost kitchen aggregator menus?
Not directly. Menujo doesn't publish to DoorDash, Uber Eats, or Grubhub. Aggregator menus live in those platforms' own systems and are managed there or via middleware (Olo, Cuboh, Otter). Menujo's role for ghost kitchens is the direct-channel customer-facing menu: the URL on bag inserts, SMS/email links, and your direct website that converts aggregator customers to direct.
What's the unit economics target for direct vs aggregator?
Aggregator: once commission, delivery subsidy, payment processing, and promotions stack, a sizable share of each order's gross revenue goes to the aggregator. Direct (your own website): you mainly pay payment processing, so most of the order lands in operations. Per-order margin on direct can be much higher than on aggregator orders. The strategic target for a healthy ghost kitchen: grow direct-channel revenue steadily as a share of total revenue. Even a small direct channel transforms total margin.
Should I run multiple virtual brands or one strong one?
Depends on demand and operational capacity. Multiple brands let you test concepts cheaply (one shared kitchen, multiple branded fronts) and capture different customer segments (a burger brand and a salad brand from the same kitchen). One strong brand concentrates marketing investment and earns deeper customer loyalty. A small portfolio of brands is a common middle ground: enough variety to capture multiple segments without diluting brand quality.
