PrepStation

For commissary kitchens

Produce once Allocate to every satellite

Central production, transfer orders with a paper trail, and location inventory, so commissary output becomes on-hand stock at every kitchen that needs it. One canonical recipe and one trail is how you open the next satellite without adding chaos.

No credit card · Multi-location demo · Cancel anytime

Running shared recipes without a hub kitchen? Multi-unit restaurants.

Central Kitchen · Today

3 satellites · transfer queue

4 open TOs

TO202607-0003

Commissary → LA Kitchen

Shipped

4 items · $312.80

TO202607-0004

Commissary → OC Kitchen

Approved

6 items · $488.20

TO202607-0005

Commissary → SD Kitchen

Draft

3 items · $156.40

Hub allocation $957.40

Approve · ship · receive

Transfer queue mirrors the production card list with route, status, item count, and estimated value.

Why PrepStation for commissary kitchens

01

Open the next site without a new binder

Region → city → kitchen hierarchy under one account. Recipes shared from commissary; inventory stays local per site.

02

No mystery shortages on the dock

Approve, ship, and receive stock between locations with printable documents—no mystery shortages on the dock.

03

Cook to confirmed numbers

The hub’s production pool fills from sales, meal plans, and menus. Cook against that pool, then ship to satellites with approve → ship → receive.

No credit card for the live demo

Transfer orders with printable docs

Cancel anytime

Central production without a shared record Spreadsheets and group chats do not count as allocation.

Satellites guess what’s on the truck. The hub rekeys demand. Receiving argues about what left the dock. That isn’t multi-site ops—it’s finger-pointing with pallets.

Take the commissary seriously

Growth across sites breaks on rekeyed demand and missing pallets. You need one recipe library, a demand pool the hub cooks against, and transfer orders that prove what shipped and what landed.

Commissary transfers

Accountability on every pallet

Transfer stock between locations with an approve → ship → receive workflow. Incoming and outgoing filters show each kitchen the correct direction of work, with printable transfer documents for the run.

  • Commissary produces; satellites receive
  • Printable paperwork for the truck
  • Vendor or commissary sourcing in purchase mode

Deep dive on commissary transfers.

TO202607-0003

Commissary Kitchen → LA Kitchen

Shipped
  • Submit

    Done

    Sent for manager approval · 4 lines

  • Approve

    Done

    Approved by Maya Chen

  • Ship

    Current

    Source depleted · documents printed

  • Receive

    Next

    Destination confirms quantities

Next action: Receive Items
Transfer lifecycle follows the guarded production states from submit through destination receiving.

Production Hub · Thursday, July 18

Customer packing and pooled batch production

Live demand

Orders

14

Pack cards

12

Batch items

4

Packing · by customer

2

Thu

Jul 18

12:30

Delivery

Riverside Holdings

SO202607-0042

To pack

Packing notes

Loading dock handoff

2 items to pack

  • Herb chicken lunch

    22 gluten-free
    ×86
  • Chocolate tart

    ×86

Thu

Jul 18

7:00

Delivery

Northside HQ

SO202607-1184

Packing

Packing notes

Floor 14 cart

2 items to pack

  • Breakfast boxes

    ×24
  • Fruit cups

    ×24
Production Hub keeps customer packing separate from pooled batch production.

Production & inventory

Cook against your demand pool, then ship it

The hub’s production pool collects its sales orders, meal plans, menus, and manual demand, so the prep sheet reflects confirmed numbers. Ship what satellites need with approve → ship → receive transfers. Each kitchen keeps its own on-hand, storage locations, and par levels—so hub production doesn’t invent a shared warehouse count.

See meal & production planning and inventory & receiving.

Recipe library

One canonical card, every kitchen

Share recipes across locations so the commissary owns the formula. Live cost rolls through prep recipes; satellites inherit yields and allergens without rebuilding the card.

Recipe Library

Central Kitchen · shared with 3 locations

3 recipes

Herb Roasted Chicken

Entrées

Shared from Central Kitchen

50 servings 9 ingredients

Cost Summary

$124.00

$2.48 / serving

Allergens roll up from ingredients.

Chicken Stock

Stocks & Sauces

Prep Recipe

Internally Shared

64 servings 7 ingredients

Cost Summary

$18.20

$2.28 / gal

Cost flows into every parent recipe.

Tomato Basil Soup

Soups

Shared from Central Kitchen

50 servings 11 ingredients

Cost Summary

$61.50

$1.23 / serving

Scale controls preserve yield and rules.

Recipe library cards mirror production sharing badges, recipe metadata, and location-aware cost summaries.

Open the demo and walk a transfer from hub to satellite.

Commissary kitchen team packing bulk trays for satellite kitchens

Same stack—different center of gravity.

You are here

Commissary kitchens

  • Central production + allocation
  • Transfer orders with docs
  • Hub demand from sales & plans

Also a fit

Multi-unit restaurants

  • Shared recipes across regions
  • Local inventory and pricing control
  • Shared modifiers for every site

Go to multi-unit restaurants →

Roux for commissary kitchens

Run the commissary by asking.

Roux reads what's owed on the production day and adds batches, drafts transfers to your locations and moves them through shipping and receiving, and takes purchase orders from draft to received. Ask him for waste or transfer reports across every site.

Try asking Roux

  • “What do we still owe for Thursday?”
  • “Send 20 qt of tikka sauce to Westside”
  • “Order 4 cases of romaine from Valley Produce”
  • “Waste cost by location for October”

Roux proposes, you approve. Nothing saves until you do, and he only works in the apps you have turned on.

Meet Roux, the AI sous chef

Roux Commissary
Send Westside 20 quarts of tikka sauce and 10 pans of short ribs tomorrow.

AI Tool

Using Transfers (drafting)

  • Both in stock at the commissary
  • Destination: Westside
  • Ships tomorrow

Roux

Draft transfer to Westside: 20 qt tikka sauce and 10 pans short ribs, shipping tomorrow.

Changes waiting for your approval

  • Create transfer to Westside, 2 lines Leave out
Waiting Approved, 1 change saved
Submit it for approval What else is Westside low on?
Type your message...

Questions commissary teams ask

Is PrepStation built for commissary production?

Yes. Run multiple kitchens under one account, share recipes from the commissary, keep inventory local per site, and move stock with approve → ship → receive transfer orders.

How do commissary transfers work?

Create a transfer order with lines from commissary stock, approve it, ship with printable transfer documents, and receive at the satellite so on-hand updates with a trail.

Can satellites pull from commissary instead of outside vendors?

Yes. In purchase mode, staff can order from external vendors or pull commissary transfer-eligible items in one mobile workflow when stock should come from the hub.

Do recipes stay consistent across satellite kitchens?

Yes. Share recipes across locations so commissary and multi-unit ops use one canonical recipe library while inventory stays scoped to each kitchen.

Can production demand feed the commissary?

Yes, for the commissary’s own demand. Sales orders, meal plans, menus, and manual demand land in the commissary kitchen’s production pool, so it cooks against confirmed numbers instead of a spreadsheet. Satellites then get that stock through approve → ship → receive transfer orders.

Do I need a credit card for the live demo?

No. The live demo does not require a credit card. Explore transfers and multi-location ops, then cancel anytime.

PrepStation

Move product across every kitchen you run

Spin up the demo and walk demand → transfer → receive at the satellite.

No credit card required · Cancel anytime