Talk to an Expert

Help Center

Find answers, explore features, and get the most out of Grasshopper with our step-by-step guides and resources.

Home » Help » Release Notes » Help » 17 June 2025

17 June 2025

External release notes – Grasshopper – Version 3.24.26

New Features

  • Grouped Stops Column in Carrier Manifest Export
    • A new “Grouped Stops” column has been added to the manifest export (by stop and by item) to help identify stops delivered to the same address and recipient.
    • Key Enhancements
      • When enabled, the export will group stops that share the same full address and recipient full name (first + last), case-insensitively.
      • The lowest stop number among the group will be shown in the “Grouped Stops” column for all stops in the group.
      • Single, ungrouped stops will display their own stop number.
      • If no match is found, the column remains blank.
      • Controlled by feature flag
        • This flag is maintained in the account configuration schema and toggled by the development team.
  • Payload Attribute Display in Order “Other” Tab
    • Payload field—under the Other tab. This enhancement introduces a structured, configurable view of selected payload attributes for all user roles.
    • Key Enhancements
      • A new “Custom Attributes” section is now available under the Other tab for all roles.
      • This section displays specific fields from the order’s payload, based on a shipper-level configuration.
      • Configuration Details:
        • Each shipper can define a list of payload attributes to display
        • If no attributes are defined, the Custom Attributes section will not appear.
        • This flag is maintained in the account configuration schema and toggled by the development team.
      • Display Rules
        • If a value exists: display the label and value as plain text.
        • If the value is a document or date: display as plain text (no formatting applied).
        • If the value is missing: show the label with an empty value.
        • If the label is missing entirely: show N/A as the label.

Bug Fixes

  • Enable Initiating Cycle Count for Tasks with 0 Expected Items
    • Previously, users were blocked from initiating task-based cycle counts when all selected locations had zero expected items. This limitation prevented the inclusion of potentially miscounted or untracked inventory.
    • The system now allows users to initiate a cycle count even if the selected locations have 0 expected items. This supports scanning of physically stocked but system-untracked locations, improving inventory accuracy.
    • Issue Summary
      • The initiation dialog now shows the following message when no expected items are found
      • No items found in the selected location(s). The count will start with 0 expected items.
  • Incorrect Serial Number Display in Order Details
    • In orders containing serial numbers, the first serial number was incorrectly appearing in an unintended section at the bottom of the order details page. This display issue occurred consistently across all orders with serial numbers.
    • The system now correctly displays all serial numbers only in their designated section within the order details. The erroneous display of the first serial number has been removed.
  • Add to Cart Now Validates Against Reserved Inventory
    • Previously, users could add items to the cart or create orders without the system validating against reserved inventory levels. This led to over-allocation and potential fulfillment issues due to insufficient stock.
    • The system now validates available inventory, considering reserved quantities, during both Add to Cart and Create Order from Cart actions.
    • Issue Summary
      • If the reservation feature flag is enabled and the vendor ID is present, the system checks if the requested quantity exceeds available (non-reserved) stock.
      • On insufficient stock, the following error message is shown:
        • “Allocation failed — no available inventory for this item.”
        • If the reservation flag is disabled, the validation is bypassed.
        • Items without a vendor ID are allowed to be added to the cart, even if the flag is enabled.
  • Unable to Set or Cancel Order Hold as Shipper
    • Shippers were previously unable to set or cancel order holds. This issue occurred when logged in with a shipper-level role, where the hold actions were not functioning as expected.
    • The permissions and functionality have been corrected. Shippers can now successfully place orders on hold and remove holds, as intended.
  • Incorrect Default Email in Time Frame Confirmation SMS
    • Time Frame Confirmation SMS messages were incorrectly defaulting to the email address of the carrier regardless of the delivery region. This led to customer confusion and misrouted replies.
    • The SMS notification logic has been updated to use the correct region-specific email address based on the delivery location.