How Postal Tracking Numbers Actually Work

A tracking number is a structured code, not a random string

Every tracking number follows a defined format set by the carrier that issued it. Segments within the number typically identify the carrier, the specific service level, and a unique serial identifier for that shipment.

This structure exists so that any scanning system worldwide can instantly recognize which carrier a package belongs to and route tracking queries to the correct database, even before checking the number against any records.

The leading digits usually identify the service type

Many carriers use a fixed prefix of several digits at the start of a tracking number to indicate which mail service was used, such as express, priority, or standard ground shipping.

This means two tracking numbers of similar length from the same carrier can represent very different delivery speeds and handling priorities purely based on those leading digits, before any tracking event has even occurred.

A checksum digit catches typing and scanning errors

Most tracking number formats end with a checksum digit, calculated mathematically from all the preceding digits using a formula the carrier defines, commonly a variant of a modulo calculation.

When a number is typed into a tracking website or misread by a barcode scanner, the system recalculates this checksum and rejects the entry if it does not match, catching a mistyped digit before it causes a false result.

A scan event is logged at physical checkpoints, not continuously

Tracking updates do not stream in real time as a package moves. Instead, a barcode scanner records a discrete scan event only when the package physically passes a specific checkpoint, such as arrival at a sorting facility or loading onto a truck.

Between two such checkpoints, the package is genuinely in transit but produces no data at all, because nothing scans it again until it reaches the next facility on its route.

Sorting facilities are where most scans actually happen

A typical package passes through several regional and hub sorting facilities between origin and destination, and each facility scan is logged as a status update visible to the sender and recipient.

The number of these facilities, and therefore the number of visible scan events, varies enormously depending on distance, whether the shipment crosses a border, and which carrier network handles each leg of the journey.

Long gaps between scans are usually normal, not a red flag

A package can spend a full day or more physically in transit inside a truck, plane, or shipping container between two facilities, during which no new scan event occurs at all, even though the package is moving correctly.

This is the single most common reason tracking appears frozen: the absence of an update reflects the absence of a scan checkpoint along that stretch of the route, not a problem with the shipment itself.

Crossing an international border introduces a distinct gap

When a shipment crosses a border, it typically leaves the origin country's postal tracking system and must be picked up by the destination country's own carrier system, which often does not share data instantly with the origin system.

This handoff commonly produces the longest visible gap in tracking history, sometimes several days, because the two national systems only exchange status updates at set intervals rather than continuously.

Customs holds are logged separately from transit scans

A shipment held for customs inspection or duty assessment sits in a specific customs facility, and depending on the country, this status may or may not generate a visible tracking update distinct from a normal transit scan.

Some customs authorities post a clear status like held by customs, while others simply produce no new scan for an extended period, making a customs hold visually indistinguishable from an ordinary transit gap to the recipient.

Third-party marketplaces often display a partial tracking record

When a package is purchased through an online marketplace rather than tracked directly on the carrier's own site, the marketplace's tracking page sometimes only pulls a subset of scan events from the carrier's full record.

Checking the tracking number directly on the originating carrier's website, rather than solely on the marketplace's page, frequently reveals additional scan events the marketplace simply did not display.

A last-mile carrier handoff can reset the visible tracking history

For many international shipments, one carrier handles the long-distance leg and hands the package to a completely different local last-mile carrier for final delivery, each running its own separate tracking number and system.

This handoff sometimes produces a new tracking number specific to the local carrier, and looking up only the original number after this point can show no further updates even though delivery is actually proceeding under the new number.

Barcode format determines how automated the scan process is

Standard tracking numbers typically use a linear or two-dimensional barcode, such as Code 128 or a Data Matrix code, that automated sorting machines read at high speed without any human handling.

In facilities without full sorting automation, staff scan packages manually with a handheld device, which introduces the possibility of a package physically passing through without being scanned at every single point, especially during high-volume periods.

