PitneyTrack Inbound Release Notes version 1.101.0 (April 4, 2025)

• New Features
• Enhancements
• Issues Fixed

New Features

Web browser: Package Statuses - Default and Custom as Active and Inactive

In the Receiving Settings, the Custom Status menu has been renamed to Package Statuses. To access it, click the Settings icon > Receiving tab > Package Statuses.

On the Package Statuses page, desktop users can mark Default and Custom Package Statuses as Active or Inactive. By default, all statuses are marked as Active.

Users can edit a status by clicking the pencil icon and marking it as Inactive. However, Received and Delivered statuses cannot be marked as Inactive. Inactive statuses will appear at the bottom of the list and will not be shown in the Status menu.

Web browser: Package Statuses – Type and Active columns

Two new columns, Active and Type, have been added to the Package Statuses page.

The Type column helps desktop users differentiate between Default and Custom Package Statuses, while the Active column allows users to identify which Package Statuses are Active or Inactive.

Web browser and mobile app: Package Statuses – Order arrangement

Users can utilize the Reorder Statuses option on the Package Statuses page to arrange the order of active package statuses. This feature enables default and custom package statuses to be displayed in the configured order within the Status menu across all desktop and mobile app pages.

Mobile app: Manage the Receive during checkpoint behavior for new packages

On the checkpoint Settings page for web browser users, there's a new option to manage the Receive during checkpoint behavior. This setting allows admins to restrict mobile app users from scanning new packages on the Checkpoint screen. If the Only checkpoint packages which have been received option is selected, mobile app users won't be able to add new packages during the checkpoint workflow. By default, the setting is set to Allow receive during checkpoint.

Web browser: Import Expected Packages for Carrier and Inbound Site

Users can now import the expected packages for the day, including information about recipients and the senders. This feature allows the details to automatically populate on the Receive page when scanning the expected package.

Web browser and mobile app: Auto-populate information for Recipient, Sender, and Carrier for an Expected Package

When users import package data, the carrier, sender, and recipient information will automatically fill in the corresponding fields on the received form when a package is scanned. For this feature to function correctly, the imported contact information must match the existing contacts in the Address Book. If the sender or recipient information does not match, their respective fields will remain empty when scanning the package on the Receive page.

Mobile app: Select Expected package file from Manifest menu on quick receive

Users with access to the Expected Packages feature will see a Manifest menu below the Tracking Number field on the Quick Receive screen. This menu displays the names of the Expected Packages files imported for the default site selected on the landing page. Users can scan the expected packages listed in the specified file when they choose an option from the Manifest. If a user scans packages not included in the selected file, a pop-up modal will prompt them to decide whether to add the package to the scanned packages list.

Enhancements

There were no enhancements in this release.

Issues Fixed

There are no new fixes in this release.