Cancelling an order in your own ERP or TMS does not cancel it in Dockflow. The two are only connected
in one direction: your system sends orders in, and a cancellation is only reflected here if it is
sent as an update.
So a cancelled order keeps its tradeflow, keeps tracking, and keeps appearing in views and reports -
often with its workflow steps sitting at waived, which is what makes it look stuck rather than
cancelled.
What to do: send the cancellation as an update from the source system if your integration
supports it. If it does not, send support the order references and they can be deactivated here.
Deactivating is the right end state - it takes them out of active views without destroying the
history. See automatic deactivation policies for how a
shipment normally closes out on its own.
Example
A user cancels a purchase order in their ERP, but the order remains active in Dockflow with its tradeflow and tracking still visible. Because the integration only sends orders in and cancellations appear only when sent as updates, the order looks stuck. They send the cancellation as an update; if their integration cannot do that, they send support the order references so it can be deactivated without destroying history.