Every field, badge, and state on the production plans list, a plan's detail, and the production needs queue — plan types, statuses, quantities, and how "left to plan" is figured.
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.
A retail buyer moves next week's sauce order up, and before you commit the floor
you need two answers: what do you actually have to make, and how much of it is
already spoken for. Two screens hold those answers. A
is one line on the running list under
Production plans,
and every open order still waiting to become one sits in the production needs
queue next to it. This page names every field on both, and where each value comes
from. Kitchen+
The production plans list
The list holds every plan in the company you're working in, newest first, one per
row. The controls above it:
Search by plan number — filters the list to plans whose number matches what
you type, like PP-00003.
Filter by type — All types, Sales order, or Recipe.
Filter by status — All statuses, Pending, In production,
Finished, or Cancelled.
Clear all — appears once any search or filter is active, and returns the
list to its default.
New sits in the top corner for roles that can create plans. It doesn't open a
blank form — it takes you to Production needs, because a plan always starts
from an open order or a recipe, never from an empty page. When nothing matches,
the list reads No production plans found.
What each row shows
Reading a row left to right, then down:
The plan number — PP- followed by a five-digit count that Bettr assigns per
company when the plan is created — then a type badge and a status badge.
A second line: the plan's subject, then its numbers. For a recipe plan the
subject is the recipe name; for a sales-order plan it's the product code
and name. After it comes the total quantity (40 planned), the delivered
share for a sales-order plan (0% delivered), and the schedule state — either a
count like 3 scheduled days or Not scheduled.
Plan type
A plan's type is fixed when it's created and shown as a badge everywhere the plan
appears:
Sales order — the plan is built from one or more open order lines, so it
carries what those customers are waiting on and tracks delivery against it.
Recipe — the plan is made straight from a recipe, with no order behind it —
a buffer batch, a stock build, a base sauce made ahead of the runs that use it.
Plan status
A plan's status is its live state. Bettr figures the first three from what's
happened to the plan's schedule — you don't set them as a field — and the last
from whether someone has cancelled the plan:
Pending — nothing on the plan has started. A plan with no schedule yet is
Pending, and so is one whose scheduled days haven't been pulled into a run.
In production — at least one of the plan's scheduled days has been started
on the floor.
Finished — every scheduled day on the plan has been finished in its run.
Cancelled — someone took the plan out of play with the Cancel action.
Cancelled outranks the rest: a cancelled plan reads Cancelled whatever its
schedule shows, until it's reinstated.
Cancelled is not deleted
Cancelling and deleting both take a plan off the floor, but they aren't the
same. A deleted plan drops from the list entirely. A cancelled plan stays on
the list, keeps its schedule on record, and reads Cancelled — but it stops
competing for work: its scheduled days drop off the production schedule so no
one runs them, the cases it had reserved on its order lines free up for other
plans, and it no longer counts toward demand on the master calendar.
Reinstating it puts all of that back.
A plan's detail
Selecting a plan opens its detail page. The header repeats the number, the
type badge, and the status badge, over the plan's subject — the recipe
name, or the product code and name. Schedule, Edit, Cancel, and
Delete sit in the corner for the roles that can change or remove plans. On a
cancelled plan, Schedule, Edit, and Cancel give way to a single
Reinstate action, and a banner reads This plan is cancelled. Reinstate it
to schedule or edit it again.
The field tiles
A row of tiles carries the plan's numbers:
Total quantity — everything the plan is set to make: its extra quantity plus
the quantities scheduled against its order lines. A recipe plan has no order
lines, so its total is just the extra quantity.
Extra quantity — a buffer added on top of the orders, for overage, samples,
or a little safety stock.
Delivered — for a sales-order plan, the share of the ordered units already
shipped, rounded to a percent. It doesn't appear on a recipe plan, which has no
order to deliver against.
Department — the department that runs the plan's recipe, shown when the plan
resolves to a single one.
A sales-order plan's field tiles: total quantity is the extra quantity plus what's scheduled against the order, and Delivered tracks the ordered cases already shipped.
Order lines
A sales-order plan lists the order lines it's filling under Order lines. Each
row links to its sales order and shows the product, then three running numbers for
that line: how many cases are scheduled on this plan, how many have been
delivered, and how many are still remaining on the order.
Schedule
The Schedule section is the plan's dated production: one row per scheduled day,
with the date, the recipe, and the quantity in the recipe's yield unit. Add
schedule opens the scheduling screen when nothing is scheduled yet; Edit
schedule opens it once days exist. Until you remove the schedule, the plan's
quantities are locked — a banner reads Remove the schedule before updating this
plan, and the edit form says the same. Building the schedule is its own task; see
Schedule a plan into runs.
Cancelling and reinstating a plan
Cancel takes a plan out of play without removing it. You confirm against the
plan's number, and from then on the plan reads Cancelled: it stays on the
list and keeps its schedule days on record, but stops competing for work — its
scheduled days leave the production schedule so no one can turn them into a run,
the cases it reserved on its order lines are free for other plans again, and it
drops out of master-calendar demand. While a plan is cancelled you can't schedule
or edit it.
Reinstate undoes that. The plan returns to whatever status its schedule
derives — Pending, In production, or Finished — and counts toward capacity and
demand again. A plan can go back and forth as circumstances change, and each
cancellation and each reinstatement stays on record.
Notes
A free-text Notes field, shown only when it's filled in — a line for whoever
picks the plan up next.
Editing and deleting keep the record
Editing a plan writes a new revision rather than overwriting the last; deleting
one records a deletion and drops it from the list, schedule and all. As
everywhere in Bettr, nothing is erased — the plan and every earlier revision stay
on record.
Production needs
Production needs is
the queue of open order lines still waiting to be planned. A line shows here only
when all of the following hold, so the queue is exactly the work you can act on:
Its sales order is approved — a draft order doesn't appear until it's
approved.
It still has cases remaining to deliver.
Its expected ship date is on or after the Ships from date, which starts
a week back so nothing already due slips off the list.
Its product has a
registered. An order for a product with no final recipe can't be
planned, so it stays off the queue.
What each row shows
A checkbox to pick the line, the sales order number, and a badge: In
plan with the plan's number, linking to it, when the line is already on a plan,
or Not planned when it isn't.
A second line: the product code and name, the customer, the ship
date, the cases still remaining on the order, and the cases left to
plan.
Remaining and left to plan are different numbers, and the gap is the point
of the queue. Remaining is what's still owed on the order. Left to plan nets out
what you've already committed: it's the remaining cases minus everything already
scheduled for that line across your plans. A line 18 cases short with 4 already on
a plan shows 18 remaining and 14 left to plan.
This line is already on plan PP-00001, so its badge links there and 'left to plan' nets the cases already committed out of the 12 still remaining on the order.
Filtering and sorting
Above the queue: Ships from and to dates to bound the ship window, a
product code search, an order number search, an All lines / Not yet
planned filter to hide lines already on a plan, and a Newest first / Oldest
first sort by when the order came in. Clear all resets them.
Selecting lines
Select all ticks every line with cases left to plan — but only within a single
product. Tick lines for one product and the rest disable; try to select all across
two products and Bettr asks you to filter to a single product first. That's
because a plan built from order lines is for one product, made by one final recipe.
Turning needs into a plan
The bar at the bottom of the queue is where planning starts. With order lines
ticked, Create production plan opens a dialog to set the cases to schedule for
each line, an extra quantity, and notes. With nothing ticked, Plan from a
recipe opens a dialog to pick a recipe and an extra quantity instead — the way to
build stock with no order behind it. Both land you on the new plan's detail. The
step-by-step is in
Create a production plan and review needs.
Who can view and change production planning
Access is set per role, under Production in the permission catalog:
View production plans — open the plans list and the needs queue and read any
plan. Without it, both pages redirect to an unauthorized notice.
Create production plans — show New and let you build a plan from needs or
from a recipe.
Edit production plans — let you revise a plan's lines, quantities, notes, and
schedule, and cancel or reinstate a plan.