A comma-separated text file will be created containing confirmation information about the day's processed shipments. The file will be placed on Landmark's FTP server in the "Confirmation" folder. Login credentials will be provided by Landmark Global. There will be one row for each type of Item passed to Mercury. For a shipment with multiple items, the shipment-level details will repeat on each row. Client Name Customer Provided Reference Ship To Name Ship To Address Ship To City Ship To State/Province Ship To Postal Code Ship To Phone Number Landmark Service Code Service Description Date/Time Imported Date/Time Processed Package Count Total Weight Tracking Number(s) - multiple numbers will be combined with a comma and a space. SKU Item Count Item Value Item Currency Serial Numbers - multiple numbers will be combined with a ~ character Landmark Tracking Number Please See Attached Example of Confirmation File

The following details how to import shipment data to Mercury via an API request . Overview The protocol is based on XML data exchange with HTTP used as a transport. A non-validating parser is used and hence no internal or external DTD needs to be specified. The data must be well formed and all validation is handled at the application (not parser) level. Error handling will be done by always including the container in the response. The Errors element will not be returned if no errors are found. Connection To connect to the site use the following HTTPS URL via regular POST method with the parameter RQXML= https://api.landmarkglobal.com/v2/Ship.php Encoding Mercury uses UTF-8 for character encoding. If your system outputs in an encoding other than UTF-8, please include an encoding flag in your XML header.       Example:      Example: Test Mode When first given access

The following details how to retrieve sku inventory information via an API request . Only applicable to clients using Landmark for fulfillment. Overview The protocol is based on XML data exchange with HTTP used as a transport. A non-validating parser is used and hence no internal or external DTD needs to be specified. The data must be well formed and all validation is handled at the application (not parser) level. Error handling will be done by always including the container in the response. The Errors element will not be returned if no errors are found. Connection To connect to the site use the following HTTPS URL via regular POST method with the parameter RQXML= https://api.landmarkglobal.com/v2/InventoryLevel.php Encoding Mercury uses UTF-8 for character encoding. If your system outputs in an encoding other than UTF-8, please include an encoding flag in your XML header

The following details how to track a package with Mercury via an API request . Usage Note The Track Request API should be used to look up tracking information for individual shipments on an ad-hoc basis. Each package may be tracked once per hour (24 times per day). If you need updates for multiple shipments at once, please use the tracking file . Overview The protocol is based on XML data exchange with HTTP used as a transport. A non-validating parser is used and hence no internal or external DTD needs to be specified. The data must be well formed and all validation is handled at the application (not parser) level. Error handling will be done by always including the container in the response. The Errors element will not be returned if no errors are found. Connection To connect to the site use the following HTTPS URL via regular

A comma-separated text file will be created containing information on received inventory for Stock Shipment Inventory being handled by Landmark. This file will be placed on Landmark’s FTP server in the "Fulfillment" folder. Login credentials will be provided by Landmark Global. This file is generated daily. Header information included in this file: SKU Facility Time Location Type Event Description Shipment # Before Value After Value Lot Number Lot Before Value Lot After Value Expiration Date The Location Type to expect for this file will always be "RESERVE". The Event to expect in this file will always be "Received Inventory". Description will display a description of stock shipment as logged by operations.

important file. The four different OptionTypes are Option (for setting shipment options), Memo (for pick slips), Charge (for pick slips) and Additional (additional shipment fields). To add any of these, you need to add columns for OptionType, OptionName, and OptionInfo. For example, to import shipments with pickslip memos, add the following: OptionType - must set to "Memo" OptionName - can be any text, but must not be blank OptionInfo - the text of the memo To include more than one option for a single shipment , you will need to add an additional row for each extra option you want to add to the shipment. Each of these additional rows should include the same shipment reference so the shipment will import as one record in Mercury with all ship options attributed. Dangerous Good. An item containing articles or substances capable of posing a significant risk to health, safety or property, and that ordinarily require

A comma-separated text file will be created containing confirmation information about the day's processed returns. The file will be placed on Landmark's FTP server in the "Returns" folder. Login credentials will be provided by Landmark Global. Headers MySQL Type Max Length / Set Description/Notes Shipment Reference varchar 50 Client-provided customer reference Customer Name varchar 50 First and last name City varchar 40 Original outbound shipment State varchar 20 If a country for original outbound shipment has states or provinces. Use 2- or 3-character abbreviations when possible Postal varchar 10 If country for original outbound shipment uses postal codes. Canada format: "A9A9A9" // USA format: "12345" 4-digit suffix optional Country varchar 50 Original outbound shipment. Use 2-character ISO code when possible Return Date datetime 21 When return was processed (US Central Time). Format: '000-00-00 00:00:00' Return Code varchar 10 Landmark letter

