Skip to main content

July 2025 - Release Notes

S
Written by Stephanie Kelley
Updated this week

Volume-Based Product Putaway

We are pleased to introduce Volume-Based Product Putaway, a feature engineered to optimize warehouse storage and maximize space utilization by suggesting the most space-efficient locations. A new putaway algorithm action enables the calculation of volume during putaway by using either standard product and location dimensions (H x W x L) for uniform items or specific, pre-defined volume fields for irregular goods.

To ensure the highest accuracy, location capacities are dynamically recalculated in real-time after any inventory transaction and whenever location master data is updated. You can further refine the logic with suggestion strategies and use the "Order By Location Empty Volume" option to prioritize either the tightest fit for maximum density or locations with the most available space.

For a comprehensive guide on configuration, please refer to our detailed knowledge base article: Volume-Based Putaway.


Adding "Picking Task Order By" to Job Types

The Order By section is now available in the Conditions tab of the Job Type creation/edit screen. It allows you to create a prioritized list of rules that dictates the order of items in a picking job.

For example, you can configure the system to first sort items by Location Aisle (to keep pickers in the same aisle), then by Location Level (to pick from top to bottom), and finally by Item Weight (to place heavier items at the bottom of a tote).

Default Behavior: To ensure a logical picking flow is always active, Logiwa IO automatically applies a default sorting rule to all new and existing Job Types:

  • Walking Path Priority (Ascending)

You can customize, add to, or replace this default rule to fit your specific operational needs.

For a comprehensive guide on configuration, please refer to our detailed knowledge base article: Configuring Job Type Order By Rules.


Instantly View Billing Charges on Orders

You can now instantly calculate and review billing charges associated with a specific Shipment Order (SO) or Purchase Order (PO). This enhancement provides an on-demand calculation of costs based on your approved billing contracts, allowing for quick cost verification without leaving the order page.

  • A new button has been added to the SO and PO screens. Clicking it will trigger a real-time calculation of all applicable charges.

  • The calculated charges are displayed in a clear, tabular format directly on the order screen.

  • The system will only consider billing contracts that have been marked as "Approved" to ensure financial accuracy.

  • New user-based permissions have been introduced to manage who can view these billing charges. This feature allows for on-the-spot verification of transaction costs, eliminating the need to navigate to the Billing page for charge information.

For more detailed information, please view our knowledge base article about this feature: Displaying Billing Charges in Shipment/Purchase Order Screens.


Integration Monitoring Module

We’ve introduced the new "Integration Monitoring" menu, which provides access to "Missing Shipment Orders", "Recent Errors", “Workflow Blocked Shipment Orders”, and “Product Listing Exceptions”.

  • The "Missing Shipment Orders" module enables users to view and export details of Shopify orders that failed to be downloaded to Logiwa, including the Error Reason and a link to the relevant Intercom Troubleshooting Article.

  • The "Recent Errors" module provides the number of occurrences and the number of affected Shopify orders related to recent integration errors, with links to the Intercom Troubleshooting Article.

  • The "Product Listing Exceptions" module helps users identify and report "SKU Difference" and "Multi Listing" issues between Logiwa SKUs and Seller SKUs on their Product Listings.

  • The "Workflow Blocked Orders" module provides visibility into orders that have been fully or partially blocked by a workflow rule, with a hyperlink to the related Workflow Screen.


FedEx Electronic Trade Documents (ETD) Process

LogiwaIO now supports FedEx Electronic Trade Documents (ETD), a feature designed to make your international shipping process faster, more efficient.

While printing physical commercial invoices, you can now transmit all necessary customs documentation, including your commercial invoice, company letterhead, and signature, directly to FedEx electronically.

Key Benefits:

  • Accelerate Customs Clearance: Submitting documents electronically allows for pre-clearance assistance from FedEx, significantly reducing the risk of customs delays.

  • Increase Efficiency: Save time and reduce manual errors in your fulfillment workflow by automating the customs documentation process.

Action Required: One-Time Setup for FedEx ETD

To enable this feature, you must complete a simple one-time setup to add your company's letterhead and signature images to your FedEx configuration.

