FAQ & Troubleshooting

Stock is tracked against each item's default variant (items.default_variant_id). To produce the finished good, the module writes a positive stock movement against that default variant. If the finished good item has no default variant set in Inventory, there is nowhere to add the produced stock, so completion is refused.

What to do: Open the item in Inventory and give it a default variant, then return and click Mark as Done. See Getting Started → Prerequisites. Note that components without a default variant behave differently — they are silently skipped (no stock deducted), only the finished good blocks completion.

In Base Production, inventory only moves when a Manufacturing Order reaches Done. Creating, confirming, or starting an order has no stock effect:

• Draft — nothing committed; no stock impact.
• Confirmed — the BOM components are snapshotted (planned) onto the order, but no stock moves.
• In Progress — records the actual start time only; no stock moves.
• Done — this is the only step that posts stock: each component is consumed (flow -) and the finished good is produced (flow +).

What to do: Confirm the order actually reached Done (not just In Progress). If it is stuck in Confirmed or In Progress, click Mark as Done. See the Manufacturing Orders lifecycle.

You tried a lifecycle action that isn't valid from the order's current status — for example confirming an order that is no longer Draft, starting one that isn't Confirmed, or completing one that is already Done or Cancelled.

What to do: Reload the order to see its real status, then use only the buttons offered for that state. The allowed moves are:

Two independent things must be true for a group to appear in the left sidebar: the module toggle must be on, and your role must hold the permission for at least one item in the group.

The Finished Good and Component pickers on a Manufacturing Order are sourced from your core Inventory items — specifically active items of type product. The module reads Inventory even when the Inventory UI is off, but the item must already exist there.

What to do:

• Create the item in Inventory first (finished goods and every raw material/component).
• Make sure its status is active and its type is product.
• Give it a default variant so it can carry stock — required on the finished good, recommended on components (a component with no variant is skipped at completion).

See Getting Started → Prerequisites. In the Advanced Manufacturing requisition/issue forms, by contrast, Item Name is free text (not a catalog picker) — a different mechanism entirely.

No. Completion is irreversible. When an order reaches Done the module sets an internal stock_posted flag, records the produced quantity and actual end time, and marks each consumed component. Done is a terminal state.

• Trying to complete it again is refused — “This manufacturing order is already completed.” (mo_already_completed).
• You cannot cancel a Done order.
• Cancelling other (non-Done) states does not reverse any stock either.

What to do if you posted in error: make the correcting stock adjustment in the Inventory module. There is no in-app "un-complete" action.

The BOM snapshot at Confirm happens only once, and only if the order has zero component lines at that moment. If you manually added any component before confirming, the BOM is not snapshotted at all.

What to do: On the Components tab, click Add Component to add lines manually, or delete your manual lines and re-confirm on a Draft order that has no lines so the BOM copies over. Component lines stay editable through Draft, Confirmed, and In Progress. See Manufacturing Orders.

At Confirm, each component's Required Quantity is computed as:

Required Qty = BOM component qty × (Quantity to Produce ÷ BOM output quantity)

If the BOM's output quantity is 0 or missing, it is treated as 1, which inflates every component to the full per-unit quantity multiplied by your whole planned quantity.

What to do: Open the BOM and set its output quantity correctly (e.g. a recipe that yields 10 units should have output quantity 10). See Bill of Materials.

At completion, components whose item has no default variant (for example a service line) are silently skipped — no stock is deducted and their Consumed Quantity stays 0. Every stocked component is consumed for exactly its Required Quantity (its Consumed is then set equal to Required).

What to do: If a component should have been consumed, give its item a default variant in Inventory before completing. See Manufacturing Orders.

Editing scope depends on status:

• The header Edit button appears only while the order is Draft or Confirmed.
• Component lines remain editable through In Progress as well.
• Done and Cancelled orders cannot be edited at all.
• Delete requires the production_delete permission; deleting an order soft-deletes it and its component lines, with no undo in the UI.

What to do: If you only need to fix a component quantity on an In Progress order, use the Components tab (still editable) rather than the header Edit button. If you lack the delete option entirely, ask an admin to grant production_delete. See Permissions & Roles.

Manufacturing Order references (MO-#####) derive from MAX(id)+1, so deleting orders can leave gaps. The reference is fixed at creation and never renumbered.

Advanced-area document numbers (Work Orders, BOMs, ECOs, QC Plans, Inspections, NCRs, CAPAs, Requisitions, Issues) use the prefixes set in Mfg Settings. Their next number is derived from the highest existing (non-deleted) number for that prefix, so:

• Soft-deleting the latest record can cause a number to be reused.
• Changing a prefix starts a fresh sequence at -000001; existing rows keep their old numbers and are not renumbered.

This is by design; gaps and the occasional reuse are expected.

No — that is how Material Requisitions & Issues works today. Recording a Material Issue does not:

• deduct or update any Inventory stock,
• increase the requisition line's Qty Issued (it stays 0, so Remaining doesn't change), or
• advance the requisition's status.

Only Draft → Approved is automated (via the Approve link). The other statuses — Submitted, Issued, Partial, Completed, Cancelled — are valid values with badges and filters but have no built-in trigger.

What to do: Track fulfilment manually per your local procedure, and deduct real stock separately in the Inventory module.

In Quality Control, a measurement's Result is auto-computed from the parameter's Min/Max spec (a value below Min or above Max is FAIL, otherwise PASS). But the inspection's own Status and Overall Result are independent free-choice dropdowns — nothing rolls the per-measurement results up automatically.

What to do: After recording measurements, edit the inspection and set its final Status and Overall Result to match reality (e.g. Failed / Fail). Then raise an NCR and, if needed, a CAPA from it.

The measurement form accepts only a numeric Measured Value (it is required and numeric); there is no input for a text value. So Visual, Attribute, and Functional parameters must still be given a numeric value to save a measurement.

What to do: Adopt a local numeric convention (for example 1 = pass, 0 = fail) and, if you want it auto-graded, set the parameter's Min/Max around your "good" value. Record the plain-language detail in the measurement Notes.

Correct — QC parameters cannot be edited. There is no edit action, only Add and Delete, and adding one reloads the whole page.

What to do: To change a parameter, delete it and re-add it with the corrected target/min/max/UOM.

The CAPA for NCR screen's New CAPA modal does not pre-fill the Related NCR. If you leave that dropdown unset, the CAPA is created without a link and won't show in that NCR's filtered list.

What to do: In the New CAPA modal, manually select the correct NCR in Related NCR before saving. See Quality Control → CAPA.

The dashboard's Expiring Documents panel uses a fixed 30-day window. The Expiry Warning (Days) value in Mfg Settings is stored, but the dashboard panel does not read it — changing the setting will not change what the panel shows.

What to do: Treat the dashboard panel as a fixed 30-day look-ahead. This is a known behaviour, not a fault.

No. The module helps you gather compliance evidence and stay audit-ready (quality records, inspections, NCR/CAPA, compliance-document expiry tracking), but it does not by itself grant ISO certification, GMP certification, FDA product approval, or product registration. Those are decisions made by regulators and accredited bodies and require your own SOPs, qualified staff, and validated processes.

A granted API scope is not enough on its own. Even with production:read or manufacturing:read, the endpoint returns 404 "module_unavailable" if the matching module toggle (module_production / module_manufacturing) is off for the tenant. The 404 deliberately hides the feature's existence rather than returning a 403.

What to do: Ask an admin to confirm the module toggle is enabled, then retry. The APIs are strictly read-only and GET-only — any non-GET verb returns 405. See Read-only API.