Tracking Overview

You can track shipments using many methods, including the Landmark Global website, API integration, SFTP files, Mercury deeplinks and Mercury’s search function.

How to track and trace shipments

Via the Landmark Global website

The easiest way to view a shipment’s tracking status is by using the Landmark Global tracking page. You can search for up to 25 shipments at a time using either their LTN or the tracking number provided by the end-carrier.

The tracking page will provide a quick overview of where the shipment is and its expected arrival, and you can also click “Full Event History” to see individual tracking events and their timestamps. When viewing the full tracking history, the most recent events will be at the top, and you can scroll down to see more.

Certain kinds of events (e.g. being held for inspection by customs) may cause a “Possible Delay” alert to appear at the top of the tracking page.

Via API integration

To get tracking information via API, send a TrackRequest for a specified shipment and get the TrackResponse containing the latest tracking status for the specified shipment or package. If you want to retrieve a history of all statuses for a shipment, make sure to include the optional RetrievalType node and set it to “Historical”.

Via SFTP integration

If you have tracking via this integration enabled, a CSV file will be placed on Landmark’s SFTP server in the “Tracking” folder. Login credentials will be provided by Landmark Global. This tracking file will contain all new statuses received since the previous file was generated. See Tracking File Specifications.

Via Mercury deeplinks

Mercury deeplinks allow you to track any shipment without having to log in. The structure of the deeplink depends on what reference you are using for the shipment.

• Landmark Tracking Number or End-Carrier Tracking Number
  • Structure: https://track.landmarkglobal.com/?trck=<tracking number>
  • Example: https://track.landmarkglobal.com/?trck=LTN62000715 
• Shipment (Order) Reference
  • Structure: https://track.landmarkglobal.com/?cid=<client account number>&refid=<shipment reference>
  • Example: https://track.landmarkglobal.com/?cid=127&refid=AER12142017
• Package Reference
  • Structure: https://track.landmarkglobal.com/?cid=<client account number>&pkgrefid=<package reference>
  • Example: https://track.landmarkglobal.com/?cid=127&pkgrefid=00000000246706
• LPR Value*
  • Structure: https://track.landmarkglobal.com/?trck=<LPR value> 
  • Example: https://track.landmarkglobal.com/?trck=LPR00158504744930

*LPR values are tracking seeds you can generate by appending a unique value to an account-specific prefix and Mercury will accept that as a tracking number. LPR values can be submitted to our system via the PackageReference field. LPR values passed to our system should be unique so duplicates aren't sent between facilities. The format of the LPR value is:  LPR00<4-digit-clientID><reference>.

Via Mercury’s search function and shipment detail page

Use Mercury’s Shipment Search page to find the shipment you want to track. When the results appear, click on the name of the shipment to pull up the shipment detail page.

There are two ways to see tracking information from the shipment detail page.

1. Expand the Shipment Tracking History section to see tracking events with time stamps.
   1. This section will show Attempted Delivery and Delivered codes at the top of the list (regardless of timestamp). Otherwise, it sorts by event time descending.
2. Clicking on “View Latest Tracking Status” will take you to a page with more information.

From this tracking page, you can click to “View Complete Tracking History”.

Tracking statuses and codes

Codes and subcodes

Landmark uses a few standardized codes to categorize tracking events. These codes have general meanings such as "Shipment In Transit/On Hold/Delayed" (275) or "Shipment Delivered" (500). Within these codes, subcodes can provide additional details. For example, code 275 contains many subcodes, including 2000 ("Parcel departed"), 2006 (Parcel may be delayed due to weather"), and 2750 ("Parcel damaged"). Landmark codes are shown in the table below; subcodes may be seen in the spreadsheet attached at the end of this section.

Different carriers have their own unique tracking codes. These codes must be mapped to the relevant Landmark codes when the carrier is integrated so that we can correctly interpret tracking information. See the full tracking mapping spreadsheet here: 

List of possible tracking statuses

• 50 - Shipment Data Uploaded
• 60 - Shipment inventory allocated
• 75 - Shipment Processed
• 80 - Shipment Fulfilled
• 90 - Shipment held for payment
• 100 - Shipment information transmitted to carrier
• 125 - Customs Cleared
• 135 - Customs Issue
• 150 - Crossing Border
• 155 - Crossing Received
• 200 - Item scanned at postal facility
• 225 - Item grouped at Landmark or partner facility
• 250 - Item scanned for crossing
• 275 - Item in transit with carrier
• 300 - Item out for delivery
• 400 - Attempted delivery
• 410 - Item available for pickup
• 450 - Item re-directed to new address
• 500 - Item successfully delivered
• 550 - Return Received at handling facility
• 570 - Return Received
• 800 - Claim Issued
• 900 - Delivery Failed

Getting tracking events from carriers

Each carrier is set up uniquely, and the way we get tracking events differs based on the integration. Here are the possible methods, listed from most preferred to least preferred:

1. SFTP via the carrier's server (we pull the files).
2. SFTP via Landmark's server (carrier pushes the files).
3. Webhook for tracking data (carrier pushes the data).
4. Bulk tracking fetch via carrier API (several tracking numbers per request, we pull the data).
5. Tracking fetch via carrier API (one tracking number per request, we pull the data).