Overview : The Landmark Label is used in the Landmark Overlabel Process. Sizing:  Standard Labels generated by Mercury will be sized to 4x6 inches at 203 dpi. These are the recommended specifications for labels created by clients, but not required.  Required Fields:  Client Company Name Consignee Name Consignee Address Barcode* This either relates to the ShipmentReference or PackageReference field provided to Landmark as part of the data import process. It is recommended that a PackageReference be used when a shipment (i.e. order) has multiple physical packages associated with it. Barcode symbology supported by Landmark - list provided below. Barcode is at least 2 inches wide for ease of scanning purposes. Human readable barcode value - in case the barcode cannot be scanned. Landmark currently supports the following barcode types: Code 39 Code 128 GSI-128 (recommended) Note:  There must be only one barcode on the label sent to Landmark. Recommended Fields: These

...

monization Importer: A person or company responsible for preparing accounting documents for imported goods and paying the duties and taxes owed. IOR: Importer of Record. IOSS:  Import One Stop Shop number. An IOSS number is required by distance sellers and marketplaces in order to sell goods to buyers in the EU. The IOSS allows suppliers and electronic interfaces selling imported goods to buyers in the EU to collect, declare and pay the VAT to the tax authorities. Low Value Goods Tax ID:   A type of low-value tax ID used when clearing to Malaysia. Low Value Tax ID (LVTID): A general field for storing tax IDs that meet requirements for low-value clearances (e.g. the EU's IOSS or Norway's VOEC Number ). LTS:  Landmark Trade Services, a Landmark-specific customs broker. NFR: Not for Resale or Non-Commercial, basically meaning goods that are going direct to consumers, not

                      UN3481                       II                       PS967S1                       10                       kg                       30                       ML                                       (i.e. manufacturing) . Contact your integration manager if you plan to use this feature -->                                                         MANUFACTURING                                     Include as many Instruction tags as needed. -->                               Font: Arial                               Color: Blue                               Text: My text on the t-shirt                                                                 ValueAddedServices >                                 LGBR020409E           Pallet       ImportResponse                                 State                 State-Province is invalid, must be 2 characters.                       true                 true           Shipment 3245325 was successfully imported.                                                                                 https://api.landmarkglobal.com/download/get-label.php?hid=5SalTlxR8JkpE%2FCW4HxGD0ghMOXXA%2F0rebjGm9EeaVlkG58%3D_5KAZZsOEn9E4p5Sy                                                                   23987B3KD0LK211AF......                                           LTN329122N2                     LTN329122N2                     98233310                                   Possible Errors This table lists all errors that may be returned by the ImportRequest API endpoint. [Brackets] in the ErrorMessage are used to represent to the value passed for the related element. An example is provided when an ErrorMessage is variable. Related Element(s) ErrorMessage Details/Action General Errors User, API User [username] does not have permissions to this API Failure authenticating user User is not available. Check your username/password

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

This document outlines Landmark's API Specification for the electronic (via the Internet) exchange of information between Landmark and their customers. Overview The protocol is based on XML data exchange with HTTP used as a transport. A non-validating parser is used and hence no internal or external DTD needs to be specified. The data must be well formed and all validation is handled at the application (not parser) level. Error handling will be done by always including the container in the response. The Errors element will not be returned if no errors are found. Connection To connect to the site use the following HTTPS URL via regular POST method with the parameter RQXML=   ">https://api.landmarkglobal.com/v2/ Encoding Mercury uses UTF-8 for character encoding. If your system outputs in an encoding other than UTF-8, please include an encoding flag in your XML header.       Example:      Example

A comma-separated file containing new tracking statuses on all in-transit packages for a client. The file will contain all new statuses received since the previous file was generated. The file will be placed on Landmark's SFTP server in the .../OUTBOUND/Tracking folder. Login credentials will be provided by Landmark Global. The file can also be transmitted by Landmark to a separately hosted SFTP server if desired. File Name Convention  (timezone is in American/Chicago) TransitReport- -yyyymmddhhiiss.csv Example: TransitReport-218-20200729154801.csv The file contains a header row. Below is a file format table. Headers MySQL Type Max Length / Set Description / Notes Client smallint 5 Landmark client identification number Reference varchar 50 Client-provided customer reference Landmark Tracking Number varchar Carrier Tracking Number varchar 50 Assigned per package, carrier specific Carrier varchar 8 To City varchar 20 To State varchar 40 If country for original outbound shipment

