postalref

Product Tracking and Reporting (PTR)

Product Tracking and Reporting is the USPS database that stores tracking scan data for all barcoded packages and extra services products. It sends tracking updates to USPS.com, Informed Delivery and external APIs. Mailers send it data on each package and get back a scan event extract file and a Confirmation/Error/Warning file.

Updated October 28, 202622 sources

What it is

PTR stores scan events from acceptance all the way to delivery. Its data comes from business mailers' files, handheld scanners, retail equipment, mail processing equipment and other Postal systems. Signature images are also available for applicable products.

Business customers receive extract files of tracking events. Individual customers use the USPS Tracking website to check delivery status and request proof of delivery or email notification.

PTR also processes and edits each Shipping Services File a mailer submits. A Shipping Services File is the electronic file containing all manifest and payment information.

USPS is moving PTR to a modernized platform, PTR2. PTR2 is designed for improved availability and performance with less latency and downtime.

How it works

  1. The mailer transmits its Shipping Services File to PTR over a secure protocol.
  2. PTR processes and edits the file against USPS specifications.
  3. PTR returns a Confirmation/Error/Warning file on the processing of each record.
  4. Scanners, retail terminals and processing equipment capture events from label creation to delivery.
  5. USPS sends the mailer a scan event extract file with every scan on its packages.
  6. The events also appear on USPS Tracking, the USPS mobile app and the USPS Tracking API.

The regular schedule sends the scan event extract file 16 times a day, and the premium schedule sends it 96 times a day.

Getting tracking data

PTR and PTR2 give customers their data through four channels.

  • The Tracking API, version 3.0 for PTR and version 3.2 for PTR2.
  • Webhooks, in the same two versions.
  • Scan Event Extracts.
  • Notifications by email and text message.

A user reaches the Tracking API by creating an app on the USPS developer portal. The app gives the user a key and secret, which every API call needs. The limit on calls per hour applies to the application, not to the CRID or auth token.

USPS encourages customers to move from flat file extracts to a Webhook that gives more real-time tracking updates. The default format of the scan event file is version 1.5. A customer who wants version 1.6 or 2.0 contacts the Confirmation Services Support Team.

Scan events

USPS lists each domestic scan event with its event code and the scripting customers see on USPS.com.

Domestic scan events in the Delivered status category. The filters show the other categories and the events that start or stop the clock.

PTR Domestic Scan Events, October 2026
EventAttributeExtract descriptionUSPS.com wordingStatus categoryStarts the clockStops the clock
01DELIVEREDDeliveredDeliveredNoYes
0101DELIVERED IN/AT MAILBOXDelivered, In/At MailboxDeliveredNoYes
0102DELIVERED FRONT DOOR/PORCHDelivered, Front Door/PorchDeliveredNoYes
0103DELIVERED PARCEL LOCKERDelivered, Parcel LockerDeliveredNoYes
0104DELIVERED LEFT WITH INDIVIDUALDelivered, Left with IndividualDeliveredNoYes
0105DELIVERED FRONT DESK/RECEPTION/ MAILROOMDelivered, Front Desk/Reception/Mail RoomDeliveredNoYes
0106DELIVERED GARAGE/OTHER DOOR/OTHER LOCDelivered, Garage or Other Location at AddressDeliveredNoYes
0107DELIVERED NEIGHBOR AS REQUESTEDDelivered, Neighbor as RequestedDeliveredNoYes
0108DELIVERED PO BOXDelivered, PO BoxDeliveredNoYes
0109DELIVERED INDIVIDUAL PICKED UP AT USPSDelivered, Individual Picked Up at Postal FacilityDeliveredNoYes

1 to 10 of 22 codes in the PTR Domestic Scan Events, October 2026.

USPS publishes a separate list of PTR2 domestic scan events, dated April 2026. Some event scripts differ, and some events exist in one system but not the other. PTR2 retires three events across tracking channels. One of them is the departure scan from a USPS facility:

PTR Domestic Scan Events, October 2026, EF

Event
EF
Extract description
DEPART USPS FACILITY
USPS.com wording
Departed USPS Facility
Status category
In Transit
What it means
Sortation process at the distribution facility is complete; the item is being dispatched on the next available transportation to the next processing facility or the destination delivery unit

The Confirmation/Error/Warning file

The Confirmation/Error/Warning file is PTR's report on the records of each Shipping Services File. When data does not meet USPS specifications, PTR generates an error or a warning. The file comes as a human-readable report or as a data file.

