Landmark Delimited Import Format
- 15 Nov 2024
- 8 Minutes to read
- Contributors
- Print
- DarkLight
Landmark Delimited Import Format
- Updated on 15 Nov 2024
- 8 Minutes to read
- Contributors
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
This is the specification document for the Landmark Global Delimited Shipment Data File v2.0.
Row
Rows provide information about specific shipments.
Rows can provide package and/or item information pertaining to a shipment.
Delimiters
The following file types/delimiters are supported at this time:
- Excel (xls and xlsx)
- .csv, .txt, or no-extension:
- Comma ","
- Tab
- Pipe "|"
- Semi-colon ";"
If commas or other delimiters are used as part of a field, it must be wrapped in double quotes. Example(csv):
ItemUnitPrice, ItemDescription, ItemCountryOfOrigin
73.41, "Desc, complete with comma", US
If a double-quote is part of a field value (e.g.: ItemDescription of 12" Statue), then the quotes should be doubled to retain the original value -- 12" Statue should be formatted as "12"" Statue".
Field Count & Headers
The fields being used must be specified in the first line of the file. Spelling should match headers listed below.
The order that headers are specified does not matter (e.g. ShipmentReference can be column 1 or 15 as long the field data in the column is consistent).
There must be the same number of fields on every line of the file. Empty fields must still be present in the form of empty cells or a delimiter.
"Cond." in the Required column stands for "Conditional". See Note column for specifics.
Scanning Note
Either the ShipmentReference or PackageReference must match the barcode on physical packages.
Type & Length
Values in Fields may not exceed the specified max length.
International Characters
To ensure proper data processing, please encode the file in UTF-8.
If you are using a different character encoding, or cannot support UTF-8, please inform Landmark IT.
If Created via Script
(i.e. code vs MS Excel or Open Office):
It is preferred that you enclose string fields with double quotes.
| Headers | Required | Type | Max Length/Set | Description/Notes |
|---|---|---|---|---|
| AccountNumber | Char | 50 | Optional Character field. Only used by clients with multiple account numbers, e.g. "L0218A", "L0218B". See integration manager for relevant account numbers. | |
| ShipmentReference | Yes | Char | 50 | Customer Reference, or Order Number, that links to all packages and items travelling to the same address. This is your primary identifier and we recommend all barcodes printed on packages scan to this reference. ShipmentReferences must be added in order (e.g. cannot be "Ship1, Ship2, Ship1"). |
| Name | Yes | Char | 50 | First and last name of consignee |
| ConsigneeTaxID | Cond. | Char | 50 | Required if shipping DDP to a country that requires submission of a consignee tax id (e.g. South Korea) |
| Attention | Char | 50 | ||
| Address 1 | Yes | Char | 60 | |
| Address 2 | Char | 60 | Apartment, Floor, Suite, etc. | |
| City | Yes | Char | 40 | |
| StateProv | Cond. | Char | 20 | Required when destination country has States or Provinces. Use 2 or 3 character abbreviations where possible (e.g. CA, AZ, MN, QC, etc.) |
| PostalCode | Cond. | Char | 10 | Required when destination country uses Postal Codes. Canada format: "A9A9A9" // USA format: "12345" 4-digit suffix optional |
| Country | Yes | Char | 50 | Use 2-character ISO codes where possible |
| Phone | Char | 20 | 8051234567 x456 | |
| Char | 80 | |||
| ServiceCode | Yes | Char | 10 | Landmark Specific Shipment Method only (e.g. LGINTSTD). See Integration Manager for service code information |
| ShipmentInsuranceFreight | Yes | Decimal | 8,2 | Amount charged for shipping and insurance on the whole order. This value does not include the amount charged for items in the order. |
| ItemsCurrency | Char | 3 | 3-character ISO code. Defaults to USD (or requested client currency) unless configured by Landmark IT. | |
| PackageCount | Cond. | Integer | 2 | Default 1; designates the total number of packages in a shipment (may be repeated for multi-package shipments). Required if a multi-package is specified in the file |
| PackageReference | Char | 50 | Primary identifier of a package that is part of a shipment (all packages are part of a shipment). Can be used to search for and track a single parcel. If a shipment contains multiple packages, it is recommend that this field be used for the label barcode instead of the ShipmentReference | |
| PackageWeight | Decimal | 8,2 | Default in pounds (LB). Should be the total weight of a package. May be omitted if final shipping weight is unknown. If omitted, 1 will be entered and updated upon receipt of package. | |
| WeightUnit | Char | 2 | LB, KG, or G. Defaults to LB if not specified. | |
| Length | Decimal | 8,2 | In inches. Defaults to 1 if it cannot be provided. | |
| Width | Decimal | 8,2 | In inches. Defaults to 1 if it cannot be provided. | |
| Height | Decimal | 8,2 | In inches. Defaults to 1 if it cannot be provided. | |
| DimensionsUnit | Char | 2 | IN or CM. Defaults to IN if not specified. | |
| ItemSku | Cond. | Char | 64 | Item Sku (i.e. UPC code). Required if passing item information in a row. If a row has a non-empty ItemSku, an item will be added to the shipment. |
| ContainsDangerousGoods | Cond. | Boolean | 1 | Required if the ItemSku value in the same row is a dangerous good. |
| UNCode | Cond. | Char | Required if item is a DG. Valid UN codes: 3091, 3481 | |
| PackingGroup | Cond. | VarChar | Required for DGs with some UN codes. Must contain a valid packing group value (i.e. "I", "II", "III"). More info. | |
| PackingInstructions | Cond. | VarChar | Required for DGs with some UN codes. Must contain a valid packing instructions value (e.g. "P001", "PI966S1"). More info. | |
| ItemWeight | Cond. | Decimal | Required if item is a DG. This should be the weight for a single quantity of the item (i.e. product). | |
| ItemWeightUnit | Cond. | VarChar | Required if item is a DG. The unit used to declare the item weight (i.e. “KG”, “LB”, “OZ”, “G”). Defaults to LB if not specified. | |
| ItemVolume | Cond. | Decimal | Required for DGs with some UN codes. This should be the volume for a single quantity item. | |
| ItemVolumeUnit | Cond. | VarChar | Required for DGs with some UN codes. The unit used to declare the item volume (i.e. "ML", "L", "OZ"). | |
| ItemQuantity | Cond. | Integer | 11 | Number of items. Required if passing item information in a row. |
| ItemUnitPrice | Cond. | Decimal | 8,2 | Retail price paid by the end consignee for a single unit of the item purchased. This value should not include shipping. tax, or insurance values. Landmark cannot accept a $0 value item price due to customs clearance requirements. Required if passing item information in a row. |
| ItemDescription | Cond. | Char | 255 | Detailed description of goods for customs classification. Required if passing item information in a row. |
| ItemHSCode | Cond. | Char | 50 | Harmonization Code for the product being declared. |
| ItemCountryOfOrigin | Cond. | Char | 50 | Use 2-character ISO codes Required if passing item information in a row. |
| ItemURL | Cond. | Char | 256 | Product URL from the website the item was purchased from (e.g. https://store.com/browse/product) |
| USMID | VarChar | 15 | Value for a US Manufacturer's Identification Code. Required for US formal customs entries. Must be an alphanumeric value. | |
| ReturnHSRegion | Char | 3 | Country code value for the ReturnHSCode if provided. iso-3166-2 standard. "EU" will be used to represent the European Union. | |
| ReturnHSCode | Char | 20 | Harmonization Code to be considered for a return clearance. | |
| CommercialClearance | Char | 1 | 1 or 0 (true/false) to denote shipments that are to clear commercially. | |
| OptionType | Char | 50 | Used to tell Landmark what kind of option will be added to the shipment. Allowed OptionTypes: Option (for setting shipment options), Memo (for pick slips), Charge (for pick slips) and Additional (additional shipment fields). | |
| OptionName | Char | 50 | Specific shipment option being requested (e.g. signature required). Check with your account rep prior to passing any values. | |
| OptionInfo | Char | 50 | Value for shipment option being selected. Typically true/false | |
| VendorName | Cond. | Char | 50 | Required if providing third-party logistics. Vendor (retailer) name |
| VendorPhone | Char | 50 | ||
| VendorEmail | Char | 50 | ||
| VendorAddress1 | Cond. | Char | 150 | Required if providing third-party logistics. Vendor (retailer) address |
| VendorAddress2 | Char | 150 | ||
| VendorCity | Cond. | Char | 100 | Required if providing third-party logistics. Vendor (retailer) city |
| VendorStateProv | Cond. | Char | 100 | Required if providing third-party logistics. Vendor (retailer) state or province if applicable |
| VendorPostalCode | Cond. | Char | 10 | Required if providing third-party logistics. Vendor (retailer) postal code if applicable |
| VendorCountry | Cond. | Char | 2 | Required if providing third-party logistics. Vendor (retailer) country |
VendorLowValueTaxID | VarChar | 50 | Populate with the vendor's Low-Value Tax ID if relevant for tax compliance such as Norway's VOEC, or Australian GST Number | |
| VendorCCN | VarChar | 50 | Populate with the vendor's commercial clearance (b2b) value if that is being requested | |
| VendorBusinessNumber | Cond. | Char | 50 | Used for clearing customs (if CCN is not available). Vendor business number |
| VendorRGRNumber | Cond. | Char | 50 | License number for customs. Vendor RGR number |
| VendorIOSSNumber | Cond. | Char | 50 | Required if providing third-party logistics. Vendor (retailer) IOSS number (used to make VAT to EU tax authorities). This number is needed for shipments that LGI receives in the US and sends DDP to the EU. |
| VendorEORINumber | Cond. | Char | 50 | Required unique identification number used when exchanging data with Customs in all EU Member States. |
| AdditionalAddressType | Char | 50 | Additional address option (i.e. Fulfillment, Return to Sender) | |
| AdditionalCode | Char | 20 | Identifier code for additional address | |
| AdditionalName | Char | 50 | Name for additional address | |
| AdditionalAttention | Char | 50 | ||
| AdditionalAddress1 | Char | 50 | ||
| AdditionalAddress2 | Char | 50 | ||
| AdditionalAddress3 | Char | 50 | ||
| AdditionalCity | Char | 20 | ||
| AdditionalState | Char | 20 | ||
| AdditionalPostalCode | Char | 20 | ||
| AdditionalCountry | Char | 30 |
Multi-Package and/or item shipments
There can be multiple packages and/or multiple items in a single shipment. (A shipment is a quantity of goods shipped; also called a consignment or order. A package is physical box belonging to a shipment.)
If there are duplicated ShipmentReferences in the file, the contents of each row having that reference will be treated as part of the same shipment. ShipmentReferences must be added in order (all entries for shipment 1, then all entries for shipment 2, etc.). No new packages will be added for out of order ShipmentReferences.
All items in a shipment will be treated as a single package unless the PackageCount is greater than 1.
- Multi-Item
- If multiple of the same item (referenced by sku) are part of the same shipment, use the ItemQuantity field.
- If there are several different items (2 or more skus) being sent as part of the same shipment, there should be multiple lines in the file; one for each sku. (See ShipmentReference 1243 in Landmark Import Examples v2.xls).
- Multi-Package
- The PackageCount field is meant to represent the total number of packages in a shipment. (See Multi-Package Example in Landmark Import Examples v2.xls).
- If multiple of the same item are part of the same shipment, but being sent via separate shipping boxes (packages), utilize the PackageCount field. For example, if 3 of the same item are being sent via 3 packages there should only be 1 row used in the file with the PackageCount and ItemQuantity fields both set to 3. (SeeShipmentReference 1235 in Landmark Import Examples v2.xls).
- If there are more packages in a shipment than skus, a row without item information may be used to add a package to the shipment. (See ShipmentReference 1244 & 1245 in Landmark Import Examples v2.xls).
Using option columns
The option columns allow you to add additional information to an 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.
Was this article helpful?