🧱 Product Builds
What a build is, the approval workflow from Draft to Active, in-window editing, and flagging.
8 sections · ~6 min read
What a Product Build is
A build is "this recipe, in this format, for this brand", for example MAD Korean Pizza, Large, Maestro. It owns the assembly BOM: each component, its code, tool, quantity, weight and cost, plus the build cost, selling price, COGS %, and bake settings. Branch SOPs are generated from builds, so the build is the source.
📍 In RecipeHub: Product Builds page
The lifecycle: Draft → In Progress → Active
A build now has one clear status (it replaced the old separate status and launch toggles):
Draft: being put together by R&D.
In Progress: submitted, under review.
Active: approved and live.
Inactive: retired (can be reactivated). A build never goes back to Draft once Active. The stat band at the top of the list counts each stage, and the header shows one status badge.
📍 In RecipeHub: Product Builds page
Submit for Review (the trigger)
When the build is ready, R&D opens it and clicks 📤 Submit for Review. The build moves to In Progress, and an email goes to Caterina and Finance (Mohd) so both know it is ready to check. This is the only step that emails.
📍 In RecipeHub: Product Builds → open a build
Role-specific notes
NPD: this is your hand-off button. Build it in Draft, then Submit for Review.
FINANCE: you get the email, review the costing, and flag anything that needs a fix.
Approve, or send back
On an In Progress build, Caterina (Admin) only can ✓ Approve (the build becomes Active) or ↩ Send back to Draft for rework. Everyone else viewing an In Progress build sees "Awaiting Caterina's approval".
📍 In RecipeHub: Product Builds → open a build
Role-specific notes
ADMIN: Approve and Send back are yours alone. Approving makes the build live (Active).
Active and Inactive
Once a build is Active, Admin can ✕ Set Inactive to retire it, and ✓ Reactivate to bring it back. Inactive builds stay in the catalogue but are marked clearly and drop out of the active count.
📍 In RecipeHub: Product Builds → open a build
Edit the components in the window
On the Components card, click ✏️ Edit to edit the whole BOM in place: Type, Item, Code, Tool, Qty, Weight and Cost, with + Add Component and a row delete. Pick an Item from the search to link its recipe or ingredient code; cost then auto-derives from the link and weight, or type a Cost to override. Hit ✓ Done to save. The "Edit Build" button at the top is still there for the name, brand, bake settings, and so on.
📍 In RecipeHub: Product Builds → open a build → Components card
Role-specific notes
NPD / QA: you can edit the BOM in the window.
FINANCE / VIEWER: read-only on the BOM; Finance reviews and flags instead.
Flag a build
The 🚩 Flag chip sits on the navy header of a build (next to the status). Click it to raise a note (tag a teammate with @name to email them). Flags stack, each shows who raised it and when, and any reviewer can clear them. Same idea as recipe flags.
📍 In RecipeHub: Product Builds → open a build → 🚩 on the banner
Role-specific notes
FINANCE: this is how you query a build without editing it.
Cost and the "Cost incomplete" strip
Build cost is the sum of its components. When a component has no derivable price (its linked sub-recipe or ingredient is not costed yet), the build shows a yellow Cost incomplete strip listing what is missing, and the total reads low. It clears by itself once those items are priced, or you can type a manual Cost override per line in the Components editor.
📍 In RecipeHub: Product Builds → open a build