Auto Populate Attributes During Receiving

The mobile Receiving flow can now auto-fill Lot Number, Expiry Date, and Production Date on the mobile receiving/select product screen when the scanned product and pack type match exactly one attribute combination on the Purchase Order line, cutting manual re-entry and transcription errors at receipt.

When a PO line has multiple possible attribute combinations — or none at all — associates can resolve the correct values by picking from a filtered list or entering them manually, and One-by-One Receiving now retains a confirmed set of values across repeated scans of the same SKU instead of prompting for re-confirmation on every unit.

The capability is enabled per Purchase Order Type through a new "Auto Fill Attributes on Receiving" toggle on the PO Type Create/Edit screen, and defaults to off for all existing and new PO Types. (51834)

For more information, please check the article: Auto-Populating Lot, Expiry, and Production Date During Receiving

Carrier Errors Page — Carrier Integration Monitoring

Integration users can now see carrier label generation and rate call failures directly in the UI — previously, there was no record of these errors to review. The Integrations navigation has been reorganized into Plugin Integration, Channel Monitoring, and Carrier Monitoring sections, with the new Carrier Errors page's Label Generation and Rate Call tabs available under Carrier Monitoring. This is the first release of the feature; upcoming releases will add request/response visibility and an error-guidance drawer. (51261, 52072)

For more information, please check the article: Understanding the Carrier Errors Page

Manufacturer Product Identifier & Carrier Shipper/Receiver Classification

Ahead of the EU De Minimis removal , Logiwa IO now supports capturing a Manufacturer Product Identifier on products — available from the Product screen, Excel import/update, the Open API, and passed through to custom carrier label and rate requests for compliant customs documentation. Separately, UPS shipment requests now include Shipper and Consignee type classification, ensuring shipments are correctly classified for international and customs handling. (51843, 51845, 51846, 51848, 52050, 51831)

For more information, please check the article: EU De Minimis Removal

Role-Based Field-Level Security (FLS)

Building on last month's release, Restriction management can now be delegated beyond the account Owner.

From Settings → Users & Roles → Roles, an Owner can grant any role a new “Manage Restrictions” permission; once granted, users in that role can assign or remove Restrictions on their own, without needing the Owner for every change. Granting or revoking the Manage Restrictions permission itself remains Owner-only. Restrictions themselves are still managed the same way as before — by enabling or disabling Logiwa's predefined Restriction groups (Carrier Cost, Carrier Account Data, Rate Shopping Data) for a role.

On the Shipment Order Create and Edit screens, fields covered by an active Restriction now appear disabled and without a value. A new info tooltip explains why the field can't be viewed or edited. (51879, 51880, 51027, 51022, 52066)

For more information, please check the article: Role-Based Field-Level Security (FLS)

• Added a Tracking Number field to the RMA Create sidebar’s Shipment tab and enabled it on the RMA create and update flows (UI and Open API), so a tracking number entered or sent with an RMA is now saved and returned instead of being silently dropped. (52135, 32399)

• Added the return tracking number as a valid scan identifier at the Return Station’s SO lookup tab, so staff can pull up a Shipment Order by scanning its return tracking number instead of searching manually. (32405)

• Added the RMA tracking number as a valid scan identifier at the Return Station’s RMA lookup tab, so staff can pull up a Return Order by scanning its tracking number instead of searching manually. (51774)

• Added support for using a Kit-to-Stock product as a component of another Kit-to-Order or Kit-to-Stock product, enabling multi-tier bundle configurations that were previously blocked by a system-wide rule against nesting kit items. (29583)

• Extended the new Kit-to-Stock component nesting rules to the bulk Excel import pipeline, so imported product and kit-type changes are validated the same way as changes made through the UI or Open API. (51853)

• Corrected the put-side quantity split logic in Pick & Put replenishment jobs so multiple put tasks for the same over-picked product are no longer left incomplete or duplicated with an orphaned task. (50872)