How to Set Up:

  1. Navigate to the Integrations > Shipping > FedEx Carrier screen.

  2. Find your existing FedEx carrier integration in the list.

  3. Click the "..." menu on the right-hand side of your FedEx setup.

  4. Select the "Add Signature and Letterhead" option

  5. In the fields provided, enter the direct image URLs for your company's Letterhead and Signature. Logiwa will securely upload these to FedEx for use in all subsequent ETD submissions.

Once this setup is complete, Logiwa will automatically transmit customs data electronically by default for all your applicable international FedEx shipments.


What's New/Improved

  • Enhanced the mobile "One by One Count" workflow by adding the ability for users to report damaged products before the item is officially scanned and counted.

  • On the packing screen, the camera recording process has been improved. The recording will now begin when the first item of an order is scanned, rather than starting automatically when the order appears on the screen.

  • Implemented frontend permission checks for the "Transfer LP/Location" and "Transfer Product" actions, ensuring unauthorized users are now correctly blocked with an error message. These access settings can be adjusted on the Roles screen.

  • Enhanced the inventory/transaction webhook by adding note and adjustmentReasonName fields to provide more detailed context for inventory adjustments in external systems.

  • Improved the ‘List inventory by location zone and location group’ API endpoint by adding the warehouseLocationIsPreventInventorySync field, offering more granular detail on inventory sync status.

  • Improved the stability of the /Inventory/list API endpoint by enforcing a consistent sort order, which prevents duplicate or missing records when retrieving paginated data.

  • Users can now add more information to their pick list designs. This update makes custom fields from both the Shipment Order and its lines, specific retailer fields (like BOL, PO number, and Mark For), and the Location Barcode available in the document designer.

  • Improved the Replenishment Job Type configuration by ensuring that "Location Group Based" and "Zone Based" replenishment settings cannot be enabled at the same time.

  • Introduced new consolidated printout templates for Packing Lists and Location Labels, allowing multiple shipment orders or location labels for the same account to be grouped into a single print job.

  • Introduced a new "Amazon Pack List" template, allowing users to generate and print Amazon-compliant packing lists directly from the packing list printout screen.

  • Improved the rate shopping process for multi-package shipments with FedEx Smartpost and UPS Surepost by sending individual requests for each package to ensure accurate rates.

  • The Easypost integration has been enhanced to improve how carrier accounts are identified and used. Logiwa will now use a more descriptive name for Easypost carrier accounts and store Easypost's unique account ID. This will ensure greater accuracy when multiple accounts from the same carrier (like USPS,UPS etc.) are connected.

  • Introduced support for the Passport carrier through the Easypost integration, adding multiple new shipping services.

  • The shipping label logic has been updated to support two configurations:

    • When "Warehouse Address" is selected in the carrier setup, the client name is used as the Company Name on the label.

    • When "Create New Address" is selected, the entered Company Name is displayed on the label instead.

  • Enhanced the Carrier Shipment Details report by adding a "Zone" information column, with data currently available for the Shipium Carrier Integration.

  • Rate Shopping presets now only display carrier services marked as "active" in the carrier integration settings, ensuring inactive services are excluded from both setup and rate selection.

  • Enhanced the Easypost integration to exclude customs information for domestic shipments, preventing errors for orders without a specified sales price.

  • Standardized the "Carrier" and "Shipping Service" columns on the "Shipped & Cancelled" page to match the display format of the "Order Backlog" page.

  • Improved the label generation process by automatically using a default phone number (999-999-9999) when a customer's phone number is missing.

  • Introduced a new API endpoint that supports shipping multiple License Plates (LPs) in a single call.

  • Resolved an issue in the retailer picking flow to ensure UCC labels are correctly managed after a 'missing' item action triggers a reallocation of inventory.

  • Enhanced the Custom Branding feature by separating the "Text and Icon Color Code" and adding two new hover state color options for the search bar.

  • Clarified the wording in the welcome email for new users on accounts with custom branding.

  • Improved the performance of Consolidated and Detailed Billing Reports to prevent timeouts.

  • Enhanced the Open API Swagger documentation by adding character-limitation information to the top 10 most-used endpoints.

  • Consolidated all Open API endpoints into a single Swagger page.

  • Updated the ShipStation integration to ignore digital products.


