NEW FEATURE HIGHLIGHTS
Sequential Putaway
A new Sequential Putaway workflow guides operators through putting away an entire parent LP's child LPs in a single guided session. Operators scan the parent LP to start a session, and the system suggests each child LP's destination in turn, present in the order of walking path priority of suggested locations with options to transfer, skip, request another suggestion, or cancel along the way.
Sessions can be resumed if interrupted, and a soft reservation layer prevents two operators from being suggested conflicting locations at the same time: each session's reservation expires 60 minutes after the last operator action (placement, skip, suggest another, or bypass), automatically refreshing on every subsequent action. The underlying session engine, suggestion logic, and resume/abandon endpoints are in place, with the mobile screens and a new "Sequential LP Putaway" role-access permission rolling out alongside it. (49853)
For more information, please the Sequential LP Putaway Article Collection.
Max Inventory Capacity for Locations
Warehouses can now define and enforce capacity limits at the individual location level. A new Location Capacity Type can be set to either Max Unit Quantity or Max Pack Quantity, each paired with a maximum capacity value, and if configured, the related Putaway Algorithm action checks this limit before suggesting a destination, helping prevent locations from being overfilled. Capacity Mode and its limit can be configured per location on the Location Setup screen, imported or updated in bulk via Excel, or set and retrieved through the Open API. (51502)
For more information, see: Max Inventory Capacity for Locations
Auto Remove LP After Transfer
Building on the previously released Auto Remove LP capability for replenishment, inventory moved into a designated location through the Transfer LP/Tote flow or the Directed Putaway LP Putaway flow can now also be automatically stored without an LP association once the operation completes. Operators continue to scan the LP exactly as they do today; Logiwa IO checks the confirmed destination location's configuration at completion and removes the LP association automatically when enabled, with no change to the mobile scan flow. The Auto Remove LP After Transfer setting can be configured per location on the Location Setup screen, imported or updated in bulk via Excel, or set and retrieved through the Open API. (51491)
For more information, see: Auto Remove LP After Transfer
Zone Priority & Check Max Locations Per SKU
Two new tools give warehouses finer control over how putaway and replenishment tasks are distributed across zones. A new "Zone Priority" Order By method lets admins sort candidate locations by their zone's configured priority, in ascending or descending order, so the algorithm always tries the highest-priority zone first; zones with no priority configured are always sorted last and existing rules are unaffected unless this order by is explicitly added to the algorithm. Alongside it, a new "Check Max Locations per SKU" action caps how many distinct locations a single SKU can occupy within a zone: once a SKU reaches that cap, the engine stops opening new locations for it in that zone and cascades to the next priority zone, while locations that already hold the SKU remain eligible for top-up regardless of the cap. Both options are available for putaway and replenishment algorithms, are additive options to existing rules, and the Location Zone screen has been updated with the corresponding Zone Priority and Max Locations Per SKU fields. (49852)
For more information, see :Zone Priority & Check Max Locations Per SKU
Merge Orders
Logiwa IO now supports merging multiple shipment orders into a single order for fulfillment. Order Merge Rules let warehouses define which orders qualify to be merged, and Order Merge Wave Rules trigger the merge automatically as part of wave allocation; a new MergeOrder webhook notifies external systems when a merge occurs, and orders can be unmerged or have their master order unlinked when needed. Shipment Orders and Shipment Order Lines carry new fields to track merge relationships, a new set of Shipment Order cancel reasons supports merge-specific cancellation scenarios, and allocation logic has been adapted to handle merged orders correctly. Since an original order can no longer be updated once it has been merged, store updates received for that order now add a Store Update Note to both the original order and the merged order to flag that a change occurred, and unmerging an order automatically re-fetches the latest details from the originating store channel. When a merged order ships, a Send Shipment Info fulfillment message is dispatched to each original store channel for its respective original order, with the correct line items, tracking number, carrier, and shipped quantities. Reporting has been extended to match: the Wave Log Report includes new merge wave run columns, and the Shipment History, Transaction History, and Serial Number Tracking reports all display the Original Order Code as a column and filter, alongside the Original SO Code, Store Update Notes, and Is Store Updated fields now exposed on the Shipment Order Line Details endpoint. Order merge rules currently in use by a wave can no longer be deleted, the "Same Order Date" merge condition now matches on date only instead of requiring an identical timestamp, and Merge Order wave rules are capped at 15,000 orders per wave, processed oldest-first by creation date. Update, cancel, and delete actions are restricted on shipment orders that have already been merged to protect data integrity, and the wms/shipmentorder/create webhook now fires correctly when a merge order is created.
For more information, see: Setting up and using Order Merge for Shipment Orders
Print & Apply
Warehouses using print-and-apply hardware at the packing station can now route LP label printing to happen at packing completion instead of relying on carrier or pre-produced labels. A "Print & Apply on Packing" toggle on the Location screen — available in both the Create and Edit panels, and surfaced on the Packing Station Dashboard's station picker — marks a packing station location as print-and-apply enabled. When active, Multi Box Packing prints the LP label for every package at packing complete and suppresses carrier and pre-produced label output, while all existing packing behavior is preserved for locations where the toggle is off. Label printing at the packing station has also been made more precise: instead of always printing every attached label, the system now prints only the labels the backend specifies for the order, with the option to print all attached labels when instructed to do so.
For more information, see: Setting up Print & Apply for Packing Stations
Multi-Item Bulk Pick Short Resolution
Warehouses can now resolve pick-shorted orders in bulk through a new guided multi-step flow directly from the Shipment Order screen. When pick-shorted orders are selected, the Resolve Pick Short action offers three resolution paths: create a new Resolution Job with a searchable job type dropdown, merge the unresolved tasks into an existing Resolution Job from a paginated job list, or cancel the pending picking tasks. All three paths complete within the dialog without any additional manual consolidation steps. Resolution jobs are now identifiable across the platform via a new column and filter on the Job Management screen, a visual indicator and filter on the mobile Pick to Location job list, and a new Pick Short Consolidation printout action available directly from Job Management.
For more information, see: Retain Allocation During Missing (Pick Short Scenario)
Role-Based Field-Level Security (FLS)
You can now restrict specific roles from viewing sensitive carrier and account data using three ready-made Restrictions: Carrier Cost (shipping rates, carrier fees, and related cost information), Carrier Account Data (carrier account numbers and billing details), and Rate Shopping Data (rate shopping usage and selected rate shopping shipping options). Once turned on for a role, a Restriction applies consistently across the UI, the API, and Excel exports. Restrictions are configured per role from Settings → Users & Roles → Roles; in this release, only the account's Owner user can manage them, though any user with role-view permissions can see which Restrictions are assigned to a role. Delegating Restriction management to other roles is planned for a future release.
For more information, see: Role-Based Field-Level Security (FLS)
WHAT'S NEW & IMPROVED
The pack type conversion capability introduced for Replenishment and Transfers is now available on the mobile Directed Putaway screens as well, for both Bulk and One-by-One flows. Associates with the Convert to UOM role permission can turn on a new "Convert Pack Type to UOM" toggle from the Other Actions menu on directed product putaway screens. (51559)
Added visibility into pack type conversion on the Replenishment Task List by exposing the Pack Type Conversion Applied field and adding a corresponding column to the UI table. (51607, 51642)
Added Location Zone Filter & Search, making it easier to locate zones when managing locations. (51703, 51379)
Wired the Replenishment Wave Filter Panel's Location Zone and Location Group dropdowns to warehouse-scoped endpoints, ensuring only zones and groups relevant to the selected warehouse are shown. (51643, 51595)
Added Warehouse, Job Code, and Note columns to the Count Location Details and Count SKU Details Excel export. (51649)
Moved the "Kit-Components" bulk import option from the Import section to the Update section on the Products screen for clearer placement. (51648)
Lot Number, Expiry Date, and Production Date now render as read-only across the Add, Adjust, and Remove sidebars on the Inventory by Location screen, providing clarity on the inventory being edited. (51647)
Improved the Return Station search flow to properly handle merged or canceled shipment orders. Operators are now alerted with a clear warning and guided to use the correct parent order code, preventing invalid returns. (51809, 50352)
Added an "Override Serial Number Scanning on Packing" toggle to the Shipment Order Type setup, and updated the packing station to skip the serial scan step and unlock serial import for orders where the toggle is enabled. (51532, 51531, 51523)
Added timezone parameter support to the Pick/Pack Short Printout Export endpoint and passed the user's timezone through on the frontend, so exported printouts reflect the correct local time. (51701, 51700)
Replaced the Order Tag filter dropdown with a paginated, searchable lookup on both backend and frontend, removing the previous behavior of loading the entire tag list at once. (51361, 51360)
The screen recording option in the header menu has been re-enabled and restored to its previous behavior. (51619)
Added a confirmation prompt when refreshing or closing an edit screen (User, Role, and Billing Contract) with unsaved changes, to help prevent accidental data loss. (47873)
Added the ability to export the Client table to Excel, including key configuration and notification settings, for easier bulk review. (30591)
Added Retailer PO as a selectable field in the Carrier Setup Label Messages and Commercial Invoice No Reference dropdowns, letting warehouse admins route retailer PO data to carrier labels and customs documents. (51586)
Aligned the Techship Get Rate request with the Get Label request by including full SKU-level item details, so estimated rates now match what's charged at label creation for international shipments. (51584)
Added carrier logo and partner name to the rate shopping response, allowing the Carrier Connection column on the Create Label and Packing Station rate comparison modal to display carrier branding. (51581)
Extended Integration Monitoring's Health Overview and Channel Setup Details screens to include Custom Channel setups, giving visibility into Open API order health alongside native channel integrations. (51551)
Extended the Product changelog to track create, update, and delete events on inventory sync rules, whether made through the UI, API, or Excel import. (51480)
Added a Simulate option to the Inventory Channel Allocation section, letting warehouse admins preview synced quantities for a hypothetical inventory value before committing to a sync cycle. (51479)
Added fallback logic to the Techship integration so international shipments use the free-text state/region value when a standard state code isn't available, correcting missing province data sent to the carrier. (51448)
Redesigned the Other Rates pop-up on the Create Label and Packing Station screens to display the carrier setup name alongside each rate, making it easier to distinguish between multiple setups for the same carrier. (49441)
Added a Return Label Settings section to the eHub carrier connection setup and added eHub to the list of supported return label carriers, so return labels can now be generated automatically for eHub on both the Create Label screen and the Packing Station. (51484, 51652)
Fixed an issue at the packing station where scanning a tote multiple times caused pick short labels to be re-printed for orders that had already received a label. The system now tracks whether a pick short label has been printed per order, and only triggers label generation when at least one order in the tote still has an unprinted pick short label. (51759)
Fixed an issue at the packing station where scanning a tote containing an Identical job with pick-shorted orders did not trigger the pick short handling flow. The pick short detection logic, previously limited to single job types, has been extended to cover identical job types as well, ensuring packing stations correctly identify and handle pick shorts regardless of job type. (51702)
Updated the pack short resolution flow so that when a pack short is triggered at the packing station, all allocated products for the order — both scanned and unscanned — are transferred to the hospital location. Previously, only scanned products were moved, leaving unscanned allocated items in their original locations and requiring manual inventory correction. The pack short label is unchanged and continues to display only the unscanned products. (51672)
PERFORMANCE IMPROVEMENTS
Reduced PO Receiving Report load times when damaged quantity including receivings are viewed. (51374)
Resolved a query timeout on the Available to Promise Report export when fetching the first page with no filters or only Client/Warehouse provided. (51593)
Optimized serial number checks during packing and import processing to eliminate N+1 query patterns, improving performance for serialized order handling. (51499)
Improved the reliability of certain large-scale billing calculations to help prevent processing failures. (51580)
Viewing billing charges on Shipment Order and Purchase Order screens no longer requires waiting for an on-screen calculation — the report now generates in the background and can be downloaded as an Excel file. (51368)
WHAT'S FIXED
Fixed an issue where PO lines were not sorted alphabetically after Excel import, causing PO lines to be viewed in random order on mobile during receiving. (51635)
Fixed an issue where the Zero Inventory Location auto-update status was not triggered on count completion. (51515)
Fixed missing Excel import validation when converting products with existing inventory into kit-to-order items. (50165)
Fixed an issue where deleting a Job Type assigned to a Wave Rule was allowed, causing UI corruption (list rotating) on the Wave Rule edit screen. (44328)
Fixed an issue duplicating location label printouts when the location code contained an underscore followed by text. (36974)
Fixed an issue on the mobile receiving screen where the success pop-up notification failed to appear after successfully completing a Purchase Order configured with Auto Complete and 1-1 Receiving. (51192, 51440)
Fixed an issue that prevented importing locations with valid special characters and spaces in their location codes. Single quotes remain the only restricted character. (51867)
Fixed an issue where the pick short pop-up did not appear at the packing station when scanning a tote containing pick-shorted orders. (51704)
Fixed an issue where shipment history records disappeared from the Shipment History Report after a product's pack type was deleted post-shipment; historical records now retain their original pack type data. (51533)
Fixed picking task sequencing so tasks at the same location are grouped together as a secondary sort tie-break regardless of which primary Order By method is configured, reducing unnecessary picker travel. (51509)
Fixed an issue where the Order Type section on the Job Type Edit screen remained editable for cluster-pick-enabled job types; the section is now read-only when cluster picking is active. (51446)
Added the SO Line Custom Field Text Box 3 fields to the Shipment Order export, resolving missing data in exported files. (51430)
Fixed an issue preventing users from importing a second serial number for shipment order lines via the Serial Number import screen. (51347)
Fixed an issue at the packing station where the scale carried over the previous order's weight onto a newly scanned order in high-volume, multi-scale environments; the system now waits for a weight change before assigning weight to a new order. (49236)
Added mandatory validation to the Job Type setup screen so a Group By picking method must be selected when grouping by Location Zone or Area Type, preventing downstream allocation errors. (49004)
Added warehouse-scope validation to mobile picking and license plate endpoints to prevent cross-warehouse data access or actions. (45439)
Fixed a scheduler error where warehouse task deletion jobs were skipped when a user's local scheduled time crossed midnight in UTC; the scheduler was adding an extra day to the next run date instead of executing on schedule, and now runs reliably at the specified local time regardless of UTC offset. (51705)
Fixed a misleading error message shown to mobile pickers who lack access to a client: Pick to Location and Pick & Sort now display "You don't have any access to complete process for the related order's client" instead of the incorrect "This inventory not Found" message. (51573)
Fixed an issue where Shipment Plans without order details, or plans with all orders shipped, could not be updated to the correct status, leaving plans stuck at "Loading Started" or "Loading Completed." (33963)
Fixed an issue where Custom Branding emails could contain broken links when the branding configuration was incomplete. (51626)
Fixed an issue that prevented users with view-only access to Roles from opening and viewing role records. (51449)
Fixed an issue where the Product Listings search box returned no results when the exact, full SKU code was entered, requiring users to type a partial code instead. (47549)
Fixed an issue where initiating a return for a shipped serialized order incorrectly returned a "Serial Number Already Exists" error, blocking the return entry flow. The root cause was in the Packing and Shipping layer, where second-time processing of a serial number was overwriting the existing tracking status record with an incorrect state that the return validation logic then rejected. The serial number lifecycle handling has been corrected so that packing and shipping leave the tracking status in a valid state that the Return Station accepts without conflict. (51639)
OPEN API UPDATES
Extended Auto Remove LP After Transfer logic coverage to the Open API. (51519)
Added Location Capacity Mode support to the database and Open API, enabling capacity limits to be created, retrieved, and updated through the Open API. (51543)
Fixed an issue where the Open API was missing the Return Reason field. (47488)
Improved the ShipmentOrder/Create endpoint (v3.1) to return a specific validation error — instead of a generic Bad Request — when line note fields exceed the 300-character limit. (44013)
Fixed an issue where updates to a product's isUseItemsOwnBoxForShipping packing setting via the Product/update endpoint (v3.1–v3.4) returned a success response but were not reflected in the Logiwa UI. (32924)
Added a new endpoint (GET /v3.1/Product/listing/list) to retrieve Product Listing records programmatically, closing the gap where this data was only available via the UI or export files. (51682)
Added channelOrderLineId support to the Create Shipment Order Open API endpoints (single and bulk), allowing integrations to supply channel-level line identifiers at order creation. (51637)
Added carrierCode and shippingOptionCode to the ShipmentOrder list endpoint response, removing the need for secondary lookup calls to resolve these values. (51483)
Fixed an issue where editing a Shipment Package's code did not update the carrier integration layer, causing webhooks and the Open API to continue returning the outdated code. (51444)
Aligned the Patch Product Open API endpoints with their ShipmentOrder equivalents by adding path-parameter identifier support and a bulk identifier/document envelope format, and fixed patch failures on the carrierPackageIdentifier, upc, and pack type list fields. (51615)
Extended the Execute Picking endpoint (POST /v3.1/WarehouseTask/pick) to support automatic LP creation at pick time. A new optional targetLicensePlateTypeCode field has been added to the request — when the submitted targetLicensePlateNumber does not exist in the system and a valid LP type code is provided, the system automatically creates the LP using the submitted number, the task's warehouse, the resolved LP type, and the target location, then continues the pick operation without requiring a separate LP creation call beforehand. If the LP is not found and no type code is provided, a descriptive validation error is returned. (50840)