Features
Grasshopper 3.24.37 Release Notes
Overview
We are enhancing the Location object to provide a richer, more structured representation of physical warehouse locations.
Location Object v2 introduces standardized zones, types, physical addressing, and capacity definitions, creating a consistent foundation for current and future warehouse management capabilities.
This enhancement improves data consistency across warehouses, simplifies location configuration, and enables downstream features such as location-based reporting, smarter inventory flows, and improved warehouse planning — without disrupting existing customers.
Key Enhancements
● Structured Location Model
Added standardized fields to better describe physical warehouse locations:
○ Zone (e.g., Inbound, Outbound, Storage, Returns)
○ Type (e.g., Storage, Door, Staging, Workstation)
○ Location Code: Aisle, Bay, Level, Bin
○ Capacity: Width, Height, Depth, Cube
● Validation & Data Quality Controls
Introduced server-side validations and constraints to ensure consistent and reliable
location data across hubs and accounts.
● Enhanced Location Management UI
Updated the Location creation and management experience to support zones, types, physical codes, and capacity configuration.
● Location Import Support
Enabled bulk creation of locations via CSV import to simplify onboarding and updates at scale.
● Backward Compatibility
Existing locations remain unchanged and functional, with no mandatory backfill required. New structured fields are optional for existing records and enforced only for newly created or updated locations.
Warehouse Utilization Report
Overview
We are introducing the Warehouse Utilization Report, a new location-level report that provides warehouse teams with a single, reliable view of inventory utilization per location within a hub.
This enhancement consolidates fragmented inventory visibility into one actionable report, enabling warehouse managers to quickly understand what is stored in each location, identify empty or underutilized locations, and detect location-related inventory issues earlier — before they impact customers.
Key Enhancements
● Location-Level Inventory Visibility
Introduced a hub-level report with one row per location, surfacing key inventory metrics such as SKUs, orders, allocated, available, on-hand quantities, and cube usage.
● Utilization & Slotting Insights
Enabled fast identification of empty and underutilized locations to support better slotting decisions without relying on manual floor walks or tribal knowledge.
● Operational Audit Support
Provided a centralized, system-based view for location audits, reducing dependency on ad-hoc exports and manual Excel analysis.
● CSV Export Capabilities
Added export options for:
○ Full Location Utilization Report (CSV)
○ Item-level breakdown per location (CSV)
● Actionable Workflows
Enabled direct actions from the report, including the ability to create cycle counts for selected locations.
● Foundational WMS Capability
Established the data and reporting foundation for future enhancements such as advanced filters, RNL by inbound manifest, and deeper inventory discrepancy analysis.
Self-Service Webhook Configuration for Shippers
Overview
The existing UI for linked orders—particularly Tag-Along orders—relied on legacy popups that often caused confusion and led to multiple bugs due to unclear hierarchy and relationship context.
This release introduces a new React-based Linked Orders View, replacing the old popups with structured, intuitive components that clearly visualize how orders are connected and where the current order fits within each relationship.
The new UI supports all linkage types and provides consistent navigation, visibility, and (where applicable) controlled management actions.
Key Enhancements
We are introducing self-service webhook configuration for shipper accounts, allowing users to independently manage webhook subscriptions without relying on development team intervention.
This enhancement gives shippers greater control over how Grasshopper events are pushed into their systems, reduces operational overhead, and improves integration agility while maintaining validation, security, and governance standards.
● New Integrations Page for Shippers
Added a dedicated Integrations section within shipper settings, providing a centralized location for managing webhook configurations.
● Self-Service Webhook Management
Shipper users can now:
○ Add new webhook subscriptions
○ Edit existing webhook configurations (HTTP method and URL)
○ Delete webhooks when no longer needed
All changes are stored and managed within the user’s Webhook Collection.
● Supported Event Subscription
Users can subscribe to a predefined list of supported Grasshopper events (e.g., order lifecycle changes, item status updates, tracking updates, assets, notes, delivery and ETA changes) via a searchable event dropdown.
● Webhook Configuration Controls
Each webhook supports:
○ Event selection (required)
○ HTTP method selection (POST / PUT / PATCH; default POST)
○ Target URL with validation and length limits
○ Optional HTTP headers (up to two key/value pairs with enforced completeness and validation)
● Inline Validation & Error Handling
Added real-time validation to prevent invalid or incomplete webhook configurations from being saved, with clear error messaging per field.
● Improved UX for Webhook Management
Webhooks are displayed as read-only cards by default, with inline edit and delete actions. Deletion is protected by a confirmation modal to prevent accidental removal.
● Role-Based Access Control
Access to webhook configuration is restricted to shipper accounts with Admin or Super Admin permissions.
● Developer Documentation Access
Direct access to webhook API documentation is available from the UI to support integration implementation and troubleshooting.
Defect Fixes
Manifest Export – Customer Name Field Empty
Overview
Fixed an issue where the Customer Name field was missing in exported manifest files, resulting in incomplete customer information in the export.
Key Fixes
● Ensured the Customer Name field is correctly populated in manifest exports.
● Improved data consistency and reliability for downstream processing.
● No impact to existing workflows or manifest generation logic.
Manual Lasso Tracking – Missing User
Overview
Fixed an issue where manual lasso actions were logged without capturing the associated user, making it unclear who performed the action.
Key Fixes
● Ensured the user who performs a manual lasso is always captured and recorded in tracking.
● Prevented manual lasso events from being logged without an associated user.
● Improved auditability and accountability for manual actions.
Orders – Timezone Mismatch Between Orders and Manifests
Overview
Fixed an issue where orders assigned to the client in Illinois, the server displayed EST timeframes while the corresponding manifests showed CST, causing customer confusion around delivery times.
Key Fixes
● Corrected timezone handling to ensure orders and manifests display consistent local time (CST).
● Aligned order timeframes with the hub/server timezone configuration.
● Improved clarity and consistency of delivery time communication to customers.