Getting Started

Getting Started

Enable the module, create the database tables, and grant the right people access — then confirm everything is wired up before you build your first Bill of Materials.

Prerequisites

Production does not create raw materials or products itself — it consumes and produces Inventory items. Before you can build a BOM or run a Manufacturing Order:

• The Inventory module data must exist. Production reads and writes the core inventory tables (items, item_variants, units, item_inventories) through the shared application models — so it works whether or not the Inventory UI is enabled, but the items themselves must be created first.
• Every finished good and every raw material / component must exist as an Item with a default variant — stock is tracked against items.default_variant_id. An item with no variant cannot receive stock movements.
• You need the relevant units of measure (pcs, kg, L, …) set up so quantities read sensibly.

Activation — four steps

1. Create the tables

   Run the module migrations from the project root. They are idempotent and reversible, and are tracked in their own migrations_production table.

   php erpat migrate:modules
   # (or) php erpat migrate:latest

2. Turn the module on

   Go to Settings → Manage Modules and enable Production (this sets module_production = 1). To also use the advanced shop-floor tools, enable Manufacturing as well (module_manufacturing = 1) — it is a sub-feature that sits beneath the Production master switch.

3. Grant permissions (for non-admins)

   In Roles, assign the Production / Manufacturing permissions to the roles that need them. Administrators see everything by default. See the Permissions & Roles matrix for the full list.

4. Verify the routes

   Confirm the controllers resolved through the HMVC layer:

   php erpat route:list   # look for production/... entries

   You should now see a Production group in the left sidebar (and a Manufacturing group if you enabled it).

Two toggles, two sidebar groups

Who does what

Typical roles that map onto the module's permissions:

These are conventions, not hard-coded roles — grant the matching permission keys to whichever roles fit your organisation.

Next steps