Every field, badge, and state across the schedule list, a scheduled day's panel, the daily-order dialog, and schedule picking — and where each figure comes from.
On this page
Was this helpful?
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
Two rooms are cooking the same Tuesday, one recipe on the board carries peanut and
the rest don't, and the warehouse still holds only half of what the day needs.
Before the floor starts you settle two things: the sequence each room runs its
recipes in, and what stock has to leave the warehouse to feed them. The
Schedule list
holds the first, and Schedule picking the second. This page names every field,
badge, and state on both, and where each number is figured.
Kitchen+
The schedule list
The list gathers every
across all your plans into one place, oldest date first. It's a
read-and-sequence screen: you don't create days here — plans do that — you set the
order the floor runs them in.
The controls above the list narrow it:
From and To — a date range that bounds which scheduled days show.
Filter by department — one team, or All departments.
Search by recipe — matches days whose recipe name contains what you type.
Clear all — appears once any filter is active and returns the list to its
default.
When nothing matches, the list reads No scheduled days found. A per-page
control and pagination sit beneath it once there are more days than one page holds.
Two scheduled days for the Production room. Each row carries its running-order badge, the date and department, and the quantity scheduled against the quantity produced once the floor logs output.
What each row shows
Reading a row left to right, then down:
The recipe name, then its Order badge (see Order states),
then up to two allergen chips for the allergens that recipe carries, with a
+N chip when it carries more.
A second line: the date, the department that runs it, the quantity
scheduled in the recipe's yield unit, and — once the floor has logged output —
the quantity produced beside it. A day with nothing produced yet shows only
the scheduled figure.
Order states
Two things on the row report where a day's sequence stands — a badge, and the
control on the right:
Order not set — the day hasn't been sequenced. The badge reads orange, and
the control is a Set order button, also orange, so an unsequenced day stands
out.
Order 1, Order 2, … — the day is sequenced, and the badge carries its
position. The control reads Update order.
Locked — the day is in the past. It shows no order button and no Order not
set badge; a past day's sequence can't be changed.
Selecting a row's recipe name — not its order button — opens the day panel, a
read-only breakdown of that one recipe on that one date. Its header names the
recipe, over a subtitle that links to the plan behind the day (like PP-00010)
and names the department.
A row of tiles carries the day's numbers:
Scheduled — the quantity set to make, in the recipe's yield unit.
Yield — the recipe's full-batch yield, in the same unit.
Desired batch — the batch size the plan asked for, shown only when the plan
set one.
Original yield — the recipe's yield before the plan scaled it, shown only
when the day carries one.
Batches — how the scheduled quantity breaks into batches: 3 full, or 2 full + 40% partial when it doesn't divide evenly.
Demand breakdown
Below the tiles, Demand breakdown traces what the day draws down — a tree with
one node per ingredient the recipe needs, and their ingredients beneath them. Each
node carries a Product or Sub-recipe badge, the ingredient's name and
department, and three figures: its original quantity in the recipe's own unit,
the pounds it needs per batch, and the pounds it needs in total for the
day. A recipe with no ingredients reads This recipe has no ingredients yet., and
the whole section is hidden from roles that can't view a recipe's tree.
The daily-order dialog
Set order or Update order opens the daily-order dialog for one department
on one date — a day that runs recipes in two rooms is sequenced separately in each.
Its header reads Set the daily order over the department and date. On a past
date it carries no fields, only the notice Cannot set order for past dates.
The dialog holds:
A cleaning tally — either No allergen cleanings needed. or a count like
2 allergen cleanings in this order. It counts every
the current sequence forces,
and it recounts live as you reorder.
A Suggest order button — arranges the day for the fewest cleanings, which
usually runs the recipes carrying the most allergens last.
One position field per recipe — type where a recipe should run, 1 first,
and the list resequences as you go. Each row shows the recipe's name and its
allergen chips, and an Allergen cleaning badge appears beneath a recipe whose
allergens the next one drops.
Save — writes the sequence back to the list. It shows only for roles that can
set the daily order.
The demo data carries no allergens
Every recipe seeded for a fresh company runs allergen-free, so the tally reads
No allergen cleanings needed. and no cleaning badges appear. Give a recipe's
products their allergens and the tally, the badges, and Suggest order start
earning their keep.
Schedule picking
Schedule picking
turns a scheduled day into picking orders that pull each recipe's ingredients out
of the warehouse. It reads a Schedule date, scales every recipe that day's
plans have scheduled by its quantity, totals the pounds each product needs, and
lays the products out grouped by the department that runs them. The date defaults
to tomorrow; a date with nothing scheduled reads No product demand for this
schedule date.
Two more controls sit above the table:
Locations — which warehouse locations count toward the figures. All
locations counts every stock location for the numbers on screen, but you must
tick at least one specific location before Bettr will create an order, so it
knows where to pull from.
Expected picking date — the day you want the stock pulled by. It defaults to
today and can't be earlier.
The demand columns
Each row is one product, and the columns walk from what the day needs to the cases
you'll pull:
Demand (LB) — the pounds this product's scheduled recipes need for the day.
On hand (kitchen) — the pounds already in the kitchen as
.
Need (LB) — demand minus the kitchen's on-hand. It reads zero when the
kitchen already covers the day.
On hand (warehouse) — the warehouse stock you can pull, counted in cases,
with the pounds per case beside it.
Minimum quantity to pick — the whole cases it takes to cover the remaining
need after the kitchen's stock.
In picking order — cases for this product already committed to a pending or
approved picking, so you don't double-order.
To request — the minimum to pick, less what's already on a picking. This
seeds the last column.
Quantity to pick — the editable field, in cases. Your edits hold even when
you change the location filter.
When a product sits out
A product can show demand and still stay out of the order, flagged with an orange
note:
Missing units per case or case weight — excluded. Bettr sizes cases from the
product's case weight, so a product without one can't be sized. Fill it in on the
product first.
Department has no customer linked — excluded. A schedule picking is created
against the customer behind each department, so a department with no customer has
nowhere to send it.
A short warehouse makes a partial picking
Ask for more cases than the selected locations hold and Bettr doesn't refuse — it
lists each product's requested, available, and missing cases and offers Create
partial picking. Confirm, and it pulls every case it can find and leaves the
rest short, telling you the order came up partial so you know to top it up.
Access to the two screens is set per role. The schedule list is gated under
Production in the permission catalog:
View the production schedule — open the schedule list, a day's panel, and the
daily-order dialog. Without it, the screens redirect to an unauthorized notice.
Set the daily production order — save a sequence in the daily-order dialog.
Without it, the dialog shows the order but offers no Save.
Schedule picking is gated under Warehouse, because the orders it creates are
warehouse work:
View pickings — open Schedule picking.
Create pickings and Approve pickings — turn the day's demand into picking
orders. Create picking order stays off without both, and the screen says so.