A missed scan does not necessarily mean a missed step

Occasionally a package genuinely passes through a facility without triggering a scan, due to a barcode being damaged, poorly printed, or obscured, or simply a handling error at a busy sorting point.

This produces a tracking history with an apparent jump, where the package's next confirmed location is much further along the route than its last logged scan, without any of the intermediate steps having failed.

Weekends and holidays pause scanning without pausing transit

Sorting facilities and delivery routes generally reduce or halt operations on weekends and public holidays, meaning packages already in the network simply wait without new scans until operations resume.

A package that appears stalled starting on a Friday evening and resuming Monday morning is very often just following this operational schedule rather than experiencing any actual delay in handling.

Estimated delivery dates are separate from actual scan data

The estimated delivery date shown on a tracking page is typically calculated from historical averages for that route and service level, not derived from the real-time location of the specific package.

This means the estimate can shift, sometimes without a clear reason shown to the customer, as the carrier's system recalculates based on updated network conditions rather than any change to the package itself.

Duplicate or reused tracking numbers are rare but possible

Carriers design their numbering systems to avoid reuse within a reasonable timeframe, but very old formats or high-volume periods have occasionally led to collisions or number reuse across different shipments.

When a tracking number appears to show information for the wrong package entirely, checking that every digit was entered correctly is the first step, since even one transposed digit points to a completely different valid shipment.

Address labels and tracking numbers are two separate systems

The physical destination address printed on a shipping label is read separately from the tracking barcode by sorting machinery, meaning an address error and a tracking anomaly are unrelated problems with different causes.

A package can have a perfectly functioning tracking number while still being misrouted due to an address issue, and conversely a correctly addressed package can show gaps in tracking purely from missed or delayed scans.

Some carriers offer more granular tracking than others

Premium express services generally log more frequent scan events, sometimes including vehicle-level GPS updates, while economy or standard mail services often provide only a handful of major checkpoint scans for the entire journey.

This difference in granularity is a deliberate cost trade-off rather than a technical limitation, since more frequent scanning requires more infrastructure and staff time per package.

A tracking status label does not always match the physical reality precisely

Status labels like out for delivery or in transit are generalized categories applied by the carrier's software, and the exact physical state of the package at any given moment can be slightly ahead of or behind what the label suggests.

This is a known limitation of batch-processed tracking systems, where a status update sometimes reflects a scan that occurred minutes to hours earlier rather than the package's true current position.

Rural or remote destinations naturally produce sparser scan data

A package heading to a remote address typically passes through fewer intermediate sorting points with automated scanning and more legs handled by smaller regional carriers with lighter-weight tracking infrastructure.

This is why two packages sent the same day from the same origin, one to a major city and one to a rural area, can show very different amounts of tracking detail despite both eventually arriving successfully.

A carrier's own app can lag behind its website, or vice versa

Some carriers run their mobile app and web tracking page on slightly different update cycles or cached data layers, which can result in the two showing a different most-recent scan for the same tracking number for a short period.

Refreshing both, or waiting a short interval, typically resolves the discrepancy, since it usually reflects a caching delay rather than genuinely conflicting data about the package.

Multiple tracking numbers can apply to one order

A single order containing several items is often split into multiple physical parcels for shipping efficiency, and each parcel receives its own separate tracking number even though the customer placed one order.

Confusion arises when a customer tracks only one of these numbers and assumes the entire order status, missing that other items are following an entirely separate, and sometimes slower, path.

A carrier's system occasionally shows a scan out of order

Because scan data from different facilities sometimes uploads to the central system on a delay, a later scan can occasionally appear in the tracking history before an earlier one that was simply slower to sync.

This produces a brief, confusing display where the timeline seems to jump backward, which usually self-corrects once all pending scan data finishes syncing to the central tracking database.

Contacting the carrier is more useful after a defined threshold

Most carriers publish a guideline, often several business days beyond the estimated delivery window, after which a customer is advised to open a formal inquiry rather than continuing to just refresh the tracking page.

