Source Formulas

Grain — one row per formula at one unit spec

SF-0044 and SF-0051 are the same chemistry at 90 and 60 capsules and they are two records, deliberately (MR‑059). Weight and dimensions only exist once a count exists, and a purchase line is written for a count, not for a powder. That pair is also why the create screen’s formula field searches rather than drops down — two records can differ only by count.

The catalog product inherits its unit spec from here and never types one.

Every physical fact is owned here

Weight, dimensions, bottle, bottle size, label size, cost and the ingredient list are true of what arrives on the pallet, not of any label printed over it. They are read-only everywhere else — and filling a blank from over there is not allowed either, because the rule is ownership rather than “don’t overwrite”. The trip is avoided instead of the rule bent: the formula’s editor opens as a drawer over whatever screen you are on.

Cost is QuickBooks’ and read-only; we never write a corrected cost back.

Stock is shown and gates nothing

SF-0031 sits at 0 on hand and is still perfectly listable — the goods are on a truck. Status is awaiting stock → stocked → discontinued; the first transition is derived from QuickBooks recording a receipt, the last is a person’s act, because QuickBooks never learns a supplier dropped a line. SF-0012 is discontinued with 604 units still on hand, which is exactly why the two are separate ideas.

Needs a decision (D13)

Derived, never typed: a formula needs one when a fact it alone owns is blank and something downstream waits on it — unit weight (the physical product and the label rating) or the ingredient list (content generation and the claims gate). The same filter sits on the catalog products list; the bell is the combined cross-entity view. No new nav item — this settles MR‑004’s open question as no.

The Gaps saved view is the same answer as a column layout: SF, house name, the reason, and the two fields it points at.

Open questions