PitneyTrack Enterprise Release Notes version 1.122.0 (March 11, 2026)
Products affected: PitneyTrack® Enterprise
What's New
Web browser and mobile app: Retain last entry
A new Retain Last Entry option allows the system to automatically fill in the last saved value for certain fields when receiving or editing a single package. This helps speed up data entry and improves workflow efficiency.
Admins must enable the Quick Receive feature in Subscription Roles before users can access this option. In Receiving Settings, a new Retain Last Entry checkbox appears next to each field. It can only be turned on if that field is set to Display. By default, the option is off.
When a user enables Retain Last Entry for the first time, a popup explains how it works. An info icon next to each field also provides guidance. This feature only applies to single‑package Receive and Edit workflows.
When Retain Last Entry is enabled for a field, that field will automatically populate with the value used in your most recent saved transaction. If the previous transaction didn’t include a value, the field stays blank.
System‑generated or existing data always overrides retained values. This includes values from scanning decode logic, previously saved packages, automation rules, or recipient custom fields.
For List or Barcoded Entry fields, if both Set First Value as Default and Retain Last Entry are turned on, the system will use the retained value first. If no retained value exists, it falls back to the first default option.
On Mobile, retained values are stored per device and do not transfer when the same user logs in on another device.
Web browser and mobile app: Front‑loading package handling options
The mobile front‑loading workflow now follows the Delivery setting Receive while placing packages into lockers from the front – when using mobile device, allowing admins to control how scanned packages are handled during locker placement. If the setting allows receiving during placement, users can receive and place both new and already‑received packages in a single workflow. If the setting allows placement only for packages already received, the system will block new packages and display a message. If the setting requires a package to be received and have an existing locker reservation, the system will block any new package or any received package without a reservation. These rules ensure that locker placement follows the exact process defined by the admin.
Web browser and mobile app: Add to existing Locker Reservation – New delivery setting
A new option in Delivery Settings allows administrators to decide whether users can add more packages to an existing locker reservation for the same recipient. This setting appears as an Add to Existing Locker Reservation checkbox, located below the front‑loading configuration in Delivery Settings, and is turned on by default.
When using the web browser, this applies to the Receive and Edit package workflows. When using the mobile app, it applies to Receive, Edit, Rear Loading, and Front‑loading. When the setting is enabled (default), users will see a modal offering the choice to add a package to an existing locker reservation if one already exists for the same recipient, or continue with a new locker assignment. When the setting is disabled, the modal will not appear, and the workflow will move forward using the standard locker reservation process without offering the option to add to an existing reservation.
Web browser and mobile app: Configurable Manifest filter fields
A new Delivery Settings option now allows admins to choose which custom fields appear as filter options on the Mobile Manifest page. When the Only confirm if more than X packages setting is selected, a new section, Select additional fields that you would want to filter by on manifest page, becomes available. Several core fields (Package Location, Received Date, Department, Recipient, Given To, and Status) are always included, shown as checked and disabled so they cannot be changed. Admins can then choose which active custom fields should appear as additional filters. All existing and newly created custom fields are selected by default, but admins may uncheck any that should not appear in the Mobile Manifest filters.
Latest Updates
Mobile app: Improved locker loading selection
The mobile app’s Place in Locker workflow now offers a smoother experience by replacing the old toggle with a simple dropdown menu. When users go to Landing Page > More > Place in Locker, they can choose either Load from Front or Load from Rear from the new dropdown. The selected option is immediately applied to the workflow, highlighted for clarity, and saved on the device so it becomes the default for future sessions. The interface automatically adjusts based on the choice, making the process more intuitive and consistent.
Mobile app: Pairing multiple locker banks in one front‑loading session
Mobile users can now scan and pair multiple locker banks during a single front‑loading session. A helper message on the Place in Locker scan screen explains this capability, and all paired banks appear in a list that users can manage or remove before continuing. When scanning an additional locker bank, users can choose to add it, switch to it, or discard it. The Continue button becomes active once at least one locker bank is paired, and the paired banks are shown at the top of the Package Scan screen with a Manage option for easy updates.
UPDATED: March 11, 2026