nknown preclearance ID Contact Integration Manager A MAWB (Master Airway Billed) number is an 11-digit number that identifies the airline and the shipments involved. A unique 3-letter combination that identifies an airport. For a list of airports and their codes, visit http://www.airportcodes.org/. Delivery Duty Unpaid. For orders sent by DDU service, the buyer is responsible to settle duty fees with customs. This means that the cost paid at checkout may not be representative of the total final cost. A unique 3-letter combination that identifies an airport. For a list of airports and their codes, visit http://www.airportcodes.org/.

This document describes version 1 of Landmark's electronic invoice format. This format is a standard comma-separated value file (csv) with data optionally enclosed in quotes ("). Invoice files can either be stored on Landmark's secure server for pickup or can be sent to the client's FTP. Landmark invoices for 3 different services and depending on the service in the electronic file, the format will change slightly. Each service's format is listed below. Each invoice will always begin with a line starting with "I". Each invoice will have one or more detail lines (D1,D2,D3,L). Each detail line will have one or more charge lines (C). Parcel Distribution I, , , , , , , ,   D1, , , , , , , , , , , ,   L,   C, , , , Sample Parcel Data: Tax Remittance and Disbursement I, , , , , , , , D2, , , , , , , , , , , , , L, C, , , , Sample Tax Data : Fulfillment Services I, , , , , , , , D3, C, , , , Fulfillment Sample Data:

The following details how to cancel a fulfillment order with Mercury via an API request . The CancelOrder API request should not be confused with the Cancel API  request, which is used to unprocess standard (non-fulfillment) shipments. Overview The protocol is based on XML data exchange with HTTP used as a transport. A non-validating parser is used and hence no internal or external DTD needs to be specified. The data must be well formed and all validation is handled at the application (not parser) level. Error handling will be done by always including the container in the response. The Errors element will not be returned if no errors are found. Connection To connect to the site, use the following HTTPS URL via regular POST method with the parameter RQXML= https://api.landmarkglobal.com/v2/CancelOrder.php Encoding Mercury uses UTF-8 for character encoding. If your system outputs

The following details how to cancel a carrier label with Mercury via an API request . The Cancel API request unprocesses shipments and also has the option to delete them. This request is typically used alongside ShipRequest in cases where the client does not use a generated label. The Cancel API request should not be confused with the CancelOrder API request, which is used to cancel and delete fulfillment orders.  Overview The protocol is based on XML data exchange with HTTP used as a transport. A non-validating parser is used and hence no internal or external DTD needs to be specified. The data must be well formed and all validation is handled at the application (not parser) level. Error handling will be done by always including the container in the response. The Errors element will not be returned if no errors are found. Connection    To connect to the site

s QuickBooks and Sage, the details of which can be configured by system administrators. Features Full data visibility Support tools for client, client support teams, sales, operations, network, product and any other depts with stake in service provision Issue resolution - historical data and event logs including user who performed action Plentiful reporting options throughout the system, customizable reports, metrics and ad-hoc reporting Self-serve Mercury platform access - self-serve Mercury portal as well as email or automated connections to view status of orders, manage issues, submit claims and invoices Financial tools Vendor billing system (with cost assignment and margin analysis tools) Client invoicing, including secure, automated electronic transfer Customizable reports for financial management Local finance system integrations: QuickBooks, Sage, Unit4, bpost System and user administration Because all Mercury users within a company share a centralized database, it’s crucial that clients be able to manage who has access to

This guide provides basic information regarding the integration between ShipStation and Landmark Global’s TMS platform, Mercury. The integration allows users to generate and retrieve Landmark international shipping labels and tracking within ShipStation. Processed Mercury shipments can also be voided from ShipStation. Requirements Use provided Landmark Client ID, username, password to set up Landmark Global as a carrier in ShipStation. Customs information MUST be linked to SKUs. To do this, set ShipStation to create declarations from order items in Settings > Shipping > International Settings. Users must have a Platinum plan or higher with ShipStation in order to integrate with Landmark. Sending orders to Landmark Filter by international orders, then select a service code to use and create a label. Order information is entered into Mercury and the label is viewable within ShipStation. A tracking number is also returned. After this the order will need to be processed through Mercury—client