Logiwa IO Shortage Report will be available as a Beta version starting with the January Main Release. 
For more details about Beta feature releases, please refer to the related article.
Shortage Report is a dynamic report designed to empower warehouse managers with instant visibility into orders facing allocation challenges.
By highlighting shortages and partial allocations, this feature enables quick identification of issues, helping to resolve them efficiently and prevent shipment delays.
Shortage Report introduces a user-friendly interface to manage and monitor allocation issues effectively:
Two Distinct Shortage Types:
Insufficient Inventory: When the required stock is not enough to fulfill the order in the whole warehouse.
No Eligible Stock Found: When allocation fails due to allocation algorithm constraints, such as location restrictions or attribute mismatches.
Detailed Filters: Narrow down the report by parameters like Warehouse, Client, SKU, Shipment Order Code, Order Date, and more.
Excel Export: Export the report for offline analysis and sharing.
Dynamic Refresh: Update the report in real time as stock levels or allocation parameters change.
Columns Included in the Shortage Report The report provides granular details to help you pinpoint issues effectively. Below is a summary of the key columns:
Column | Description |
Warehouse | The warehouse of the shipment order. |
Client | The client of the shipment order. |
SKU | The SKU of the product that failed allocation. |
Product Name | The product name of the failed SKU. |
Shipment Order Code | Code of the order facing shortages. |
Store Order Code | Store order code (if any). |
Order Date | The creation date of the shipment order. |
Shipment Order Type | Type of the shipment order. |
Order Line Pack Quantity | Total pack quantity required for the SKU. (Pack Quantity of the SKU in the Shipment Order Line) |
Order Line UOM Quantity | The UOM Qty of the Shipment Order Line for the SKU |
Shortage Pack Quantity | Unallocated pack quantity for the SKU for the Shipment Order. |
Shortage UOM Quantity | Unallocated UOM quantity for the SKU for the Shipment Order. |
Total Free Pack Qty | Total Free Pack Qty for the SKU in the Warehouse (Inventory Status: Stock) |
Total Free UOM Qty | Total Free UOM Qty for the SKU in the Warehouse (Inventory Status: Stock) |
Damaged Pack Qty | Total pack quantity for the Product that has Damage Reason in the Warehouse |
Damaged UOM Qty | Total UOM quantity for the Product that has Damage Reason in the Warehouse |
Onhand Pack Qty | Available, allocatable pack quantity based on the allocation algorithm. |
Onhand UOM Qty | Available, allocatable UOM quantity based on the allocation algorithm. |
Shortage Reason | Specific reason for the allocation failure: Insufficient Inventory or No Eligible Stock Found. |
Last Allocation Trial Time | Date-time of the last allocation attempt. |
Order Age | Order Age of the Shipment Order Code |
Expected Shipment Date | Expected Shipment Date of the Shipment Order Code |
Master Order Code | Master Order Code of the Shipment Order Code (If the Order is a Back Order) |
Order Status | Current Order Status of the Shipment Order |
How It Works
Example Scenario:
Imagine three shipment orders below: Order100, Order101 and Order102.
Order100 can be only allocated fully per its Shipment Order Type settings, whereas, Order101 and Order102 can be allocated and fulfilled partially.
Shipment Order Code | SKU | Pack Quantity | Shipment Order Type |
Order100 | SKU A | 5 | Full Allocation |
Order100 | SKU B | 3 | Full Allocation |
Order101 | SKU C | 4 | Partial Allocation |
Order101 | SKU D | 2 | Partial Allocation |
Order102 | SKU E | 2 | Partial Allocation |
Order102 | SKU D | 2 | Partial Allocation |
Order 102 | SKU G | 2 | Partial Allocation |
Also, imagine that the inventory looks like below in the allocation trial time:
SKU | Quantity | Location Zone | Inventory Status |
SKU A | 2 |
| Stock |
SKU B | 3 |
| Stock |
SKU C | 2 |
| Stock |
SKU D | 6 |
| Stock |
SKU E | 2 | Storage | Stock |
Please note that based on the allocation algorithm in our example, the inventory in Storage zone cannot be allocated.
Thus, here is a snapshot of the Shortage Report after allocation trial at t=1:
The inventory changed as the following:
SKU | Quantity | Location Zone | Inventory Status |
SKU A | 2 |
| Stock |
SKU B | 3 |
| Stock |
SKU C | 2 |
| Allocated |
SKU D | 4 |
| Allocated |
SKU D | 2 |
| Stock |
SKU E | 2 |
| Stock |
Once the allocation is tried again, the Shortage Report's snapshot will look like the following:
If a product has multiple Pack Types and multiple inventory lines with different pack types exist for the SKU during allocation, the Free Pack Quantity column will display a "Multi" flag instead of the total pack quantity. This prevents misleading calculations, as the quantities are not directly comparable. Instead, users can refer to the Free UOM Quantity column, which accurately reflects the UOM quantity based on the UOM ratios of each pack type.
Your Feedback Matters
As this is a beta release, we value your insights to make the Shortage Report even better. Share your feedback directly via our support channels.