Manage multiple virtual brands from a single ghost-kitchen physical location without one brand's rush accidentally pausing or throttling a sibling brand

Steps

1. Register each virtual brand as its own store/location entity on every aggregator (DoorDash, Uber Eats, etc.) even though they share one physical address and kitchen line — aggregators generally require distinct store ids per brand storefront
2. Track kitchen capacity (ticket count, prep-time load) at the physical-location level internally, even though each brand's aggregator-facing store status is managed independently
3. When physical capacity is overwhelmed, decide deliberately whether to pause/throttle all sibling virtual brands together or selectively, since aggregators have no native concept of shared kitchen capacity across brands
4. Keep menu and pricing data per virtual brand in your source-of-truth system, but route all resulting orders through a shared kitchen queue keyed by physical location, not by brand
5. Reconcile payout and commission reporting per brand storefront even though costs (rent, labor) are shared at the physical-kitchen level, since aggregator financial reports are scoped to the store id, not the kitchen