Production owns recipes, sub-recipes, portions, yield, batch instructions, versioned cost and allergen publication. Stock remains the physical movement ledger, and EPOS remains the source of sales facts.
Recipe and batch workflows
/production offers Overview, Recipes, Batches and Allergens. Overview shows recipe/EPOS
mapping and production exceptions. Recipe detail retains version evidence; batches show recorded output and
posted consumption; allergens shows candidate decisions and the publication rule.
Create a recipe with name, reference, Site and yield/timing information. Create a version containing ingredient variants or a published sub-recipe, quantities, waste allowance and method. A parent pins the exact published sub-recipe version. Publish deliberately when complete; publishing freezes recipe content and the current ingredient/sub-recipe cost evidence. Later edits require a new version.
For a physical batch, select the exact recipe/version, batch reference, input and output Stock locations, required ingredient lots, actual output and production time. Recording atomically posts consumption and yield through Stock. Traced output creates its own attributable Production lot. A batch operator's operational projection does not grant the full private recipe-cost workspace.
Sales depletion and allergen review
Map an EPOS product to a recipe, stock source and effective start. Normalised sales can then produce replay-safe theoretical depletion using the recipe effective at the trading timestamp. Missing mappings or impossible unit conversion appear as Production exceptions. A corrected current sales fact reverses its exact earlier movements before replacement; it never edits the EPOS source or existing Stock movement.
Supplier allergen changes create candidates and propagate through affected current parent recipes. A separately authorised reviewer approves or rejects the candidate; rejection preserves the published declaration. Approval requires authority at every affected recipe Site. Linked Bookings dishes refresh their reviewed source/draft revision, while published menus and existing guest orders retain frozen declarations. Migrated recipes remain drafts and cannot bypass publication or allergen review.
Permissions and settings
production.view reads permitted recipes/work; production.manage authors recipes and mappings;
production.batch.record records operational batches; production.publish publishes recipe versions;
production.allergen.review decides allergen candidates. The current main web workspace admits view/manage/
publish/allergen-review roles; batch-only operation has a narrower native projection rather than implying full
web authoring access.
Settings uses production.settings.view and production.settings.manage. General, Recipes, Costing and
Allergens currently expose section shells. Published versions preserve historical content, but current
permission checks still apply to every source ingredient/sub-recipe and Site before disclosure.