Grasshopper 3.24.31 Release Notes

 

Features:

Add Dimension Fields to Inventory Import

Overview:

Enhances the inventory import process by allowing users to include item dimensions (Length, Width, Height) in the import template, API, and preview, with robust validation for data integrity.

Key Enhancements:

●  Adds Length, Width, and Height as optional columns in the inventory import template.

●  Updates import API and preview screen to support new fields.

●  Validates dimension values for correctness and format.

 

Overview:

Improves data quality and user experience by adding validations to new optional fields in the manifest creation process.

Key Enhancements:

● Implements validation rules for new optional manifest fields to prevent incorrect data entry.

 

Overview:

Enhances the tracking page by allowing customers to view and optionally specify requested delivery hours, improving scheduling transparency.

Key Enhancements:

●  Adds support for displaying and capturing optional requested delivery hours on the tracking page.

 

Overview:

Improves the tracking page by enabling customers to select a preferred scheduling date, streamlining the delivery coordination process.

Key Enhancements:

●  Keep the scheduling date field blank by default or display “Select your preferred date” as a prompt to guide consignees/scheduler/users

●  Disable the Schedule Delivery (greyed out) button until a date is selected

●  This update will prevent accidental scheduling without a confirmed date, ensuring accuracy and reducing rescheduling requests/customer contact requests.

 

Overview:

Upgrades the quote calculator to consider the requested region, providing more accurate and region-specific pricing.

Key Enhancements:

●  A single zip code might be assigned to multiple regions. The calculator now provides the option to select the requested region.

●  Adds requested region support to the quote calculator for improved pricing accuracy.

 

Warehouse Inbound Report

Overview:

Introduces a new Warehouse Inbound Report, giving users better visibility into inbound inventory and warehouse operations.

Key Enhancements:

●  New report placement: Analytics → Warehouse.

●  Supported manifest types: Linehaul (Inbound) and Inventory.

●  Operational columns with deep links: Jump to the Manifest page and Carrier page directly from the grid.

●  Smart filters: Date (default Today, selectable back 2 years, up to a 30-day window per query), Hub (single select), Type (single select), Shipper (multi-select, searchable), with pagination.

●  Consistent sorting: Default sort by Arrival Date (newest → oldest), then Start Appointment Time (first → last), then End Appointment Time (first → last). Columns are not sortable.

●  BOL actions (single-select):

     â—‹  Download Master Manifest BOL (system-generated; includes manifest details + order IDs)

     â—‹  Download Manifest BOL (compiles all Order BOLs in the manifest) — disabled for Inventory manifests

     â—‹  Download External BOL (if an external BOL file was uploaded; otherwise disabled).

●  Insight boxes (KPIs): Manifests, Total Cube, Total Weight, Total Pieces.

●  Export options: CSV and PDF (exports current view, or only selected rows).

 

Overview:

We’ve added a new Cycle Count report that surfaces user-initiated counts in the Cycle Count area. This view helps supervisors and inventory teams review who counted what, where, and when—along with quick access to the scanned items. A banner clarifies that data is not real-time (periodically refreshed).

Key Enhancements:

●  Dedicated placement: Cycle Count area (user-initiated counts).

●  Human-readable run name: Server-generated ID in the format MDCC-##### (non-sortable).

●  Operational context: Hub, Location, User, start/end timestamps, and total scanned items.

●  Actionable detail: Click a cycle count name to open the scan results and item list.

