Pull A Fulfillment Back From The Warehouse Holding It

A fulfillment sent to the wrong warehouse can now be pulled back from the order screen. Revert to Allocated has always been there for a ready fulfillment; it now also appears on a fulfillment that is already out, and asks the system holding it to cancel first before releasing the fulfillment inside Endless.

When the warehouse or system on the other end cannot accept a cancellation, the action turns into a question rather than a refusal. Confirming drops the link — the fulfillment stops counting as sent and can be routed again, edited, sent from a different building, or shipped later — and if the outside system was in fact carrying a copy, any later reconciliation reaches you through company notifications. Endless is the record either way.

The cancel dialog now tells the truth about what the outside system can do. It used to say “the external system will be notified” whatever was on the other end, which was false for the four integrations that never accept a cancellation. It now reads whether cancellation is available and says one of three true things: nobody outside holds a copy, they will be told, or they cannot be told and the link will be dropped.

Some fulfillments had already accumulated in a stuck state because those four integrations declared cancellation as available without wiring the action, so a background failure never reached the user. Those integrations now read as “cannot cancel” up front, and this flow is the way through them.