Why every tracking site says "not found" — and how to read the number before you search

I run TrackJet, and the most instructive part of running a tracking site is not the searches that succeed. It is the anonymised stream of searches that fail. Almost none of them are lost shipments. They are readable, diagnosable input problems — and because every tracking site answers them with the same unhelpful "not found", nobody ever learns what actually went wrong.

Here are the failure patterns we see over and over, and how to read a tracking number the way a tracking system does.

Pattern 1: the fragment

People rarely get a tracking number as a clean string. They get it inside an email sentence, a photographed label, or a supplier's spreadsheet cell — and something gets lost on the way.

The classic example is an ocean container pasted without its owner code. A full container number is exactly four letters plus seven digits — say MSCU1234566. The first three letters identify the owner (MSC in this case), the fourth is the equipment category (almost always U), then six serial digits, then one check digit. Registries of those owner codes are maintained by the Bureau International des Containers, which administers them under ISO 6346. If you only have the seven digits, no tracking system on earth can tell you whose box it is — the identity of the carrier literally lives in the letters you dropped.

The same thing happens with air waybills. An air cargo number like 020-12345675 starts with a three-digit airline prefix — 020 is Lufthansa Cargo — and people routinely paste only the eight digits after the hyphen. Without the prefix, the number is an orphan: the prefix is the routing information.

What to do: go back to the source document and find the missing half. If you have four letters and seven digits, you have a container. Three digits, a hyphen and eight digits: an air waybill. Two letters, nine digits, two letters: an international postal item.

Pattern 2: the right number in the wrong box

A four-letter code followed by nine digits is not a container number — containers always carry exactly seven digits after the letters. A code like MAEU plus nine digits is almost certainly a bill of lading or booking reference (here: Maersk, whose SCAC is MAEU). It will fail on every container tracker, and it will work fine on a [bill of lading tracker](/bill-of-lading-tracking).

This distinction — container number vs. B/L vs. booking — is probably the single most misunderstood thing in ocean tracking. One shipment has all three at once: a booking reference (yours), a bill of lading (the contract), and one or more container numbers (the physical boxes). They answer different questions. If you want to know where the box is, track the container. If you want the shipment's paperwork status, track the B/L.

TrackJet's [universal detector](/track) reads the shape of whatever you paste and routes it to the right vertical precisely because of this pattern: the shape tells you which question the number can answer.

Pattern 3: one mistyped digit

Container numbers, air waybills and UPU postal numbers all carry a check digit — a final digit computed from all the others. Mistype one character and the arithmetic stops working. This is a feature: the number is telling you it is corrupted. But classic tracking sites don't check it; they just query their database, find nothing, and say "not found", leaving you to wonder whether the ship sank.

Take MSCU1234565. It looks perfectly plausible — four letters, seven digits. But run the ISO 6346 arithmetic and the check digit of MSCU123456 comes out as 6, not 5. A tracking system that validates structure first can tell you, immediately and for free: this number was mistyped, don't bother searching. That is exactly what TrackJet does, and you can run the full calculation yourself, step by step, with our [container check-digit tool](/container-number-check-digit).

The air waybill check is even simpler: take the seven-digit serial (the prefix does not participate), divide by 7, and the remainder must equal the final digit. For 020-12345675: 1234567 mod 7 = 5. It checks out.

What to do: if a number fails everywhere, don't keep re-pasting it into more trackers. Re-read it against the original document character by character — especially easily-confused pairs like 0/O, 1/I, 8/B. One of them is usually the culprit.

Pattern 4: too early

Not every "not found" is your fault. A number can be perfectly valid and simply not exist in the carrier's public systems yet — labels are often created hours (sometimes days) before the first physical scan. Postal items in particular can stay dark until the destination country's system picks them up.

What to do: validate the structure (patterns 1–3), and if the number is clean, wait for the first scan rather than assuming the worst. If you [save the shipment on TrackJet](/track), we re-check it for you and label every event with its real source when data appears — we never fabricate a status to fill the silence.

The habit that fixes most of it

Before you search, spend ten seconds reading the number itself:

• Four letters + 7 digits → ocean container ([format guide](/container-tracking))
• 3 digits – 8 digits → air waybill ([format guide](/awb-tracking))
• 2 letters + 9 digits + 2 letters → international post ([format guide](/post-ems-tracking))
• Four letters + 9+ digits → probably a B/L or booking, not a box
• 1Z… → UPS parcel

The number's shape tells you what it is, which carrier family owns it, and whether it survived transcription. Every failure pattern above is diagnosable before a single search — which is, in the end, the entire idea behind TrackJet.

All worked examples in this article were computed with TrackJet's own open validation logic — the same code that powers the live detector. Found an error? See our [editorial & data policy](/editorial).