Planning
See what is on hand, what becomes ready and what is owed each ship week, with a suggested quantity to make, and start a plan-a-day from it.
Planning
The Planning page answers one question each week: how many of each recipe should we start, and when? For every recipe (and, for an any-strain recipe, every strain) it shows what you have, what becomes ready and what is owed in each of the next few ship weeks, and a suggested quantity to make, rounded up to whole racks. It is read-only: nothing on it is saved, and nothing is made until you create a day on Plan a NOC day.
What the page shows
Each row is a line: a recipe, such as “Lion’s Mane 10 lb”, and the strain its lots and orders carry. For each line the page works through the same steps a planner does on paper:
- On hand. Every unit in every open lot of the line, whatever stage it is in, including units already allocated to orders and units on hold. Under the number you see how many are ready now and how many are held.
- Ready by week. When each unit becomes shippable. A lot inoculated yesterday with a 21-day lead time is counted in the week 21 days from its NOC date, not today.
- Owed by week. What every open order line (planned or packed) still owes, by its ship week: the line’s quantity, less any units already shipped on it (an order with part of it shipped and the rest on backorder owes only the rest; units allocated but not shipped yet are still owed), with where it came from (entered by hand, Shopify, CSV, the portal, QuickBooks, or a recurring order that has already been created). An order whose ship week has passed is counted in this week and marked late.
- Balance. What you have plus what becomes ready, minus what is owed, week by week, running on. Allocated units count on both sides: they are on hand and they are owed.
- Suggested. The worst balance from the first week a run started on the run day can be ready, plus your buffer, rounded up to whole racks. Weeks a run can’t reach in time are greyed.
A worked line: you have 360 units maturing into week 4 and 435 owed by then, so the balance in week 4 is -75. With a buffer of 30 the line needs 105, and with racks of 60 the suggestion is 120 (two racks, six lots of 20).
What Planning does not include yet
Planning counts lot stock and open orders. It does not yet count:
- Standing orders. Orders a standing order has already created are counted like any other open order, but its future orders are not.
- Unit-tracked blocks. Blocks tracked one by one carry no strain link Planning can read yet.
If your farm has either, the page says so in a plain sentence and shows no numbers: “This farm has standing orders. Planning does not include them yet.” or “This farm has unit-tracked blocks. Planning does not include them yet.” A plan built without them would hide stock or orders, so it shows none rather than a wrong one. You can turn Planning off again until both are supported.
Unit-tracked blocks made, or brought back from Discarded or Contaminated, in the last minute also stop the page, even before they show in lists elsewhere.
A standing order counts when it is on and has not ended. Planning checks every customer for one; a paused standing order, or one whose end date has passed, does not stop the page.
Who can do it
Managers and Owners. Workers and Viewers don’t see Planning.
Turn it on
Planning is an optional feature, off until your farm turns it on.
- Open Settings and go to the Optional features card, or Configuration > Lifecycle and the Planning card.
- Turn on Planning (on the Lifecycle card, check Turn on the Planning page and click Save Planning).
Planning then appears in the sidebar under Operations, and recipes show three new fields. Turn it off the same way; nothing is lost.
Set buffer, racks and lead time
Open a recipe and click Edit. With Planning on, the Planning section has three fields:
| Field | What it does |
|---|---|
| Buffer (units) | Units you keep beyond what is owed. Added before rounding. Blank is 0. |
| Rack size (units) | Suggestions round up to a multiple of this, for example 60 for one strain per rack. Blank means no rounding. |
| Lead time (days) | Days from NOC to ready to ship. Blank means Planning works it out from your stage schedules. |
Without a lead time and without stage schedules to work one out from, Planning names the recipe and asks you to set one. The box-by days on a recipe are not a lead time.
How the page reads your stages
Under the table, How this page reads your stages lists every stage of every item type in use and how Planning treats it:
- Growing: units here become ready in the ordinary course. A stage marked not usable that a Worker may leave is still growing.
- On hold until released: a stage marked not usable that only a Manager may leave. Units here are counted as held and never as supply until someone moves them on.
- Finished: an end stage.
A lot with an uncleared contamination flag is also held. Change stages in Configuration > Item types.
QC checks
For a lot sitting in a stage that asks QC questions, Planning looks up the lot’s latest check at that stage:
- Failed: the lot stays where it is (that is what a failed check does), and its units are counted as held, never as supply, until a check passes and the lot moves on. The On hand cell shows them as held.
- No check yet: the lot is growing like any other; it becomes ready by its lead time or stage schedule.
- Passed: the lot has moved on to its next stage, and is read there.
If there are too many lots at QC stages to look up in one go, the page says it couldn’t build the plan and offers Retry, rather than guess which ones failed.
When a recipe has no lead time, Planning uses your stage schedules, starting at the item type’s first stage (its entry stage): a lot is ready on the day it entered its current stage plus that stage’s least days and every later planned stage’s, up to the first stage with no planned length. A lot already at that stage is ready now. A lot in a stage before the entry stage is not counted as ready; Planning asks you to set a lead time on its recipe instead.
Read the table
- Under the header, As of says when the page read your stock and orders. A change made in the last few seconds can take a moment to show; refresh to confirm.
- Pick how many Weeks ahead to show (1 to 8; 4 by default) and the Run day (today by default). While the plan for a new choice loads, the page says Updating the plan, greys the table and hides Run this day, so you never run a day from the previous plan.
- Each week cell shows what becomes ready and what is owed (
+120 / −80), then the balance. A negative balance is red. Hover a week to see where the orders came from. - Ship weeks follow your farm’s pack week (Sunday or Monday) when you pack by the week; otherwise weeks start on Monday.
- A line marked Strain no longer made by this recipe is stock of a strain a recipe used to make. It is shown with its stock, matched only by orders for that strain, and never given a suggestion.
Run this day
Run this day opens Plan a NOC day with the chosen lines filled in: the run day as the NOC date, each recipe, the suggested units, the lot size and, for an any-strain recipe, the strain. Every line with a suggestion is chosen; uncheck a line in the Run column to leave it out.
A day holds at most 50 rows and 200 lots, and each link has a size limit, so a large suggestion (or one with long strain names) is split. The page then shows Run this day (3 runs) with one Open run 1 of 3 link per run. Open each one and create it; together they make exactly the units suggested.
Nothing is made by the link. You still preview the day and click Create on Plan a NOC day.
When it won’t answer and what to fix
| What you see | What it means and what to do |
|---|---|
| A product on an open order that doesn’t map to exactly one recipe | Pick the product’s recipe in Configuration > Fulfillment > Products. A product naming a strain its recipe doesn’t make, or naming no strain on an any-strain recipe, shows here too. |
| A recipe with no lead time and no stage schedule | Set its Lead time (days). |
| A lot with no NOC or inoculation date | Set the inoculation date on the lot. |
| A lot with no recorded stage entry | The lot moved before stage times were recorded. Set its stage again, or set its inoculation date and a recipe lead time. |
| A lot in a stage before the stages Planning times | The lot sits in a stage before your item type’s first stage (Bagged before Inoculated, say), where no planned length counts it down. Set a lead time on its recipe, so it is timed from its NOC date. |
| A stage with a maximum but no minimum | Set a minimum on that stage in Item types. |
| Strain text that matches more than one strain, or a link to a strain that is gone | Link the product or lot to one strain from your list. |
| A strain on order that no recipe makes now | Add an any-strain recipe, or map the product to a recipe that makes it. |
| ”Stock changed while the plan was being read.” | An order shipped or a lot changed while the page was reading. Click Retry. |
| ”Couldn’t build the plan in time. Retry in a moment.” | The farm’s lots, orders, customers or QC checks took too long to read, or there were too many to read in one go. Click Retry. |
Planning answers whole or not at all: while anything on this list is open, it shows the list, never a partial plan.
The page reads your stock and orders as one snapshot. If stock changes while it is reading (an order ships, say), it reads again; if it keeps changing, it says “Stock changed while the plan was being read. Try again in a moment.” Click Retry.