• Resolved an issue where the mobile Inbound Receiving Select Product screen rendered blank for Purchase Orders with 75 or more SKU lines, blocking item selection on high-density shipments. (51721)

• Introduced a whole-quantity location fallback in replenishment source-location selection, so that when FIFO/FEFO and walking-path priority are both tied or unavailable, the system prefers a single source location that can fulfill the full need over a random multi-location split. (51734)

• Restricted the Dynamic Replenishment Engine’s Open Order Quantity calculation to Open and Shortage status orders only, eliminating double-counted demand from orders already reserved through allocation and reducing over-generated replenishment tasks. (52035)

• Added the session holder’s first and last name to the mobile "Active Putaway Session" error message during Sequential Putaway, so operators know who to contact instead of guessing or escalating. (52048)

• Mapped the Mobile Cart screen’s Suggestion Sequence field to the Walking Path Priority field on Cell Locations, allowing users to bulk-update this value via the Location Bulk Update sheet instead of editing carts one at a time. (29167)

• Extended cell suggestion logic on the Pick and Sort and Sorting screens to prioritize cells by Walking Path Priority (Cell Suggestion Sequence), directing operators to the most reachable cell first while preserving existing suggestion validations. (29173)

• Updated Identical Order batch packing so orders are filtered and grouped based on pre-produced (pre-attached) label counts, and pre-produced labels now print correctly as part of the batch packing flow. (51525, 51526)

• Added Store Order Number as a filterable field on the Shipment History report, letting users isolate shipments tied to a specific store order without scrolling through the full dataset. (51603)

• Resolved wave trigger delays and cross-warehouse interference in Wave Management by moving to a per-warehouse isolated, parallel trigger mechanism, so waves consistently start at their scheduled time. (51666)

• Capped Merge Order wave rule executions at 15,000 orders per wave, processing the oldest eligible orders first by created date and leaving any excess for the next wave cycle. (51706)

• Added a hasActiveJobs indicator to the Shipment Order Backlog so users can see at a glance which orders already have active job activity in their fulfillment lifecycle. (51760)

