Carrier Performance in Pacejet helps you understand what is really happening with your in-transit shipments. Behind the scenes, Pacejet calls supported carrier status APIs several times per day, captures status changes for in-transit shipments, and makes that information available to you through:
The Pacejet UI
The Pacejet API
Webhooks that can push updates to ERPs, such as NetSuite
Selected reports and analytics
This article introduces how Carrier Performance works at a high level.
Key Topics Covered
Here are the key areas we will cover. With detail, screenshots, and examples below.
What is Carrier Performance? A plain-language explanation of what the feature does, how often it runs, and why it matters for shippers and operations teams.
How Pacejet collects carrier status updates: How Pacejet calls carrier status APIs, how frequently this happens, and which shipments are included in each polling cycle.
Understanding in-transit status transitions: What a status transitions are, how Pacejet records them, and how this creates a shipment-level status history over time.
Where you can see carrier performance data in Pacejet: An overview of where this data shows up in the Pacejet application (pages, views, and related), with screenshots.
Accessing carrier performance data via the Pacejet API: How the ShipmentStatus endpoint makes this data available to external systems.
Using webhooks to update ERPs: How webhooks can push carrier status changes from Pacejet into ERPs, and common integration patterns.
What is Carrier Performance?
Carrier Performance keeps Pacejet in sync with what your carriers are actually reporting about each shipment’s journey from origin to final delivery.
At the carrier level, every shipment is identified by a tracking number (for example, a UPS tracking number for each package). Behind the scenes, carriers continuously record status changes as a shipment moves through their network — from label creation, to pickup, through intermediate facilities, and ultimately to delivery. A typical UPS ground shipment might look like this:
Label created: The carrier receives the electronic shipping information, but the package has not yet been picked up.
Origin facility processing: (for example, Minneapolis, MN): The package is received, scanned through several internal steps, and prepared for linehaul.
Intermediate hubs: (for example, Hodgkins, IL → Maumee, OH): The package arrives and departs through multiple facilities as it moves closer to the destination.
Destination-area facility: (for example, West Carrollton, OH): Final processing, loading onto a delivery vehicle, and out for delivery.
Delivery scan: (for example, Franklin, OH): The package is scanned as successfully delivered.
In a well-executed delivery, all of these transitions can happen in under 48 hours from label creation to final delivery — and each scan represents a status transition that answers the everyday question: “Where is my shipment right now?”
The challenge for shippers, customers, and connected systems is that this information is constantly changing. Without automation, it is difficult to:
Keep internal operations teams up to date on the latest shipment status.
Provide timely and accurate answers to customers asking about their orders.
Drive downstream workflows in ERPs and other systems based on real-world status changes.
Pacejet’s Carrier Performance solves this by:
Polling supported carrier status APIs up to four times per day to capture the latest in-transit status transitions (default is one time/day).
Providing multi-carrier status updates for different carriers, depending on carrier API support, including webhooks.
Providing full shipment-level status visibility, not just a single current status snapshot.
Surfacing this data across Pacejet — in the UI, through the Pacejet API, and via webhooks that can update systems such as NetSuite.
This gives shipping, operations, and customer service teams timely, reliable visibility into what carriers are actually doing with each shipment, so they can respond faster, reduce manual tracking effort, and build more proactive customer communication.
How Pacejet Collects Carrier Status Updates
Pacejet keeps shipment status information current by running an automated status update process multiple times per day and by allowing users to request on-demand updates for specific shipments.
Scheduled Status Update Process
For each customer, Pacejet runs a status update process up to four times per day across all configured carriers in use.
During each run:
The up to four-times per day status update process is generally scheduled for morning, day, evening, and night updates.
The default setting for most customers is to call for status updates one time per day.
Custom schedules per customer are not supported; the schedule is optimized for update accuracy and resource utilization.
All shipped but not yet delivered and <30 days old shipments are included in the check.
For example, if a customer processes several thousand shipments per day, they may have 20k-60k shipments being checked with every status update process.Pacejet calls supported carrier status APIs to retrieve the most recent tracking events for each shipment.
Any new status transitions (for example, arrival at a new facility, out for delivery, delivered, or exception events) are made visible.
This approach ensures that in-transit shipments are refreshed several times per day without any manual effort, so downstream users and systems can rely on up-to-date information.
Example Performance Metrics - Sample job
The example below illustrates example performance for a large-volume status update job. Customer-specific details have been removed, but the numbers show how the process scales in practice.
Sample Job Execution
Start time: 2025-12-09 00:25:04
End time: 2025-12-09 04:19:25
Duration: ~3.9 hours
Total shipments processed: 60,137
Shipments with status updates: 1,913 (≈3.2%)
Webhooks raised: 330
First webhook raised: 01:02:41
Last webhook raised: 04:13:53
Webhook window: ~3.2 hours
Performance Insights
Shipment processing rate: ~15,420 shipments per hour
Webhook throughput: ~104 webhooks per hour
Webhook conversion: ~17% of shipments with new status updates triggered a webhook
These numbers highlight Pacejet’s ability to process tens of thousands of shipments per job while still delivering timely updates and webhooks for shipments that experience meaningful status changes.
Best-Practice Notes
Not all status updates raise webhooks — typically, only qualifying events (for example, Delivered or configured exception statuses) trigger them.
Webhook throughput depends on carrier volume, carrier API responsiveness, total undelivered shipments, and actual shipment activity during the job window.
Understanding in-transit status transitions
Carrier Performance is built around the concept of status transitions — the individual events that describe how a shipment moves through a carrier’s network over time.
What is a Status Transition?
A status transition is any meaningful change reported by the carrier for a shipment. Examples include:
Label created or shipment information received
Shipment picked up from origin
Arrival and departure scans at intermediate hubs
Out-for-delivery events at the destination-area facility
Final delivery scans
Exception or delay events
Each transition includes at least a status, timestamp, and location (where available), and becomes a line in the shipment’s status history.
Status History vs. Current Status
Traditional tracking views often focus on a single current status (for example, In transit or Delivered). Carrier Performance goes further by:
Recording a full view of all transitions as new ones occur
Building a timeline of events for the shipment
Surfacing historical context, so users can see how and when a shipment moved through the network
This richer view makes it easier to understand patterns such as repeated exceptions, long dwell times at specific facilities, or unusually fast/slow lanes.
On-demand Status refresh for Individual Shipments
In addition to the scheduled status update processes, Pacejet also supports interactive status refresh for specific shipments:
Users can drill down into the status view of an individual shipment.
Clicking the Status function (or similar control) triggers a real-time call to the carrier’s status API.
Pacejet then displays an up-to-date list of all available transitions for that shipment, even between scheduled status update runs.
This combination of scheduled polling and on-demand checks gives operations and customer service teams a reliable, current view of shipment progress whenever they need it. The screenshot below provides an example of a drill-down status display where users can see the full series of delivery events update from a specific shipment.
Where You Can See Carrier Performance Data in Pacejet
Carrier performance status information is integrated into core Pacejet workflows so users can quickly see shipment health, drill into problem areas, and answer "where is my shipment?" in a few clicks.
Shipments page overview
The Shipments page provides a high-level view of shipments during their delivery cycle, including a summarized breakdown of shipment status. Typical status groupings include:
Total Shipments
Tracked
Delivered
In transit
Exception
Late
Delivered late
These counts give a fast snapshot of overall performance — for example, how many shipments are still in transit, how many are late, and how many have been successfully delivered. The screenshot below shows an example data set for a customer using only UPS and FedEx.
Drilling Down Into Status Groups
From the Shipments page, users can click any status grouping (for example, Exception or Delivered late) to drill down into a filtered list of the shipments in that category. This makes it easy to:
Focus on problem shipments that require attention.
Review detailed status histories for specific shipments.
Prioritize follow-up work for customer service or operations teams.
The screenshot below shows an example drill-down from clicking on the UPS logo in the Shipments summary page. In this example drill-down, a recent date range of shipments for UPS can be viewed in more detail. Users can further narrow the view via searching or by clicking on the detail in each status transition group.
Searching and Filtering Shipments
To narrow the view further, users can combine status groupings with search and filter options. Common filters include:
Specific carriers (for example, UPS, FedEx, regional carriers)
Date ranges (for example, shipments created or shipped in a certain window)
Individual shipments (by tracking number, order number, or other identifiers)
Together, these tools let users move from a high-level performance summary down to the exact shipments they need to investigate, always backed by the underlying status transition history collected from carrier APIs.
Accessing Carrier Performance Data via the Pacejet API
The ShipmentStatus endpoint in the Pacejet API provides direct access for ERPs, WMS platforms, and other external applications to query shipment status through the carrier connections that Pacejet manages.
How ShipmentStatus works
The ShipmentStatus API exposes the in-transit status transitions that Pacejet collects from carrier status APIs. This gives external systems a way to retrieve the same rich shipment-level status history that is visible inside Pacejet, including key details such as:
Current shipment status
Full status transition history (events, timestamps, locations where available)
Exception or delay indicators
Flexible Lookup Options
You can call the ShipmentStatus API using several different identifiers, depending on what your upstream system knows about the shipment:
Carrier tracking number (for example, a UPS or FedEx tracking ID)
Pacejet transaction ID
-
External transaction identifiers such as:
ERP fulfillment numbers
WMS shipment IDs
Other external reference values
This flexibility makes it straightforward to embed shipment status lookups into existing order, fulfillment, or customer service workflows without changing how those systems identify shipments. The screenshot below illustrates using the Pacejet API Samples Page to run the ShipmentStatus API endpoint while using a Transaction ID to find status of a shipment.
Using Webhooks Together with the ShipmentStatus API
Pacejet also provides webhook event subscriptions so external applications can react to important shipment events without constantly polling for updates.
What Webhook Subscriptions Do
You can configure webhook subscriptions so that Pacejet sends an event notification to your ERP, WMS, or other application when a shipment is considered to delivered to the consignee. This includes:
A shipment reaching a Delivered status on-time
A shipment is delivered with Exception status (for example, delivered late)
Each webhook provides enough identifying information (for example, tracking numbers or transaction references) for your external system to know which shipment changed.
Common Integration Pattern
A typical integration pattern combines webhooks with the ShipmentStatus API:
Subscribe to webhook events for shipment milestones that matter to your business (for example, Delivered is currently supported).
When a relevant event occurs, Pacejet raises a webhook to your ERP, WMS, or integration service with the shipment identifiers.
Your application then calls back to the ShipmentStatus API endpoint using those identifiers to retrieve the latest current status, full status transition history details for downstream processing.
Your ERP or WMS uses that data to update internal shipment records, drive workflows (such as invoicing or exception handling), or trigger customer notifications.
This approach minimizes unnecessary polling while still giving external systems on-demand access to detailed, up-to-date carrier status information whenever an important event occurs.
The screenshot below illustrates a sample webhooks configuration for shipment status updates.