The first letter of each message line says what happens to the record:

  • An E line whose text does not start with FAIL means the record is rejected.
  • An E line whose text starts with FAIL means the record is loaded, and a corrections file is required.
  • A W line means the record is posted.

A record that fails the edits for a required field is rejected as an error. A record that fails the edits for a non-required field is listed as a warning but is still stored. PTR2 returns the file in the same format with the same information.

PTR2

The way mailers submit manifest data does not change with PTR2. PTR2 does not accept Shipping Services File versions 1.3, 1.4 and 1.5. It also does not accept Shipping Partner file versions 2.0 and 3.0.

The original PTR runs in parallel with PTR2 until customer migration is complete. USPS has not set a retirement date for the original PTR. The retirement date for the WebTools platform was January 2026.

Since June 2025, the PTR Tracking API gives no package origin and destination details. USPS.com and Informed Delivery still use the v3 API, so their messages and events can differ from v3r2.

Rules

Customers must transmit their Shipping Services Files to PTR using one of the following communication protocols:

A mailer must send its Shipping Services File to PTR by SFTP, by EDIINT AS2 or through Parcel Data Exchange. No other way of sending the file is allowed.

Customers must not repeat (duplicate) serial numbers for Electronic File Numbers used in Header Records or Package Identification Codes (PICs) used in D1 Records for 120 days from date of first use.

A mailer must not reuse an Electronic File Number or a Package Identification Code within 120 days of its first use.

Mailers must review their error/warning files to determine if there are errors or warnings that need to be addressed.

A mailer must read each Confirmation/Error/Warning file and find the errors and warnings it has to fix.

Mailers must use versions 1.6, 1.7 or 2.0

For PTR2, a mailer must send its Shipping Services File in version 1.6, 1.7 or 2.0.

Corrections should be resubmitted within 24 hours, to ensure receipt of all delivery information.

A mailer should send corrected records within 24 hours so that it gets all the delivery information.

During the file certification process, mailers should submit their manifest files to the PTR TEM environment

While its files are being certified, a mailer should send its manifest files to the PTR test environment, not to production.

What goes wrong

A rejected record can be corrected and sent to USPS again. The corrections file must use the Electronic File Number of the original file.

Duplicate Detail Records 1 within 120 days are charged by USPS Ship as duplicates. Duplicate Header Records that PTR processes may be rejected by USPS Ship. USPS Ship customers who send corrections after the 10th of the next month can be charged twice for the same mailpiece.

USPS lists each message PTR can return in its Confirmation/Error/Warning Message List. For example, CHECK DIGIT ERROR means the check digit in the label number is invalid.

Terms

Product Tracking and ReportingPTR, PTS, Product Tracking and Reporting system, Product Tracking Reporting, Product Tracking and Reporting (PTR) system, Product Tracking System
Each time a mailer submits a Shipping Services File, PTR processes and edits the file.
Shipping Services FileSSF, Shipping Service Files
The electronic file containing all manifest and payment information.
Confirmation/Error/WarningCEW, confirmation/error/warning file, Confirmation Error Warning (CEW) Report, PTR Confirmation Error/Warning Report
The confirmation/error/warning file identifies issues associated within the Shipping Services File record.
scan event extract fileCDE, Scan Event Extracts (PTR), Scan Event Extract, Customer Data Extract, Customer Daily Extract
This file contains every scan event that occurs on every package that the mailer included in the Shipping Services file.
Electronic File NumberEFN
Electronic File Number uniquely identifies the transmission of an electronic manifest, and must be unique for a period of 120-days. It is located in the header record of the Shipping Services File.
Package Identification CodePIC, Piece Identification Code
A Package Identification Code or PIC is a unique data string that serves as a unique tracking number for a mailpiece. Each PIC will consist of an Application Identifier, service type code, data string that will vary based upon the specific data construct, and a MOD 10 check digit.
Test Environment for MailersTEM, Testing Environment for Mailers, TEM (Testing Environment for Mailers)
The Test Environment for mailers (TEM) is a test platform designed to allow mailers to test their ability to submit electronic mailing information such as Full Service (FS) mailings to the Postal Service.

Documents

Technical Specifications

Publications

Fact Sheets

FAQs

Data Files

Release Notes

Contacts

  • Questions about PTR2 and its APIs go to PTR2APITesting@usps.gov.
  • Requests to raise the API call limit go to the Customer Access Team at APISUPPORT@usps.gov.
  • Technical support for manifest and extract files comes from the Package Services Customer Support Team, delivery.confirmation@usps.gov or 877-264-9693, Option 1.
  • USPS APIs support takes requests through its web form at https://emailus.usps.com/s/usps-APIs.

Sources