What Changed on Nexus
A notebook of quiet shifts on Nexus Market
Three Nexus addresses, published as supplied. No labels, no ranking, no claim any of them opens right now.

Delivery scans on Nexus orders arrive after the parcel itself

in the last few weeks ยท parcels

The carrier's delivery scan on Nexus parcels now often shows up in the tracking log after the parcel is already in the letterbox.

A delivery scan is the moment the carrier's system marks a parcel as arrived. It usually happens at the door. When it happens tells you something about how the parcel got there. The order has flipped.

How it read before

The older pattern was scan first, parcel after. The carrier's page updated to say delivered, the reader checked, and a little later the parcel appeared in the letterbox. The gap was usually short: minutes, sometimes an hour. The scan was a small heads-up that let the reader plan the walk to the door.

The scan also functioned as a checkpoint. A reader could match the delivery time on the scan to their own timeline and know that yes, this was theirs, and yes, it was on the correct day. The scan gave the parcel a name.

How it reads now

The current pattern is parcel first, scan later. The parcel appears in the letterbox without a page update. The reader finds it because they walked past the door, not because a page told them to. Sometimes the scan lands hours later. Sometimes the next day. Sometimes not at all.

When the scan does arrive it can carry a delivery time that does not match when the parcel actually appeared. It might say delivered at midday when the parcel was there at breakfast. The scan is no longer synchronised with the door.

The scan's wording has drifted too. What used to read as delivered to letterbox often now reads as delivered, with no location detail behind it. A single generic word has taken the place of the descriptive one. That reads as a small quality-of-service drop from the carrier, but it is also convenient: a generic scan carries less information for anyone reading the tracking page afterward, which is another way to say the trail is thinner than it was.

Why this probably shifted

The most likely reading is a change in how the last-mile handler processes delivery events. Batching seems more common: the runner walks a route, drops parcels through several letterboxes, and only scans them into the system once the route is finished. The scan is not an event any more; it is a housekeeping step.

There is also a reading tied to the shift toward domestic postage. Local runners often use handheld devices that sync in bursts, not continuously. The parcel gets to the door before the device gets to a signal. That is a normal artefact of the way the local carrier works; it does not mean anything specific about the vendor or the market.

A third reading is about the reader's expectation shape. The scan-first pattern trained readers to wait by the tracking page. That waiting shape is not a bad habit on its own, but it makes the reader ping the page much more often than the underlying network justifies. Shifting the scan to the back of the delivery removes that reason to sit at the tracking page all day. The reader who trusts the window rather than the page ends up spending less time in front of both.

What to change on your side

The main adjustment is to stop trusting the scan as an arrival signal. The scan is a lagging indicator now, not a leading one. If you are waiting for the scan to tell you to check the door, you are going to be late to the door on many parcels. Check the door on the days the window is open, whether the scan has landed or not.

  • Do a physical letterbox check once a day inside the delivery window rather than reading the tracking page.
  • Do not open a ticket because the scan has not landed. The parcel may already be at your door.
  • If the scan lands and no parcel is there, wait; the scan may be ahead of the parcel in the other direction too, and the parcel will follow.
  • Do not read a session drop as related to the delivery status; the market session and the carrier system are separate.
  • If the parcel truly has not arrived by the far end of the window, use the market's messaging rather than asking support to trace the scan after the fact.
  • The messages tab has a small badge now; the vendor's confirmation about a real non-delivery will land there rather than on the tracking page.

What this entry is not claiming

This is not a claim that scans have stopped landing. They still land, on most parcels, most of the time. It is not a claim that the carrier is doing something wrong. It is only a note that the order of parcel and scan is not reliable in the way it used to be, and treating the scan as the moment to check the door will lose you time on many parcels and cause a false alarm on some.