📋 Branch SOP
How branch-facing instructions are auto-generated from product builds, with portion tools and 2nd shelf life.
6 sections · ~5 min read
Branch SOP ≠ Factory SOP
Factory SOP = how to make the product. Branch SOP = how the branch team stores, portions, finishes and serves it. Both exist for the same recipe but read totally differently.
Open Branch SOP
Listed by recipe + branch (each branded brand has its own colour code).
📍 In RecipeHub: Branch SOP page
Auto-generated from Builds
Branch SOPs aren't created directly — they're generated from a Product Build. The build defines portion size, components, packaging, and the SOP picks those up automatically. Delete a build → its branch SOPs are deleted too, no orphans.
📍 In RecipeHub: Branch SOP page
Open Product Builds to see the source
A build = "this recipe in this format for this brand." E.g. Bechamel 200g cup for Telliano. The build owns batch sizes, components, packaging spec.
📍 In RecipeHub: Product Builds page
Role-specific notes
FACTORY: You spec batches here. Branch SOP follows.
NPD: You define the build during recipe finalisation.
2nd shelf life
When a component is opened or assembled at the branch, a second shelf life kicks in (e.g. cooked product opened: 48h chilled). The Branch SOP shows both the master shelf life from QA and the 2nd-life rule.
📍 In RecipeHub: Branch SOP page
Portioning tools auto-fill
Ladles, scoops, drizzles — each has a base weight stored in the system. When you spec portion size, the tool quantity calculates automatically. No mental math at the line.
📍 In RecipeHub: Branch SOP page