Phoenix3 Collective
Phoenix3's culinary operating system — across Restaura, Culinour, and Infuse. This is the 30,000-foot view. The goal is to orient you, not overwhelm you; your hands-on role training comes next.
Galley is our single source of truth. Every recipe, ingredient, cost, yield, and portion lives in one place — and everything we plan, buy, cook, and report pulls from it. Enter it once, correctly, and it stays consistent everywhere downstream.
Build recipes; cost rolls up automatically.
Cycles, plans, and dated events.
Pack sizes, costs, POs, and invoices.
Production sheets and allergen labels.
USDA nutrition and Top-9 allergens.
Counts, variance, Actual vs. Theoretical.
Five levels, each built from the one below it. A clean foundation is what makes accurate costs, menus, and labels possible at every level above. Bad data at the bottom corrupts everything on top.
POs · production · invoices · counts · labels · reporting
What we serve — Cycles, Plans, Events
What we cook — yield, procedure, sub-recipes; cost rolls up
The foundation — unit, allergens, USDA nutrition
What we buy — pack size, cost, SKU
The library — yields, procedures, allergens.
Cycles, Plans, and Events.
Counts and on-hand by sub-location.
Production, purchasing, and variance.
What appears in Menus, Inventory, and Reports reflects the location you're assigned to.
New users begin read-only — scoped to their location and domain — until role training is confirmed.
Every ingredient and linked sub-recipe contributes — plate cost and full nutritionals come straight from the recipe.
Allergen and dietary data set on each ingredient appears automatically on every recipe that uses it.
Three layers carry a menu from a reusable structure down to a specific dated service. Each is a more specific instance of the one before it.
Repeating menu structures — the reusable template, published by culinary leadership.
A location's working version of a cycle for a given period.
A specific dated service. Production, purchasing, and reporting all originate here.
PO in Galley
Verify dock-side
Email invoice
Map line items
Costs & inventory update
System-of-record receiving; refreshes vendor costs in real time.
One full count per period-end; two-person rule for full counts & alcohol.
Sheets & labels from the event's recipes and yields.
Recipe-driven vs. counted usage. Big variance = a flag to route up.
Route to the RD on site first, then the Director of Nutrition. When in doubt — flag it, don't edit it.
Galley is our single source of truth for recipe and ingredient data. Enter it once, correctly, and it stays right everywhere downstream.
Space play / pause · ← → previous / next chapter · Captions follow the narration · click any chapter or script paragraph to jump