PitneyTrack Enterprise Release Notes version 1.131.0 (September 18, 2026)

• What's New
• Latest Updates

What's New

Requiring photo and signature proof for custom package statuses

You can now configure photo and signature proof requirements for custom package statuses, giving you more control over how package updates are verified. When setting up or editing a custom status, you can choose whether proof collection is available or required and configure photo and signature options separately for web and mobile users. This allows you to tailor proof requirements to specific workflows, including requiring no proof, a signature only, a photo only, or both a photo and signature. When proof collection is enabled, users are prompted to provide the required proof before they can complete the status update. This enhancement helps improve package traceability, supports auditing and compliance requirements, and allows proof collection processes to align with your organization's operational needs.

Collecting proof for custom status updates

When you update a package to a custom status, the desktop application and mobile app now display photo and signature options based on the proof requirements configured for that status. Depending on the settings, users may be asked to provide a signature, a photo, both, or no proof before completing the update. The proof collection experience is consistent with existing delivery and checkpoint workflows, making it easier to use across the application. Any photo or signature collected is stored with the specific status event and remains linked to that event, creating a complete history of package activity. This enhancement improves package accountability, supports chain-of-custody tracking, and helps maintain accurate records for status updates.

Configuring additional fields for locker deliveries in the mobile app

You can now customize the information collected when delivering packages to lockers through mobile locker workflows. A new Delivery to Lockers settings page lets you control which additional fields are displayed, required, or prefilled with the previous entry for locker deliveries. Supported fields include sender, carrier, carrier service, comments, PO number, cost account, and custom fields. Any changes you make are automatically reflected in both front-loading and rear-loading locker workflows, and the same settings can be copied to other sites to maintain consistency. This enhancement helps streamline locker deliveries by displaying only the information your organization needs while simplifying administration across multiple locations.

Capturing additional package details when loading lockers from the rear

The Load from Rear locker workflow in the mobile app now supports additional package and custom fields, giving you more flexibility when placing packages into lockers. Administrators can control which fields are displayed, required, or automatically populated with the previous entry through the Delivery to Lockers settings. Supported fields include sender, carrier, carrier service, comments, PO number, cost account, and custom fields. Required fields must be completed before a package can be placed in a locker, and fields configured to retain the last entry help reduce repetitive data entry. Field order follows the configured settings, and information entered during a locker placement transaction can be applied to multiple packages for the same recipient. This enhancement streamlines locker workflows, improves data consistency, and makes it easier to capture the information needed during package placement.

Capturing additional package details when loading lockers from the front

The Load from Front locker workflow in the mobile app now supports additional package and custom fields, allowing you to collect more information when placing packages into lockers. Administrators can control which fields are displayed, required, or automatically populated with previously entered values through the Delivery to Lockers settings. Supported fields include sender, carrier, carrier service, comments, PO number, cost account, and custom fields. Required fields must be completed before a package can be placed in a locker, and fields configured to retain the last entry help reduce repetitive data entry. Additional fields appear in the configured order, while standard locker placement fields remain unchanged. When placing multiple packages for the same recipient, entered values can be applied across the transaction, helping improve efficiency, consistency, and data accuracy.

Including package photos in receiving notifications

Receiving notification emails can now include package photos, making it easier to identify and verify deliveries. A new Package Photo variable is available when creating or editing notification templates and can be added directly to the email content. When a notification is generated, the system automatically attaches the most recent package photos available for that package. If no photos are available, the notification is sent without attachments. Package photos are also supported for consolidated receiving workflows, helping provide recipients with additional context and visibility into incoming packages. This enhancement improves package identification and gives recipients a clearer view of the packages associated with their notification.

Updating and deleting multiple packages at once

You can now manage multiple packages from a single location using the new Bulk Update Packages feature. Search for packages using tracking numbers or advanced filters such as recipient, carrier, sender, date, package status, package location, department, and custom fields. After finding the packages you need, you can update multiple records in one action, and users with the appropriate permissions can also delete multiple packages at the same time. You can then download and print updated package manifests as needed. This enhancement reduces repetitive package maintenance tasks, makes it easier to work with large volumes of packages, and helps improve efficiency by allowing package updates and searches to be completed more quickly.

Latest Updates

Configuring photo and signature proof for checkpoints

Checkpoint settings now offer more flexibility by allowing photo and signature proof requirements to be configured separately for web and mobile checkpoint workflows. The Signature Option setting has been renamed to Proof of Checkpoint, and a new Photo Proof option is available for both platforms. You can choose whether signature proof and photo proof are turned off, optional, or required, making it easy to support different proof collection requirements, including signature-only, photo-only, either proof type, or both. Updated settings apply to future checkpoint transactions only and automatically sync to supported mobile applications. This enhancement helps improve package accountability, supports more complete proof of completion records, and delivers a consistent checkpoint experience across web and mobile devices.

Capturing photo proof for checkpoint transactions

You can now capture photo proof when updating a package to a checkpoint status in the desktop application or mobile app. If photo proof is enabled in checkpoint settings, users may be prompted to provide a photo, a signature, or both, depending on the configured requirements. When photo proof is required, the checkpoint transaction cannot be completed until a photo is captured. Users can take, retake, replace, or remove a photo before saving, and each checkpoint event can include one associated photo. Photos and signatures are stored with the related checkpoint activity, making it easy to view proof details from package history and confirmation records. This enhancement improves package tracking, strengthens accountability, and provides a more complete record of checkpoint activity.

Including photo proof in checkpoint email notifications

Checkpoint email notifications can now display photo proof captured during checkpoint transactions. When creating or editing a notification template, you can add the Proof of Delivery Photo variable from the available data fields and place it anywhere in the email content. If a photo is captured as part of the checkpoint event, the image is automatically included in the notification sent to recipients. Existing notification templates are not changed and will only include photo proof if you add the new variable. This enhancement improves visibility into checkpoint activity, provides recipients with supporting proof information, and helps strengthen package tracking and accountability.

Selecting package activity and report dates from the last two years

The date selection experience has been updated to provide a more consistent and streamlined way to filter package activity and report data. Custom date range filters now support dates from the previous two years only, and the year selection list displays only years within that available data range. The same behavior is used across package activity and reporting pages, helping ensure a consistent experience whenever you select dates. This enhancement makes it easier to find available data, reduces confusion caused by unsupported date ranges, and simplifies date filtering throughout the application.

Controlling contact actions in receiving workflows

Receiving workflows on desktop and mobile devices now follow your assigned contact management permissions. Based on your access level, you may be able to add, edit, delete, view, or select contacts during receiving activities. Contact-related actions and options are displayed only when you have permission to use them, helping keep workflows simple and relevant to your role. Users without contact management permissions can still view required contact fields, but those fields are read-only and cannot be changed. This enhancement improves security, creates a more consistent experience across receiving workflows, and ensures users can access only the contact functions they are authorized to perform.

Expanding and collapsing workflow settings

The Input Field Options page now includes expand and collapse controls for workflow sections in both web and mobile settings. Workflow areas such as Receive, Edit, Deliver, Delivery via Manifest, Delivery to Lockers, and Pouch can be expanded when you need to view or update settings and collapsed when they are not needed. This enhancement helps keep configuration pages organized, reduces on-screen clutter, makes settings easier to navigate, and minimizes scrolling when managing input fields across multiple workflows.