Skip to main content

Unconfirm Manufacturing Order

POST 
/api/manufacturing/manufacturing-orders/:manufacturingOrder/unconfirm

Take the order back to Draft so its planned quantity and warehouses can be edited again: releases its component inventory allocations and discards the BOM-derived component lines, output lines, and operations, which are rebuilt at the current planned quantity on the next Confirm. Operations added manually after confirmation are kept. Allowed from Confirmed, and from In Progress while nothing has been produced — starting an order records only a status and a start time, so it is reversible until production is recorded. An In Progress order also has its start time cleared. Refused with 422 once work has been recorded against the order. The response carries a code: production_recorded (production has been recorded, or completed quantity is above zero), components_consumed (component consumption or scrap has been recorded), operations_worked (a BOM-derived operation has been started, completed, or costed), or status (the order is in a status with no path back to Draft, e.g. Partially Completed or Completed). Auth: requires Bearer token. Path param: manufacturingOrder = manufacturing order id. Body: reason (optional, string, max 1000) recorded on the order's event log together with the status the order came back from.

Required scope: manufacturing:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Request​

Responses​

OK

Response Headers
    Content-Type