We are excited to announce an upcoming release scheduled for Tuesday, August 6th. This planned maintenance will bring new features and enhancements aimed at improving your experience with Logiwa IO. In this release, we are introducing Cam Recording on Packing, dynamic replenishment capabilities, and several other updates designed to streamline your inventory and shipping processes. Please read on to explore the details of these exciting new features and improvements.
Cam Recording on Packing
Introducing Cam Recording on Packing in Logiwa IO, providing reliable recording of packing operations to ensure order accuracy and quality.
Key Features:
Seamless Integration: Connect IP/RTSP cameras to your Logiwa IO accounts, warehouses, and packing stations.
Automatic Recording: Captures the packing process from start to finish without manual intervention.
Order Association: Each recording is linked to the order code and timestamp, sent to a user-provided API to receive and store the recordings. Please note that Logiwa IO does not store the recordings.
Contact your CSM for more information about this exciting add-on feature.
Dynamic Replenishment
Dynamic replenishment optimizes inventory management at picking locations by maintaining product levels between a defined minimum and maximum capacity, by considering product’s demand.
Introduced the ability to define minimum and maximum replenishment levels for each product, ensuring optimal stock levels are maintained.
Enhanced location settings to designate source and target locations with specific replenishment types, improving accuracy in inventory movements.
Added a dedicated job type for dynamic replenishment with options to suggest alternative target locations, increasing flexibility in the replenishment process.
Enabled the creation and assignment of putaway algorithms specifically for dynamic replenishment, allowing users to tailor replenishment strategies to their operational needs.
Integrated dynamic replenishment tasks with the mobile app, streamlining the execution of replenishment activities and enhancing on-the-go operations.
Developed a dynamic replenishment report that provides comprehensive insights into replenishment processes, including product levels, quantities, and task statuses, aiding in better decision-making.
Please see the following knowledge base articles for more information about the dynamic replenishment feature:
Transfer Processes from Inventory by Location
We have enhanced the Inventory by Location screen with two new Transfer buttons: Transfer Product and Transfer Location/LP. These improvements include detailed inventory status checks and the ability to transfer allocated inventory. Users can now select single or multiple lines for product transfers and utilize a toggle for splitting pack types. The Transfer Location/LP button supports various flows between LPs and locations, with mandatory warehouse selection and error messages for mismatches. These enhancements aim to streamline inventory management, ensuring accurate and efficient transfers.
Allow Unique SKU Barcodes
A new Allow Unique SKU Barcodes parameter has been added to Client settings, which ensures that SKU barcodes are unique during product creation & editing, via UI, Excel imports, Open API operations, and downloading products from sales channels.
This validation prevents duplicate barcodes across selected client’s products.
Further information can be found in this article.
What’s New/Improved
A Shipment Plan selection step has been added to the Mobile Loading screen. This development enhances user experience and efficiency by simplifying the loading process and reducing manual entry errors.
All Open, In Progress, Loading Started Shipment Plans will be listed and users can now search and/or select a Shipment Plan from a list.
Two new fields have been added to the Transaction History Report in Logiwa IO: Algorithm Name and Algorithm Rule Name. The Algorithm Name field displays the name of the allocation algorithm applied during the allocation process, while the Algorithm Rule Name field shows the specific rule within the algorithm used for the allocation. These enhancements provide users with enhanced visibility and improved tracking by allowing them to easily identify which allocation algorithm and rule were applied, thus offering greater transparency and insight into the allocation process.
The phone number format validation on the UI for creating shipment orders has been removed. Users can now enter phone numbers in any format when creating shipment orders through UI, API, and channel integration. This change aims to improve user flexibility and convenience.
The insert order endpoint has been updated to include new fields: carrier, shipping option, carrier setup name, and isSetUnmatchedShippingOptionAsRequested. The new logic allows for handling unmatched shipping options based on the value of isSetUnmatchedShippingOptionAsRequested.
The user interface for integration management has been updated to support categorizing integrations by type. Users can now distinguish and manage integrations as Logiwa Integrations, Partner Integrations, and Custom Integrations, providing a more organized and efficient workflow.
The shipment order insert endpoint has been updated to include a new field ChannelSetupIdentifier. This allows for the assignment of the correct channel setup during the order creation process, improving the accuracy and efficiency of shipment handling.
The system has been updated to retrieve currency information from the responses from TechShip, ShipStation, and Stamps. This enhancement allows for accurate processing and display of currency data for shipments, improving the overall efficiency and accuracy of the system.
The Packing Station screen now automatically displays items in alphabetical order based on the product SKU. This change ensures a more intuitive and efficient packing process for users by reducing the time spent on locating items.
Product Look Up Screens: The field Product Name has been added. This addition allows users to easily view and identify products by name in the product look up screens, enhancing usability and efficiency.
A restriction on the Job Management screen has been implemented to limit job cancellations to a maximum of 10 jobs at a time to prevent performance issues and disruptions to other operations.
At the billing module now users can set "0" as a price in any pricing field within the billing contract's fee cards.
Enhanced the "Edit Billing Screen" with advanced filtering options. Users can now filter billing contract fee cards by operation type, fee calculation type, fee name, fee by, and charge by. The summary part also has its filter.
A new client field has been added to the data source for the Packing List printout.
The pack type selection bottom sheet in the mobile app's receiving, count, and transfer screens has been enhanced by displaying the equivalent unit number for each pack type, enabling users to accurately identify and select the correct pack type when different pack types share the same barcode value.
The "Tracking Numbers" field in the "Set Shipment Instructions" action has been modified to be conditionally editable. The field is now non-editable by default and becomes editable only after a shipment method is selected from the dropdown.
A new "LP Carrier" condition has been added to the putaway algorithm. This allows users to specify actions based on the carrier associated with the LP number.
Replenishment Phase column has been added to the Task Details Reports. It allows users to understand whether the replenishment is a pick or a put task.
Replenishment Report role permission has been added under the Roles, Inventory section in Reports & Analytics.
What's Fixed
Email validation error on Shipment Order creation is fixed. Users were receiving "Email is not valid" errors for emails with uppercase letters or hyphens.
This update fixes the rate display in the packing station for carriers without master tracking numbers. Now, the total rate of all packages is shown instead of the first package, ensuring accurate shipping costs.
The carrier dropdown on the create label and packing station screens has been improved to handle long text properly. The new design ensures that the full text of carrier names is visible or accessible, improving the user experience and reducing confusion during carrier selection.
A bug was fixed on the packing station where the "Get Rate" button did not include product information in the rate request. This fix ensures that all relevant product details are sent, resulting in accurate shipping rates.
Fixed an issue with the "Don't Match These Products" button on the product listing page to ensure it functions correctly and allows users to manage their product listings effectively.
Removed the number of shipping and store integration information from the main screen to simplify the interface and improve user experience.
A bug was fixed on the create label screen where the "Ship From" field was not displaying the warehouse address correctly when rate shopping was selected as a carrier.
New logic formats phone numbers to the correct format before sending to carriers, ensuring valid and consistent phone numbers for integration. Supports various international formats, converting them to the carrier's required standard.
The "Create Non-Existent Product When Orders are Downloaded" setting in the Shopify channel integration has been fixed. This setting now properly creates and links new products with product listings during order downloads from Shopify.
The packing process has been enhanced to handle situations where kit components are packed into different packages. In such cases, a master tracking number will be generated and sent to the shipment channel, ensuring that all kit components are correctly associated and the shipment process is not disrupted.
When the inventory is updated with count and if there is a pack type conversion, the system previously changed the UOM pack type. This issue has been fixed so that the UOM pack type will no longer be changed during inventory updates with count.
When the count job has canceled lines, it previously stayed in the started status even though all other lines were completed. This issue has been resolved, and the count job will now correctly show as completed.
When users try to create a backorder for a shipment order in “Shortage” status, the frontend previously showed a warning popup indicating that only Shortage and Open Orders can be used for “Create Backorder.” This issue has been fixed, and users can now correctly create backorders for orders in Shortage status.
Restrictions now prevent selecting "Pick to Location" (as Mobile Screen Type) for "Single SKU Cluster Pick" and "Pick and Sort" for "Single Item" and "Identical Item" job types. This ensures logical consistency and enhances the usability of the Picking Job Type creation process.
Multi Item Jobs were always being listed on the Pick and Sort screen (Mobile Screen Type selected on the Job Type screen was not taken into account). This issue has been corrected.
Shipment Orders couldn't be found by entering related Tracking Number or Channel Order Code at the Return Station while Returning with SO. This issue has been corrected.
A performance issue in the billing module that caused the calculation of the billing contract function to exceed 60 seconds and display errors was resolved. Calculations are now complete within the time limit.
Wave Rule Auto-Deletion issue is resolved. Now, users can set up “Delete The Jobs If Not Started” and delete the pending jobs based on the entered Delete Method.
The issue in the Billing Module's Pick&Pack operation type is resolved by adding "split-second" precision to task completion times. This ensures accurate product counting and billing when multiple SKUs are picked quickly.
The Billing Module's Consolidated Billing Report was not correctly consolidating the label charges. Now, charges for "Percentage," "Label + Percentage," and "Label Charge" are combined into a single line, with the "Unit Price" column displaying as “1”. Users can check the "Total Price" column to see the actual price.
Fixed an issue in the replenishment module where the system failed to recognize existing stock in the target location when replenishment setup and inventory had different pack types.
The issue causing workflow failures when multiple states were selected has been fixed, now “contains” comparator works fine when multiple states are selected in the State & State (Billing) conditions.
The issue causing duplicate LP Numbers and errors during file import has been resolved. The system now correctly identifies and halts the import process if duplicate LP Numbers are found, ensuring unique LP Numbers and allowing non-recurrent LP Numbers to be imported successfully.
Fixed an issue in the Open API product creation method to ensure the isInsert parameter reflects the correct value passed in the API request.
Corrected the "Price per Item" calculation for components of kit-to-order items in shipment orders. Previously, the entire kit price was incorrectly assigned to each component, causing inflated values. Now, the kit price is accurately divided among the components to reflect the correct pricing.
API/Webhooks
Custom fields have been added to "ShipmentInfo" array in "List Shipment Order" endpoint.
isLocked and preventAllocation parameters have been added to the List inventory API.
New fields have been added to the count plan, location details, and SKU details in Logiwa IO: InventoryUpdatedDateTime and InventoryUpdatedBy. These fields will be triggered when the related line status changes to InventoryUpdated. InventoryUpdatedDateTime records the exact date and time of the inventory update, while InventoryUpdatedBy captures the user who performed the update.
Two new fields have been added to the Transaction History Report in Logiwa IO: Algorithm Name and Algorithm Rule Name. The Algorithm Name field displays the name of the allocation algorithm applied during the allocation process, while the Algorithm Rule Name field shows the specific rule within the algorithm used for the allocation. These enhancements provide users with enhanced visibility and improved tracking by allowing them to easily identify which allocation algorithm and rule were applied, thus offering greater transparency and insight into the allocation process.
A new "Note" field has been added to the "Create Inventory Endpoint." This field allows users to add additional information when creating inventory records. The "Note" field is now also available in the "Transaction History Report," enabling users to track and review any notes associated with inventory transactions. Usability has been improved by including Code counterparts for fields that previously only worked with Identifiers, making it easier to work with and reference these fields in various processes.
We have resolved a bug in the order status change webhook in Logiwa IO. Previously, the webhook failed to send an event notification when the order status changed from "Loading Started" to "Ready to Ship." This bug has been fixed to ensure that the webhook now correctly triggers an event for this specific status change.
Sincerely,
Logiwa IO Team