• Expanded email validation on the Shipment Order Customer Email and Billing Address Email fields to accept RFC 5321-compliant special characters (! # $ % & + - = _), on both the entry form and the Shipment Order creation API, so orders containing these characters are no longer blocked. (51781, 51782)

• Added a flag to the Shortage Report distinguishing shortages triggered by a picker’s Missing or Damage action during picking from those triggered by wave or manual job allocation, with a corresponding column and filter on the report grid. (51814, 51815)

• Added a new client-level parameter — configurable on the Client screen and through the Packing Station endpoint — to control automatic pack-out behavior. (51816, 51817)

• When automatic pack-out is enabled via the new client parameter, packing now completes without requiring the operator to click Complete Packing. (51819)

• Sequenced tasks within Single Item and Identical Item batch-pick jobs by pick location instead of order created date, so pickers can clear every pick at a location in one visit instead of revisiting it later in the same job. (51830)

• Improved the allocation engine to exclude inventory lines that already have an active Replenishment Job, preventing a double-reservation conflict between replenishment and standard order allocation. (51837)

• Added a hasCancelledLines flag to the Shipped & Cancelled tab, with a corresponding filter, letting users distinguish orders that shipped in full from orders that shipped with a partial cancellation. (51858)

• Aligned the sort order of bulk-printed pick lists with carrier label print sequence, so a batch of printed pick lists follows the same order as the corresponding label batch. (51864)

• Extended the post-allocation shipment order type change exception to also cover orders with an open or resolved Pack Short status, matching the exception already in place for Pick Short. (51977)

• Corrected the pack short label’s location/LP barcode population so it also fires for full pack short cases where no items were scanned, matching the transfer logic that moves the full order’s inventory to the hospital location in that scenario. (51979)

• Extended the pack short Report Issue flow so operators can capture a hospital location (and license plate, if applicable) directly in the popup, with the backend now transferring the tote’s inventory to that destination as part of the same action. (51981, 52001)

• Aligned the Edit Shipment Order screen’s status display with the Shipment Order List view by adding the same "Shipped (P)" partial-shipment indicator for partially shipped orders. (52021)

• Exposed Shipment Order custom fields in the Pick Short and Pack Short report data sources, so any custom field configured on the order can now be added to these printouts in ReportDesigner. (52031)

• Added HasPickShortLabelPrinted as a filter criterion on the SO Backlog screen, letting users quickly locate orders whose pick-short label has already been printed. (52070)

• Added a fallback so Pack Short and Pick Short labels print the product’s SKU as the barcode on Unscanned Items lines when the Pack Type has no barcode defined, ensuring every line always has a scannable identifier. (52215)

• Added the required commercial invoice letterhead and signature options to every EasyPost shipment request, resolving FedEx label failures on international shipments to countries requiring an ETD (52117)

• Extended EasyPost shipment creation to send the correct predefined package value when a Carrier Package is selected, and explicitly send null for user-defined Shipment Packages, enabling accurate carrier-specific rating and handling. (52116)

• Added support for four new Veho service levels — groundPlusOne, groundPlusTwo, groundPlusThree, and groundPlusFour — for rate retrieval and label generation through EasyPost. (52115)

• Added FedEx Cross Border as a selectable carrier and service level for warehouses with a FedEx Cross Border EasyPost account. (52047)

• Added the FLAT package type to UPS Mail Innovations under EasyPost carrier configuration, enabling correct labels and rates for StandardFlats shipments. (51947)

• Extended EasyPost international shipments to automatically populate the correct EEL code for shipments valued under $2,500, reducing manual customs paperwork corrections. (51731)

• Extended the custom carrier request model to include product custom fields, giving custom carrier integrations access to additional product data for label and rate requests. (50961)

• Added APC as a supported carrier under the EasyPost integration, and added the BPMFLAT and BPMPARCEL package types to UPS Mail Innovations, enabling accurate rating, labeling, and voiding for these shipment types. (52267)

• For "Receiving" fees billed "Per SKU", added a new "Dimension/Weight/Volume Updated" (Yes/No) condition, letting administrators charge based on whether a product's dimension, weight, or volume data was entered or updated during receiving. (37692)

• Added an independent "Daily inventory by location" notification toggle, letting clients set separate recipient emails and a separate scheduled time from the existing daily inventory notification. (41446, 51818)

• Improved Total Inventory Report load times by applying the pre-search pattern already used on other high-volume screens, so the report no longer auto-loads every record on open. (51749)

• Improved the performance of the Serial Shipment History list endpoint for large data volumes, addressing slow response times at scale. (51505)

• Resolved a race condition during AI Job Optimization that could leave an AI-optimized wave stuck in Started status. (51665)

• Improved the performance of the Job Management screen and its underlying API for faster load times. (51762)

• Improved the performance of the Order Operations Task Details screen and its underlying API for faster load times. (51764)

• Fixed an issue where the "Use this Shipping Box Only" field on Product Create/Edit displayed shipment packages the product’s client did not have access to, by scoping both the backing endpoint and the UI request to the product’s client. (30745, 52036)

• Fixed an issue where Excel-imported Purchase Orders allowed a Parent LP to be used for receiving, even though this was already blocked on the UI and Open API. (32382)

• Fixed an issue where the return address on the Return Order screen, its Excel export, and the Open API always appeared empty instead of showing the address assigned to the linked Shipment Order. (40120)

• Fixed an issue where the Receiving Date column on the Replenishment tab of the Task Details screen was always empty because the field was missing from the underlying API response. (50094)

• Fixed an issue where Carrier Directed Putaway rules using the LP Carrier condition failed to suggest a destination location after scanning a valid carrier tracking number. (51507)

• Fixed an issue on the Inventory by Location screen where transferring inventory tracked by PO number or lot number silently moved a different lot or PO at the same location instead of the one selected. (51724)

• Fixed an issue where the mobile Cycle Count screen’s "SKU to Count" and completed-task counters did not update in real time after completing a location, requiring operators to exit and re-enter the job to see accurate progress. (51728)

• Fixed an issue where zone-based and location-group-based Replenishment Job Types could generate a single job containing tasks from multiple zones or groups when the same product had open tasks in more than one group. (51733)

• Improved Inventory Movement logging to capture additional diagnostic detail when inventory remains allocated with no active orders or allocation records, supporting faster root-cause investigation of similar cases. (51973)

• Fixed an issue where Count Plan, Job Management, and Task Details records could get stuck in Started status instead of resolving to Completed or Cancelled when an inventory update was triggered without completing all locations or without using the Finalize endpoint. (51197)

• Added validation to ensure the "Prevent Exceeding Shipped Quantity" control reliably blocks over-quantity returns during Return Station SKU scanning across all entry paths. (50160)

• Fixed an issue where the LP inventory location conflict error message displayed a literal placeholder instead of the actual conflicting location, affecting both the UI and the equivalent Open API error response. (51732)

• Fixed an issue where clicking Search again on the Shipment Order Assign User screen retained the previous search results instead of resetting to the full list. (27246)

• Fixed an issue where backorders created from unfulfillable quantities were set to Open status instead of Shortage, preventing them from appearing on the Shortage Report until a later allocation attempt. (28549)

• Fixed Picking List printing from the Shipment Order Detail screen so it correctly resolves client-specific report designs instead of always falling back to the system default, and now prompts users to choose a design when more than one is available for the client. (33271)

• Fixed an issue on the Order Backlog screen where flagging a filter in the "Saved" section did not move it to the top of the filter list, matching the behavior already working for the "New" section. (34235)

• Fixed an issue where Shipment Transaction logs showed a null Shipment Order Code for inventory-tracked packaging materials, by correctly linking their Shipment History entries to the originating order. (38109)

• Fixed the Shipment Order grid’s Customer Name search so it correctly matches records when the search term is stored only in the first name field and the last name is empty. (46303)

• Fixed a status inconsistency between MongoDB and SQL during a Loading operation timeout that could leave a shipment plan and its orders stuck in an intermediate status, blocking downstream picking or cancellation. (50945)

• Fixed a data integrity issue where the Serial Number Report did not consistently reflect the same serial number’s history shown in the Serial Number Transaction History. (51349)

• Fixed a false error popup at the Packing Station caused by a stale document fetch response resolving after the board had already reset for the next order. (51498)

• Fixed a 500 error on the Wave Rules "Assign to User" sidebar that occurred whenever the grid was sorted, caused by grid sort state being incorrectly included in the sidebar’s request. (51500)

• Fixed an issue where the "Save Shipment Order" button did not respond when adding a tracking number to an order in "Ready to Ship" status. (51503)

• Fixed an issue where reporting a packing issue transferred inventory to the hospital location without recording the corresponding Inventory Movement transaction, breaking the audit trail. (51585)

• Fixed an inconsistency where the same transaction could show different timestamp precision depending on whether the record was served from SQL or Elasticsearch. (51654)

• Blocked disabling an AI job type on the AI Add-on while an active Wave Rule still references it, preventing wave rules from silently failing with a stale AI subscription reference. (51866)

• Fixed report resolution for Pack Short and Pick Short so the Packing Station flow reliably auto-selects the most recently created active report instance, and the Shipment Order screen correctly prompts users to choose among multiple active instances instead of resolving silently. (51869)

• Fixed a race condition in the product search dropdown on the Create Shipment Order and Purchase Order screens where out-of-order network responses could display stale search results instead of matching the latest typed input. (51870)

• Fixed a false "LP Does Not Exist" error during mobile picking, caused by a missing transaction wrapper around the LP location update at pick completion. (51874)

• Fixed the Pick Short popup so it consistently shows the correct design and content — including the transfer location/LPN prompt — for every combination of pick-short status, instead of defaulting to the wrong variant in some scenarios. (51976)

• Fixed the Scanned Items count on Pick Short and Pack Short labels so cancelled picking tasks no longer inflate the total, and corrected the Unscanned Items list on both labels to correctly reflect open pick-short or pack-short tasks. (51980)

• Fixed an issue where a partial (non-whole-order) shortage during the mobile Missing action did not correctly apply Pick Short status and mobile visibility rules at the individual task level when the client’s Retain Allocation During Missing setting is enabled. (52132)

• Fixed an issue where a Kit-to-Stock order in Ready to Pick status could incorrectly move to Open when a new line was added manually in Logiwa, separate from the store order lines, or when no line change happened at all. Also removed an extra Store Update Note that was added when an order moved to Open as expected. (51723)

• Fixed an issue where the packing-error void flow incorrectly voided manually uploaded carrier labels alongside system-generated ones; manually uploaded labels are now preserved. (51835)

• Fixed an issue in the TechShip integration where the ship-from contact name was incorrectly populated with the company name instead of the actual contact name. (51727)

• Fixed an issue where the duplicate-label safeguard blocked new label creation for the remaining portion of a partially shipped order; the check now correctly ignores labels that have already shipped. (51657)

• Fixed an issue where the multi-order Create Label screen could not correctly handle shipment packages configured with gram or ounce weight units, breaking carrier label generation for affected packages. (51651)

• Fixed an issue where the Default Return Shipment Method dropdown pulled from an incorrect data source, showing shipping options inconsistent with the carrier setup's active services. (51752)

• Fixed an issue with storage charge allocation during billing contract transitions, ensuring the transition date is assigned to only one billing period. (51785)

• Fixed an issue where the billing period shown on a printed invoice did not match the period shown on screen due to a timezone mismatch. (51685)

• Fixed an intermittent issue where the "Export as Excel" button failed to start a file download in receipt listings. (46407)

• Fixed an issue preventing SSO users from logging in through Okta, caused by an identity provider configuration error. (51888, 51889)

• Added five new Open API endpoints for License Plate Type — list, get by identifier, create, update, and delete — enabling integration partners to manage LP Type configuration without WMS UI access. (51710, 51854, 51855, 51856, 51857)

• Extended the Product create, create/bulk, update, and patch endpoints to support Kit-to-Stock products as components of other kit products. (29583)

• Added a missingTriggered field to the Dynamic Shortage Report endpoint (GET /v3.1/Report/WaveLog/dynamic-shortage), identifying shortage records that originated from a picker’s Missing or Damage action during picking. (51814)

• Added a hasCancelledLines flag to the Shipment Order list endpoint (GET /v3.1/ShipmentOrder/list), allowing API consumers to distinguish orders that shipped in full from those that shipped with a cancellation. (51858)

• Fixed the pick endpoint (POST /v3.1/WarehouseTask/pick) so it no longer returns a false "LP Does Not Exist" error during API-driven picking, caused by a missing transaction wrapper around the LP location update. (51874)

• Fixed a timestamp precision inconsistency in Transaction History API responses that could cause integrations to treat identical transactions as duplicates or misses. (51654)

• Renamed the webhook v2 topic wms/shipmentorder/mergeorder to shipmentordermergeactions to accurately reflect that it covers both merge and unmerge actions and to align with v2’s topic-naming convention; webhook v1 is unaffected. (52069)

• Added a ShipmentOrderMerged event to Webhook V2, bringing merge and unmerge notifications to V2 subscribers. (51091)

• Added accurate, database-sourced maxLength values across applicable Open API write-endpoint fields, so integrators can validate payload values against real system limits before sending requests. (51511, 52044)

• Added Manufacturer Product Identifier support to the Product Open API's create, bulk create, update, and detail/list endpoints. (51845)

• Tracking Number field of the/v3.2/ReturnOrder/create and /v3.2/ReturnOrder/update is activated, so a tracking number entered or sent with an RMA is now saved and returned instead of being silently dropped.(52135, 32399)