The question this page answers
What defaults do the engines plan on for this workspace: how stock is synced, the service level, how often replenishment runs, the default lead time, the calendar every buy plan follows, the guardrails on the envelope, the tolerances the verdicts read, and the containers a fill plan counts in?
What you see
The head is the page's name; like every Settings page it carries no sentence. For anyone who is not an admin the head carries "Only an admin changes these." and every control stays closed.
The sets, in order:
Stock and replenishment: Stock sync (a Shopify source may sync stock; any other reads "Only a Shopify source syncs stock; deliveries are tracked in Tightly"), Target service level (a percentage, with the line "Stock protection target used to calculate safety stock; a higher target holds more buffer."; one option is marked recommended), Replenishment frequency, Default lead time (whole days, one or more) and Order-to-dispatch time (whole days, zero or more; "Days from receiving an account order to dispatch. Transit time is added separately.").
Calendar: Fiscal year, one row for one window, the month it opens in a select and the month it closes beside it. On Tightly Pro it also holds Spring-summer length in months and Season windows, the two windows this shape pre-fills a new season with. On Pro, open to buy counts 4-5-4 retail weeks, and a fiscal year's first week starts on the Sunday on or before the first of the month it opens in.
Replenishment policies is one row, not a card: how many policies run your restocking and how many are inactive, with the door Open to the Policies page. With only Tightly's own it reads Tightly’s own policy only.
Guardrails (Pro): Mode (Soft warning or Hard stop), Tolerance, Ceiling (No ceiling when off), Warn within, Surplus. Tolerances (Pro): Sign-off tolerance and Drift tolerance, the two the weekly verdicts read.
Containers, on every plan: one row per container type with Container, Internal cube, Payload, Pallet positions (Not on file where nobody gave one), Usable and Default, on the basis line CBM · kg; then Carrying cost rate and Hold back below. On Pro the carrying cost rate reads Finance's declared figure with the words Declared on Finance beside it, or Not declared, with the door Finance, because one economic fact is declared once; off Pro it is typed here.
Off Pro the page carries the replenishment defaults, the fiscal year, the Policies row and the containers; the season rows, guardrails and tolerances are Pro's and are absent rather than shown empty.
What to do
Change a row and save it. A percentage row refuses what cannot be true: "That is not a number.", "Cannot be negative.", "Keep it at or under {max}%." A days row reads "Whole days, one or more." or "Whole days, zero or more." On Pro, when the calendar's shape moves, a table appears under it, Plan, Fiscal year, Spring-summer, Fall-winter, Effect, with one row per buy plan and the words Same shape, Keeps its own shape or Shape not reported; the table is absent at rest.
Add container type opens the drawer New container type: Start from (a preset, or Custom), Name, Internal cube, Payload, Pallet positions (optional), Usable (a percentage between 1 and 100, 85 by default) and the switch Use as default container. Delete on a container carries its consequence first: "Deleting drops this container from every lane and supplier that names it, and each falls back a rung.", then Delete this container type.
When it is empty or failed
A failed read prints "The planning defaults did not load." in place of the page, with Try again; a set that did not load reads Did not load in its rows. No container types prints "No container types yet." A write the server refused without a sentence prints "The change was not saved and no reason came back."