What's Fixed

  • Resolved an issue where a corrupted data relationship between inventory and its associated tasks caused orders to get stuck with a "Packing Started" status.

  • Resolved a critical bug that prevented updates to product pack types from being saved correctly through the UI, API, or Excel import.

  • Fixed an issue where the system would generate a "Call Stack Size Exceeded" error when validating serial numbers against formats that used an "OR" condition.

  • Corrected the list shipment order API endpoint to ensure it returns a proper error when it fails to retrieve shipment information.

  • Fixed an issue in the Putaway Algorithm UI where using the "is not empty" comparator for a text field incorrectly required a value to be entered.

  • Resolved an issue on the Mobile Picking "Pick to Location" screen where using the filter to find job codes would cause a timeout.

  • Fixed an issue where reporting a 'missing' item during an AI-optimized picking task could cause the associated job to become invisible and the task unpickable.

  • Corrected the Putaway Algorithm's "Check Location Capacity" action to properly prioritize locations with defined LP capacities and fixed the non-functional "LP Count in Location" sorting option.

  • Fixed an issue in the Purchase Order Create/Update API where identical product lines were not being merged.

  • Fixed a bug that caused an incorrect "LP/Tote has inventory in different location" error during replenishment.

  • Fixed an issue where the location for a Parent LP was not correctly updated on the LP Numbers screen after being transferred via the mobile app.

  • Fixed an issue where the packing slip selection was incorrectly using the default slip instead of following the complete fallback hierarchy.

  • Fixed a sequencing issue in the Identical Order Packing flow to ensure that packing slips and shipping labels now print in the same, matching order.

  • Fixed an issue where the "Next Period Start Date" in billing contracts was advancing incorrectly after the contracts were run manually.

  • Fixed UI color inconsistencies when Custom Branding is active.

  • Fixed an issue in the change log where updates to billing fees were incorrectly attributed to the creator of the fee.

  • Fixed a service error that occurred when applying the "Ship To" condition to "Per Label" shipment fees in billing configurations.

  • Fixed an issue where "Per Label" shipment fees were calculated based on the master tracking number instead of the proper count of individual labels.

  • Improved billing reports to ensure the decimal value details for "VAS Quantity" is displayed fully.

  • Fixed a weight calculation issue in LP Based Label Generation where the weight of the license plate was incorrectly added to the weight of the products within it.

  • Corrected an issue with EasyPost integrations where the total package weight was inaccurately sent for each customs item, causing declaration errors.

  • Fixed an issue in the Techship integration where the system was incorrectly summing rates for the same shipping service from different accounts.

  • Fixed an issue on the carrier integration setup screen where both an API Key and an API Secret were incorrectly required for eHub and Shipium integrations. Users can now successfully create these carrier setups by providing only the necessary credentials.

  • Fixed a bug to ensure that the Tax ID is correctly included in label requests for backorders.

  • Fixed an issue where discounts applied to store orders were not being correctly reflected on commercial invoices and customs declarations.

  • Fixed an issue where items marked as "Is Not Declared to Customs" were still included in customs declarations

  • Enhanced security by preventing users designated for API access from logging into the web interface.


API Deprecation Notice

Effective Date: October 1, 2025

The following API endpoint is being deprecated and will be removed on October 1, 2025:

  • GET /v{version}/Report/WarehouseTask/i/{index}/s/{size}

This endpoint is being replaced by three new, more specific endpoints to provide better-defined responses.

New Endpoints

Please update your integrations to use the following new endpoints:

  • To get count task details, use: GET /v{version}/Report/WarehouseTask/count/i/{index}/s/{size}

  • To get order operation task details, use: GET /v{version}/Report/WarehouseTask/order-operation/i/{index}/s/{size}

  • To get replenishment task details, use: GET /v{version}/Report/WarehouseTask/replenishment/i/{index}/s/{size}


Open API Page Notice

Our API page at https://mydeveloper.logiwa.com/ will now be updated in real-time, directly reflecting all changes. This eliminates the need to separately track the Swagger page for the latest updates.

Did this answer your question?