Why is this order held?

A held order is waiting because the current synthetic workflow cannot safely move it to the next local state without a correction, validation result, or approval.

No live carrier action. The current contract models synthetic held orders. It does not connect to live channels, carriers, bookings, labels, customer notifications, or source-system writeback.

Read the named reason

Open the order in the authenticated Dispatch workspace. The correction view carries a bounded reason and the current version. Treat the reason as guidance for the next review, not permission to bypass validation.

Common reason families

Reason family	What to review	Escalate when
Address or contact data	Compare the source value, supported format, and proposed correction.	The correct value cannot be established from approved evidence.
Weight, dimensions, or contents	Check the declared values and the current synthetic fixture or authorised scan evidence.	Measurements conflict or the source record should be corrected upstream.
Missing classification	Identify the exact line or field that needs catalogue ownership.	The change would alter a reusable product record or customs decision.
Policy or approval	Read the current policy context and required approval count.	You do not hold the required capability or separation of duties applies.
Stale revision	Reload the canonical record and compare the latest change.	The competing update cannot be reconciled safely.

Follow the state, not the colour

State	What it means in the current source contract
Held	The synthetic order is waiting for a bounded correction or review.
In correction	An authorised user has opened a correction session.
Ready to release	The current correction version has passed its local gates and any required approvals are visible.
Released	A local release and outbox intent were recorded. This does not prove a carrier booking, label, writeback, or notification.

Correct safely

Confirm you are in the intended authenticated workspace.
Open the current correction view and note its version.
Record only the supported field change and its writeback mode.
Run validation again against the new correction version.
Complete any required local approval before release.

If the version changed while you were working, reload the current state instead of overwriting it. If access is denied, do not retry with identifiers from another workspace.

If the order remains held

Confirm the correction was made against the current revision.
Read every failed or stale validation result.
Check whether a named local approval is still missing.
Keep the order held if evidence is incomplete or authority is unavailable.
Escalate with a safe request reference and approximate time, not customer data or credentials.

See rules and approvals for the review gate and shipment statuses for the local state model.