Skip to main content

June 2025 - Release Notes

S
Written by Stephanie Kelley
Updated over 3 weeks ago

Force Package Type Validation

To improve packing accuracy and reduce costs from incorrect packaging, we've launched Force Package Type Validation. This feature ensures the correct package type is scanned and used.

Key Updates:

  • Activation: Enable the new "Force Package Type Validation" parameter in Client screen > Packing Settings to use this feature.

  • Mandatory Scanning: When active, if the scanned package differs from the one in the Shipment Order, a confirmation is needed to update the package type thus the packer must scan the package type barcode before finalizing a pack (e.g., "Close Pack").

  • Improved Tracking: Two new columns, "Suggested Shipment Package Type" and "Target LP Type," in the "Order Operations Task Details" screen will display the planned versus actual package types used, helping identify discrepancies. Note: This validation does not apply to "Item with Box" products.

Please find the related Intercom documentation here.

Cycle Count Enhancements

  • The "Difference (%)" calculation in Count Location Details & Count SKU Details screens has been corrected to use the absolute sum of differences at the SKU level relative to total stock, preventing inaccuracies where over- and under-counts cancel each other out. The field type was also changed from integer to decimal.

    • Example: Location A has 10 units of SKU1 & SKU2. Once Location A’s count is finalized, SKU1 is counted as 8, SKU2 counted as 12.

    • The difference will be calculated per product basis, and the total difference will be 4 units out of 20 units & will be represented as %20, instead of calculating the difference based on total location quantity.

  • The GET /WarehouseCountPlan/detail Open API endpoint response has been updated in a new API version(3.2) to include clearer field names: InitialStockQty, CountedQty, ApprovedStockQty, and ApprovedCountQty, mapped from existing task detail fields, while maintaining backward compatibility.

  • Performance for the Count Plan screen loading speed has been improved, with load times reduced by an average of approximately 97.47%. This significantly reduces wait times for large datasets and enhances user experience. Query performance for the "More Details"

  • Excel export on Count Location Details & SKU Details Screens and the GET /WarehouseCountPlan/detail API endpoint has been improved by optimizing the difference calculation logic, aiming for significantly reduced execution times, resulted more than 100% faster loading time.

