Enhancement: Break Support for Case Packs and Pallets with Batched Constituent SKUs

Enables breaking of case packs and pallets with batched constituent SKUs at hub locations.

Version: 1.0
Owner: Omniful Product Team

Summary

This enhancement extends the break functionality in Omniful WMS to allow users to break case packs and pallets with batched constituent SKUs at hub locations. Previously, such pallets and case packs could only be broken during GRN. The updated flow now enables break operations at picking locations and backstorage locations, ensuring essential validations and batch traceability.

The existing break experience remains unchanged where the constituent SKU is non-batched. Additional handling is introduced only for scenarios where the constituent SKU is batched and requires batch selection for items generated after break. If the constituent SKU is serialised, break operation is still blocked at hub locations.

How It Works

1. The system first validates whether break is allowed

   The break action is blocked when the constituent SKU is serialised. It is also blocked when the constituent SKU is not configured for the current hub.

2. The operator can create or select a batch during break when required

   When the parent SKU is non-batched but the constituent SKU is batched, the break flow prompts the operator to select an existing batch or create a new one for the constituent SKU. The batch can be created directly from the break screen, including entry of manufacturing and expiry details.

3. Manufacturing and expiry details of the parent SKU's batch are inherited when both parent and constituent SKUs are batched

   When both the parent and constituent SKUs are batched, the constituent SKU inherits the parent SKU's manufacturing and expiry dates. The operator can map the break to an existing constituent batch with matching details or create a new batch by entering only the batch number, with manufacturing and expiry dates pre-filled from the parent batch.

4. Location-level validations protect batch and QC integrity

   In bin-enabled hubs, the same SKU cannot exist at the same location from multiple batches. If the location already contains the constituent SKU in a different batch, the break is blocked when the user tries to assign another batch to the constituent SKU.

5. Prevent mixing QC types for the same SKU at a location

   The same SKU cannot exist at the same location in different QC types. If the break operation would create that conflict, the system blocks it.

6. Standard break flow remains unchanged for non-batched constituent SKUs

   For parent–constituent combinations where the constituent SKU is non-batched, the operator follows the standard break flow: select the quantity to break and confirm, with no additional batch-handling steps required.

7. Breaking a serialised parent SKU

   If the parent SKU is serialised, the operator must scan the serialised barcode of the parent item to initiate the break. Since each serialised unit is uniquely tracked, the break is performed one unit at a time, with no quantity selection required.

Technical Details