Booking CSV format
- Henrik Bjerregaard
Analytics
The booking CSV format allows shipments to be imported into Leaps.
The CSV file contains 1 shipment per row. The first row is ignored. Fields must be separated by semi colon (;). Text must be in UTF-8. Numbers use full stop (.) as decimal point.
The tabel below shows the content of each column.
| Column (#) | Meaning | Example | Required |
|---|---|---|---|
| A (1) | Name of the responsible user (*) | “kevinsmith” | Y |
| B (2) | Pickup date | “2017-02-07” | Y |
| C (3) | Template name (*) | “Transatlantic” | Y |
| D (4) | Receiver name | “MegaCorporation” | Y |
| E (5) | Receiver address 1 | “Industrial Road 2” | Y |
| F (6) | Receiver address 2 | Y | |
| G (7) | Receiver zip | “W12 123” | Y |
| H (8) | Receiver city | “London” | Y |
| I (9) | Receiver country | “UK” | Y |
| J (10) | Receiver state | Y | |
| K (11) | Contact person | “Tony Blair” | Y |
| L (12) | Contact phone | “1234 5678” | Y |
| M (13) | Contact email | “tony@blair.co.uk” | Y |
| N (14) | Num. pieces | 2 | Y |
| O (15) | Total weight, in kgs | 12 | Y |
| P (16) | Description of the packages | “Rubber ducks” | Y |
| Q (17) | Senders ref. | “SHIP3245345” | Y |
| R (18) | Pickup name | N | |
| S (19) | Pickup address 1 | N | |
| T (20) | Pickup address 2 | N | |
| U (21) | Pickup zip | N | |
| V (22) | Pickup city | N | |
| W (23) | Pickup country | N | |
| X (24) | Pickup state | N | |
| Y (25) | Delivery name | N | |
| Z (26) | Delivery address 1 | N | |
| AA (27) | Delivery address 2 | N | |
| AB (28) | Delivery zip | N | |
| AC (29) | Delivery city | N | |
| AD (30) | Delivery country | N | |
| AE (31) | Delivery state | N | |
| AF (32) | Product (*) | “Airfreight” | N |
| AG (33) | Delivery date | “2017-03-02” | N |
| AH (34) | AWB number | “123345123345” | N |
| AI (35) | Ordering GID (*) | N | |
| AJ (36) | Total volume, in m3 | 0.023 | N |
| AK (37) | Incoterm (*) | “EXW” | N |
| AL (38) | Sender name | N | |
| AM (39) | Sender address 1 | N | |
| AN (40) | Sender address 2 | N | |
| AO (41) | Sender zip | N | |
| AP (42) | Sender city | N | |
| AQ (43) | Sender country | N | |
| AR (44) | Sender state | N | |
| AS (45) | Sender contact person | N | |
| AT (46) | Sender contact phone | N | |
| AU (47) | Sender contact email | N | |
| AV (48) | Pickup contact person | N | |
| AW (49) | Pickup contact phone | N | |
| AX (50) | Pickup contact email | N | |
| AY (51) | Delivery contact person | N | |
| AZ (52) | Delivery contact phone | N | |
| BA (53) | Delivery contact email | N | |
| BB (54) | Portal code (*) | “DKVENTUCPH” | N |
| BC (55) | Goods value | 123.50 | N |
| BD (56) | Goods currency | “DKK” | If BC is set |
(*) These must match existing values in the Leaps system.
BB is only used when importing via CCS.
Date must be within 3 months.
Columns A - Q are required, although C may be empty if AF is set (see below).
If column R isn't empty, then columns R - X will overwrite any pickup address specified in the template.
If column Y isn't empty, then columns Y - AE will overwrite any delievery address specified in the template.
If column AL isn't empty, then columns AL - AR will overwrite any sender address specified in the template.
Address2 and state fields are optional for all addresses.
Countries must be specified as the 2-letter code, eg. “DK” for Denmark, “DE” for Germany.
The selected template determines things like incoterms (unless AK is set), pickup times, sender address, product (unless AF is set, see below) etc.
The contact information in columns AS - BA overwrites the contact info from the template.
If BC isn't empty, then BD is required, and BC and BD specify the duty value of the shipment, and the shipment will have the 'reliable to duty' flag set.
AF
The column AF (product) determines if you are importing a normal shipment (which should be sent to the carrier) or if you are importing an existing shipment. It also determines if several other columns are required.
If AF is set then you are importing an existing shipment (previously created elsewhere), and columns AG - AI are required, and nothing will be sent to the carrier. AF must hold the name of a valid product that is available for the portal.
If AF isn't set, then you are importing new shipments. The product will be taken from the template, and the shipment may be sent to the carrier, if this is relevant for the product. Columns AH - AI are ignored.
Import methods
The CSV file may either be imported from within the portal, or it may be uploaded to the Leaps FTP server.
When uploading to the FTP server, the CSV file should be given a unique name (eg. something that includes the timestamp) and its name must end in .csv. The file must be uploaded to the book/ folder on the FTP server.