External release notes – Grasshopper – Version 3.24.24

New Features

• Receiving Hours in Orders Export Reports
  • To better support operational needs, we’ve introduced a new feature that displays Receiving Hours in the Orders Export reports. This enhancement adds two new columns — Receiving Window Start and Receiving Window End — allowing better scheduling and visibility into delivery timeframes.
  • This enhancement is controlled via a feature flag and has to be activated.
  • Key Enhancements
    • Applies only to standard orders
    • Displayed in: Orders Export CSV (All Columns), Orders Export CSV (Items Breakdown)
    • UI Enhancement
      • Orders Grid
        • Receiving Window Start and Receiving Window End are added as optional columns
• Include Delivery Questionnaire in Exported Reports
  • Some clients requires visibility into delivery questionnaire responses within the Orders Export reports. This enhancement introduces a new column that consolidates all question/answer pairs from the delivery questionnaire, aiding in better delivery context and quality assurance.
  • This enhancement is controlled via a feature flag and has to be activated.
  • Key Enhancements
    • Applies To:
      • Orders Export CSV – All Columns
      • Orders Export CSV – Items Breakdown
    • Format
      • Question 1: {question1}; Answer 1: {answer1}; Question 2: {question2}; Answer 2: {answer2}; …
      • In a single cell
  • Known Limitations
    • Applies only to local export (no Virtual Carrier support)
    • Out of scope for Pick Up, Return, Billing, and Service Ticket orders
• Grouped Stops Column in Manifest Export
  • FGO requires better visibility into cases where multiple stops in a manifest share the same customer and address. This impacts their billing process, as they charge per stop—even when multiple orders are for the same location. Currently, the system treats each order as a distinct stop.
  • This enhancement is controlled via a feature flag and has to be activated.
  • Key Enhancements
    • Applies to Manifest Export by Stop and Manifest Export by Item
    • Column Name: Grouped Stops
    • Grouped Stops Column Logic
      • Applies To:
        • Manifest Export (By Stop)
        • Manifest Export (By Item)
        • Position: Immediately after “Stop #” column (2nd position)
      • Input Logic:
      • For stops sharing both:
        • The same full address (case-insensitive)
        • The same full customer name (First + Last)
        • Display the lowest Stop # among those stops in the Grouped Stops column
        • If the stop is unique (no other stop with same name/address) → leave the field blank
      • Matching Criteria:
        • Address comparison is case-insensitive
        • Full name is constructed from First + Last Name
        • Comparison is limited to stops within the same manifest
• Filters and Columns for Related Orders Report
  • This enhancement introduces new filters and columns to the Related Orders report to improve search-ability and visibility of tag-along relationships between orders.
  • Key Enhancements
    • New Filters
      • Consignee Name
        • Behavior: Case-insensitive matching (ILIKE ‘%value%’)
        • Purpose: Enables flexible search for consignee by name fragment
        • Example: Searching john will match John, Johnson, etc.
      • Consignee Phone Number
        • Exact match
        • Behavior: Must match the number as it was entered into the system
    • New Columns
      • Tag Along Type
        • Values:
          • P (Parent)
          • F (Follower)
        • Only orders with a tag-along relationship will display this field
      • Tag Along Order IDs
        • Format: Comma-separated list of related order IDs
        • Shown only for orders with tag-along relationships
• Tag Along Linking from Related Orders Report
  • The ability to tag along related orders directly from the “Related orders report”.
  • Key Enhancements
    • New Action
      • Clicking on that will open a react dialog  – based on order picker page. 3 cases are possible:
        • Clicking on regular order → then user need to choose role [parent, follower]
        • Clicking on Parent → then “parent” is populated and can not be changed and user can only add follower/s
        • Right click on Follower → then click on action -> will not open the dialog window but will show error message
      • Dialog page will have these columns:
        • order id
        • status
        • scheduled date
        • consignee name
        • shipper
        • type
        • tag along column
      • Option To
        • “Add Followers” or “Add a Parent” according to the selected role 
      • Errors
        • Show sneak bar with status that can open a full batch (multi action) report with the correct error messages for each failure. 
• Addition of “Require COI” Column and Filter to Orders Grid
  • This enhancement adds support for visibility and filtering of orders that require a Certificate of Insurance (COI) by introducing a new column and filter in the Orders Grid, as well as including this information in Orders Export CSV reports.
  • This enhancement is controlled via a feature flag and has to be activated.
  • Key Enhancements
    • Add new “Require COI” column to the grid
    • Add filter to allow users to search based on COI requirement
    • UI Enhancement
      • The column and filter are hidden by default
      • Can be manually enabled via the UI “More Columns” menu
      • Filter Options:
        • Yes (Require COI)
        • No (Don’t Require COI)
        • Both (no filter)
      • Export
        • Add “Require COI” column
          • Orders Export (All Columns)
          • Orders Export (Items Breakdown)
  • Know Limitations
    • Virtual Carriers are not supported
    • Column is not sortable

Bug Fixes

• Missing Customer Name for Return Orders in Carrier Report Export
  • The Carrier Report (Order Breakdown) export was not displaying the Customer Name for return orders. This occurred because the report incorrectly referenced the delivery address instead of the pickup address, which contains the correct customer information for returns.
  • Issue Summary
    • The report should display the Customer Name for all order types, including returns, by sourcing the name from the correct pickup address.
  • The export logic for the Carrier Report has been updated to properly reference the pickup address for return orders. This ensures that the Customer Name is correctly populated for all order types.
• Incorrect Address for Pickup Stops in Manifest Export
  • When exporting manifests by stops or items, the address for pickup and return orders is incorrect. The export references the vendor address instead of the actual pickup information (typically the customer or source address for returns).
  • Steps to Reproduce
    • Create a last mile manifest
    • Add a pickup order and a return order
    • Export the manifest by stops or items
    • Observe that the vendor address appears instead of the pickup address.
  • Issue Summary
    • The exported manifest displays the vendor address for pickup and return orders, which is misleading.
  • The export logic has been updated to reference the correct pickup address for return and pickup orders. This ensures address accuracy in exported manifests.