Welcome to our April release notes. As the vibrant hues of spring emerge in many areas, we're sprouting new features of our own. From major billing updates to a refined missing process, these enhancements are designed to empower your workflow. We also have an important policy change to announce that we hope will make use of the mobile app smoother in the future. Read on to discover what we've got in store this month.
Future Policy Change for Logiwa IO Mobile App Updates
In the upcoming months, Logiwa IO will introduce a significant change to its mobile application update policy. Starting in July, a new feature will roll out that mandates users update their mobile applications based on a minimum acceptable version number, as defined by the team at Logiwa IO. Users who possess versions older than that will be prompted with a pop-up notification requiring them to update the application. This alteration is being implemented to address issues related to motion data, enhance the adoption of new features, and improve the overall user experience. The objective is to ensure that all users are utilizing the most recent versions of the application.
Replenishment Algorithm Option
A new Replenishment Algorithm option has been added to the Replenishment Job Type screen, now offering both FIFO and FEFO options. Customers can now prioritize either the order of stock received or the expiration date, respectively. Please note that FEFO will be applied by default. This enhancement to the algorithm will help fulfillment centers maintain better inventory management and minimize waste.
Serial Number Import
The Serial Number Import process is now available for shipment orders. If Skip Scan Serial Number is enabled for the product, the system will not ask for the serial number during Packing. Once the order is ready to ship, the system will not ship the order until the Serial Number Import Excel is uploaded for the orders. Users will enter Shipment Order Code, SKU, and Serial Number(s) on this sheet.
As part of the Serial Number Import process, users will also have the option to remove the imported serial numbers. If Skip Scan Serial Number is enabled for the product, the Serial Number Import Excel should be uploaded for the shipment orders. If the user enters an incorrect serial number during that process, they will have the option to disconnect the serial number from the shipment order by using the Remove Serial Number button on the Shipment Order screen. Please note, in this scenario, the imported serial numbers will revert from the Packed status to the Received status.
Shipment Package Charges with Billing
Shipment package charges have been added to Billing. This development empowers users to establish distinct pricing for shipped shipment packages, offering two management options.
Users can set the Fee By: Per Label, which requires label printing through Logiwa for utilization. With the Shipment Package Type condition, users can define pack types and access the pricing section, featuring options like flat charge, percentage, label charge, and label charge with additional percentage.
For example:
Flat charge (per label): here the user has to enter an amount to the free text which will be multiple with the number of labels that the user got for the client during the billing period.
Percentage: The user will enter the percentage amount that will be calculated as per label charge.
Label Charge: This information should be automatically captured from the “carrier shipment detail” report.
Label Charge (+ Percentage): The user will enter the percentage amount. Per label charge will be label price plus the percentage entered in the setup.
Alternatively, for users not utilizing Logiwa for label printing, the Fee by: Per LP option captures shipment packages under LP count, allowing users to define pricing based on the number of LP shipped during the billing period, offering flat charge price options.
New Inventory Attributes for Production Date and Receiving Date
Production dates and receiving dates are both crucial for managing shelf life and organizing stock effectively. The following production and receiving date additions have been made to the system:
Receiving Date
A new parameter is available under the Client screen: Keep Receiving Date on Inventory. It allows users to choose whether to track and display the receiving date on screens and reports, enhancing flexibility in inventory visibility.
Receiving dates are now displayed on the Inventory by Location, Task Details, and Shipment History screens.
Putaway and Allocation Algorithms can now use receiving date for Order By and as a Condition for algorithms.
Receiving date and production date fields have been added to the Purchase Order List, Picking List, Consolidated Picking List printouts.
Production Date
A new parameter is available on the Product screen: Production Date Tracking. Similar to the expiration date tracking, this toggle enables or disables tracking of the production date for products, integrating closely with inventory reports and alerts for better inventory accuracy.
Production Date Match has also been added as a parameter to Returns setup. If this parameter is enabled, if the production date entered during a return is not the same as the production date in the system, the system will display an error. If disabled, any production date can be accepted during the return process.
A new parameter is available for PO Types: Production Date Match. This toggle enforces validation checks that the entered production date matches the production date in the PO.
A new parameter has been added to the Location and LP Types screens: Only 1 Production Date. When enabled, this parameter ensures that each location can only have one unique production date for a product.
Production dates can now be entered in bottom-of-screen mobile menus during the Receiving, Transfer, Picking, and Count processes.
Production date info is now available on the Look Up, Pick Target, and Pick and Sort by Tote mobile screens.
Production date has been added to key reports, including Inventory by Location, Receiving History, Transaction History, Task Details, Shipment History, PO Details, and SO Details.
Production date tracking info have been added to the table and filter on the Product screen, allowing users to easily sort and filter inventory based on these values.
The option to change the production date under the Change Attributes option in the Inventory by Location screen has been implemented.
The production date field has been added to the Shipment Order, Purchase Order, Inventory, Location and Product Excel import and export templates.
Production dates have been added to the Return Station and Create RMA screens.
Putaway and Allocation Algorithms can now use production date for Order By and a Condition for algorithms.
Production Date has been added to the Conditions section of Workflows.
API Updates for Receiving Date and Production Date
The production date can now be transmitted in purchase order inserts and shipment order inserts via API.
The receiving and production date have been added to the following Open API methods:
Inventory by Location
Receiving Date
Production Date
Receiving History
Production Date
Transaction History
From Production Date
To Production Date
Task Details
Receiving Date
Production Date
Shipment History Logiwa
Receiving Date
Production Date
PO Details Logiwa
Production Date
SO Details Logiwa
Production Date
Product
Production Date Tracking
Plus much more below!
What's New/Improved
As part of our new Missing process, we have added a parameter called System Default to the available Damage Reasons. This parameter is hidden and is only used for the "Missing" damage reason. When the account is created, the "Missing" damage reason will be automatically created with the System Default flag. Thus:
"Missing" damage reason cannot be deactivated.
Inventories with a "Missing" damage reason cannot be allocated, even if not specified by conditions in the Allocation Algorithm.
This default "Missing" damage reason will not appear in the Report as Damaged menu or when adding/changing inventory attributes. It will only be utilized by the system during "Missing" operations and will be removed from Inventory by Location and Mobile Transfer.
When picking on mobile, multiple pack types may be available for an item and stored in the location. To increase clarity for pickers, the mobile screen now visibly indicates the pack type to be picked and the pack type to be picked from (the From Pack Type).
Please note this only applies when there is a different From Pack Type.
Menus are now hidden if the user does not have permissions to access the corresponding screens. Additionally, modules and sub-modules will also be hidden if the user does not have permissions to view the pages within them.
Column sizes on reports can now be expanded for easier viewing.
Billing updates:
A Per SKU option has been added within the Fee By dropdown, meaning that users can define fees based on the quantity of SKU received, offering more flexibility in billing methods alongside existing options like Per Product, Per Pallet, and Per PO. This will help with the implementation of precise billing strategies tailored to SKU quantities.
Pack Type conditions have been added to the billing for Picking and Packing. These conditions allow distinct pricing based on the pack type of products. Pick and pack billing has also been enhanced to allow users to set tiered pricing based on:
Total number of products associated with the shipment order.
Total number of products associated with SKU lines within the order.
Total number of products.
Additionally, users can charge for items based on the sequence of picking, allowing for more granular and customized billing processes.
A new feature has been introduced to track the number of shipped shipping packages. Each package type can have its own pricing set up under the Operation Type: Shipment with the Fee By: Per Label. This includes conditions for specifying shipping package types and offering both unit-based and tier-based pricing options. Users can choose between flat charges (per label) or percentage-based charges, with the system automatically capturing label charges from the carrier. Additionally, a markup option allows for adding an extra percentage charge to the label price received from the carrier.
Users can now arrange their storage charges based on volume. With the option to select Fee by: Total Volume, users can calculate charges by multiplying the product volume by the number of products stored and specify relative conditions that also influence fee calculation. The introduction of Charge By: Volume enables users to define pricing structures based on the volume of each stored item.
Two new conditions have been incorporated into the billing module, Number of Shipment Orders and LP Type. Number of SO enables users to establish pricing tiers based on the quantity of shipment orders. This involves defining shipment charges per order, depending on the number of shipped orders during that billing period. LP Type is available per LP and allows users to filter shipped LPs by their types and define unique pricing for each LP type.
Billing now includes tier-based billing for Picking, so users can manage billing charges according to the number of shipment orders or the number of products picked.
Import improvements:
Location custom fields have been added to the Create Location and Update Location Excel import options. Now, users can populate those custom fields when using the Excel import functionality to create or update locations.
Product custom fields have been added to the Create Product and Update Product Excel import options. Now, users can populate those custom fields when using the Excel import functionality to create or update products.
A new informative flag has been added to the Pick to Location screen's first step to indicate when a job contains full LP tasks. Once a job is selected, the user will see a message stating, "This job contains Full LP tasks." They will then choose where these LPs will be picked and fill out the Pick To field accordingly.
The Open status has been added to the Workflow Action: Assign This Status dropdown when creating or editing workflows. This status selection will change the status of a shipment order to Open, but only if the sales order's status is On Hold. Only sales orders with the On Hold status can be changed to Open using the Assign This Status workflow action.
A new parameter called Prevent Reallocation if Missing has been added to the Client setup. If the user is reporting a product as missing:
When this parameter is enabled, the system will not attempt to reallocate the order. Inventory will be adjusted immediately, and the Task Cancellation process will be applied.
When this parameter is disabled, the system will attempt to reallocate the order based on the available free inventory as determined by the Allocation Algorithm.
LP number-related changes are now visible on the Change Log Report.
Carrier Setup screens have been updated to visually enhance the user experience.
Sorting and filtering options have been incorporated into the Pick and Sort screen. Users will have the ability to filter by location zone, group, order status, creation date and more.
For Shipment operations, users now have the ability to adjust markup rates depending on Ship To, Ship From, and Package Weight criteria, specifically for label charges. When the printed label meets the set criteria, pricing will be applied accordingly.
UOM Pack Type and UOM Quantity have been added to the Receiving History Excel export.
Users that have permission to edit the User screen will now be able to change the passwords of other users as well.
Volume and weight conditions now accept 0 as a value for tiering purposes. This enhancement accommodates scenarios where a 0 is relevant for volume and weight conditions in the Billing module.
An LP Edit option has been added to the Loading screen. Once the LP number is scanned, if there is a pending loading task for it, the user will have two options:
Load LPN.
Edit LPN.
In the Edit LPN menu, users can edit the Length, Width, Height, Actual Weight, and Actual Volume fields, as well as view LP Type, Calculated Volume, and Calculated Weight.
The system now ensures the uniqueness of Location Barcodes, thereby prohibiting users from assigning the same Location Barcode to different Location Codes. Any attempt to assign a duplicate Location Barcode will prompt a validation error, alerting the user to the duplication and halting the operation until a distinct Location Barcode is provided.
What's Fixed
The reallocation process when reporting products missing was temporarily inactive, but it has now been fixed. Once the user reports a product as missing, the reallocation process begins. If there is available inventory for the product, it will reallocate the order. The system takes the Create Backorder and Allow Partial Shipment parameters into account:
If the order type only allows full allocation and there is no inventory found to fully fulfill the order, allocation will be canceled.
If Create Backorder is enabled for the order and there is no inventory found to fully fulfill the order, a back order will be created for the missing product.
The Select All issue on reports has been fixed; up to 1000 lines can now be selected at once. When more than 1000 are selected for deletion, a pop-up will confirm that 1000 lines will be deleted to clarify the maximum.
Product export fixes:
Previously, products' UOM quantities, Customs Declaration Descriptions, and custom fields were showing up blank when exported via excel despite the information existing in the system. This has been corrected.
Additionally, the Is returnable field's name conflicted with the name used in the system, Non-Returnable?, which caused errors. This conflict has been resolved.
Users can now receive purchase orders with multiple different pack types for the same product within the PO without issue.
The issue with inactive user authorization has been resolved. Inactive users will no longer have the ability to log in.
We are now receiving shipping options from Shopify and WooCommerce without issue. These values will be visible in the Requested Shipping Option field.
We have added the Store Order Number to the Shipment Order Detail screen on top of the Shipment Order screen to enhance traceability.
We resolved the total price calculation bug that occurred when there was a discount equal to the total price of an order.
The issue with LP conditions for Storage Operations under Billing has been successfully resolved.
Location Code search on the Add Inventory screen was previously not working. This has been corrected.
The Received PO e-mail notification has been fixed.
After a product was received and another receiving operation had been started, we used to show: "2 units of [product name] received to [location name]." However, "unit" in this text caused confusion with unit pack types, so this text has been changed to: "2 [pack type name] of [product name] received to [location name]."
Previously, status changes on a Shipment Order did not trigger workflows. Now, workflows will process shipment orders after the status changes and, when the workflow conditions are satisfied, the workflow will execute its action.
The issue with custom fields sending a null value rather than a false value when the custom field toggle was enabled but the toggle was disabled has been corrected.
Expiry Date for Purchase Orders moving forward by a day when entered due to time zone issues has been fixed.
The select all issue when selecting clients with access on Printouts Reports has been fixed.
API/Webhooks
We have added Account Numbers to our Custom Carrier endpoints. Account numbers are used in both the Get Rate and Get Label processes.
Couldn’t Find What You Were Looking For?
Visit our Help Center to search for more documents!