PitneyTrack® Update Hub

We’ve curated the key updates from our latest release for you below. For more details and to explore additional changes, view the full release notes here.

Release Date - September 18, 2026

What’s new

Set proof requirements for custom statuses

Configure photo and signature requirements for custom package statuses to support the proof collection needs of different workflows.
How it works:
  • Configure photo and signature options separately for web and mobile.
  • Make each proof type unavailable, optional or required.
  • Required proof must be provided before the status update can be completed.

Customize fields for locker deliveries

Control the additional information collected during mobile locker deliveries so your teams can capture the package details your organization needs.
How it works:
  • Choose which supported package and custom fields are displayed or required.
  • Configure fields to use the previous entry when appropriate.
  • Settings apply to front-loading and rear-loading locker workflows and can be copied to other sites.

Update multiple packages at once

Find and update multiple packages in one place to reduce repetitive package maintenance and simplify work with larger package volumes.
Where to view:
  • Search using tracking numbers or advanced package filters.
  • Select multiple packages and update them in one action.
  • Users with the appropriate permissions can also delete multiple packages and download or print updated manifests.

Include package photos in notifications

Add package photos to receiving notification emails to give recipients more information to help identify and verify incoming packages.
How it works:
  • Add the Package Photo variable to a receiving notification template.
  • The most recent available package photos are attached when the notification is generated.
  • Notifications are sent without attachments when no photos are available.

Manage contacts with role-based permissions

Give administrators more control over contact management by assigning specific permissions for shared and private contact actions based on each user’s role.
How it works:
  • Assign permissions for creating, editing, deleting, importing and exporting contacts.
  • Control shared and private contact permissions separately.
  • Users see only the contact actions available to their assigned role.