Grasshopper 3.24.36 Release Notes
Features
Feature Enhancement Update Damage Type Field to Claim Type
Overview
To better align with current terminology and supported workflows, the existing Damage Type field has been updated to more accurately represent the nature of claims handled in the system.
Key Enhancements
1. Field Renamed to Claim Type
The field label has been updated from “Damage Type” to “Claim Type” to reflect broader claim scenarios beyond physical damage.
2. New Claim Type Option Added
A new “Service” option has been added to the Claim Type dropdown, enabling users to accurately classify service-related claims.
This enhancement improves clarity, consistency, and flexibility when creating and managing claims.
Per-Hub Availability in Unallocated SKU View
Overview
To improve inventory visibility and cross-hub fulfillment decisions, the Unallocated SKU View now provides per-hub availability insights. Warehouse operators can quickly see reserved vs. available quantities per SKU, scoped to their local environment, enabling faster and more informed allocation decisions.
Key Enhancements
1. Check Availability Action
○ Added a “Check availability” action to the Unallocated SKU View:
■ Context menu (left-click on a SKU row)
■ Top toolbar action when exactly one SKU is selected
○ The action is disabled when no SKU or multiple SKUs are selected (bulk not supported).
2. Per-Hub Availability Modal
○ Header: Item name, SKU, Shipper, Vendor, and close icon.
○ Body: Scrollable table with a sticky header.
○ Columns (left → right):
■ Hub (text, left-aligned)
■ Reserved Pieces (numeric, right-aligned)
■ Available Pieces (numeric)
○ Rows are alphabetically sorted by hub name and sortable.
○ Hubs with 0 available quantity display an “Out of stock” warning with a tooltip in the Available Pieces column.
○ Footer: Close button.
○ Accessibility: ESC closes the modal; header receives initial focus.
3. Availability Display Logic
○ Availability is shown per SKU, Vendor, and Shipper as:
{ hub_name, available_qty, reserved_qty, total_qty }
○ Local-only calculation: For VC users, availability reflects local item statuses only and does not expose reservations from remote partner environments. 4. User Permissions
○ The action is available to:
■ Super Admin
■ Grasshopper Admin
■ Inventory
■ Supervisor
■ Customer Service
■ Retailer
This enhancement delivers clear, actionable per-hub inventory insights directly within the Unallocated SKU workflow.
Defect Fixes
Local RTBS Report Missing Eligible Orders
Overview
The local RTBS report was displaying fewer RTBS cases than expected. In certain scenarios, eligible RTBS orders were omitted from the report, resulting in incomplete visibility for operations teams.
It is important to note that this is an analytical, scheduled report that runs once per day at the beginning of the day, and is not a real-time report.
Key Fixes
1. Correct Inclusion of VC-Sent Orders
The report logic has been updated to include RTBS orders sent by VC, ensuring these cases are no longer excluded.
2. Consistent Order Source Handling
RTBS orders are now evaluated consistently regardless of whether they originate from VC or carrier retailers, eliminating unintended filtering based on source.
3. Improved Accuracy of RTBS Counts
The report now reflects the full and accurate set of RTBS-eligible orders, aligning reported counts with expected operational data.
This fix ensures the local RTBS analytical report provides complete and reliable daily visibility into all RTBS cases.
Accessorial Page: Shipper Picker Missing Options
Overview
On the Accessorials page, the shipper picker did not display all available shippers. Specifically, although accessorials exist for some retailers, some of those retailers options were not available in the shipper filter, preventing users from filtering and managing those accessorials.
Key Fixes
1. Complete Shipper List in Picker
The shipper picker now loads and displays all relevant shippers that have accessorials configured.
2. Consistent Filter Behavior
The shipper filter logic has been aligned with the underlying accessorial data to ensure no valid shipper options are omitted.
New Warehouse Interface: Search Option Sensitivity
Overview
In the new warehouse interface, the PO and Ref Record filters in the Unallocated Items view were implemented using strict, exact-match logic. As a result, searches became case-sensitive and space-sensitive, limiting usability for common workflows and preventing users from easily locating items unless the exact text format was entered.
This regression reduced the effectiveness of search and filtering compared to the previous behavior.
Key Fixes
1. Case-Insensitive Search Restored
PO and Ref Record searches are now case-insensitive, allowing users to find results regardless of text casing (e.g., ford vs. FORD).
2. Improved Handling of Spaces and Multi-Word Values
Searches now correctly support values that include spaces (e.g., CANYON ROCK), restoring the ability to find project allocations and similar records.
3. Enhanced Ref Record Chip Input Behavior
The Ref Record chip filter has been updated to:
○ Support spaces within values
○ Treat input as case-insensitive
○ Split comma-separated values into individual chips for easier multi-value filtering
Unallocated Items View: Status Filter Shows Irrelevant Statuses Overview
With the release of the new Unallocated Items view, a Status filter was introduced. However, for inventory items, only a limited set of statuses is relevant. The current implementation allows users to select from all order and item statuses, which creates noise, confusion, and redundant filtering options.
Key Fixes
1. Status Filter Limited to Relevant Inventory Statuses
The Status filter in the Unallocated Items view now includes only the applicable statuses for inventory items:
○ Pending Arrival
○ Received
○ Failed Deluxe
○ Inspection
2. Cleaner Filtering Experience
By removing irrelevant statuses, the filter is now easier to use and better aligned with the operational workflow for unallocated inventory.
Manifest Export No Longer Displays Locations
Overview
When exporting or printing manifests, location information is no longer included. Previously, all associated locations were displayed on the manifest export, but they are now missing from every downloaded or printed manifest. This regression reduces the usefulness of the export for operational review and handoff.
Key Fixes
1. Restore Location Data in Manifest Exports
Location details are now correctly included in all manifest exports and printouts.
2. Consistent Output Across Export Types
The fix applies to both downloaded and printed manifests, ensuring parity with prior behavior.
This correction restores complete and expected manifest information for downstream use.