I do not run a ghost kitchen and I do not run a catering company. I run a CFIA-licensed (Canadian Food Inspection Agency) mushroom production facility in Brantford, Ontario, with a private-label division that ships product under multiple client brand names from one kitchen. That is structurally identical to a ghost-kitchen operator running four virtual brands on Uber Eats and a caterer who plates the same chicken dish at a hospital cafeteria on Monday and a wedding on Saturday: one kitchen, multiple brands, off-premise consumption, no inspector in the room when the customer eats. The compliance pain rhymes. Here is what transfers.
01The mismatch
Why off-premise and multi-brand operators need different software than dine-in.
Most food-safety software was built for the single-concept, single-location restaurant — one menu, one dining room, one inspector, one set of records. The vertical I keep hearing from is not that operator. It is the cloud-kitchen tenant in a CloudKitchens unit running a burger brand, a wing brand, a salad brand, and a taco brand off one cookline. It is the wedding caterer who prepped 220 plated chicken dinners in a base kitchen at 2 PM, loaded a refrigerated van at 4, and served at 7 in a hotel ballroom 80 minutes away. Different operators, identical headache: the food and the records and the inspector are not in the same place at the same time.
The paper version of compliance was already strained at a dine-in restaurant. It breaks completely when the food leaves the building or when one kitchen has to defend four different brand promises to four different inspectors plus three delivery platforms plus the customer with a peanut allergy whose kid ordered from your dairy-free salad brand.
$99.3B
Global ghost-kitchen market in 2026, growing to $223.66B by 2033 at 12.3% CAGR (Coherent Market Insights). North America holds 31.7% of the global share — the largest region.
8,000
Virtual restaurants removed by Uber Eats in a single 2024 crackdown for menu duplication and deception. Underlying virtual-brand count is multiples larger.
9 allergens
FDA Food Code 2022 §3-602.12(C) now requires written disclosure of all nine major allergens — milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, and sesame (added January 2023 under the FASTER Act).
The job of food-safety software for this vertical is not to invent new rules. The FDA Food Code already tells you what to monitor. The job is to make the records survive multi-brand-one-kitchen and off-premise consumption — the two structural realities the Food Code was not written around.
02The license question
What a "cloud kitchen license" actually is (and the four other permits nobody told you about).
The primary thing every aspiring cloud-kitchen operator types into Google is some variation of "cloud kitchen license requirements." The honest answer: there is no single license called that in any state code I have read. A ghost kitchen, virtual kitchen, or cloud kitchen is regulated as a retail food establishment under your state's adoption of the FDA Food Code. The Food Code is a model — your state adopts the 2017 or 2022 edition with amendments, and your local health department enforces.
The actual stack a US cloud-kitchen tenant needs is closer to six or seven documents, not one license. Walk through it before you sign the commissary lease.
- 01
State retail food establishment permit
The one most operators mean by "the food license." Issued by your local health department after a pre-opening inspection. Typically $300 to $2,000 in fees. Lead time is one to three months at busy departments — plan around the wait, not against it.
- 02
Business license
City or county level. $50 to $500. Not optional, not food-specific, but the inspector and the platform onboarding team will both ask.
- 03
Certified Food Protection Manager (CFPM)
Required in most US states under FDA Food Code section 2-102.12. At least one manager-level employee on duty during all hours of operation must hold a current CFPM certificate from an ANSI-accredited program (ServSafe, Prometric, 360training, National Registry). Cost roughly $99 to $179, validity typically five years.
- 04
Food handler cards (some states)
California, Texas, Oregon, Illinois, New Mexico, and others require every food worker to hold a food handler card. $7 to $15 per worker, valid two to three years. Track expiry from day one — a lapsed card on inspection day is a citation.
- 05
Commissary letter of use
If you rent kitchen space (and most ghost-kitchen operators do), the host commissary signs a letter naming the facility, its license number, you the tenant, your hours of access, and the services included (water, waste, parking, storage, dishpit). The inspector asks for this first. Without it, you do not get your retail permit.
- 06
DBA (doing business as) per virtual brand
Every brand name that shows up on a delivery app needs a fictitious business name registered with your county or state. $20 to $100 each. If you run five virtual brands, that is five DBAs filed and renewed.
- 07
Sales tax permit + (sometimes) fire marshal + building department
State sales tax permit is usually free. If your commissary build-out involved any structural change, the fire marshal and building department want a sign-off too. Zero to $5,000 depending on scope.
Total upfront for a three-brand commissary tenant: roughly $1,500 to $5,000 in fees plus $300 to $1,500 a month in commissary rent, with a one-to-three-month lead time before you can legally cook a paid order. The CloudKitchens and Juris Law Group guides walk through state-by-state variation; the FDA's State Adoption Tracker tells you which Food Code edition your state is on, which dictates which specific rules apply.
On the FSSAI question (India)
About a third of US Google searches for "cloud kitchen license requirements" pull from operators consuming Indian startup content — Rebel Foods, Box8 — and surface FSSAI (Food Safety and Standards Authority of India) results. FSSAI is the Indian regulator and does not apply in the US or Canada. In India, cloud-kitchen licensing is tiered: Basic for under ₹12 lakh annual turnover (₹100 a year), State for under ₹20 crore (₹2,000 to ₹5,000 a year), Central for over ₹20 crore or multi-state operations (₹7,500 a year), all filed through the FoSCoS portal. Under 2026 reforms, FSSAI licenses now have perpetual validity. If you are operating in North America, ignore the FSSAI results and pull state retail-food-code guidance instead.
03The allergen rule
The 2022 Food Code rule that quietly rewrites every multi-brand operator's job.
The single most consequential change in the 2022 FDA Food Code for ghost-kitchen and catering operators is section 3-602.12(C). It added a new requirement: food establishments must notify consumers in writing of the presence of any of the nine major food allergens in unpackaged food. Written notification can be on the printed menu, a digital menu, a table tent, a deli case sign, a label, or "other effective written means." Only one method is required, but it has to be accurate.
The nine allergens, as of January 2023 under the FASTER Act:
- Milk
- Eggs
- Fish
- Crustacean shellfish
- Tree nuts
- Peanuts
- Wheat
- Soybeans
- Sesame (added 2023, the one most often missed on legacy menus and recipe cards)
Adoption is state-by-state. Some states (California, New Jersey, Massachusetts, and others) have adopted the 2022 edition; others are still on 2017. The trend line is clear and most states will include section 3-602.12(C) by 2027. The FDA Summary of Changes in the 2022 Food Code is the cleaner companion document if you need to brief a partner.
What 3-602.12(C) looks like for a five-brand kitchen on three platforms
Five brands × three platforms equals 15 menu surfaces. Each needs accurate per-brand allergen disclosure. The printed menu, the DoorDash listing, the Uber Eats listing, the Grubhub listing, the in-app kiosk, and the brand's own website all have to agree.
A recipe change cascades. Switching from cow milk to oat milk in your latte brand. Subbing a tahini dressing into a salad. Adding a peanut sauce as a special on your wing brand. Each change rewrites every disclosure that includes that item.
Cross-contact is its own dimension. Your dairy-free salad brand uses no dairy in the recipe. But it is plated on a board your burger brand just used for cheese. The salad is no longer truthfully dairy-free. The disclosure that says it is becomes the basis for a lawsuit.
Per-brand sync is not a feature — it is the job. A single spreadsheet that maps brand to menu item to ingredient to allergen, with cross-contact flags from shared equipment, is the minimum viable structure. Anything less and you are guessing.
The cross-contact dimension hooks into a second regulation. 21 CFR Part 117 Subpart C — the FSMA (Food Safety Modernization Act) preventive controls rule — requires hazard analysis to treat allergens as a chemical hazard. Most retail food establishments are exempt from Part 117 under section 117.5(g), but ghost kitchens that hit the manufacturing threshold (selling product wholesale, packaging for resale through a third party, or operating at a scale that triggers FDA food facility registration under FSMA section 415) come under it. The legal line between "retail" and "manufacturer" is fuzzier than the trade press makes it sound — when in doubt, ask your local health department in writing.
04Transport CCP
Off-premise transport is the catering CCP nobody trained you on.
Catering is older than ghost kitchens and shares the off-premise problem in a sharper form. The food leaves the kitchen at safe temperature. It rides in a van or a cambro or a hot box for 30 minutes or two hours. It holds at the event venue at some temperature for some duration. It gets served. Hours later, a guest who has no idea which kitchen made it gets sick, and you are on the phone with a public-health investigator who wants the time-temperature log.
If you cannot produce the log, the food might have been fine. You still fail.
The FDA Food Code 2022 time-temperature rules apply equally to a dine-in restaurant and a catering operation. The difference is that the dine-in restaurant has the food inside its own walls the whole time, and the caterer does not.
Hot hold
3-501.16
At or above 135°F (57°C) for hot TCS (Time/temperature Control for Safety) food — during transport, holding at the event, and service. The chafing dish, the hot box, the cambro insert have to be measured, not assumed. A pre-warmed hot box does not stay at 135 indefinitely once you load cold-ish food into it.
Cold hold
3-501.16
At or below 41°F (5°C) for cold TCS food. The refrigerated van or the gel-pack insulated tote needs a probe in the food, not on the wall. A 41°F van air temperature does not guarantee a 41°F potato salad in a six-quart pan that you loaded at 38°F twenty minutes ago.
Cooking
3-401.11
Poultry and stuffed items 165°F for 15 seconds. Ground meats 155°F for 17 seconds. Whole muscle meats, fish, eggs 145°F for 15 seconds. The cook target is the same whether you serve it in a dining room at 6:15 PM or at a wedding two counties away at 7:30 PM. The verification step is what changes — the caterer needs a probe-in-the-food reading at the prep kitchen AND a reading at the event before service.
The 4-hour rule
3-501.19
TCS food in the danger zone (41°F to 135°F) for more than 4 hours cumulative — including prep, transport, holding, and service — must be discarded. Cumulative is the word that catches people. The 90-minute drive plus the 2-hour cocktail hour plus the 45 minutes of service is 4 hours 15 minutes. Even if the chafing dish read 138°F the whole time, if it dipped below 135 at any point and the cumulative time-in-danger-zone crosses four hours, the food is regulatory garbage.
“
Catering inspection. They wanted my time-temperature log for the 90-minute transport to the event. I had nothing. The inspector said next time it is a closure.
”Paraphrased — IFSQN catering thread, 2024
The practical workflow that survives an inspection: departure temperature at the prep kitchen, arrival temperature at the event venue, periodic holding temperatures during service, end-of-service disposition (served, donated under cottage-food rules, discarded), all tied to a specific event reference. For events more than two hours from the kitchen, a continuous probe sensor logging every five minutes inside the cambro beats discrete checkpoints. The discrete-checkpoint approach can hide a 90-minute spike between the 4 PM reading and the 5:30 PM reading; a continuous log cannot.
Most catering inspection findings are not "the food was unsafe." They are "you could not show me the records." That is the entire failure mode for off-premise foodservice — records, not controls, are what fails.
05Multi-brand math
The multi-brand math nobody warned you about before you signed the CloudKitchens lease.
Here is what changes the day you turn on your second virtual brand from the same kitchen. The inspector still sees one kitchen, one cookline, one set of equipment. They write one citation, and it hits every brand the kitchen serves. A Salmonella outbreak attributed to "Wingz brand spicy chicken sandwich" gets investigated against your kitchen, which means every other brand at that address — your burger brand, your salad brand, your taco brand — has its delivery histories pulled into the same investigation. Reputational damage flows to all five.
The reverse is also true. If your kitchen's CFPM cert lapses, every brand loses its compliance basis simultaneously. If your commissary host fails their pest inspection, your retail permit at that address is at risk, and every brand that operates from that address is dark.
What multi-brand operation actually requires from your records:
- 01
Per-brand traceability — brand × order × ingredient lot × delivery
When the public-health investigator asks "which lot of chicken went into which brand's orders on which day, and to which customers," you need to answer in hours, not days. A general food-safety log that records "chicken cooked to 165 at 11:14 AM" is not enough. The data model needs brand as a first-class dimension alongside batch, lot, recipe, and delivery.
- 02
Per-brand allergen matrices, shared cookline aware
Each brand needs its own allergen disclosure. The matrix has to know that brand A's salad is plated on a board brand B used for cheese at 10:40 AM, and that this introduces dairy as a cross-contact allergen the brand A disclosure has to surface. Shared equipment is the variable that breaks single-brand allergen tools.
- 03
One HACCP plan, multiple brand applications
The Hazard Analysis and Critical Control Points plan covers the kitchen, not the brand. Cooking, cooling, hot/cold holding, allergen control, sanitation — these are kitchen-level controls. The brand-level layer maps each brand's menu items to those kitchen-level CCPs (Critical Control Points). One inspector ask: "show me which HACCP plan covers the Wingz brand." Your answer is "the kitchen plan; here are the menu items and the CCP touchpoints for each."
- 04
Delivery-platform compliance tracking
Not strictly food safety, but adjacent risk. DoorDash imposes a cap of 10 virtual brands per address (with exceptions) and quality requirements — minimum 4.0 lifetime rating, at least 3 orders per week, under 5% merchant cancellation, under 5% missing/incorrect, under 20% downtime over 90 days. A brand removed by the platform is revenue zeroed overnight. Tracking your standing against the platform requirements alongside your food-safety records is how you avoid surprise deactivation.
The Reef Technology cautionary tale is worth knowing. In 2022, Reef ran modular ghost kitchens across NYC under temporary food-truck permits while applying for long-term permits that did not exist as a clean category in the NYC code. NYC Department of Health and Mental Hygiene flagged Reef for "food from an unapproved source" and "inadequate personal cleanliness" and operating without an active permit after the temporary ones expired. Multiple NYC kitchens closed. The structural lesson: jurisdictions do not always have a clean permit category for the ghost-kitchen model, and operating in regulatory gray zones is a closure risk. Confirm your permit category in writing with your local health department before you go live. Do not infer it from what the host commissary's sales team told you.
06The commissary binder
The commissary binder the inspector wants on the counter when they walk in.
A commissary tenant runs into one specific inspection failure mode: the inspector wants documents that live with the host, documents that live with the tenant, and a clear understanding of which party is responsible for what. If you cannot produce that picture in a single binder, you spend the inspection digging through emails and texting the host's facilities manager.
The packet that survives a commissary inspection:
- 01
The signed commissary letter of use
Names the commissary, the host's license number, you the tenant, your hours of access, the services included (water, waste, parking, storage, dishpit), and the renewal date. Updated when any term changes.
- 02
The host's documents you have a copy of
Host's retail food permit. Host's most recent pest control report. Host's plumbing certification. Host's water test if applicable. These are not your records to maintain — they are the host's. But the inspector wants to see that you know they exist and where they are.
- 03
Your tenant-level records
Your retail food permit (the one that names the commissary as your base of operation). Your CFPM certificate. Your food handler card register. Your HACCP plan or food-safety plan. Your training log. Your hire-date Form 1-A (Conditional Employee / Food Employee Reporting Agreement) for every food worker — this is the FDA-recommended Big 6 illness reporting agreement under Food Code section 2-201.11.
- 04
Operational logs against your CCPs
Cooking, cooling, hot/cold holding, dishwasher final rinse, cleaning and sanitation, temperature checks on the equipment you actually use. For ghost-kitchen tenants, this is per shift. For caterers, this is per event with the transport CCP front and center.
- 05
Brand-level documents
DBA registrations for each virtual brand. Per-brand allergen matrices. Per-brand menu (printed and the screenshot from each delivery platform). Recipe cards keyed to the kitchen's CCP touchpoints.
- 06
The inspection-day export, ready to hand over
All of the above generated as a single PDF in the order the inspector typically works through it. The goal is to hand the tablet over and stop searching. The 90-minute archaeology dig through binders is what makes inspections feel adversarial; a clean export changes the dynamic.
From my own facility
My CFIA inspector at the Brantford facility audits against the Preventive Control Plan every six months. He pulls a random month of records, walks the production area with the PCP in hand, and asks "show me the entry that matches what I am looking at." The system has to make that retrieval fast or the inspection becomes a 90-minute archaeology dig through binders. That is the bar I built HACCPlan to. A US health-department inspector at a ghost kitchen works the same way — different chapter of the rulebook, identical reflex.
07Insurance gap
The insurance gap nobody mentions until the claim lands.
Standard restaurant Business Owner's Policies (BOPs) were written for dine-in operators with a dining room, table service, and a small delivery footprint. Ghost kitchens and caterers have a different risk shape: no slip-and-fall in a dining room, much higher products-completed-operations exposure (every revenue dollar is product going out the door), hired and non-owned auto (HNOA) exposure if 1099 drivers do any portion of delivery, additional-insured obligations to the commissary host and the delivery platforms.
A short version of what brokers who specialize in this vertical recommend (validate with your own broker, not this article):
- General liability $1M per occurrence / $2M aggregate, with the CG 21 51 fungi/bacteria carve-back endorsement to restore bacteria coverage that standard ISO forms exclude. The bacteria carve-back is the most-missed coverage in foodborne-illness defense.
- Product liability bundled with GL, not sublimited to a small amount.
- Food contamination standalone $250K to $500K, including notification, recall, and government-closure-induced loss costs.
- Commercial umbrella $5M follow-form.
- HNOA matched to your GL limits if any portion of delivery is on 1099 drivers or hired vehicles. Personal auto policies generally exclude commercial delivery.
- Cyber $500K to $1M for POS and platform data exposure.
- Equipment-of-others $25K to $100K for commissary tenants using host-owned equipment.
A single multi-claimant foodborne-illness outbreak can produce $300K to $1.5M-plus in stacked claims — well past what a standard restaurant BOP contemplates. The food contamination standalone is the policy operators routinely skip and later wish they had purchased.
08The build
What is inside the catering and ghost-kitchen build of HACCPlan.
None of this is generic restaurant software with a "ghost kitchen" label glued on. Each piece exists because the multi-brand, off-premise reality forced a different data model.
- 01
Brand as a first-class dimension
Every record — recipe, batch, log entry, allergen mapping, traceability event — is tagged with brand. The data model is brand × menu item × ingredient lot × order × delivery from the bottom up. A "show me everything for Wingz brand last Tuesday" query returns in seconds. This is the design choice that copied directly from my private-label division, where Nature Lion produces under several client brand names from one CFIA-licensed kitchen.
- 02
Per-brand allergen matrices with shared-equipment cross-contact flags
Add a recipe; the system maps each ingredient to the Big 9 (plus mustard and sulphites for Canadian operations under SFCR). The kitchen schedule layer knows which boards, utensils, fryers, and prep stations are shared across brands and which time slots overlap. Brand A's dairy-free salad gets flagged with a cross-contact dairy warning if brand B's quesadilla shared the prep board within the cleaning window. The disclosure exports for printed menu, digital menu, and delivery-platform allergen fields stay in sync.
- 03
Off-premise transport log with departure + arrival + cumulative time-in-danger-zone
The catering-event view bundles every CCP step from cook through service. Departure temp at the prep kitchen, in-transit reading (manual or continuous probe), arrival temp at the venue, holding temps during service, end-of-service disposition. The cumulative time-in-danger-zone counter sums prep, transport, holding, and service to flag the 4-hour rule under section 3-501.19 before service runs over.
- 04
Tablet-first floor UI for the cookline
Single-task screens with large tap targets sized for gloved hands. Auto-timestamp from the device clock. Voice entry for hands-busy moments. Photo capture for probe readings and allergen sub-recipes. Offline mode that holds entries locally when the commissary wifi drops at peak service and syncs when it comes back.
- 05
Bluetooth probe integration with per-brand cooking targets
The pocket thermometer reads the food; the reading goes straight into the cooking or cooling log against the brand and menu item you selected. The log knows the Food Code section 3-401.11 target for the dish and flags an under-temp before the order leaves the cookline. Supported probes (verify the current list before you commit) include the Thermapen Bluetooth and several Cooper-Atkins and Comark models.
- 06
Commissary compliance binder, generated on demand
The signed commissary letter of use, the host's permit and pest log copies, your retail food permit, your CFPM cert, your food handler card register, your HACCP plan, your last 30 days of CCP logs, your Form 1-A register, your per-brand allergen matrices, your DBA registrations. Exportable as a single PDF in the order the inspector typically works through it, or visible directly on the tablet you hand them.
- 07
Delivery-platform compliance tracker
DoorDash, Uber Eats, Grubhub, and Skip the Dishes standing tracked per brand alongside your food-safety records. Lifetime rating, missing/incorrect rate, cancellation rate, downtime, days-since-last-platform-message. Not strictly food safety; adjacent risk that ends your revenue if you ignore it.
- 08
Per-brand recall and traceability drill
A simulated recall pulls "brand X, lot Y, dates Z, delivered to customers via platform W" in under four hours — the window FDA expects for retail food. The drill output names the brands affected, the orders, and the customer contact list pulled from the platforms via the appropriate API or export. A real outbreak does not give you 48 hours to reconstruct the chain.
09Free templates
Where to start — the free logs that cover the most-cited gaps.
If you are not ready to commit to software, start with the logs that get cited most often. The catering operator's biggest gap is transport temperatures; the ghost-kitchen operator's biggest gap is the per-shift cleaning and cooking logs against a shared cookline. Each of these is a fillable PDF you can use on a tablet or print to a clipboard. No account, no email gate.
Free templates — catering and ghost-kitchen essentials
Free, ungated. Fillable on a tablet or computer in any PDF viewer. Print blank and fill on a clipboard. No account needed.
Most operators run on the free templates for a few weeks before deciding whether the software fits. That is the right order. Get the logs filled out reliably on paper first; the software is just the version that keeps the records integrated, time-stamped, brand-tagged, and inspector-ready.
10Getting started
What the first 30 days on HACCPlan looks like for a multi-brand operator.
A realistic onboarding for a three-brand commissary tenant or a small catering company runs roughly like this. The order matters; skipping the brand-and-recipe setup until week three turns the allergen matrix into a back-fill exercise.
- 01
Days 1 to 3 — set up the location and the brands
Create the commissary location, upload the signed commissary letter of use, add the CFPM and food handler card details, register every brand you operate (with DBA reference). Upload the existing HACCP plan or generate a starter from the built-in template. Sign Form 1-A for the manager-on-duty under section 2-201.11.
- 02
Days 4 to 10 — load the team and the menus
Add every food employee, assign roles, attach food handler cards with expiry dates, sign Form 1-A. Import each brand's menu — printed version, DoorDash listing, Uber Eats listing, Grubhub listing. Tag each menu item to the brand it belongs to.
- 03
Days 11 to 20 — go live on the CCP logs
Switch cooking, cooling, hot/cold holding, dishwasher, and cleaning logs from paper to the tablet. Pair Bluetooth probes if you use them. For catering operators, build the transport-CCP workflow against your next three booked events. Spend one shift shoulder-to-shoulder with the cookline making the entries until the rhythm clicks. Keep paper backups for the transition month.
- 04
Days 21 to 30 — build the per-brand allergen matrix
Map every menu item across every brand to the Big 9 (plus mustard and sulphites for Canadian operators). Flag cross-contact where brands share equipment within cleaning windows. Generate the printed-menu disclosure, the per-platform allergen fields, and the table-tent format in parallel so the next platform menu sync is clean.
By day 30 you should be running a practice inspection. Hand the tablet to the GM or your most senior chef and have them play the inspector. Ask for the commissary letter of use, the last 30 days of cooking logs filtered to the wing brand, the allergen disclosure for the dairy-free salad brand including cross-contact flags, and Form 1-A for the line cook who started two weeks ago. If they can produce all four in under three minutes, the system is working. If not, that is what month two cleans up.
Start with the HACCP plan generator
Generate a catering or ghost-kitchen HACCP plan free — then upgrade if you need the multi-brand platform
Free tier covers one HACCP plan, the Big 6 illness policy with Form 1-A, and the core temperature logs. Paid tiers add per-brand allergen matrices with cross-contact flags, the off-premise transport CCP workflow, the commissary compliance binder export, and per-brand traceability for outbreak defense.
Email required to save your HACCP plan. No credit card. No upgrade prompts during the free tier.
Footnotes
1.FDA Food Code 2022 — full PDF — fda.gov
2.FDA — Summary of Changes in the 2022 Food Code (sesame, written allergen disclosure §3-602.12(C)) — fda.gov
3.FDA Food Code — State Adoption Tracker — fda.gov
4.21 CFR Part 117 — FSMA preventive controls and hazard analysis — ecfr.gov
5.FSIS — Danger Zone (40°F to 140°F) — fsis.usda.gov
6.FDA Form 1-A — Conditional Employee / Food Employee Reporting Agreement — fda.gov
7.Coherent Market Insights — Ghost Kitchen Market — coherentmarketinsights.com
8.DoorDash — Virtual Brand Quality Requirements — help.doordash.com
9.Restaurant Business Online — Reef closes some NYC kitchens — restaurantbusinessonline.com
10.NBC News — Virtual restaurant boom (Uber Eats data) — nbcnews.com
Andrew Langevin·CFIA-licensed facility, Brantford ON· Published 2026-06-04· 13 min read· Wikidata Q139112497