Placeholders — Manufacturing & Laboratory¶

Bizwiz Guide · Appendix to Books 1–7 · Review instrument Two modules ship in the codebase and render in the side navigation, but are feature-flagged OFF by default and were not confirmed live for any current distributor. This page records that they exist, sketches their scope from the navigation, and explains why they get a stub and not a chapter — so a reviewer knows they were seen, not missed.

Everywhere else in this guide, "documented" means traced nav → routes → controllers → models → migrations. These two are deliberately not traced to that depth. They are real, non-trivial modules (each is arguably a small ERP of its own), but until a tenant is confirmed running them, a full deep-dive would document capability, not live behaviour — the same trap the rest of the guide works to avoid. When a distributor switches one on, promote its stub to a full 8-section chapter.

Why these are stubs, not chapters¶

Both are gated the same way the rest of the ERP gates optional behaviour (Book 7 Ch27): an administration_settings feature flag, read into $adminSettings and checked in the nav Blade in addition to the usual permission string. If the flag is off, the whole menu tree never renders and none of the routes are reachable from the UI.

Module	Feature flag	Permission root	Route prefix	Nav file
Manufacturing & Production	`ACTIVATE_MANUFACTURING_MODULE`	`manufacturing-and-production-management___view`	`manufacturing-and-production.*`	`manufacturing_and_production.blade.php`
Laboratory	`ACTIVATE_LABORATORY_MODULE`	`lab-management-module___view` (or `role_id == config('app.allowed_role')`)	`lab.*`	`laboratory.blade.php`

Note the Laboratory gate uses config('app.allowed_role') rather than the hard-coded role_id == 1 superuser check seen elsewhere — a small variant worth confirming against the live config.

Manufacturing & Production (stub)¶

A discrete/light-manufacturing module — plausibly the destination for distributors that assemble, blend, or pack rather than only buy-and-sell. From the nav tree, its intended scope is:

Production Orders (production-order) — the work-order header: what to make, how much.
Visual Scheduler (visual-scheduler → manufacturing-and-production.planning) — a planning/Gantt surface over production orders.
Shop Floor — the execution layer: Material Requisitions (pull raw stock), Production Releases, WIP Returns, Production Scrap Records, Machine Data Reports. This is where a production order consumes inventory and yields output — i.e. the seam into Book 2 (stock moves) and, on any costing/variance posting, Book 4 (GL).
Quality Control — quality.*: sampling plans, incidents, inspection profiles, assignments, inspections, samples, sample collection, inspection overrides. An in-process QC loop distinct from the Laboratory module below.

Likely seams (to confirm when activated): Material Requisitions → inventory depletion (wa_stock_moves, Book 2); finished-goods yield → item master (Book 2); any WIP/COGS/variance posting → wa_gl_trans (Book 4); approvals on production releases → the approval-queue + approver-limits surface (Book 7). If manufacturing is live, the procure-to-make-to-sell chain would extend the Book 3 → Book 2 → Book 1 spine with a make stage in the middle.

Status: built, flag-gated, deep dive deferred.

Laboratory (stub)¶

A standalone testing-laboratory module with a strong tyre-testing / ISO-17025 flavour — which lines up with the tyre sub-ERP already documented in Book 5 Ch20 (a laboratory that inspects, tests, and certifies tyres/retreads fits that distributor profile). From the nav tree, its intended scope is:

Customers (lab receivables) — lab-customer-accounts, lab-customer-statements, lab-customer-cheques: the lab runs its own debtor sub-ledger (accounts, statements, cheques), apparently separate from the Book 1 wa_debtor_trans customer ledger. Whether lab receivables ever consolidate into the main GL is an open seam.
Sample & Testing (the operational flow) — lab-samples (registration) → lab-test-requests (work orders) → lab-pre-inspection → lab-test-execution → lab-results-review (approval) → lab-post-inspection → lab-tyre-storage, with lab-pre-inspection-config. A clean maker-checker testing pipeline with an approval gate at results review.
Methods, assets & calibration — lab-test-methods, lab-iso-test-methods, lab-tyres, lab-tyre-categories, lab-rims, lab-instruments, lab-equipment-job-cards, lab-equipment-work-orders, lab-calibrations.
Audit & compliance — lab-audit-checklist, lab-audits, lab-findings, lab-documents, lab-test-reports, lab-audit-reports, lab-trend-compliance. This is the ISO-quality-system half: document control, internal audits, findings, and trend/compliance reporting.

Likely seams (to confirm when activated): its own receivables ledger (does it post to Book 4 GL, or stay standalone?); tyre/rim catalogues vs the Book 5 tyre sub-ERP (tyre_*) — same physical objects, possibly two registries; approvals (results review, audits) → the Book 7 approval + notification surface.

Status: built, flag-gated, deep dive deferred.

For the reviewer¶

If either module is live for a distributor you care about, say so — that promotes its stub to a full chapter (same 8-section template as the other 30) and pulls its seams into the cross-module handoff map. Until then, they are recorded here as known and deliberately deferred, so the guide's "30 chapters" is understood as 30 chapters of confirmed-relevant modules, not "everything in the repo."