Logiwa IO has introduced a logic-based validation layer to prevent the accidental cancellation of picking jobs for orders that are already staged or ready for shipping. This feature ensures order integrity by reducing duplicate shipment errors and maintaining inventory accuracy.
Why Use This Feature?
Currently, if a user cancels a picking job for an order that is already packed or labeled, it can lead to operational gaps. Key benefits include:
Prevention of Physical vs. System Gaps: Avoids situations where the system thinks items are back in bins, but they are physically in a sealed box.
Reduction in Duplicate Shipments: Prevents new pick jobs from being generated for items already packed.
Inventory Accuracy: Eliminates "Inventory Ghosting" where items leave the building but remain untracked.
Configuration & Setup
1. Shipment Order Type Configuration
To enable this validation, a specific flag must be activated at the order type level:
New Flag:
Validate Allocation Cancellation.TRUE: Enables validation logic and warning modals.
FALSE (Default): Maintains current behavior with no validation prompts.
2. Role & Permission Setup
Access to override these warnings is controlled by two new permissions:
Override Job Cancellation Warning: Found under Job Management permissions.
Override Order Allocation Cancellation Warning: Found under Shipment Order permissions.
How it Works: "At-Risk" Logic
An order is classified as "At-Risk" (ineligible for immediate cancellation) if it meets the following conditions simultaneously:
Configuration is Active: The specific Shipment Order Type must have the
ValidationOnAllocationCancellationflag set to TRUE.Presence of Downstream Tasks: The order has reached a stage where it is typically packed or staged. The system specifically looks for active, pending tasks that occur after packing:
Shipment Tasks: These tasks are never visible on the UI. They are system-generated backend tasks created once packing and loading(if there is) are finalized to handle manifesting or final dispatch.
Loading Tasks: Any pending task related to moving the parcel or pallet onto a carrier vehicle.
User Workflows & Warning Modals
When you click Cancel Job or Cancel Picking, the system evaluates the selected orders. If "At-Risk" orders are identified, the system displays an Attention modal.
Interaction Based on User Permissions
The options available in the warning modal depend strictly on the user's assigned permissions:
Scenario | Available Actions | Result |
User WITH Permission | Go Back, Cancel Eligible Only, & Yes, Force Cancel All | Can choose to bypass the warning and de-allocate all orders, including at-risk ones.
|
User WITHOUT Permission | Go Back & Cancel Eligible Only | The "Force Cancel" button is disabled or hidden. The user can only proceed with orders that are not at-risk.
|
Note: As seen in the interface, if a user lacks the override permission, they will only see the options to Go Back or Cancel Eligible Only. This ensures that high-risk cancellations are only performed by authorized personnel.
User with permission:
User without permission:
Warning Modal Actions & Button Functions
When the "Attention" modal appears, the system offers two primary ways to resolve the cancellation request:
Button 1: Cancel Eligible Only (Proceed with Eligible):
Action: The system identifies and de-allocates only the orders that are NOT "At-Risk".
Result: Any "At-Risk" order remains allocated and active in the system to prevent physical-to-system gaps.
Button 2: Yes, Force Cancel All:
Action: This is an override function that de-allocates every order in the selection, regardless of its "At-Risk" status.
Result: All associated tasks are canceled, and the Job status is updated to Canceled.
Important Considerations
Exclusions: Checking for the physical existence of a carrier label is currently out of scope.
Task Dependency: Validation is strictly dependent on the existence of "Shipment" and "Loading" task categories.