Landmark Global Tracking

What is Landmark Global?

Landmark Global is Bnode's current cross-border commercial brand. Bnode is the corporate group identity; bpost is a separate last-mile/postal brand for Belgium and the Netherlands. Group membership does not make Bnode, bpost, Apple Express, or another group company an automatic Landmark Global tracking alias.

This matters because Landmark's cross-border model can use:

• Landmark-managed data and facilities;
• Mercury, Landmark's shipment platform;
• group-affiliated delivery capabilities on some lanes;
• external postal and parcel carriers;
• customs brokers or agents;
• destination-country final-mile partners.

The result is a tracking history in which the brand displayed on the page and the actor that created a particular event can be different.

Which number should I use?

Landmark/Mercury can expose several identifiers that serve different jobs.

The LTN documentation conflict is real

Current first-party Landmark documentation is not fully aligned on LTN granularity.

The Europe/Asia consumer FAQ describes the LTN as Landmark's unique identifier created for every parcel. Mercury's Standard Fulfillment Confirmation documentation describes the Landmark Tracking Number as an order-level tracking value while listing end-carrier tracking numbers per carton.

For a public tracking guide, the safe conclusion is:

Treat the LTN as Landmark's tracking identity within the shipment/order data model. Do not assume it is always exactly one-per-parcel or always exactly one-per-order. Use the actual shipment structure and any end-carrier number shown for the item.

The important operational distinction is simpler:

Both can exist for the same cross-border journey.

Why can a Landmark status come from another carrier?

Mercury receives tracking events through carrier-specific integrations such as SFTP feeds, webhooks, and carrier APIs. It then maps those events into standardized Landmark/Mercury status families.

That architecture creates a critical evidence rule:

A useful tracking interpretation therefore needs all three pieces:

normalized status
+
actor / carrier provenance
+
route or service context

For example, a normalized Item Touched By Carrier event says that a carrier-processing event exists. If the tracking record identifies a destination carrier, the word carrier should be read in that actor context rather than automatically as Landmark.

This is also why the final-mile carrier's own tracker can become more detailed than Landmark's aggregate view after local acceptance.

Does Landmark actually have the parcel?

There is no single current Landmark/Mercury code that can safely be treated as a universal Landmark has physical possession event across every route and service.

Use an evidence ladder instead.

merchant order exists
→ Landmark/Mercury shipment data object exists
→ Shipment Data Uploaded
→ processing / fulfillment states
→ actor-specific physical handling
→ destination carrier selected
→ data transmitted to destination carrier
→ destination carrier item-level acceptance / processing
→ local delivery execution
→ Delivered / route-specific proof

Weaker evidence: shipment data and fulfillment states

Statuses such as:

• Shipment Data Uploaded
• Shipment inventory allocated
• Shipment Processed
• Shipment Fulfilled

show that shipment data, inventory, processing, or fulfillment activity exists in the Landmark/Mercury workflow.

They do not establish one universal physical-custody conclusion for Landmark.

If your parcel appears to remain at a data or processing stage without later physical evidence, use the next actor-specific scan rather than a fixed waiting-time rule. If tracking stays silent, see Why Has My Package Tracking Not Updated?.

Stronger evidence: actor-specific physical handling

An event that is explicitly attributable to a named operator's physical item processing is stronger possession evidence than data upload or data transmission.

Even then, keep the actor attached to the event. A postal-facility scan is evidence about the postal operator/facility. A destination-carrier acceptance event is evidence about that destination carrier. A partner-facility event should not be relabeled as Landmark custody unless the provenance supports it.

"Shipment Information Transmitted To Carrier" means data handoff

Mercury code 100 — Shipment Information Transmitted To Carrier is one of the most important Landmark-specific statuses to interpret correctly.

Mercury's current tracking documentation says this code can be used when Landmark submits data to the final-mile carrier.

So the safe evidence model is:

Shipment Information Transmitted To Carrier
=
data sent to the final-mile carrier

NOT
=
proof that the final-mile carrier physically received the parcel

The next decisive evidence is normally the destination carrier's own item-level acceptance or processing event.

A local tracking number may already exist at the data-handoff stage. That number is useful, but its existence alone does not prove physical local custody.

If Landmark shows a final-mile carrier but the local tracker remains silent, see Why Is the Local Carrier Not Updating After Handoff?.

When should I switch to the destination carrier?

Use a progressive system-of-record switch rather than one assumed handoff moment.