What's New/Improved

  • Created a new API endpoint for retrieving carrier shipment details, replicating the functionality of the existing endpoint (https://myintegrationquerystage.logiwa.com/api/carrierlabel/list/report/i/0/s/100). The new endpoint supports pagination and returns shipment data in the same format.

  • UPS carrier integration has been enhanced to correctly map hazmat-related fields (ProperShippingName, Hazmat Quantity & Unit, Hazmat Type, Hazmat Container Type, Hazmat ID) and determine Transportation Mode & Regulation Set for international and domestic hazardous material shipments, enabling proper hazmat label generation.

  • The WarehouseTask report API endpoint (/Report/WarehouseTask) has been enhanced to allow filtering by fromLicensePlateNumber and toLicensePlateNumber for easier retrieval of tasks related to specific license plates. The order-operation sub-endpoint also received these filters.

  • The /ShipmentPlan/licenseplate/list API endpoint has been enhanced to support filtering by shipmentOrderCode (exact match) and actualShipmentDateTime (date range), in addition to existing filters like shipmentPlanCode and lpNumber.

  • A new API endpoint (POST /api/shipments/ship-lp) has been introduced to allow shipping all eligible orders within a single License Plate (LP) through one API call.

  • Introduced three new fields (LineNotes1, LineNotes2, LineNotes3) at the Shipment Order Line level. These fields allow users to store and manage specific notes for individual items within a shipment order. They are now available in the Shipment Order screen UI, Excel imports/exports, and relevant API endpoints, enhancing data management and integration capabilities.

  • The product (SKU) selection dropdown in the manual Shipment Order Create/Edit form has been improved: it displays up to 20 matching SKUs (exact matches prioritized at the top) and includes a loading indicator.

  • The display duration of the green success message in the mobile Sorting module has been reduced from 3 seconds to 1 second to improve user experience by minimizing view obstruction.

  • All custom fields defined under Shipment Order Line have been added to the Retailer Case Printout, Retailer LP Printout, and Packing List templates to provide complete shipment details.

  • Users are now able to perform the skip action while executing full LP (License Plate) picking tasks. The system will proceed to the next available LP or task accordingly.

  • The Packing Station workflow has been updated to automatically select the appropriate packing slip based on a hierarchy: retailer-specific, then store-specific, then normal packing slip, and finally the default packing slip if no custom templates are found.

  • The Return Order List API's pagination now correctly uses Return Order Headers for distinct RMAs. The new version of the "List Return Order" API endpoint also enhances responses with clientIdentifier, clientName, warehouseIdentifier, and warehouseCode, allowing filtering by clientName and warehouseCode. Note that returnReasonIdentifier and returnReason have been removed from this new version.

  • We've removed two fields from the UI to make return operations clearer and more efficient: the "return notes" field from the Shipment Order return process customer reason entry pop-up (at the return station), and the "note" field from the RMA creation process.

  • Warehouse and Client Name columns have been added to the Return Order Export Excel, ensuring the exported data matches the UI for comprehensive review and reporting.

  • Change Log functionality has been added for StoreIntegration Setups, allowing users to track changes made to these configurations within the integration setup screens.

  • The Shopify integration services (Sync Inventory, Send Shipment Info) now uses the exact 'myshopify_domain' (obtained during setup) for GraphQL and fulfillment API calls, to prevent "Invalid Shop" errors.

  • Warehouse selection has been moved to the initial "Connect Now" / "Add New Connection" pop-up for Carrier Integrations, and the selected warehouse is displayed as read-only on the Create Connection Tab.

  • Client selection has been moved to the initial connection pop-up for Store Integrations, and the selected Client is displayed as read-only on the Connect Store Tab.

  • The Amazon inventory sync method was transitioned from legacy XML Feeds to the modern JSON via Feeds API to ensure compliance and robust integration.

  • The Shopify Download Order service has been updated to retrieve 'properties' (Rest API) and 'customAttributes' (GraphQL API) from line items and map them into the new 'LineNotes3' field in Logiwa Shipment Order Lines.

  • The "Mark this item as hazardous" toggle has been moved to the Advanced tab within the Hazmat Information section of the Create/Edit Product drawer, and related fields will become editable only when this toggle is active.

  • The "Class Division" field has been added to the Hazmat Information section on the product setup page, allowing warehouse admins to configure more detailed hazmat-related information.

  • The "Expected Delivery Date" field has been added to the Shipment Order UI, allowing users to view and edit this information directly.

  • ZPL label type has been added for partner integrations.

  • An issue with UPS International Billing Type selection, specifically when 'recipient' is chosen, has been addressed. The default value for international billing type when none is selected is now configured to send nothing (null) and specific mappings for "recipient" without account numbers have been corrected.

  • The carrierpackagereference field has been added to the /ShipmentOrder/list API endpoint response, allowing users to efficiently match shipments with generated unique package reference

  • The /create and /void API endpoints for custom carrier integrations have been enhanced: the 'reference' (GUID for each package) field was added to the /create endpoint (request ) and to the /void endpoint (request); 'carrier' and 'service' fields were also added to the /void request to improve traceability and integration capabilities.

  • A new "RateShopping Info" column has been added to the Carrier Shipment Details report, displaying whether RateShopping was used for a shipment and the name of the preset applied, to help analyze automated shipping choices.

  • The partner carrier integration pop-up now dynamically displays only the required fields (API Key and/or API Secret) based on the selected carrier (eHub, BukuShip, eShipper, Shipium) to simplify setup

  • The "Country" field in the Third Party Account section for UPS & FedEx carrier integrations has been changed from a free text input to a dropdown menu to ensure accuracy.

What's Fixed

  • An issue with non-functional 'Next' and 'Previous' pagination buttons in the 'Show All Cells/Totes' list on the Packing Station screen has been fixed; users can now correctly navigate through pages.

  • An issue where editing a Job Type unintentionally altered or reset the defined sequence of Location Zones in the 'Grouping' tab (when 'Group by Method' was Location Zone) has been fixed. The zone sequence will now persist unless explicitly changed.

  • Fixed an issue on the Packing Station screen where, if the Scale Integration was active, users were incorrectly required to enter dimensions for standard carrier-defined package types (e.g., FedEx Pak). Dimension entry is now correctly optional for these package types when using scale integration, consistent with the standard workflow. Dimensions remain mandatory only for custom package types created in Logiwa.

  • An issue where leading zeros in PRO Numbers were trimmed in the Shipment Order grid view, causing a mismatch with the details view, has been fixed. PRO Numbers will now display consistently with leading zeros in all grid views.

  • An issue where the system failed to process bulk shipments of 1000 orders, while succeeding with 100, has been investigated and resolved.

  • The tracking number manually entered when uploading a shipment label via the 'Edit Shipment Order' screen will now be correctly saved and will no longer be cleared when the main 'Save Order' button is clicked.

  • PO completion emails will now be sent only after all received item data is fully recorded in the "receipt" table.

  • An issue where an error during LP location update in a transfer operation could lead to data inconsistency between the LP Number screen and Inventory by Location screen has been addressed. The transfer will not proceed if the LP update fails, and transactional consistency will be enforced.

  • The "Logiwa Product" column, containing the Logiwa Product SKU Code, is now correctly populated in the Excel file when exporting from the Product Listings - Linked Products page.

  • An issue where the Send Shipment Info message was not calculated correctly for multi-listed components of kits has been resolved.

  • An issue causing Change Log entries to incorrectly show "Auto Run" as the user has been fixed; logs will now reflect the correct user.

  • An issue where recurring fees (with "Charge one Time" unselected) were not appearing in the Billing Report for subsequent billing periods after the initial calculation has been fixed. Recurring fees will now be reflected in all relevant monthly reports.

  • Mobile app login stability has been improved, particularly during peak usage, to ensure reliable login and feature access. Error handling during login has been improved to display specific error messages instead of a generic "Invalid username or password" for various failure scenarios.

  • An issue on the mobile transfer screens that incorrectly prevented transferring a product from its License Plate (LP) to LP’s current location has been fixed. This action is now permitted.

  • A bug causing an error "This LP/Tote has inventory in different location" during replenishment put phase due to quantity mismatch in pick tasks (observed only in Sandbox) has been fixed. Pick task quantities will now accurately reflect picked amounts.

  • Fixed an issue in the Get Replenishment Report Open API endpoint where pagination was behaving incorrectly when filters such as SKU, Client Identifier, or Warehouse Identifier were applied. The totalCount of records was often inconsistent with the actual data returned on subsequent pages. This has been resolved, and pagination now correctly applies to the filtered results, ensuring accurate data retrieval.

  • An issue where discounts applied to store orders were not correctly reflected on the commercial invoice, causing the declared value to be higher than the discounted price, has been fixed. Commercial invoices will now accurately reflect discounted prices.

  • The FedEx carrier integration for rate shopping has been enhanced to include a SmartPost-specific rate request, similar to UPS SurePost handling, ensuring SmartPost rates are retrieved and considered.

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}

Did this answer your question?