Shortage Report
Introducing Beta Version of Shortage Report in Logiwa IO
Introducing the Shortage Report, providing real-time visibility into orders facing shortages or partial allocations. It displays detailed information, including SKU, Order Code, and Shortage Reason, to help warehouse managers quickly identify allocation failures.
The report distinguishes between two shortage reasons:
Insufficient Inventory: Stock is zero or below the required quantity in the Warehouse.
No Eligible Stock Found: Allocation failure due to allocation algorithm constraints (e.g., location restrictions).
Available in Job Management as a new tab and Reports → Orders in the main menu in the interface and available via Open API.
For detailed information on the Shortage Report, please check out the “Shortage Report” article.
Update Inventory After Location Count - on Mobile App
The mobile cycle count screen now allows users to instantly update inventory levels after completing a location count. This streamlines the process, reduces supervisor workload, and improves overall efficiency.
This is an access-based functionality where only mobile users with the relevant role that has access to the update inventory functionality can perform this action
This functionality is only available for location count operations.
Mobile VAS Entry
We’re introducing the Mobile VAS Entry screen, enabling warehouse staff to enter Value-Added Services (VAS) directly from their mobile devices, improving real-time data accuracy and efficiency. Access to this feature is controlled through user roles to ensure that only authorized personnel can perform VAS entries.
Direct VAS Entry: Perform VAS operations immediately on mobile without waiting for supervisor input from the web.
Order Selection: Select or scan Shipment Orders (SO), Purchase Orders (PO), Work Orders (WO), or proceed without an order.
Comprehensive Data Entry: Capture Client, Operation Date, VAS Type, Calculation Type, Operation Value, and Notes.
Summary & Confirmation: Review and confirm entries before finalizing for improved accuracy.
This enhancement simplifies VAS management, reduces delays, and ensures faster, more flexible warehouse operations. Whether working with specific orders or handling general VAS tasks, this new feature accelerates and streamlines warehouse workflows.
Return Labels
We're introducing the beta version of the Return Label Creation process. Users can now create Return Addresses directly from the client page and assign a single return address to a shipment order. If no return address is specified, the system will default to the address configured in the carrier setup when generating return labels.
On Shipment Order backlog screen “ Create Return Label” button is added
On Shipped & Cancelled orders screen “ Create Return Label” and “ Void Return Label” buttons are added
These return labels can be created via FedEx , UPS ,Easypost and Stamps as of now
Label Type field is added to Carrier Shipment Details Report. Carrier Labels and Return Labels can now be differentiated and filtered with Label Type field.
Shipment Order Detail > Shipment tab is modified to support return informations like carrier,option,tracking number etc.
Workflow Conditions and Actions are updated with Return Fields on SO. Return Address, Return Carrier and Return Shipping Option can be set as Workflow Conditions. Return Carrier, Return Carrier Setup Name, Return Carrier Shipping Option and Return Tracking Numbers can be set as Workflow Actions under Return Instructions.
What’s New/Improved
The LP with Inventory printout now includes key additional fields such as LP Weights & Dimensions, Product Barcodes, Inventory attributes(Receipt Date, Lot-Batch Number , Expiry & Production Date), Client and Product Images.
A new column, "Inventory Parent LPN," is added to the existing Carrier Shipment Details report to support the Post-Packing Segregation (Manifest) process.
A default filter that shows only orders from the last 7 days has been added to the Shipped & Canceled Orders tab in the Shipment Order screen to avoid performance issues and focus on recent data efficiently. The users still have the ability to remove this filter if needed.
Enhanced the Shipment Plan Order and Shipment Plan LP screens by adding new data columns (such as Warehouse, Client, Truck Plate Number, Carrier, etc.) to improve visibility and decision-making for warehouse managers.
Introduced a new "Excel Export History Screen" that provides users with a log of recent Excel export requests. This feature enhances user experience by enabling easy tracking of exports with an ability to redownload with provided URLs, including their status, type, and any associated errors.
“Product Group” field (ProductGroupName) has been added to the Inventory Transaction Webhook. This field can be used to provide information about the product group associated with the inventory transaction.
Enhanced the Purchase Order management endpoints in the Open API.
List Purchase Order: Now allows filtering by ActualReceivingDate and includes this field in webhook responses.
Create/Update Purchase Order Type: Added support for new fields: isAllowCreationWithoutProduct, isPackTypeMatch, isProductionDateMatch, and isCrossDockReceiving.
The Count Task Details functionality has been improved. The system now accurately reflects changes in inventory before a count is approved, including scenarios where an SKU is removed and others are added.
The Full LP Picking process has been optimized to correctly follow the walking path priority during task assignments. Tasks are now displayed in the optimal sequence based on the walking path of the LP's location, reducing travel time and improving picking efficiency.
Users can now edit the Cell Display Member, Location Barcode, Level, and Column fields for cell locations directly from the Location Screen (via Bulk Update Locations Excel Import or through UI). This update allows for easier adjustments without the need to recreate the cart or cell locations.
The mobile cart creation process has been enhanced to ensure a standardized and consistent naming convention for the Cell Name, Cell Display Member, and Location Barcode fields. During mobile cart creation, these fields will now follow the format CART_X_Y, where CART is the cart name prefix, X represents the column number, and Y represents the level number (e.g., cart_1_1, cart_2_3). This update improves clarity and ensures unique identification for each cell location within the same cart, simplifying both management and tracking.
Added an "Info" field to the Billing module, allowing users to view calculation details and clearer billing card descriptions.
The Billing module now supports UOM-based calculations for Pick & Pack operations when "Charge By" is set to either "Per Product (Pack Quantity)" or "Per Product (UOM Quantity)."
The Billing module now supports UOM-based calculations for Receiving operations when "Fee By" is set to either "Per Product (Pack Quantity)" or "Per Product (UOM Quantity)."
SKU and Pack Type fields have been added to the InventorySnapshotInfo data source in Logiwa Analytics.
The hasinventory field has been added to the LocationInfo data source in Logiwa Analytics.
Sync Inventory used to send Negative Quantities as Zero to Shopify. Now, Negative Quantities are sent to Shopify as themselves.
Export as Excel button is added to the Inventory Sync Summary page on the Product Listings - Linked Listings Screen. Export as Excel button on the Product Listings - Linked Listings grid is updated as well.
Return Address, Return Carrier, Return Carrier Setup Name and Return Carrier Shipping Option fields are added to Excel Import/Update templates and Shipment Order related OPEN APIs.
We’ve updated the Techship and Custom Carrier setups to include Tax Type and Tax ID fields. Customers can now send sender tax information directly to carriers, improving compliance and streamlining shipping documentation for their international shipments.
The Recipient Tax ID is now seamlessly included in the custom carrier request model and this can be configured from the Shipment Order Screen.
We've added missing filter conditions to the Integration Reports screen, enabling users to filter records on the Orders & Shipments and Products & Inventory pages more effectively based on their requirements.
We've added a new field called Address Type to the customer carrier request model, allowing customers to identify whether a shipment address is residential or commercial.
The Billing Type field in Logiwa IO has been standardized to use static values: "sender", "recipient", "third party", and "collect". This change simplifies integration and OpenAPI interactions by replacing complex carrier-specific enums with straightforward, uniform values.
We've updated the logic for sending the Customs Declared Value to carrier integrations. The value is now primarily sourced from the Product - Customs Declared Value field. If this field is not available, the system will fallback to using the Shipment Order Line value as before.
A new toggle has been added to carrier integrations, allowing users to configure whether Kit to Stock items will display their component SKUs instead of the parent SKU on the commercial invoice when shipped.
We've added a “Production” toggle to custom carrier setups, allowing users to change their setups configuration on their own.
We've introduced a Changelog for Rate Shopping configurations, giving users better visibility into changes and adjustments within their rate shopping presets.
We've updated the design of the Rate Shopping section on the Create Label screen, providing improved visibility and a clearer experience for customers.
“productTypeName” and “productGroupName” query parameters were added to “Total Inventory Report” and “Product List” OpenAPI endpoints.
“IsPartial” field has been added to ‘Shipment Order Status Change’ webhook payload.
“Location Group” information was added to ‘Inventory Transaction’ webhook paylod.
A new “Return Order Update” endpoint has been added to the available OpenAPI endpoints.
What's Fixed
Resolved an issue where, after filtering orders and switching to a different filter, clicking on the newly filtered order displayed details from the previously selected order instead of the correct updated selection. (Hotfix)
Fixed an issue where attempting to edit shipment orders with multiple pages of products resulted in an error, preventing users from making necessary modifications. (Hotfix)
Fixed an issue where the Shipment Order grid displayed outdated job codes after AI-optimized picking tasks, ensuring consistent job code updates across the system.
Fixed an issue where the Picked Quantity in Pick to Location screen reset to 0 when returning to the job pool, ensuring it now reflects the last scanned quantity accurately.
Fixed an issue on the Mobile Picking screen where the total number of jobs displayed for a user did not match the actual number of jobs listed in their job list.
Resolved an issue in the Full LP Picking process where the task filter option in the Pick to Location screen did not apply changes or show records as expected.
Inventory Snapshot Report’s selected snapshot dates were shown one day later for some timezones issue have been fixed.
Fixed an issue where the free quantity in SKU’s allocated lines was not visible or accounted for during replenishment job creation in Static Replenishment. This caused replenishment jobs to be created despite sufficient stock being available in the target location. The system now correctly includes free stock from allocated lines in replenishment job creation.
Switching between different replenishment methods (Product Replenish to LP Replenish) previously caused incorrect information to be carried over. This has been fixed so that each task starts fresh with the correct details.
The Replenishment Algorithm has been fixed to ensure replenishment jobs are correctly created based on Location Group and Location Zone rules. The integration with the Putaway Algorithm has been corrected, preventing job creation failures and ensuring proper location assignment.
Fixed an issue where Product Label printouts failed for Purchase Orders with more than 5 lines. The query logic has been corrected to support POs of any size, ensuring successful generation and download of printouts without errors.
The "Difference" calculation within the Count Location Details and Count SKU Details screens has been corrected for scenarios involving zero stock or zero counted quantities.
Resolved an issue in the Report Designer where reviewing printout designs with duplicated designs resulted in incorrect XML data being displayed. This fix ensures that users can accurately review and edit the duplicated design based on another printout.
The Purchase Order (PO) module now automatically populates the "Actual Receiving Date" field when a PO's status is manually changed to "Completed" through the Edit PO interface.
The Create Product Open API endpoint is allowing invalid clientIdentifier values during product creation, leading to potential data integrity issues. This fix will enforce proper validation to ensure only valid client identifiers are accepted and improve data consistency.
Fixed an issue where deleted Billing Cards or Billing Contracts were not visible in previously calculated Billing reports.
Fixed an issue in the Billing module with the Shipment Package Price calculation where multiple order lines within the same box were being double charged for multi-SKU shipments.
Fixed an issue where removed tags from an order were still being included in billing calculations.
Fixed an occasional issue where the "Forgot Password" button failed to send the password reset email to users.
We've resolved an issue where the carrier and option values from Techship responses were not properly assigned during the Get Label process. This fix ensures consistent behavior across both Get Rate and Get Label, enhancing visibility for carrier rate shopping.
We've resolved an issue with reprinting ZPL labels on the Shipment Order Detail screen, ensuring users can now reprint labels without any issues.
We've fixed an issue where shipment orders were being affected by channel updates after a workflow was triggered,and performed action of add or delete SKU . The system now tracks workflow-affected lines and prevents their modification during shipment order updates.
Improvements have been made in the display of some unhandled errors in the Channel Integration logs.
“Listing Creation” has been added among the transactions to trigger inventory sync.
Fixed an issue where client filters were not working properly in shipmentorder create/update webhooks.
Sincerely,
Logiwa IO Team