destination carrier selected
→ local tracking number may be assigned
→ shipment data transmitted
→ local carrier recognizes the record
→ local carrier records item-level acceptance or processing
→ local carrier becomes the stronger source for local execution

Once the named local carrier records physical acceptance or processing, its own system is normally the better source for:

• local routing;
• delivery attempts;
• pickup availability;
• redelivery eligibility;
• local address-control options;
• delivery completion;
• route-specific proof of delivery.

Landmark/Mercury can continue to display downstream events because carrier feeds can be integrated back into Mercury. That does not make the Landmark view the only source of record.

If the final-mile carrier is not obvious, use How to Find the Last-Mile Carrier and Local Tracking Number. A carrier assignment without physical acceptance still belongs conceptually to the Handed to Local Carrier status guide until stronger item-level evidence appears.

Do not infer the final-mile carrier from the country alone

Landmark states that it works with multiple delivery partners and can use different carrier mixes by country and service.

That means:

Canada illustrates why.

Landmark identifies Apple Express as an in-group/sister Canadian last-mile capability. Apple Express is still a distinct delivery identity; it is not a universal Landmark alias. The parcel's actual end-carrier field, local tracking number, and local acceptance event should decide which carrier owns the last-mile record.

The same principle applies elsewhere: use shipment-level evidence, not a permanent country-to-carrier table.

High-value Landmark / Mercury tracking statuses

Mercury publishes more statuses than the table below, and the actual status text can differ by route and service. Treat this as an evidence classifier, not an exhaustive status dictionary.

Why code 225 needs actor context

Code 225 is explicitly a Landmark or partner facility family. The event supports facility handling, but the generic code alone cannot tell you which of those actors physically handled the item.

Why code 275 is not "Landmark touched the parcel"

Mercury is multi-carrier. Code 275 is a carrier-processing/in-transit family. If the record identifies a destination carrier, use that carrier identity when interpreting the event.

Attempted delivery, pickup, and redirects

Attempted Delivery

An Attempted Delivery event confirms an attempt record. It does not by itself prove:

• why delivery failed;
• that the recipient caused the failure;
• how many attempts the service includes;
• that automatic redelivery will occur;
• that pickup is available.

Landmark's current Europe/Asia and US/Canada support surfaces both warn that not every service offers redelivery or pickup.

Use the final-mile carrier's instructions when that carrier owns the local route. For generic interpretation, see What Does Delivery Attempted Mean?.

Item At Pickup Location

A pickup-availability event is a readiness state, not a collection state.

Confirm the current location, release credential, identity requirement, and deadline through the local carrier or pickup operator. See What Does Available for Pickup Mean?.

Redirected To New Address

A redirect event says that a redirect was recorded. It does not identify who requested it, whether the recipient was authorized to request it, or whether another redirect is still available.

If you need to change a shipment, use the current region/service-specific official route rather than assuming that one previous redirect status creates a continuing right to reroute. See Change Delivery Address, Reroute, or Hold.

What does "Delivered" prove?

A Landmark/Mercury Delivered event is meaningful delivery evidence.

It does not, by itself, establish:

• that the named recipient personally received the parcel;
• that delivery occurred to the exact place the user expected;
• that the contents were correct;
• that the package was undamaged;
• that there was no later loss or theft;
• that a universal photo/signature/GPS proof object exists.

If the final-mile carrier has its own detailed delivery record, use that system for route-specific proof.

If tracking says Delivered but the parcel is missing, use Package Says Delivered but I Did Not Receive It.

If you need the official proof object, see How to Get Proof of Delivery, a Delivery Photo, or a Signature. If the proof appears materially wrong, see How to Challenge Incorrect Proof of Delivery.

Proof of Delivery is not one universal object

Mercury exposes a Proof Of Delivery event family, but its general tracking documentation does not define one universal POD payload or one universal consumer access method.

Do not assume every Landmark route includes:

• a delivery photo;
• a handwritten signature;
• signer identity;
• GPS coordinates;
• a downloadable POD certificate.

Those details depend on the destination carrier, service, and route.

Lost or damaged parcel: who should act?

Landmark's current consumer guidance is seller/e-shop weighted.

Europe and Asia

The Europe/Asia support page tells recipients to contact the seller for lost or damaged packages. It says the seller can provide the most accurate information, initiate necessary investigations, and liaise with Landmark. It also states that insurance options are offered to Landmark's direct customers—the e-shops.

United States and Canada

