Skip to content

The production lifecycle

Manufacturing has two layers of state. The database stores open or done; the UI shows a derived production state so operators can see whether open work is not started, blocked, or in progress.

2 stored statuses4 visible stateshistory-preserving

Select a state to see what it allows and where the order can move next.

Visible stateStored statusWhat makes it appearWhat it means
Not startedopenNo start, no picks, no completed batches.Planned work is still fully editable.
Work in progressopenstartedAt, pick progress, or completed batch activity exists.Execution has started and planning is locked.
BlockedopenisBlocked is true.Work is paused but still open.
DonedoneThe order was completed.Production history is terminal and read-only.

Completing a discrete order usually performs the whole execution write in one action: pick remaining materials, calculate actual material cost, absorb operation cost, create the finished output lot, record output-to-input consumption, close the order, clear its queue rank, and rerank open work.

Batch orders close batch rows. Partially complete records a chosen number of whole batches and leaves the order open. Done closes all remaining planned batch output.

FromAllowedBlocked
Not startedStart, block, complete, delete, edit plan.-
Work in progressBlock, complete, record output.Return to not started, edit planning fields.
BlockedUnblock, complete if execution is otherwise valid.Treat blocked as a separate stored status.
DoneView history.Edit, delete, start, block, complete again.

Open orders can be soft-deleted while no production output has been recorded. Deleting releases reversible picked stock and open demand. Once output exists, the order is preserved as production history and delete is blocked.