What the kitchen bakes, day by day. Stock cover and the gap to par sit right next to the boxes you type in — no flipping tabs, and the week rolls forward on its own.
Cap/day in the grid is the most pieces the moulds allow in one day. A ◆ means that limit comes from a physical mould count rather than a general capacity figure.
Until the portal has a shared database, this is how a plan moves between people: copy the code, paste it into the other person's portal. It carries the whole week for the team and channel you're on.
Stock on hand at Havi against the weekly forecast — days of cover, gap to par, and how much to produce.
What the kitchen actually made, against what was planned. The plan is already here, so the chefs only enter the real numbers and the variance works itself out.
Boxes packed, pieces wasted and why, what went into the in-house freezer and what shipped to Havi — the two packing files in one place, reconciling against each other.
The confirmation CFF has been waiting for — built straight from the production plan, so nobody rebuilds it in Excel.
What the warehouse sends up. Pieces from the plan become dough kilos, dough kilos become ingredients, ingredients become bags and boxes.
Every dough and what goes in it, as a percentage of the batch. Edit a recipe here and the procurement order recalculates from it — no formulas to repair.
Drag the file straight from the email onto this page — anywhere. Excel files are read as they are; there's no need to open them, and no saving as CSV.
I'll work out what it is and load it into the right place.