Evergreen B/L or container number not found: what each message means

What bexy can look up

bexy looks up an Evergreen Bill of Lading number as EGLV followed by twelve digits, for example EGLV140403294441. Enter it with or without EGLV: bexy uses the twelve digits either way.

A container number is four letters and seven digits under ISO 6346, for example EMCU0105170. Its last digit is a check digit worked out from the first ten characters, and bexy asks Evergreen about a container only when it matches; the container number check shows the calculation.

In the search on bexy, spaces, hyphens and dots are ignored and lower-case letters are read as capitals, so a number copied from a document or from a container door, such as EMCU 010517-0, works as written. The https://bexy.io/track?number= address ignores spaces and letter case but not hyphens or dots; give the MCP tools the number without any of them.

bexy has no booking-number search: twelve digits are always looked up as a Bill of Lading number.

Only Evergreen (EGLV) shipments are tracked. A Bill of Lading issued by another line starts with that line's own prefix, which the Bill of Lading prefix lookup can identify.

What each message means

When a search finds nothing, bexy says why in terms of what you entered:

… is not a valid container number: its check digit does not match the ISO 6346 rule.

The number has a container number's shape, four letters and seven digits, but its last digit does not match the other ten, so it was not sent to Evergreen. Check it against the container or its paperwork for a mistyped or misread character that keeps that shape: a wrong digit, a swapped pair of digits or a wrong letter among the first four.

… Evergreen's tracking has no record of that Bill of Lading.

Evergreen answered that it holds no shipment under those twelve digits. Check the digits, and whether the Bill of Lading was issued by Evergreen at all. bexy keeps this answer for 60 minutes, so the same number shows the same message until then.

Evergreen's tracking shows no current voyage for container …

Evergreen's container search found no voyage for that container. If it travels on an Evergreen Bill of Lading, look up that number instead. This answer is kept for 60 minutes too.

Evergreen's tracking did not answer just now …

No usable answer came back from Evergreen, which says nothing about the number. Nothing is kept, so search again in a minute.

Too many lookups have been sent to Evergreen from your network in the last minute.

bexy limits how many lookups one network can send Evergreen each minute, and a container number can take two: one to find the Bill of Lading it travels on and one to read it. Wait a minute and search again.

… enter a Bill of Lading (EGLV and twelve digits) or a container number (four letters and seven digits).

What you entered has neither shape, so bexy looked for it only among the shipments it already holds and did not ask Evergreen. Check for a missing or extra character, or a letter where a digit belongs or the other way round, such as an O for a 0 or an I for a 1.

A container number opened another shipment

A container keeps its number for life and travels under many Bills of Lading, so one container number can match several shipments bexy holds. bexy opens the latest voyage: the one with the latest loaded-on-board date.

When that voyage is over, because a status reports the shipment at its final destination or bexy has taken its final reading of it, a search on bexy also asks Evergreen's container search which Bill of Lading the container travels on now, within an hourly limit on such lookups. A newer one opens instead, with the message "Container … is on a newer Bill of Lading now: this is its current voyage." bexy keeps Evergreen's answer for 6 hours.

To open one particular voyage, search for its Bill of Lading number: a Bill of Lading names one shipment.

The page shows older data than expected

A tracking page shows Evergreen's record as bexy last read it. When you search for a shipment bexy holds and bexy last read it 6 hours ago or more, bexy reads Evergreen's record again before opening the page, within an hourly limit on such re-reads, unless a status already reports the shipment at its final destination or bexy has taken its final reading of it. The message on the page says what happened:

Re-read from Evergreen just now.

The record changed, and the page shows the new reading; or bexy stopped re-checking the shipment with this reading, which moves the page's "data as of" date too.

Re-read from Evergreen just now: bexy's record of it is unchanged …

Nothing Evergreen returned changed bexy's copy of the record; a "To be advised" ETA, for one, never replaces a dated ETA bexy holds. The page's "data as of" date moves only when a reading changes bexy's copy of the record or is the one bexy stops re-checking with, so it stays as it was.

Evergreen's tracking did not answer just now, so this is the record as bexy last read it.

No answer came back. Searches leave the shipment alone for 6 hours, and bexy's own re-checks carry on.

Evergreen's tracking gave no update for this shipment just now, so this is the record as bexy last read it.

Evergreen answered without the shipment's details, so the record was left as it was.

Where bexy never asks Evergreen

Opening a tracking page from a link, the https://bexy.io/track?number= address and the MCP tools never ask Evergreen: they open the shipment bexy holds, as stored, or report that bexy does not hold it. Of the ways to look a number up, only the search on bexy asks Evergreen about one bexy has not seen yet.