Dark kitchens with several brands: how to keep the standard without multiplying cost

Modern dark kitchens are not “a kitchen”. They are a production platform that serves several brands (4 to 8 is common) using the same legal entity, the same team, the same lines. Margins are tight, volume is high, mistakes are expensive.

What few people talk about: the shelf life standard turns into chaos when the system used by the kitchen does not separate by brand. This post is about how to fix that operationally.

The case described is a composite of real operations, anonymized. Numbers are representative of the segment.

The real problem: 5 brands, 1 kitchen, 1 app

Imagine a dark kitchen with:

• Brand A: gourmet burger
• Brand B: comfort food (stews, parmigiana)
• Brand C: vegan
• Brand D: Japanese (poke, sushi)
• Brand E: desserts

Five different menus. Inputs partially overlap: tomato, onion, lettuce, chicken. Others are exclusive: raw fish (D), plant proteins (C), confectioner’s sugar (E).

Without brand separation in the system:

• Labels come out in a single standard. Audit of one brand cannot filter.
• A marketplace recall (D asked for handling proof on yesterday’s salmon?) needs manual searching.
• Cost per brand is unclear. Partners argue.

With brand separation (internal multi-tenant model):

• Each brand has its own “virtual branch” in the app, same physical kitchen.
• Shelf life rules per brand (raw fish from D has a different shelf life from chicken from A).
• History filterable per brand for targeted audit.
• Permissions: A’s manager only sees A; owners see everything.

How to set this up in EtiquetaChef

EtiquetaChef already treats each branch as an independent logical tenant. For multi-brand dark kitchens, the standard is:

1. Create one tenant per dark kitchen (legal entity).
2. Create a branch per brand inside that tenant.
3. Each branch has its own product catalog + shelf life rules.
4. Staff who produce for multiple brands have access to multiple branches (broad-scope “cook” role); brand-specific managers have restricted scope.

There is no extra cost per brand — the Business plan supports 2 branches, Enterprise supports as many as you need (it scales to chains too).

The detail that changes the game: label with brand identity

Standard: each brand has its own label layout. Logo, color, product name in the brand’s nomenclature (not the kitchen’s internal name).

Why it matters:

• Packaging arrives at the customer with the right brand label.
• Marketplace receives a consistent operational photo.
• New staff get less confused.

EtiquetaChef allows layout per branch (in Settings → Label default) — each brand defines its own, staff pick at print time without thinking.

Typical result after 90 days

• 40% less rework on “which brand was this input for?” — questions that cost 2 min each, in volume, become hours/month.
• Marketplace audit resolved in minutes with PDF export filtered by brand + date.
• Input cost per brand visible for the first time (Brand C’s specific input no longer mixes with A’s).

When dark kitchens become franchises

Successful dark kitchens turn into multi-unit franchises. The model changes:

• 1 central tenant (franchisor operation).
• N franchisee tenants, with inherited rules but isolated data.
• Standardized label across all units for brand consistency.

That case is already on the EtiquetaChef Sprint 11 / Enterprise roadmap — reach out if it applies to you.

Summary

Multi-brand dark kitchens do not need more systems — they need the same system with the right separation. Standardized labels per brand, inside the same tenant, with role-filtered access. EtiquetaChef does this from the Business plan; you do not need an Enterprise package to start.