Enhanced Scan Method Type Parameters for Lot/Expiry/Production Date Tracking in Outbound Operations
We’ve introduced new Scan Method Parameters in Product settings to better manage Lot Number, Expiry Date, and Production Date tracking during outbound operations like Picking and Packing. These enhancements offer greater flexibility and efficiency.
Now, you can configure these settings at the product level, allowing users to choose whether to scan Lot Number, Expiry Date, and Production Date during either the Picking or Packing process, depending on your operational needs.
This customization streamlines workflows and ensures accurate tracking at the most appropriate stage. Please note that Scan Method Parameters can be added or edited during manual product creation, when importing Products via Excel, or via Open API.
Inventory Attribute Check During Picking to Optimize Attribute Scan (Lot Number, Expiry Date, Production Date)
Introduced an Inventory Check Flag in mobile picking screens to determine if Lot Number, Expiry Date, and Production Date need to be scanned during picking. This enhancement allows the system to skip scanning these attributes when the inventory in the source location or license plate number is unique for the SKU and pack type, streamlining the picking process in Pick and Sort & Pick to Location screens.
Company Name Improvements
The Order Insertion Endpoint and Excel import have been updated to include a "companyName" field. This allows each order to be associated with the correct company information, ensuring more accurate data management.
The download order process now fetches company name information from Shopify and Amazon and saves it in the Company name field in Logiwa IO. This ensures that company name data is always accurate and up-to-date.
The carrier label request logic for FedEx & UPS & TechShip has been updated to include both the company name and the name fields. This ensures that the labels are properly formatted and contain all necessary information for accurate delivery, especially with international shipments.
Inventory Snapshot Report
We’re excited to introduce the Inventory Snapshot Report, a powerful tool for warehouse managers to capture detailed inventory snapshots at any point in time, enhancing inventory management and financial reconciliation.
The new report allows precise tracking of inventory levels, locations, and item attributes, including dimensions. This ensures financial accuracy by aligning inventory snapshots with billing periods, preventing discrepancies and reducing costs. Additionally, the report supports better strategic decision-making by offering comprehensive data, enabling businesses to make informed decisions about stock levels, space utilization, and logistics planning.
Keep PO Number on Inventory
We’re excited to introduce new features that significantly improve PO number tracking across the Logiwa IO FMS system. These updates allow warehouse managers to retain and utilize PO numbers throughout inventory operations, enhancing accuracy and efficiency.
"Keep PO Number on Inventory" Setting: A new option in the client settings enables you to retain PO numbers on inventory records. Once enabled, PO numbers are automatically recorded when purchase orders are received, ensuring they are consistently tracked across the system.
PO Number Visibility Across Key Screens: PO numbers are now displayed in the Inventory by Location, Task Details, and Shipment History Report screens. This makes it easier to reference and manage inventory by PO number directly within these interfaces, improving decision-making and operational flow.
Enhanced Reporting and API Integration: PO numbers are now included in relevant reports. API endpoints have been updated to support this new functionality, making it easier to generate detailed reports that include PO data.
What’s New/Improved
A new feature enhances the shipment process by automatically retrieving tracking URLs from carrier responses and ensures that tracking information is seamlessly transmitted to customer orders in Shopify and WooCommerce.
New fields "Reference Order Type" and "Reference Number" are added to VAS Operations Screen. Our users now can link "Purchase Orders", "Shipment Orders" and "Work Orders" to VAS Operations, and are directed to the related Order Screen when selecting the order code on the grid. Once an Order is linked to a VAS Operation, its Order Code is displayed on the Reference Number field of the Billing Detailed Report.
The product and location grids, along with their Excel export functionalities, have been enhanced to support large datasets exceeding 10,000 records, ensuring that users can view, manage, and export all their data without limitations.
Added the "Order Processing Age" field to the Shipment Order grid. This field tracks the duration an order has been in the FMS system from its creation date in Logiwa IO, providing better insights into order processing times.
The "Number of Location" field was renamed to "Batch Size" in the Job Type configuration, with updated tooltip information. This change clarifies its meaning for both static and dynamic replenishment, helping users accurately configure job types based on batch sizes.
When configuring a Replenishment Job Type with Dynamic Replenishment, the selected Putaway Algorithm is now displayed as read-only information, ensuring that users can easily verify the correct algorithm is applied without additional steps.
The Replenishment Job Type configuration now features a renamed "Replenishment Type" parameter, offering clear options for "Dynamic Replenishment" and "Static Replenishment" instead of the previous "Yes/No" choices. This update enhances clarity and accuracy in managing replenishment tasks.
A "Replenishment Algorithm" toggle has been added to the Putaway Algorithm configuration, allowing warehouse supervisors to set and manage a default Replenishment Algorithm. Only one algorithm can be active at a time, ensuring consistent handling of dynamic replenishment tasks.
Change log functionality has been added to the Workflow, Wave Rule, Vendor, and Printout screens. This enhancement allows tracking of changes, including date, time, user, and details of modifications, ensuring accurate record-keeping.
The Count reports in the UI have been updated to include the "InventoryUpdatedDateTime" and "InventoryUpdatedBy" fields. These new fields allow users to track when the inventory was last updated and by whom, enhancing inventory management accuracy. The updates are reflected in both Location Count and SKU Count screens, as well as in Excel exports.
The Wave Exceptions page has been renamed to Allocation Exceptions and now includes shortage information for both wave-allocated and manually allocated orders. This update provides a comprehensive view of all shortages, regardless of the allocation method, ensuring better inventory management. For manually allocated orders, the Wave No field will display "Manual Allocation," and the Wave Rule Set Name field will remain empty.
Custom field management permissions have been added, allowing supervisors to restrict the ability to create, edit, and delete custom fields on key screens. While all users can still enter data into existing custom fields, only those with the appropriate permissions can modify the custom field settings.
A search bar has been added to the Client assignment tab on the User Screen, enabling users to quickly and easily find clients by typing in partial or case-insensitive matches. This enhancement improves the efficiency and usability of the Client assignment process.
Custom fields have been added to all relevant Analytics data sources, enhancing the flexibility and accuracy of reports. The underlying queries have been updated to include these custom fields, allowing users to incorporate them into their Analytics and reports seamlessly.
A new "LP Carrier" condition has been added to the Putaway Algorithm, allowing packages to be directed to specific locations based on the carrier associated with the LP number.
A new "Purchase Order with Inventory" printout template has been added to Purchase Order Printout, allowing warehouse managers to generate detailed labels for each purchase order, including comprehensive inventory information sourced from the Receiving History report.
UI improvements have been made to enhance the user experience on low-resolution Android devices, ensuring better display and usability.
Improvements have been made to the barcode addition process for pack types, making it clearer and easier for users to add multiple barcodes.
A Change Status Button has been added to the Return Orders Screen. Users now can change the status of RMAs/ SOs on the screen. When a return of a RMA/SO is completed on the Return Station, its status is updated to Completed automatically.
Each client can now create a maximum of one pack list per store (e.g., one for Shopify, one for Amazon) and one pack list per non-store.
The Transaction History screen has been updated to include a new Count Plan Code column. This column allows users to trace and verify inventory movements related to specific Count Plans.
A new filter option for label status has been added to the "Carrier Shipment Details" report. This enhancement allows users to filter shipments based on their labeling stage, enabling more precise management of shipment details.
Logiwa IO's ShipStation integration now allows users to bill other parties during label creation. Users can choose the billing type, select the account number, and have it sent to ShipStation.
Only carriers with authorized shipping services are displayed in the carrier dropdown. This change streamlines the carrier selection process, reducing confusion and improving the efficiency of packing operations.
A new filter option has been added to the "Product Listing" screen. Users can now filter product listings by tags, allowing for easier organization and retrieval of specific listings based on their tags.
Shopify App access scope list requirements for Shopify integration setup have been reduced. The new Access Scope list is available in the document below.
What's Fixed
The Mobile App's directed putaway suggestion now includes the damage reason, ensuring the system accurately suggests appropriate locations for damaged inventory during putaway operations.
Edits made to mobile cart cells are now accurately saved and reflected in the system.
Fixed an issue in the Location module where the Excel export function from the location's grid was displaying higher pack types as units.
The inventory counting process has been corrected to ensure that quantities are accurately recorded for each task line individually, based on the specific location and receiving date. This prevents incorrect inventory updates and maintains accurate stock levels.
The "One by One Receiving" toggle on the mobile receiving screen now accurately reflects the configured settings, ensuring consistency and reducing the potential for user confusion during the receiving process.
User changes were not being logged correctly. This issue has been fixed, and now all user modifications are accurately tracked in the Change Log.
An issue where selecting 30 or 90 days for Expiry Date, Production Date, or Receiving Date in the allocation algorithm was incorrectly converted to 1 or 3 months has been fixed. These selections are now correctly interpreted as exact days, ensuring accurate inventory allocation.
An error that occurred when printing the task-based pack list from the Shipment Order screen has been resolved. Now, the printout will successfully generate for orders in "Packing Started" or higher statuses. Additionally, the pack list will display only the lines for which packing tasks are completed, ensuring accuracy in packing operations.
The "Skip and Pick Last" button has been fixed to work correctly for products with expiry date tracking, production date tracking, and lot number tracking enabled. Previously, this functionality did not work when these tracking options were in use. Now, the button will allow users to skip a task and select the last item in the picking sequence, even when all three tracking methods are enabled.
The Serial Shipment History report has been updated to correctly reflect the assignment of serial numbers to specific packages for orders with multiple items and packages. Previously, the report showed duplication of serial numbers, which affected the accuracy of serial number tracking. Now, each serial number is accurately assigned to the package it was shipped in, with no duplication.
The "Send Shipment" process only uses active tracking numbers and excludes any voided tracking numbers from shipment messages, preventing incorrect tracking information from being sent.
The validation restricting the "Enable Saturday Delivery" action to only FedEx and UPS has been removed. This action can now be enabled for all carrier connections within Logiwa IO
API/Webhooks
The Transaction History API has been updated to include the Count Plan Code for every count transaction. This update allows users to trace and verify inventory movements related to specific count plans directly through the API.
Custom Field options have been added to the Return Order master and detail objects. These fields are also made available in Return Order Create endpoint.
New query parameters and response body fields have been added to Receiving History endpoint. New Parameters: rmaNumber, ReturnOrderIdentifier PurchaseOrderCode, PurchaseOrderIdentifier, IsExported. New Response fields: ReturnOrderIdentifier, PurchaseOrderIdentifier, PurchaseOrderLineIdentifier, IsExported
Return Order List open API endpoint has been added to the system.
Mobile App Update
To ensure optimal performance and access to all the latest features, our mobile application will now display a notification prompt if an update is required. Users will be directed to store.logiwa.com by clicking the "Update" button. store.logiwa.com provides the most current version of the application. Users should log in with their username and password to download the update.
Note: For a smooth update process, we advise uninstalling the previous version of the application before installing the latest release.