External release notes – Grasshopper – Version 3.24.17

New Features

• Cycle Count Management – Web Management
  • A new Cycle Count Management feature has been introduced in the web application allowing warehouse managers to create, track, and manage cycle count tasks efficiently. 
  • The warehouse mobile app was enhanced as well to enable cycle count
  • This feature enhances inventory accuracy by providing task assignment, progress tracking, and detailed reporting.
  • Key Capabilities
    • Create and Configure Cycle Count Tasks
      • Warehouse managers can create new cycle count tasks with specific parameters, including: Task Name, Region, Schedule, Locations & Assigned Users
    • Task List with Status and Progress Tracking
      • View a comprehensive list of all cycle count tasks.
      • Monitor status updates and progress tracking for each task.
    • Detailed Task Information
      • Access in-depth details of a cycle count task, including: Assigned users, Task progress & Exceptions and discrepancies
    • Editing and Updating Cycle Count Tasks
      • Modify cycle count details such as: Task Name, Schedule, Assigned Users & Locations
    • Marking Cycle Counts as Completed or Aborted
      • Warehouse managers can finalize tasks by marking them as:
        • Completed (when the count is successfully finished)
        • Aborted (if the task is canceled before completion)
    • Detailed Cycle Count Reports
      • Generate and download detailed reports containing:
        • Item breakdowns
        • Exceptions (missing or extra items)
        • Final task results
  • Benefits:
    • Enhances inventory accuracy with structured cycle counts.
    • Improves efficiency by allowing task assignment and tracking in one place.
    • Provides actionable insights through detailed reports and exceptions handling.
• Cycle Count Management – Warehouse Mobile App
  • The Cycle Count Management feature has been enhanced to display and manage active cycle count tasks assigned to the current user. 
  • This feature allows warehouse users to efficiently track, initiate, and complete cycle count tasks, improving inventory accuracy and operational efficiency.
  • Functional Enhancements
    • Active Cycle Count Task List
      • Displays a list of cycle count tasks assigned to the logged-in user.
      • Each task includes the following details: Task Name, Scheduled Date, Due Date & Remaining Items (Only shown if the task has been initiated)
    • Task Navigation
      • Tap on a cycle count task → Opens the Cycle Count Details screen.
      • Back Icon → Returns the user to the Warehouse Menu.
    • Empty State Handling
      • If no tasks are assigned, a dedicated empty state screen will be displayed based on the design guidelines.
    • “New Cycle Count” Button
      • A floating action button (FAB) at the bottom of the screen allows users to start an unassigned cycle count (FGO’s cycle count).
      • The button adapts its appearance in empty state mode.
    • Refresh Feature
      • Users can pull down to refresh the page.
      • Refresh triggers a new call to the Get Cycle Counts API to retrieve updated task information.
• Standardized “Arrived On Site” Button for All Order Types
  • A new enhancement has been introduced to standardize the “Arrived On Site” button across all order types in the Driver Mobile App. 
  • This update ensures consistent workflows for drivers at every stop and improves tracking of arrival times for reporting purposes.
  • Previously, the “Arrived On Site” button was not available for certain order types, including:
    • Pickup Orders (from vendors, customers)
    • Service Tickets
    • Return Orders
  • This inconsistency led to workflow variations and gaps in tracking driver arrivals.
  • Key Enhancements
    • Unified “Arrived On Site” Button Across All Stops
    • Improved Customer Interaction Flow
    • Simplified UI – Removal of “Take Action” Button & Popup
• Improved Batch Scanning for Mixed Barcode & QR Code Items
  • Previously, when users scanned a batch of items containing both barcodes and QR codes, the system would only mark as picked the items matching the last scanned code type. 
  • Additionally, the mobile app displayed a completion dialog without informing users that some items were not marked as picked.
  • Key Enhancements
    • The system has been updated to process both barcode and QR code items seamlessly, ensuring that all scanned items are properly picked.
    • The mobile app now provides clear feedback on partially successful batch picks.
    • New Error Message for Partial Success will be displayed to the user
