As we welcome the month of June, we are pleased to announce a series of enhancements and new features for Logiwa IO. Highlights include the addition of an Excel export function to be used with all Excel import processes, enabling comprehensive overviews of import details, and enhancements to custom fields, allowing for more detailed information input during imports. Additionally, we have updated our billing module to improve accuracy and customization. Please read on to learn about the latest updates and how they can benefit your operations this summer.
An Excel export function has been added for all Excel import functions to provide an overview of the import details. Now, import results can be downloaded as an Excel file after an Excel import is executed.
Custom fields can now be filled using the PO and SO Excel import function. Additionally, shipment orders can be updated by Excel import as well. The changes will be reflected only if custom fields were previously enabled.
SKU and Quantity information will be sent in Custom Carrier Create Label requests.
The Add Inventory Excel Import process now includes a Receipt Date column in the import template, allowing users to specify the accurate receipt date for inventory items.
Billing updates:
Previously, billing calculations considered a maximum of 2 digits after the decimal point (period/comma, depending on your currency settings). To improve accuracy, calculations will now consider up to 5 digits after the decimal point.
The Billing module will now dynamically display currency symbols based on each client's preferences, enhancing the accuracy and customization of billing reports.
The Storage Operation Type has been updated to include advanced fee configuration options based on LP type, LP weight, and LP volume.
Billing now supports tier-based charging for Product Receiving operations. Users can define multiple tiers with corresponding charges per product based on the quantity of items received during a billing period.
VAS Operations now includes a Calculation Type field, allowing users to select either Total Price or VAS Quantity for more precise VAS charge calculations.
When Total Price is selected, users can directly enter the total price, which will be reflected in billing reports.
If VAS Quantity is selected, the system will multiply the entered quantity by the unit price from the billing contract.
The existing Operation Quantity field has been renamed to Value in both the UI and Excel exports.
The Inventory by Location screen has been updated to include an LP Type column and corresponding filter option, allowing users to filter and view inventory based on LP type when needed.
Tracking numbers can now be added manually to shipment orders, and the Tracking Numbers field can now be edited from the UI if there is no label for the shipment order. Users can also enter multiple tracking numbers in the Tracking Numbers field.
Please note that once the shipment order is saved, manually added tracking numbers cannot be edited or removed. If they need to be removed or edited, the label will need to be voided, and the tracking numbers will need to be added manually again.
Users will no longer be able to enable or disable Lot Number, Expiry Date, and Production Date Tracking settings if there is existing inventory for the product.
Users will be able to import Location Count Plan and SKU Count Plan into the system.
Filters in the task-based have been added to the picking flow. Now, users will be able to filter the tasks in the jobs.
Users will no longer need to enter package dimensions for carrier-based pack types when using the Packing screen, as these dimension fields are now optional.
The workflow action Set Shipping Instructions, which is used to assign Carrier, Shipment Option, Tracking Number, etc., to shipment orders, has been adjusted so the system checks whether or not the shipment order has a label. This will prevent overriding existing label/carrier information on shipment orders if they already have a label.
Previously, workflows used the Set Tracking Number action to manually assign tracking numbers to shipment orders. This action has been merged with another action in the Workflow, Set Shipping Instructions. Users will now use Set Shipping Instructions to manually add tracking number(s) to shipment orders.
Carrier (e.g. UPS, FedEX), Carrier Setup (The setup name used in the system, which may vary by client), and Shipping Option (services such as Ground, Flat-Rate) selection will be required if the Tracking Number field is used in this action.
Multiple tracking numbers can be added.
Users will need to separate each tracking number with commas.
A Free UOM Quantity column has been added to the Inventory by Location screen to allow users to see the total available UOM quantity for the relevant products.
Available UOM Quantity has been added to the Total Inventory Report. Now, users can view available quantities based on the UOM.
Role permissions have been extended, and users now have more control over screens, buttons, and actions on all screens.
Two new default roles have also been added to the system: Supervisor and Warehouse Clerk.
Shipment messages will also be sent when tracking numbers are added manually or when a label is generated from the order backlog screen.
We have introduced a new field called "totalWeight" in the get and list shipment order endpoints. This field represents the calculated total order weight based on the weight of the products.
Carrier, Carrier Setup Name, Shipping Option, and Shipment Packages can now be assigned to shipment orders using Excel import.
If a shipment order comes from ShipStation, our system will use /createlabelfororder endpoint to create labels. This is a standard process designed to handle all label creation scenarios within ShipStation.
We are now supporting other carriers with our native Stamps connector.Before this development it is only designed to support USPS.
We have enabled the option to enter a specific date during the initial channel setup. This date can be selected within the past two months.
The production date function can be now utilized during task swap operations.
The list content of Logs section under Report and Analytics menu has been expanded by consolidating reports in LogiwaIO, for navigation purposes.
What's Fixed
An issue with showing the incorrect product quantity when packing the same SKU with different lot numbers and/or expiry dates has been fixed. Now, if users are packing an order that contains the same SKU with different attributes, the packing lines will be divided accordingly, and Lot Number and Expiry Date will be shown as Multi.
For Custom Carrier integrations, the system was sending the package description as Package by default. Now, the system will push the actual package code that users have selected during the process.
For the LP Type screen, Boolean (TRUE/FALSE) fields were consistently showing the True value. This issue has been fixed.
In WooCommerce, users can configure their Order Number generation, so we've adjusted our mapping to pull these configured store order numbers as well. This will be shown in the Store Order Number field on the Shipment Order.
It was still possible to receive inventory emails after disabling the Daily Inventory Notification parameter. This has been fixed.
Location Type, Area Type and Volume Unit information were missing in the Location Excel export. This issue has been fixed.
Previously, when exporting from the Serial Number Shipment History screen, the Shipment Order Code was incorrect in the exported Excel sheet. This has been corrected
Previously, when exporting product data, the system was pulling the UOM weight even for products using hierarchical pack types. Now, the export shows the correct weight information according to the pack types.
The Is Not comparator for Expiration Date and Production Date has been removed from Workflows, as this option could cause complications with date filtering.
The Do Not Download Orders action for Workflows had a minor issue during execution. This has been corrected.
The Total Quantity counter on the mobile Receiving screen has been updated to display the equivalent UOM quantities of received pack types.
There was a display issue for Carrier and Shipping Option fields on the Shipment Order screen. This will no longer occur.
We've resolved an issue in the Billing module where the print option for billing contracts was causing line duplication, resulting in more lines being printed than exist in the actual contract.
Previously, the PO Type parameter Allow Update when PO Started did not prevent new product additions during receiving. This has been corrected.
We've fixed an issue with the filter dropdown on the 3PL Billing screen where selected criteria failed to display corresponding orders, resulting in an empty page. The filter now functions as intended. Specific changes include renaming Name to Billing Name, and ensuring filters for Client, Create Date, Period, and Warehouse work correctly.
License Plate with Inventory Printout had a minor issue of showing LP inventory that only consists of "Picked" or "Packed" status, this issue has been fixed and now the printout can be generated with the accurate data.
Previously, we calculated the total weight without considering the LP's empty weight in create label screen.Now, we include the LP's empty weight in the weight calculation.
To ensure the correct generation of International labels with FedEx, we have added a few fields to our requests.
The save buttons were misleading users when adding shipping documents to orders. We have fixed misleading points to prevent any data loss.
Use Production Date parameter for the Expiry Date was not working properly when "Production Date Tracking" is also enabled for the product. This issue has been fixed by showing the Production Date on the mobile screens and the expiry dates are calculated by adding shelf lifes to the scanned production date.
API/Webhooks
allocatedUOMQuantity, loadedUOMQuantity, packedUOMQuantity, pickedUOMQuantity, shippedUOMQuantity, uomRatio, uomPackTypeIdentifier fields have been added to the Get Shipment Order endpoint.
The List Shipment Order endpoint now includes an isPartial parameter to allow users to check which orders are operated partially.
Couldn’t Find What You Were Looking For?
Visit our Help Center to search for more documents!