Shipment statuses

The current source models local held-order correction state. These are workflow states, not carrier transit, delivery, return, or customer-notification events.

Not live tracking. Carrier lifecycle states remain roadmap direction. A local release must never be presented as a booked, labelled, manifested, collected, in-transit, or delivered parcel.

Local state	What it means	Safe next action	What it does not prove
Held	The synthetic order is waiting for a bounded correction, validation result, or review.	Read the named reason and assign the correct owner.	No provider request has been accepted.
Correction in progress	An authorised user opened a correction against a specific revision.	Change only the intended field and revalidate.	The correction is not approved or released.
Ready to release	Current local validation and approval gates are satisfied.	Verify evidence and complete the authorised local release.	No booking, label, or writeback exists.
Released	A local operation and outbox intent were recorded.	Keep provider execution separate and reconcile any future outcome.	No carrier, tracking, notification, or delivery outcome is proven.

When a state looks wrong

Confirm the active workspace and selected order.
Reload the current record and compare its revision.
Read the latest validation evidence and approval count.
Do not overwrite a stale record or retry an unknown provider outcome.
Report the local state and safe request reference without sharing sensitive payloads.

For correction steps, see Why is this order held? For future connected states, see tracking, returns, and writeback.