• Benefits
  • Ensures all valid scanned items are picked, regardless of barcode type.
  • Provides clear user feedback on partial success cases.
  • Enhances batch-picking efficiency in the mobile app.
• New Tracking Events for Manual & Auto Lasso Actions
  • To improve order tracking visibility, new events have been introduced to distinguish between manual and automatic lasso actions. 
  • Previously, order-level tracking events were shared between both processes, making it difficult to differentiate how an order was scheduled.
  • Key Enhancements
    • New Events for Manual Lasso Actions
    • New Events for Auto Lasso Actions
• Master Manifest Alignment with Manifest Stop Allocations
  • To improve accuracy and consistency, the Master Manifest has been updated to align with the actual manifest’s stop and order allocations. 
  • Previously, the Master Manifest used its own logic to merge orders into stops, which sometimes led to bugs or inconsistencies.
  • Key Enhancements
    • Master Manifest Now Pulls Stops Directly from the Manifest
      • The stops list is now retrieved directly from the manifest rather than using independent merging logic.
      • Ensures that stop assignments remain identical between the manifest and the Master Manifest.
    • Improved Handling of Multiple Orders in a Single Stop
      • If multiple orders are assigned to the same stop (tag-along orders), the Master Manifest will now display them correctly.
      • Fixes prior inconsistencies where tag-along orders were sometimes not shown or merged incorrectly.
• Removal of OTP Verification for BTB Deliveries
  • To streamline the Proof of Delivery (POD) process for Business-to-Business (BTB) deliveries, OTP verification has been removed when delivering to companies. 
  • Previously, if the OTP flag was enabled, it would still be required for BTB deliveries, causing unnecessary verification steps.
  • Key Enhancements
    • No OTP for BTB Service Level Deliveries
      • For orders with BTB service level, the system will bypass OTP verification, even if the OTP flag is enabled.
      • The POD process will proceed without verification, ensuring a faster and smoother delivery experience for business customers.
    • Unaffected Deliveries
      • Non-BTB deliveries will continue to follow the existing OTP verification rules when applicable.
• Improved Serial Number Visibility in Order View
  • To enhance usability for customers working with Serial Numbers (SN) instead of Item IDs, the Order Page now provides better visibility for the SN column within the items table. 
  • Previously, users needed to manually resize the column to view the full serial number, impacting efficiency.
  • Key Enhancements
    • Full Serial Number Visibility by Default
      • The SN column will now automatically adjust its width to display the full Serial Number when opening an order.
      • No manual resizing is required to see the full value.
    • Smart Truncation on Resize
      • If a user manually resizes the SN column to a smaller width, the system will:
      • Truncate the value with an ellipsis (…) at the beginning instead of the end.
      • Ensures that the last characters of the Serial Number remain visible (important for differentiation).

Bug Fixes

• Incorrect RTBS Flag Assignment for Pending Pickup Orders
  • A defect was identified where orders in a “Pending Pickup” or “Pending Arrival” status were incorrectly appearing on the RTBS (Ready to Be Scheduled) list. 
  • This issue affected orders where some or all items were still awaiting pickup, leading to premature scheduling availability.
  • Fix Implementation & Validation Scenarios
    • Scenario A: Order Removed from Pickup carrier Manifest
      • When an order is assigned for pickup at the pickup partner’s side, but then removed from the manifest,
      • Ensure the RTBS flag is turned OFF.
      • On the virtual carrier side, RTBS remains unset until scheduling.
    • Scenario B: Order Duplication Due to Pickup Failure
      • If an order in status “Pickup Failed” is duplicated for redelivery,
      • Ensure the new order is NOT created with the RTBS flag on the Virtual Carrier side.
• Manifest Info Causing Report Failure for Return Orders
  • A recent update introduced Manifest Info to the Deliveries Report, but an issue was identified when processing Return Orders. 
  • Since manifest details for returns are retrieved from the items, and some return orders contain no items, the report failed and became undownloadable.
  • Issue Identified
    • The report broke when encountering a return order without items because the manifest info couldn’t be retrieved.
    • Running the same report while excluding the problematic date allowed it to generate successfully.