Ghost kitchens and virtual brands — what is regulated and what is not

Most coverage of ghost kitchens is about whether it is honest to sell wings under a name that exists only on an app. That is a real question and it is not this page.

This page is about what is actually regulated in Ohio, what is not, and where the exposure sits — which turns out not to be where operators look for it.

Brands are not licensed. Operations are.

Ohio licenses food service operations, and requires a separate license for each operation a person or government entity operates.¹

A brand is not an operation. One kitchen, one operator, four delivery-app names is generally one license — the brands are menu and marketing constructs running over shared equipment, not four facilities.

Two caveats worth stating plainly:

This is answered from practice, not from a published rule. We could find no Ohio provision addressing virtual brands specifically. Health districts are working it out case by case, which means the answer you get is your licensor’s answer. Ask, and get it in writing. It costs one email and it is the difference between a settled question and an argument at inspection.

Separate operators are still separate licenses. If you rent a line in a shared ghost-kitchen facility, you are your own operation and you hold your own license — the same as a food hall stall. That situation has its own guide: opening inside someone else’s building.

The real exposure: your license was issued against a menu

Here is the part nobody mentions, and it follows directly from how Ohio licenses.

Your facility layout and equipment specifications had to state the type of food service operation proposed and the foods to be prepared and served.² And the licensor may place restrictions or conditions on a license limiting the types of food that may be prepared or served, based on your equipment or facilities — with those limitations posted on the back of the license.²

So the question is not “may I run a second brand?” It is “does my approved plan cover what that brand cooks?”

A pizzeria launching a wings brand has just added frying. A sandwich kitchen adding a poke brand has added raw fish handling. A concept adding sushi rice that is acidified for room-temperature holding has entered a special process requiring a HACCP plan — see sushi rice, fresh juice and game processing.

None of those are brand problems. They are equipment and process changes that your license may not cover, and the brand name is the thing that makes them invisible on your own premises.

Before launching a virtual brand, put its menu next to your approved plan. If it needs equipment you do not have, a process you did not describe, or a storage condition you did not draw, that is a conversation with your licensor before launch rather than after a complaint.

What is genuinely unregulated — for now

There is no Ohio disclosure requirement we could find, and no federal one. Nothing obliges a delivery listing to tell a customer which kitchen is cooking or what else that kitchen sells.

Platform behavior is inconsistent and voluntary: some label virtual brands, others do not. That is a business decision by the platform, not a legal protection for you.

Build as though disclosure is coming. Other states have started requiring delivery platforms to verify that listed businesses actually hold permits, and the rules are clearly moving toward more transparency rather than less. An operation whose answer to “where is this cooked?” is already comfortable has nothing to do when a rule arrives. One whose model depends on the customer not knowing has a business-model problem, not a compliance one.

And the food code still applies unchanged. Labeling, identity and presentation rules do not soften because the customer never sees the building.³ A name that misrepresents what the food is remains a problem regardless of how it is ordered.

Traceability is the food safety problem

If four brands share a cookline, shared coolers and one prep table, a complaint about one product is a complaint about your whole kitchen — and narrowing it down is genuinely hard.

This matters twice:

For an investigation. When a health district asks what a customer ate and when, “one of these four menus, made on the same line, from partly shared inventory” is a much worse answer than a single-concept kitchen gives.

For allergens. Four menus over one cookline multiplies the cross-contact paths, and the customer ordering from one brand has no way to know the other three exist. Your allergen procedure has to be built for the shared line, not per brand.

Practically: keep prep and cook records that identify the product, not just the brand. Give each brand’s high-risk items distinct handling and labeling. And make sure whoever answers a complaint can reconstruct what happened without needing to know which app it came through.

The things that do change with delivery-only

• No dining room changes the occupancy and restroom arithmetic, since both follow the space and its use. See occupancy limits and restrooms.
• Delivery-platform tax treatment in Ohio has its own answer, including whether the platform holds a waiver — covered in POS, Wi-Fi, phones and delivery apps.
• Your insurance almost certainly assumes a restaurant. Delivery-only operations, multiple brands and product handed to a third-party driver are not what a standard policy was written around. Ask the question specifically.

The short version

1. Brands are not licensed, operations are — one kitchen, one operator is generally one license.¹ Confirm with your licensor in writing, because there is no published rule.
2. Your license was issued against a stated menu and your equipment, and the licensor can restrict food types on the back of it.² Check a new brand’s menu against your approved plan.
3. No disclosure requirement exists in Ohio today. Build as though one is coming.
4. Shared lines make traceability hard — keep records that identify the product, and build allergen procedure for the line rather than the brand.
5. Tell your insurer what you are actually doing.

Ohio publishes nothing aimed specifically at this model, so more than usual here depends on your own licensor’s view. Ask them before you launch rather than after.⁴