Before that threshold, an apparent gap is statistically far more likely to be a normal scan gap than a genuinely lost or mishandled shipment, so an inquiry filed too early often just gets closed with no new information.

Tracking numbers are also used to detect fraud and theft

Because each scan event timestamps a package's physical location, carriers and investigators use the full scan history forensically to determine exactly where in the chain a package went missing or was tampered with.

This same data that frustrates a customer waiting for an update is precisely what allows a carrier to pinpoint theft to a specific facility or delivery route when investigating a genuine loss.

Some countries lack a unified national tracking backbone

In regions where postal infrastructure is less centralized, a package may pass through several independently operated regional carriers each with its own partial tracking system, none of which shares complete data with the others.

This structural fragmentation, rather than any error in a specific shipment, explains why tracking for some international routes remains noticeably sparser than domestic tracking within a single well-integrated national system.

Scan data privacy is limited to what the customer needs to know

Carriers deliberately withhold certain operational details from public tracking pages, such as the specific vehicle, internal facility routing decisions, or staff handling information, showing only customer-relevant location and status summaries.

This is a business decision about what to surface, not a technical inability to provide more detail, since the carrier's internal systems typically log far more granular data than what any customer-facing page displays.

Air versus ground routing changes the expected scan cadence

A package routed by air passes through fewer physical handoff points relative to distance than one routed entirely by ground truck, so the number and spacing of expected scan events differs meaningfully between the two, even for similar total transit times.

Not knowing which mode a given shipment actually uses, since carriers rarely disclose this to the customer, makes it harder to judge from scan gaps alone whether a delay is unusual for that specific shipment.

A returned or redirected package restarts part of the tracking narrative

If a delivery attempt fails or an address issue triggers a redirect, the tracking history logs this as a new distinct event, sometimes making the timeline appear to move backward geographically even though nothing was lost.

Reading the full event description, not just comparing city names between two entries, clarifies whether a package is genuinely being returned or simply rerouted through an intermediate hub on its original path.

Bulk commercial shipments sometimes scan as a batch rather than individually

Large commercial senders occasionally hand off hundreds of parcels at once, and some facility systems log the batch's arrival as a single scan event applied to every tracking number in it, rather than scanning each barcode separately.

This practice, while efficient for high-volume senders, can make a customer's individual tracking history look sparser than a single retail customer's package moving through the same facility with individual scans.

Weather and operational disruptions get folded into normal transit gaps

Severe weather, strikes, or aircraft grounding can delay a shipment for days without necessarily generating a distinct status message explaining the cause, since not every carrier's system surfaces operational context to the customer-facing tracking page.

A customer seeing only a generic no update status during such an event has no way to distinguish it from an ordinary unremarkable transit gap without checking the carrier's separate service alerts or news page.

A signature-required delivery adds a final verification scan

For shipments requiring a signature on delivery, the final scan event typically also logs the recipient's name or an electronic signature capture, creating one more data point in the chain beyond a simple delivered status.

This extra verification step exists mainly for valuable or sensitive shipments, and its absence on an ordinary package is normal rather than a sign that tracking data is incomplete.

What actually matters when your tracking looks stuck

A gap in scan events almost always reflects a normal absence of checkpoints, a weekend pause, or a border and customs handoff, not a lost package. The tracking number's structure and checksum already confirm it is valid and being watched by the system.

The practical approach is patience through the carrier's published delay threshold, checking the carrier's own site directly rather than a marketplace's partial view, and only escalating to a formal inquiry once that threshold is genuinely exceeded.

Sources

1. Wikipedia: Tracking number — supports the general explanation of tracking number structure and carrier prefixes
2. USPS: Tracking a domestic package — supports the description of carrier-side scan events and status categories
3. Wikipedia: Universal Postal Union — supports the explanation of how international mail systems hand off shipments between national postal networks