●  Columns (List View)

     â—‹  Name (MDCC-#####; non-sortable)

     â—‹  Hub (sortable)

     â—‹  Location (sortable)

     â—‹  User (sortable)

     â—‹  Started at

     â—‹  Completed at

     â—‹  Total scanned items

●  Filters

     â—‹  Completed at (date)

     â—‹  Hub

     â—‹  Location

     â—‹  User

●  Row Actions

●  Left-click Name (MDCC-#####): Opens the Cycle Count Details page with the full scan results.

●  Items viewer (from “Total scanned items”):

     â—‹  Columns: item_id, serial, scan date, item name, sku, shipper, order, PO, scan status, Item Found, Exception

     â—‹  No filters or sorting in the items viewer.

     â—‹  Local display only: A Virtual Carrier (VC) cannot view remote-hub data in a local hub.

     â—‹  Visibility aligns to User profile, Warehouse profile, and Inventory profile permissions.

     â—‹  Future consideration: providing a VC cross-hub view.

     â—‹  Data is not real-time; a banner communicates this to users.

     â—‹  Item list (detail view) intentionally ships without filter/sort controls in the first version.

     â—‹  This first version enables to see a week of data, the system is being enhanced to provide a month of data

 

On-Time Performance (OTP) Report Last-Mile

Overview:

We rebuilt the OTP report for Last-Mile manifests to be fast, actionable, and multi-level. It now evaluates both pickup and delivery punctuality (leveraging new manifest-entry pickup logs) and supports drill-downs from carrier → driver → manifest → stop.

Key Enhancements:

     â—‹  Analytics → Last Mile → On-Time Performance (OTP)

●  Pickup + Delivery coverage: OTP now includes pickup performance in addition to delivery.

●  Multi-level views:

     â—‹  Carrier view – aggregated OTP by carrier.

     â—‹  Driver view – aggregated OTP by driver (filtered by selected carrier).

     â—‹  Manifest view – per-route details to spot issues.

     â—‹  Stop view – drill into individual stops for root-cause analysis.

●  Time segmentation: Toggle Daily / Weekly / Monthly to match your review cadence.

●  Data source: Last-Mile manifests only.

●  Interactions & Navigation

     â—‹  Start at Carrier → click to Driver → click to Manifest → click to Stop.

     â—‹  Filters persist as you drill down (date range and carrier selections carry forward).

●  Filters & Segmentation

     â—‹  Date range with Daily / Weekly / Monthly segmentation.

     â—‹  Carrier (required for Driver view).

     â—‹  Additional filters (e.g., driver or manifest) appear contextually as you drill.

●  KPIs & Measures (at each level)

     â—‹  On-Time Rate and counts (On-Time / Late / Early).

     â—‹  Pickup OTP and Delivery OTP shown side-by-side.

     â—‹  Basic volume context (e.g., total stops/manifests considered).

●  Notes & Limitations

     â—‹  Last-Mile only.

     â—‹  Pickup performance is available from the point we began logging at the manifest-entry level; earlier historical periods may not include pickup OTP.

     â—‹  Access and visibility respect existing role-based permissions.

     â—‹  Data availability only from year 2025

     â—‹  Covers activity up to one day before i.e., yesterday (T–1). 

 

Overview:

We’ve added optional fields to freight manifests to improve tracking, context, and coordination across systems. These updates include Freight Tracking Number, Shipper, and Appointment Hours with clear, role-based sync rules.

Key Enhancements:

●  Where it appears

     â—‹  Freight Tracking Number: Edit Freight only

     â—‹  Shipper (informational): Create Freight and Edit Freight

     â—‹  Appointment Hours (Inbound only): Edit Freight only; not shown on Outbound

     â—‹  Inventory manifests: no changes in this release

●  Freight Tracking Number (optional)

     â—‹  UI: Editable text field on Edit Freight.

     â—‹  In case of Virtual Carrier(VC): VC may add/update and publish to partners. Partners: field is read-only when received from VC.

●  Shipper (optional, informational)

     â—‹  Purpose: For cases where an entire freight manifest is dedicated to a single shipper. Not the Last-Mile “dedicated shipper” attribute.

     â—‹  UI: Autocomplete on Create and Edit Freight; editable.

     â—‹  Validation: Must match an existing shipper. If not matched, the value is cleared.

     â—‹  Global Sync: In partner accounts, the VC displays as the shipper for published manifests. Read-only for partners on VC-published manifests.

●  Appointment Hours (optional; inbound only)

     â—‹  Purpose: Receiving hours for freight (parity with Last-Mile receiving hours).

     â—‹  UI: Editable on Edit Freight; not available for Outbound.

     â—‹  For VC: VC → Partner: Published to partner; partners may edit locally (local edits do not sync back). VC updates later: Republish overrides partner’s local value.

●  Sorting, Validation & Behavior

     â—‹  Autocomplete/Validation (Shipper): User must select a known shipper; invalid text clears on blur/save.

     â—‹  Edit ability: As noted above; partner-side fields are read-only where specified.

●  Permissions & Visibility

     â—‹  VC accounts: Full edit as specified; can publish to partners. Partner accounts: Receive VC values; read-only where indicated; local edit allowed only for Appointment Hours.

●  Known Limitations (v1)

     â—‹  No Inventory-manifest specific fields in this release.

     â—‹  Appointment Hours are inbound-only; outbound is intentionally excluded.

---

Overview:

We’ve surfaced several feature flags in Settings → Advanced Settings so admins can see current configuration. These controls are view-only (not editable in UI). If you need a change, contact your Grasshopper admin/support team.

Key Enhancements:

●  What’s visible (by area)

●  Orders → Scheduling & Time Settings

     â—‹  Require a reason for rescheduling — When enabled, users must select a reschedule reason.

     â—‹  Display “Expected Arrival ETA” banner for Carrier users — Shows ETA banner to carrier roles.

     â—‹  Display “Expected Arrival ETA” banner for Shipper users — Shows ETA banner to shipper roles.

●  Orders → Data Exports

     â—‹  Include “Receiving Hours” columns in orders export — Adds receiving-hours fields to exports.

     â—‹  Include “Pre Delivery Questionnaire” columns in orders export — Adds PDQ fields to exports.

●  Orders → General

●  Show the “COI Required” column in the orders grid — Makes “COI Required” available as a grid column option.

●  Manifests → Data Exports

     â—‹  Include “Pre Delivery Questionnaire” columns in orders export — Adds PDQ fields to related exports.

 

Overview:

Fixes an issue where receiving hours were missing from the item-level export in the order grid, improving reporting accuracy.

Key Fixes:

●  Adds receiving hours to the item-level export in the order grid.