Why a shipment might be blocked and how to resolve it.
Turn a blocked shipment into a specific correction or safe hand-off by reading the preflight reason first.
Do not override validation, invent recipient data, or create another shipment to get past a block.
Shipments are halted when preflight validation returns a safety or compliance reason.
The block reason is resolved according to the specific preflight failure.
Use these signals to decide whether the work is ready to continue, complete, or needs an owner.
Blocked before shipment
StoreFulfil has prevented shipment because a current safety or preflight condition failed.
Next: Read the exact reason and identify its source-data owner.
Correction made
The owner has corrected the underlying value, but StoreFulfil has not yet confirmed the new state.
Next: Run the supported sync or re-check and read the result.
Ready or still blocked
The new preflight result either permits the shipment or names a remaining blocker.
Next: Proceed only when ready; otherwise hand off with evidence.
Warehouse Admin; Warehouse Operators must hand the visible preflight reason to an Admin
StoreFulfil has prevented shipment because a current safety or preflight condition failed.
Read the exact reason and identify its source-data owner.
Do not override validation, invent recipient data, or create another shipment to get past a block.
The named block is cleared and the shipment result is visible.