Grasshopper 3.24.32.1 Release Notes
Features:
Webhook Enhancement: Manifest Number & Stop Number in Order Delivery Changed Event Payload
Grasshopper’s Order delivery changed Change webhook currently includes the manifest
object ID but does not provide additional manifest context such as stop number or manifest
Number.
Partners have requested richer metadata to better track and synchronize last-mile statuses with
their internal systems—especially during scheduling and delivery timeline changes.
This enhancement expands the webhook payload so integrators can reliably identify where an
order sits on a manifest (its position/stop number) and which manifest it belongs to (nice
number), improving routing transparency and system-to-system alignment.
Key Enhancements
Webhook Payload Improvements
The Order Status Change webhook now includes two additional attributes (when applicable):
- manifest_route_id – the human-friendly manifest number
- stop_number – the stop position of the order within the manifest
Both values become part of the order payload as soon as the order is placed onto a manifest.
Order Timeline / Time-Frame Updates
When the order delivery changes (the schedule) (e.g.,re-sequencing):
● The webhook will publish updated values for:
- stop number
- manifest number (route id)
● Ensures downstream systems always receive real-time, accurate manifest context.
Automatic Scheduling Text Update
Overview
Users have expressed confusion about how unattended orders are automatically scheduled in
Grasshopper. The previous tooltip did not clearly communicate that unattended orders are
processed every 10 minutes, not instantly.
To improve user understanding and set accurate expectations, we updated the tooltip text in the
Automation settings.
Key Enhancements
Updated Tooltip for Unattended Orders Auto-Scheduling
- Location: Advanced Settings → Orders → Automation section
- Previous Behavior: Tooltip did not accurately describe the timing cycle of unattended order auto-scheduling.
- New Tooltip Text: “Unattended orders are auto-scheduled every 10 minutes to the next available resource — no customer action required.”
- Clarifies:
- Auto-scheduling is not immediate.
- The system runs the unattended-order scheduler every 10 minutes.
- No involvement is needed from the customer.
Increase Add-SKUs-to-Cart Limit
Overview
Users working with the Unallocated Items → SKU View in the new React interface often need
to add large batches of SKUs to the cart. Historically, the system restricted bulk additions to 25 SKUs, which caused friction for warehouse teams and partner workflows that routinely handle larger SKU sets.
To improve efficiency and support higher-volume operations, Grasshopper now raises the SKU
addition limit and updates the user-facing guidance.
Key Enhancements
1. Increased SKU Add-to-Cart Limit
● The system now supports adding up to 100 SKUs at once when using:
- Unallocated Items → SKU View (React)
● This change supports high-volume pick/pack workflows and reduces repetitive actions.
2. Updated Error Toast Messaging
● New toast message when the limit is exceeded:
“Please try adding up to 100 SKUs.”
3. Behavior Clarification
● The former limit of 25 SKUs was an old safeguard from the Angular implementation.
● It was not intentional for the new React SKU workflow, and has now been aligned with
product requirements.
Add Serial Number to Item Information in Manifest Documents (BOL & Master Manifest)
Overview
To enhance shipment visibility and improve downstream auditing, partners require item serial
numbers to appear directly inside exported manifest documentation.
This enhancement adds serial numbers to both Master Manifest and BOL documents—ensuring consistency across operational paperwork and enabling easier reconciliation between warehouse, carrier, and retailer systems.
The change applies to standard manifests and inventory manifests, following the updated
design specifications.
Key Enhancements
1. Serial Number Added to Manifest Documents
Serial numbers are now included in the item details table in:
● Master Manifest PDF
● BOL (Bill of Lading) PDF
● Inventory Master Manifest PDF (its variant template)
This ensures that all manifest-related documents contain consistent serial number visibility.
2. New Column in Templates
A new column “Serial Number” has been added to the Items table across applicable
templates:
● Master Manifest Template
● Inventory Master Manifest Template
● BOL Template
Design guidelines followed:
● Fixed column width for consistency
● Text wrapping enabled to prevent layout breakage
● No overflow or visual distortion even with long or multi-segment serials
3. Handling Missing or Long Serials
To maintain clean and predictable output:
● Missing Serial Number → leave the cell blank
● Long Serial Values → wrap gracefully within the column, maintaining the integrity of the row
4. BOL Support for Inventory Manifests
● Inventory manifests do not have a dedicated BOL template
● Only the Master Manifest PDF is updated for inventory manifests
This preserves existing workflow logic and avoids generating documents the inventory manifest
flow does not use.
Defect Fixes
Bug Fix: Missing Home Delivery Carriers in Transaction Entry
Overview
Users reported that when adding a new transaction under Order → P&L, the dropdown list of
available carriers was incomplete.
Specifically, for the transaction types:
● Last Mile
● Accessorial
● Claim
This issue prevented users from properly allocating transaction costs and contradicted the
behavior demonstrated during onboarding.
Key Fixes
1. Restored Full Carrier List for P&L Transactions
The carrier dropdown now correctly displays all Home Delivery carriers associated with the
shipper. This applies to all relevant transaction types.
2. Corrected Carrier Filtering Logic
A backend validation issue incorrectly filtered out carriers unless they matched a single specific
internal condition.
The logic was updated to:
● Include all carriers marked as Home Delivery
● Respect shipper-level carrier associations
● Apply consistent filtering across all P&L transaction types
3. Updated Transaction Type–Carrier Mapping
Fixed an internal mapping error where Last Mile, Accessorial, and Claim transactions were
not retrieving the correct carrier list.
Now all three transaction types properly reference the unified carrier selection logic.