The US/Canada support surface also tells users to contact the seller for lost or damaged next steps. Its insurance/claims wording is broader and says users may contact the seller or Landmark customer service regarding loss/damage claims.

The important conclusion is:

recipient claim standing
is not one global Landmark invariant

Keep these processes separate:

If you need to classify an open carrier case, use Carrier Investigation Open, Pending, Closed, or No Resolution.

For initial compensation routing, use How to File a Package Claim.

If a carrier compensation decision already exists and is denied or underpaid, use Package Claim Denied or Underpaid.

Can I change the delivery address?

There is no safe single global Landmark rule.

Current first-party support pages differ:

• Europe/Asia: once the item has already been processed and has a label, the current FAQ says an address change can no longer be requested.
• US/Canada: the current FAQ says address changes can be requested subject to the shipment stage and tells the user to contact customer service immediately.

So the public rule is:

Address-change eligibility is region-, service-, and stage-specific. Use the current support surface for the shipment's region. A submitted request is not proof that the route actually changed.

Official regional support:

• Landmark Global Europe & Asia customer support
• Landmark Global US & Canada customer support

If a final-mile carrier already owns the local route, that carrier's own change/hold eligibility may become the more relevant rule.

Customs: separate payment, authorization, clearance, and delivery

Landmark provides customs-clearance and trade-services capabilities, and Mercury can show customs-related states. That does not make Landmark the government customs authority.

Keep the actors separate:

Landmark / broker / agent / data system
=
transport, data, brokerage, payment or clearance coordination

government customs authority
=
official assessment, inspection, release, restriction, or enforcement decision

Also keep the states separate:

Canada: payment can be separate from authorization

Mercury's current tracking documentation says Canadian shipments can expose a Pay Now action through Cheddr when duties or taxes are unpaid. It also says Cheddr can be used when no payment is due but clearance authorization is still required.

That demonstrates a useful evidence distinction:

After Customs Cleared, look for the next downstream carrier event. Customs clearance does not prove that the destination carrier already has the parcel.

For generic customs-state interpretation, use What Does Customs Processing Mean?, What Does Customs Cleared Mean?, or Package Stuck in Customs.

Landmark returns are not the same thing as a merchant refund

Landmark's returns service can include:

return initiation / label
→ local first mile
→ consolidation
→ customs handling
→ transport
→ handling facility
→ Return Received
→ warehouse / 3PL / hub

Those are reverse-logistics states.

They do not, by themselves, establish:

merchant item match
merchant inspection
refund approval
refund instruction
payment-provider processing
refund posting

This distinction matters because a return can be physically received within a logistics network while the merchant's commercial return process is still incomplete.

If the return is still moving or the seller says it was not received, use Return Package Not Updating or Seller Says It Was Not Received.

If merchant receipt is established and the unresolved problem is now the refund, use Returned Package Received but Refund Has Not Arrived.

There is no universal Landmark waiting-time rule

Current evidence does not support one global Landmark rule such as:

• "wait X days after Shipment Data Uploaded";
• "claim after X days";
• "pickup within X days";
• "Landmark always delivers in X-Y days";
• "one address-change cutoff applies everywhere."

Delivery timing and action eligibility vary by service, destination, local carrier, and process stage.

Use the next missing evidence transition rather than a generic clock.

Next Decisive Evidence

This table is the shortest way to decide what to look for next.

Related Package Help

Use these when the problem stops being primarily a Landmark-specific provenance question:

• Find and Verify a Tracking Number — the identifier itself is unclear.
• Handed to Local Carrier — a handoff/assignment is visible but physical acceptance is not established.
• Find the Last-Mile Carrier and Local Tracking Number — the destination carrier or local number is unclear.
• Local Carrier Not Updating After Handoff — the local carrier is identified but its record is still silent.
• Tracking Not Updating — the active record has stopped producing new public events.
• Out for Delivery but Not Delivered — the expected final-delivery outcome failed.
• Delivered but Not Received — delivery is recorded but the parcel is not in your possession.
• Proof of Delivery — you need the official delivery evidence object.
• Who Should I Contact About a Package? — the responsible actor is unclear.
• Official Carrier Support Directory — you need a verified official support route.

11Tracking can help interpret public tracking evidence and route you to the responsible system. It cannot recover the parcel, create missing scans, access Landmark's private Mercury account data, contact a carrier on your behalf, change the delivery route, clear customs, file a claim, approve a refund, or guarantee an outcome.