Order Statuses
Inbound Orders
Section titled “Inbound Orders”| Status | Description | Editable | Can delete |
|---|---|---|---|
DRAFT |
Created, not yet started | Yes | Yes |
IN_PROGRESS |
Receiving has started | No | No |
COMPLETED |
Fully received | No | No |
Transitions: DRAFT → IN_PROGRESS (start receiving) → COMPLETED (complete)
Outbound Orders
Section titled “Outbound Orders”| Status | Description | Editable | Can delete |
|---|---|---|---|
DRAFT |
Created, stock not reserved | Yes | Yes |
RESERVED |
Stock allocated to staging bin | No | No |
COMPLETED |
Goods dispatched | No | No |
Transitions: DRAFT → RESERVED (reserve) → COMPLETED (complete)
Reason of request values: TRANSFER, DISPOSAL, RETURN, OTHER
Transfer Orders
Section titled “Transfer Orders”| Status | Description | Can delete |
|---|---|---|
DRAFT |
Defined but not executed | Yes |
COMPLETED |
Stock moved to destination bins | No |
Transitions: DRAFT → COMPLETED (complete; immediate, with no intermediate state)
Order number format: ITO-YYMM-NNNN (e.g., ITO-2406-0001)
Stock Counts
Section titled “Stock Counts”| Status | Description | Can record counts | Can delete |
|---|---|---|---|
DRAFT |
Session open, quantities snapshotted | Yes | Yes |
COMPLETED |
Counts finalised and adjustments posted | No | No |
Transitions: DRAFT → COMPLETED (complete)
Stock Adjustments
Section titled “Stock Adjustments”Stock adjustments have no status. They are immediate single-step operations. The underlying inventory transaction records a status of completed once applied.
Adjustment types:
| Type | Description |
|---|---|
CYCLE_COUNT |
Correction from a manual count |
DAMAGED |
Damaged goods write-off |
EXPIRED |
Expired stock write-off |
FOUND |
Unrecorded stock discovered |
LOST |
Stock that cannot be located |
CORRECTION |
General data correction |
DISPOSAL_TRANSFER_OUT |
Removed for disposal |
DISPOSAL_TRANSFER_IN |
Received from disposal |
Inventory Transaction Types
Section titled “Inventory Transaction Types”Types the documented workflows actually emit today
Section titled “Types the documented workflows actually emit today”Only three transaction types are currently written by the standard operations:
| Type | Emitted when |
|---|---|
goods_receipt |
An inbound order line is received (recorded during receive, one per received line) |
bin_transfer |
A transfer order is completed (recorded against the source quant, one per line) |
system_correction |
A stock adjustment is applied, including the adjustments auto-posted when a stock count is completed |
Outbound dispatch does not write a ledger transaction. Completing an outbound order deducts the staging quant and removes serialized units, but it does not currently record an
outbound_issue(or any other) transaction.
Full set of transaction types defined in the system
Section titled “Full set of transaction types defined in the system”The TransactionType enum defines many more values for future and adjacent flows. They exist in code, but the workflows in this guide do not emit all of them:
inbound_receipt, purchase_receipt, goods_receipt, return_receipt, transfer_in, outbound_issue, sales_issue, transfer_out, service_allocation, vendor_return, consumption, cycle_count_adjust, physical_adjust, damage_write_off, expiration_write_off, cancellation, disposal, quarantine_hold, quarantine_release, quality_reject, bin_transfer, zone_transfer, warehouse_transfer, system_correction, migration_adjustment, allocation, deallocation.
Each transaction also carries a status: pending, completed, cancelled, or failed.