System Integration Manual

Transcription

1 Geis CZ s.r.o. Geis Parcel CZ s.r.o. Geis SK s.r.o. Geis Parcel SK s.r.o. System Integration Manual Version: 2015/01 Valid From: September Last revision: August 19, 2015 This version replaces all previous versions in its full scope. Current version is also available at or

2 Contents Purpose of the document Overview of changes List of figures List of tables v vi vii vii 1 General information Modification of customer s information system Transport types Sequences Checksums Package routing National routing International routing Data types Data types valid for parcels Alpha- numeric values (AN) Integer values (CC) Numeric values including decimal places (FP) Calendar dates (KD) Phone numbers (TC) Data types valid for cargo Alpha-numeric values (AN) Integer values (CC) Integer values, the number is to be aligned to the right (CP) Integer values, the number is aligned to the left (CL) Integer values, the number is completed with the fixed value (CS) 10 i

3 1.8.6 Calendar dates (KD) Time data (KC) Phone numbers (TC) Data validator Parcel Combined (mass) shipment EDI format specification Records structure Export file denomination convention Handover protocol structure Bar code Label printing specification Shipment parcel transport services Notification on the delivery of the shipment ADZ POD services Notification on a problematic shipment APZ SMS notification on the dispatch of the shipment SMS Telephonic notification AVI Cash on delivery COD Delivery until 12 o clock D Delivery to a private address B2C Ex Works EXW Guaranteed delivery GAR Insurance POJ Card payment CDR Pickup point VM Verification parcel Go live ii

4 3 Cargo EDI format specification Records structure Convention regulating the process of assigning of names to export files Handover protocol structure Label printing specification Transport services for cargo shipments SMS notification SMS Phone notification AVI Cash on delivery COD Specified delivery time DTR B2C (Private address) EXW (Payment by the recipient) DL backwards VDL Contracts back VSM B2C Assisted delivery B2P B2C Delivery of an appliance B2S VIP delivery VIP Verification cargo Go live Symbols and abbreviations 55 Attachments 56 Handover protocol for parcel Handover protocol for cargo Předávací protokol pro parcel Předávací protokol pro cargo Previews of parcel labels iii

5 Previews of cargo labels Checklist for underlying documents parcel Checklist for underlying documents cargo Country code table subject to ISO List of codes of handling units Change of file names with routing tables iv

6 Purpose of the document System Integration Manual is intended for clients of Geis Group at Czech and Slovak territory. The purpose of the document is to provide clients with key knowledge and information related to system integration so that integration implementation takes as short time as possible. The manual defines the rules for transferring data into Geis Group information system, defines which data should be transferred, which data formats and types are used, and also provides specification of stickers and handing-over certificates for parcel and cargo transport. Prepared by IT department Last revision: August 19, 2015 v

7 Overview of changes This section includes chronological list of changes in the documentation. Version number Date of issue Description of changes Section(s) 2015/ Change of service availability for countries (CDR) / Added Pickup point service 2.5 Added Slovak version of Handover protocol Attachments 2014/ Added Payment by card service 2.5 Differentiation of packages from transport subjects 1.2 perspective Added information about data validator 1.9 Barcode size specified 2.4, 3.3 Change of order of introductory chapters v, vi, vii Correction of typos and mistakes Modified availability of cargo services abroad / Initial issue of documentation Publication on technical support website Revised Parcel specification Completed Cargo specification Table 1: Overview of documentation modifications vi

8 List of Figures 1 Simplified scheme of EDI format for parcel Export file view for parcel Example unreadable (left) and correct (right) bar code Label layout for parcel Scheme records in the format KDDS Description of records in the format KDDS Label layout for cargo Previews of parcel labels without additional services Previews of parcel labels with COD Previews of parcel labels more additional services Previews of parcel labels service VM Previews of cargo labels shipment with three pieces Previews of cargo labels shipment with three pieces Previews of cargo labels shipment with three pieces List of Tables 1 Overview of documentation modifications vi 2 Structure of records in routing table for national Structure of records in routing table for international Records structure in a parcel export file Denomination of supplementary services in the parcel export file Accessibility of services by type of transport - parcel Additional services for cargo export file Accessibility of services by type of transportation - cargo vii

9 GEIS Group 1. General information 1 General information The manual includes ZIP archive containing files with valid Post codes, sticker printing templates, sample handover protocols, sample export data, and logotypes. Current version of this manual and ZIP archive is available for downloading at at FTP server (see section 1.5 for access information), or from your Geis business manager. Make sure that you are using the most current version of the documentation. New version always replaces previous version in its full scope. Structure and contents of ZIP archive: _loga - Geis_logo_barevne.pdf - Geis_logo_barevne.png - Geis_logo_barevne.svg - Geis_logo_cerne.pdf - Geis_logo_cerne.png - Geis_logo_cerne.svg - Geis_logo_printer.zip \- geis.pcx Cargo - Cargo_Label_EPL.txt - Cargo_Predavaci_Protokol.pdf - Cargo_PSC_CZ_Vnitro.txt - Cargo_PSC_CZ_Export.txt - Cargo_PSC_SK_Vnitro.txt - Cargo_PSC_SK_Export.txt - Cargo_Obaly.csv - Cargo_Zeme.csv \- Cargo_Data_ftp txt Parcel - Parcel_Label_EPL.txt - Parcel_Predavaci_Protokol.pdf - Parcel_PSC_CZ_Vnitro.txt - Parcel_PSC_CZ_Export.txt - Parcel_PSC_SK_Vnitro.txt - Parcel_PSC_SK_Export.txt - Parcel_Zeme.csv \- Parcel_Data_CTST108c.001 EPL2_Programming_Manual.pdf 1

10 GEIS Group 1.1 Modification of customer s information system 1.1 Modification of customer s information system Implementation of integrated data communication with Geis systems frequently requires modifications of customer s information system. When ordering these modifications, it is necessary to consider the fact that certain characteristics may change over time. This includes, primarily, the business terms and conditions, the scope of provided services, sequences, supplementary services, routing tables, and other code lists. It is therefore advisable to order and implement modifications of the information system in a way which allows dynamic change or ranges as necessary. 1.2 Transport types When transporting packages, we distinguish two separate transport types: ˆ Parcel, also called traditional parcel service. These transactions are performed by Geis Parcel CZ, s.r.o. in the Czech Republic and by Geis Parcel SK, s.r.o. in the Slovak Republic. ˆ Cargo, also called pallet transport. These transactions are performed by Geis CZ, s.r.o. in the Czech Republic and by Geis SK, s.r.o. in the Slovak Republic. Customer agrees on conditions of cooperation, depending on transport type, with appropriate company of Geis Group. Structure of data interconnection (data files, handover protocols, stickers, supplementary services, routing tables, etc.) are different for both transport types, as described in detail in the chapters below. Package is the basic unit of transport. In case of parcel transport, the term parcel is used (1 package = 1 parcel). In case of cargo transport, the term cargo package is used (1 package may include multiple pieces of load defined in different handling units). Individual loads share the same package number, a particular piece s position within the package is determined by Kolli number, see section 1.3. In case of parcel transport, one parcel (packaging) is always the handling unit; different types of handling units (pallet, drum, can) may form the package; complete list of handling units is appended to this document. From the transport subjects perspective, we distinguish: ˆ Dispatches. In this case, consignor and consignee exist. Consignor, i.e. Geis customer, orders the transport. 2

11 GEIS Group 1.3 Sequences This type of transport may be ordered through data interconnection. In this document, package is defined as employing this transport type. ˆ Orders (also called Returns). In this case, consignor, consignee, and payer for the transport exist. Payer for the transport, i.e. Geis customer, orders the transport. Consignee may or may not be identical with payer for the transport. This type of transport currently cannot be ordered through data interconnection. Example 1: Geis customer (payer for the transport) needs to transport a package from company (A) (consignor) to company B (consignee). In this case, consignor, consignee, and payer for the transport exist; payer for the transport orders the transport. Example 2: Geis customer (payer for the transport) needs to transport a package from company (A) (consignor) to himself. In this case, there are 2 subjects - consignor, consignee = payer for the transport. According to consignor s country and consignee s country, we distinguish ˆ Inland parcels. In this case, consignor s country is the same as consignee s country (e.g. national transport within the Czech Republic). ˆ International (or export) parcels. In this case, consignor s country is different from consignee s country (e.g. transport from the Czech Republic to Germany). 1.3 Sequences The term Sequence means a range of numbers assigned to clients for numbering their packages.the client is assigned a range of numbers (for Cargo packages and for Parcel packages) <from, to>. In case of Cargo service, only one range of numbers is assigned, shared by national and international transport. In case of Parcel service, two ranges of numbers is assigned, one for national and one for international transport. International transport from CZ to SK or SK to CZ is perceived as national, these shipments are numbered of sequence for national transport. Sequences are always assigned so that they last for approx. a year; then, new sequence is assigned 1. The client receives two numbers - lower and upper limit of the range (see example). The client increments package numbers, starting at the lower limit, until assigned range is completely utilized. Lower and upper limit are included in the range and may be used to designate packages. The system must include a check for reaching the end of sequence! Exceeding assigned range means that data will not be processed by our system. well. 1 Assigned sequences need not have relation to previous sequence and may have different prefix as 3

12 GEIS Group 1.4 Checksums Remark: Parcel packages have 11-digit numbers, while cargo packages have 13-digit numbers. Example: The client is assigned number range to for package transport. This range suffices for packages. The first package will be designated , the second package will be designated etc. The last package of the range will be designated Checksums Checksums are generated from package and pallet (or loads) numbers, and clients must include checksums on handover protocols and stickers. The process is slightly different for parcel packages and cargo packages. Cargo Checksum of cargo packages is calculated from package number and KOLLI number 2. Method of calculation is demonstrated by the following example. Example: Package number is , KOLLI number for first load is 01. Checksum is being calculated from ) Sums of digits at odd positions and at even positions are calculated = = 9 2) Sum of digits at odd positions is multiplied by 3 and sum of digits at even positions is added. (15 3) + 9 = 54 3) Resulting checksum is the difference between next ten and the result of previous step (marked blue). 54 and complement to next ten (60) = 6 Parcel Checksum of cargo packages is calculated from parcel number only. Method of calculation is demonstrated by the following example. Example: Parcel number is Checksum is being calculated from parcel number only, ) Sums of digits at odd positions and at even positions are calculated = = 10 2) Sum of digits at odd positions is multiplied by 3 and sum of digits at even positions increased by one is added. (23 3) = 80 3) Resulting checksum is the difference between next ten and the result of previous step (marked blue). 80 complement to next ten (80) = 0 2 KOLLI is a two-digit number of a load in a package. 4

13 GEIS Group 1.5 Package routing 1.5 Package routing Routing system is used to transport packages, routing is defined by routing tables. Sections and below describe format of these tables. Tables are updated continuously (up to once a month). Current versions can be downloaded from GEIS FTP server. 3 FTP server: Uživatel: Heslo: Adresář: ftp1.geis.cz ftp integrace ftp194int integrace The client must be able to work with these tables, so that he can print correct stickers and send correct export data. Different routing tables are used to route parcel packages and cargo packages. Different structure of routing tables is used for national and international transport, described in sections National routing and International routing. Appended archive and also FTP server lists them in directories Parcel and Cargo. More information about naming of files can be found in section National routing Directory Parcel in appended archive contains the following files: ˆ Parcel PSC CZ Vnitro - routing table for national parcel packages of customers from the Czech Republic ˆ Parcel PSC SK Vnitro - routing table for national parcel packages of customers from the Slovak Republic Directory Cargo in appended archive contains the following files: ˆ Cargo PSC CZ Vnitro - routing table for national cargo packages of customers from the Czech Republic ˆ Cargo PSC SK Vnitro - routing table for national cargo packages of customers from the Slovak Republic Routes are stored at separate lines within the files. Each line contains different information, at positions listed in table 2. The following list describes all information items. 3 They are also sent to client s contact s. 5

14 GEIS Group 1.5 Package routing Fixed value: The first information in a record is so-called Fixed value. This block is always NT and need not be processed.. Depot number: This number determines a branch of Geis, assigned to the range of Post codes listed at positions ZIP from and ZIP to. The referred to branch (depot) collects or distributes shipment s in the specified extent. The depot number in the file is a three digit number, the first zero is always to be skipped. For instance, if the specified depot number is 088, the value to be used is 88. Country code: The code of the country with the presumed scope of ZIP numbers as given at positions Post code from and Post code to. For current codes see the annex Country Code Table according to ISO Blank: This way marked fields are left free they are filled with free spaces and they do not carry any information. They are included to the format just to improve its legibility by people. Post code from: This field includes the bottom limit of the scope of Post codes related to other information on the given line. The value is aligned from the left. Post codes to: This field includes the upper limit of the Post code scope. The value is aligned from the left 4. Delivery route number: This number defines the delivery route assigned to the given Post code scope. Internal data: This information does not need to be processed in any way. This information is not used for transport operations. The table 2 defines positions of values described in the line, their length and data type (for more information on data types see the section 1.6). # Name of block Position Lenght Data type 1 Fixed value NT 1 2 AN 2 Depot number 3 3 CC 3 Country code 6 2 AN 4 blank 8 1 AN 5 Postcode from 9 5 AN 6 blank 14 2 AN 7 Postcode to 16 5 AN 8 blank 21 2 AN 9 Number of delivery route 23 4 CC 10 Internal data 27 9 CC Table 2: Structure of records in routing table for national. 4 Both border digits belong to the interval. 6

15 GEIS Group 1.5 Package routing International routing The following files in the attached directory Parcel: ˆ Parcel PSC CZ Export - routing table for international parcel shipment s of clients from the Czech Republic ˆ Parcel PSC SK Export - routing table for international parcel shipment s of clients from Slovakia You will find the following files in the Cargo directory: ˆ Cargo PSC CZ Export - routing table for international cargo shipment s of clients from the Czech Republic ˆ Cargo PSC SK Export - routing table for international cargo shipment s of clients from Slovakia The international transport operations routing table includes information on lines identical to the inland transport operations routing table, the only difference being the positions and length of some values as you it is apparent in the table 3. # Name of block Position Lenght Data type 1 Fixed value NT 1 2 AN 2 Depot number 3 3 CC 3 Country code 6 2 AN 4 blank 8 1 AN 5 Postcode from 9 6 AN 6 blank 15 1 AN 7 Postcode to 16 6 AN 8 blank 22 1 AN 9 Number of delivery route 23 4 CC 10 Internal data 27 9 CC Table 3: Structure of records in routing table for international. 7

16 GEIS Group 1.6 Data types 1.6 Data types Individual data (values) have to be formatted in data files and routing tables based on the specification. The data type defines the value format in data blocks and records. The most often used data types include the alpha-numeric and full-numeric types but often also special types are used. Data types used in data files for cargo and parcel operations differ and for their detailed description see this section. An abbreviation used further in the description of the data structure is given behind the name of each data type in brackets. 1.7 Data types valid for parcels Alpha- numeric values (AN) Fields with values of this type may include any alphabet characters, digits and special symbols whatsoever (including Czech and Slovak diacritics) The text has to be aligned to the left and all empty places have to be filled with spaces across the entire length of the field. Example: Name of the Recipient Lojza Novák in a 20 character field: Lojza Novák Integer values (CC) Integer value fields may include only digits. The number has to be aligned to the right and all empty spaces have to be filled with zero characters. Example: Parcel weight gr in a 10 digit field: Numeric values including decimal places (FP) Fields with this type values may include only digits. The decimal places of the number are not divided by any special symbol, there are two places reserved for them (see the bold digits in the examples). The number has to be aligned to the right and all empty spaces have to be filled with zero characters. Example: Cash on delivery CZK in the 10 digit field: Example: Cash on delivery EUR 99.- in the 10 digit field: 8

17 GEIS Group 1.8 Data types valid for cargo Example: Cash on delivery 0.- in the 10 digit field: Calendar dates (KD) The date is written to the integer field. The parcel date format is YYYYMMDD. Example: Date of the parcel shipment loading is March 11, 2013: Phone numbers (TC) Phone numbers are recorded to alpha-numeric fields and have a strictly defined format. This type values may contain only the character "+" at its beginning and then only digits. The phone number has to be entered in the international format (+420xxxxxxxxx). The phone number has to be aligned to the left and all empty spaces have to be filled with spaces across the entire length of the field. Caution: Digits must be separated by spaces! The entire phone number has to be formatted as a single coherent unit. Example: Phone notice to the number (+420) in the international format in a 15 digit field: Data types valid for cargo Alpha-numeric values (AN) Fields with values of this type may include any alphabet characters, digits and special symbols whatsoever (including Czech and Slovak diacritics) The text has to be aligned to the left. Example: Name of the Recipient Lojza Novák in a 20 character field: Lojza Novák 9

18 GEIS Group 1.8 Data types valid for cargo Integer values (CC) Integer value fields may include only digits. The number has to be aligned to the right and all empty spaces have to be filled with zero characters. If the field contains no data, it remains blank (e.g. for supplementary services). Example: Parcel weight 15 kg in a 10 digit field: Integer values, the number is to be aligned to the right (CP) Integer value fields may include only digits. The number has to be aligned to the right and empty places (until the end of the field length) have to be filled with spaces. Example: The sender s Post code is in a 9 digit field: Integer values, the number is aligned to the left (CL) Integer value fields may include only digits. The number has to be aligned to the left and empty places (until the end of the field length) behind the number have to be filled with spaces. Example: The shipment variable symbol is in 10 digit field: Integer values, the number is completed with the fixed value (CS) Integer value fields may include only digits. A fixed numeric constant is attached at the end of the number. Example: The shipment number from the assigned scope is , the constant is 000: Calendar dates (KD) The date is written to the integer field. The cargo date format is DDMMYY. 10

19 GEIS Group 1.8 Data types valid for cargo Example: The date of the loading of the palette shipment is March 11, 2013: Time data (KC) The time is recorded in the integer value. The time format is HHMM. Example: Shipment delivery time is 11:30: Phone numbers (TC) Phone numbers are recorded to alpha-numeric fields and have a strictly defined format. This type values may contain only the character "+" at its beginning and then only digits. The phone number has to be entered in the international format (+420xxxxxxxxx). The phone number has to be aligned to the left and all empty spaces have to be filled with spaces across the entire length of the field. Caution: Digits must be separated by spaces! The entire phone number has to be formatted as a single coherent unit. Example: Phone notice to the number (+420) in the international format in a 15 digit field:

20 GEIS Group 1.9 Data validator 1.9 Data validator A data validator is available for the verification of the correctness of data in data files. The validator checks the following: ˆ Data file coding ˆ Data file structure ˆ Formal correctness of data types ˆ Logical correctness of data types ˆ Conformity with business terms and conditions ˆ Routing Moreover, the validator makes it possible to calculate the check digit for bar codes. Currently, the validator makes it possible to check parcel and cargo data files. This validator is recommended to be used as early as prior to the first dispatch of data for check to Geis. The current validator version is available for free at the technical support website including its manual or in the section Ke stažení (Downloads). 12

21 GEIS Group 2. Parcel 2 Parcel This part of the manual includes all information as necessary for the integration of Geis group clients who make use of the parcel delivery services of Geis Parcel CZ s.r.o. 2.1 Combined (mass) shipment A combined (mass) shipment is a shipment that includes several parcels addressed to the same Recipient. Each parcel assigned to a combined shipment has its own parcel number and the label shows the serial number of the parcel out of the total number of parcels, e.g. 1/2 and 2/2. For related details see below in this chapter. 2.2 EDI format specification Electronic exchange of structured text files v kódování Windows-1250 coding is used for the import of data on the transport of parcels to our IS. The data transfer file has the structure of records on individual lines. Each record corresponds to one parcel and it consists of several data blocks, as shown on the fig. 1. The preview of the export file with data blocks is shown on the fig. 2. Export EDI data file Blok 1 Blok 2 Blok 3 Blok N Blok 1 Blok 2 Blok 3 Blok N Blok 1 Blok 2 Blok 3 Blok N Blok 1 Blok 2 Blok 3 Blok N Data record for 1 st package Data record for 2 nd package Data record for 3 rd package Data record for 4 th package Figure 1: Simplified scheme of EDI format for parcel Export EDI data file H H H H H... Figure 2: Export file view for parcel. 13

22 GEIS Group 2.2 EDI format specification Records structure Individual data blocks have a fixed position (sequence), length and data format (see the section 1.7 Data types ). Some blocks have strictly defined value or enumeration of valid values. All this information is described in the list and table 4 Structure of records in the export file for the parcel below. Data blocks in the record are closely attached to each other and therefor it is necessary to make sure that recorded values could not exceed the length of the respective block! The minimum length of the record is 317 characters. All records have to be of the same length. The following list of data blocks includes the meaning, permitted values and mutual relations among individual blocks. The list is followed by a table that shows first of all positions, lengths and data types of blocks. Fixed value: The first block in the record is so called fixed value. This block has a defined fixed value 11 that has to be included anytime. Shipment number: : If the shipment is not combined (i.e. it consists of a single parcel), this block is identical to the parcel number block.if the shipment is combined (mass), records (lines) for each parcel included to such a shipment have to have the same number of the shipment. This number is determined by the first (so called superior) parcel in the combined shipment. This record will appear in the export file as first and will have the same values in the blocks shipment number and parcel number. Parcel number: It has to be specified anytime and it has to be taken from the assigned series of numbers (see the section 1.3). Collection address number: A unique client s identification number. It will be assigned to the client after the validation of the correctness of the export file. It must be assigned anytime. Collection date: This block has to show the date of the shipment collection to our depot. Delivery date: Does not need to be specified. business day 5 after the collection date. If specified, it will be the following Collection depot: This block shows the number of the depot that collects the shipment from the collection address of the sender. It may be found based on the Post code of the collection address of the sender (see the section 1.5 Routing ). It must be assigned anytime. Delivery depot: Here, the number of the depot that will deliver the shipment to its recipient is to be specified. It may be found based on the post code of the shipment Recipient (see the section 1.5 Routing ).It must be given anytime. 5 Both weekends and public holidays have to be taken into account. 14

23 GEIS Group 2.2 EDI format specification Blank: This way marked data blocks have to be left empty they should be filled with spaces or zero characters depending on their data type. These are blocks that do not carry any information at this moment and they are kept in the format only for the safe of the reverse compatibility. Delivery address: The delivery route number is to be filled in here. It must be given anytime and it may be found based on the Post code of the shipment Recipient (see the section 1.5 Směrování ). Name of the juridical/natural person: The name of the Recipient (Firma s.r.o. or Lojza Novák in case of the B2C service see the section 2.5)) has to be filled in this block. It must be assigned anytime. Contact person name: This block is not obligatory. As a rule, the name of the contact person is given if the block name of the juridical/natural person includes a company name. Street, city, country, Post code: Parcel recipient address. It must be identical for all parcels included to a combined shipment. Valid values of a country code for parcel shipments are given in the annex Tabulka kódů zemí podle ISO If the service VM (see the section 2.5) is used, it will be address of Pickup point. Weight: It must be given anytime. The value is given in grams, the minimum value is 100 grams. If the parcel has not been weighed, a flat rate of 1 kg may be specified if so approved by the Geis sales manager. According to business terms and conditions of Geis Parcel, the maximum weight of a single parcel has been set to 50 kg. Weight of individual parcels included to a combined shipment is specified. Supplementary services coding: Required supplementary services are to be defined in this block using the symbol 1 on respective positions for details see the table 5 below in this section and the section 2.5). Services are defined for the superior combined shipment parcel, only. Card payment: Card payment (CDR) is to be defined in this block, it makes it possible for the recipient to pay with a payment card the cash on delivery amount It makes sense only in combination with the shipment COD service (cash on delivery). In case of combined shipment s, it is specified only for the shipment superior parcel (i.e. the parcel that has the same shipment and parcel number). Cash on delivery value: the value (amount) of the cash on delivery payment, it the parcel is to be paid for on delivery. The cash on delivery amount is always specified in the currency of the country with the accuracy of two decimal points (hellers, cents etc.). In case of combined shipment with cash on delivery, the total cash on delivery amount is to be specified for the shipment superior parcel (i.e. the parcel that has the same number of the shipment and the parcel). It must not be specified for other parcels so that the total sum could match. According to the business 15

24 GEIS Group 2.2 EDI format specification terms and conditions of Geis Parcel, the maximum cash on delivery amount has been set to CZK respectively to EUR Pickup point code: The code of pickup point (VM-1234 or 1234 ) is to be defined in this block, where shipment will be delivered depending on used service VM (see the section 2.5). Shipment must contain only one parcel (it musn t be superior parcel) and maximum weight can be 15 kg. Variable symbol: If a parcel is cash on delivery shipment, this information is obligatory. It may specified only for the superior parcel in case of combined shipment s. Number of parcels in the shipment: This block specifies the number of parcels in the shipment and it is obligatory. The number of parcels in combined shipment s is to be specified for each parcel. References: This block includes clients references, for instance order numbers. This filed serves mainly for the senders who may include in here their registration numbers of their parcels so that they could trace them. This data is not obligatory. Phone notice/private address: What is to be specified I this block depending on the required service (see the section 2.5) is the phone number in the international format (see the section 1.8.8). Insurance: What is to be specified in the insurance value with the accuracy to two decimal points (hellers, cents etc.) as explained in the section Always enter the currency of the sender s country. According to its business terms and conditions, Geis Parcel is liable for each parcel up to the value of CZK respectively EUR Based on agreement with the Geis Parcel sales manager, this block may be used to enter higher shipment insurance values. In case of combined shipment s, the insurance is specified for the shipment superior parcel, only. Remark for driver: Information for drivers may be entered at this place. This notice is given on the handover protocol, too. Remark the recipient: Here you may enter a notice for the recipient. This notice is provided on the parcel label, too. If the service VM (see the section 2.5) is used, it will be recipient delivery address here. Notification of problematic shipment: What is added is either the address or phone number (see the section Phone numbers ), to which a message has to be sent in case of problem with the shipment delivery. Notification of delivered shipment: What is to be entered is either the address or phone number to which message on the delivery of the shipment has to be directed. Damaged shipment notification: What is to be entered is either the address or phone number to which message on a damage of the shipment has to be directed. 16

25 GEIS Group 2.2 EDI format specification POD service: Enter the address to which the confirmed delivery note is to be sent. SMS notification on the dispatch of the shipment: Here enter the phone number to which the shipment dispatch message is to be sent. 17

26 GEIS Group 2.2 EDI format specification # Data block name Position Length Data type Obligatory data 1 Fixed value CC Yes 2 Shipment # 3 11 CC Yes 3 Parcel # CC Yes 4 Collection address # 25 9 CC Yes 5 Date of collection 34 8 KD Yes 6 Delivery date 42 8 KD No 7 Collection depot 50 3 CC Yes 8 Delivery depot 53 3 CC Yes 9 blank 56 6 AN 10 Delivery address # 62 4 CC Yes 11 blank 66 9 AN 12 Name of company/ person AN Yes 13 Contact person name AN No** 14 blank AN 15 Recipient s street AN Yes 16 Recipient s country AN Yes 17 Recipient s post code AN Yes 18 Recipient s city AN Yes 19 Weight CC Yes 20 Supplementary services denomination CC Yes 21 Card payment CC Yes 22 blank AN 23 COD value FP Yes* 24 Pickup point code AN Yes* 25 blank AN 26 Variable symbol AN Yes* 27 blank AN 28 Number of parcels per shipment CC Yes 29 References AN No 30 blank AN 31 Phone notification/private address TC Yes* 32 Insurance FP Yes* 33 Remark for driver AN No 34 Remark for consignee AN No 35 blank AN 36 Notification of problematic shipment AN/TC No 37 Notification of delivered shipment AN/TC No 38 Notification of damaged shipments AN/TC No 39 POD service AN No 40 SMS notification of the shipment s dispatch ;; TC No * This data is obligatory only in case when the block supplementary services denomination includes a related service or a service is required. ** CAUTION: This data is obligatory if the shipment goes to pickup point. Table 4: Records structure in a parcel export file. 18

27 GEIS Group 2.2 EDI format specification Service name Abbreviation Position Length Value Specification in the block No. 20 Ex Works EXW / Cash on delivery COD / Delivery until 12 o clock D / Guaranteed delivery GAR / Insurance POJ / Private address B2C / Pickup point VM / Table 5: Denomination of supplementary services in the parcel export file. Specifying the phone number in the respective data block for service of the type of notification and POD services that are not entered immediately in the block Denomination of supplementary services means that the service is required for the shipment. Should the respective block be empty, the service is not required. In case of the service card payment (CDR), enter the value 0 - the possibility of card payment is not required or 1 - the possibility of card payment is required. The availability of supplementary services in individual countries and for various transportation operation types is given in the section 2.5. The attached ZIP archive in the directory Parcel includes an example of an export file Parcel Data CTST108c.001 that complies with the handover protocol provided in the annex Parcel Handover Protocol. The file includes five parcels. Two parcels are included to a combined shipment and the remaining three parcels are individual shipments. Caution: The use of supplementary services is subject to agreement between the client and the sales manager of Geis Parcel, for the current terms and conditions of the use of the services see the General Business Terms and Conditions of Geis Parcel Export file denomination convention The parcel export file number consists of several parts: xxx, dd, m a yyy. Their position in the file name is as follows: Cxxx1ddm.yyy xxx an assigned three digit clients ID. It may include digits and alphabet characters. dd day when the file was exported (sent to Geis Parcel CZ s.r.o.). m month when the file was exported. Months are coded using alphabet letters (January a, February b, March c etc. to December l). yyy export file suffix. Should the dates be sent once a day, only or after at last 30 minutes, it is always possible to send the file with the suffix 001. Otherwise, it will 19

28 GEIS Group 2.2 EDI format specification be necessary to make sure that the suffix number grows by one with each sent file (i.e. 001, max. 999 files per day). Example: The name of the parcel export file sent on March 2 by the client is ID 565: C565102c.001 Caution: The name of the file C565102c.001 a C565102c.001.txt is not the same. Caution: No mass shipment may be divided to several files (e.g. between *.001 a *.002). Export files sent later in a single day (e.g. the file C565102c.002 or C565102c.003 etc.) may, but need not necessarily, contain records for parcels exported in previous file sin the same day. That means that data exported in the file C565102c.001 need not be contained in files C565102c.002 and C565102c.003. If the exported records are contained again in follow up files and shipment data differs (e.g. another recipient), such records will not be imported/updated any further. 20

29 GEIS Group 2.3 Handover protocol structure 2.3 Handover protocol structure The handover protocol serves as a confirmation on the takeover of shipment for transport and it has precisely specified layout of individual parts. It is to be produced in two copies one for the driver and one for the sender. The annex Parcel Handover Protocol at the end of the document includes a preview check it thoroughly. The protocol has the following obligatory parts 6. Contact to the sender: The full address of the client has to be filled in the left-hand upper corner. It is recommended to include the phone contact at this place, but it is not obligatory. Collection date: In the centre of the upper part of the sheet there should be the below specified shipments collection date specified that is identical to the date given in the export file. Contact to the depot: In the upper right-hand corner, there should be the logo, address and phone contact to the collection depot. For the contact to the collection depot go to after striking the link Balíkové přepravy. For the logo go to the attached Logo ZIP archive in the directory loga. Number of pages: Each page of the protocol has to include the page number and the total number of pages. List of parcels: In the central part, there is a list of all parcels received for shipment. The parcels have to carry the following data: ˆ Position a value specifying the order of the parcel in the protocol. The initial value is 1 and it grows by 1 for each parcel. ˆ Parcel number this way marked field has to contain the parcel number (see the section 1.3), check digit (see the section 1.4) and the bar code (see 2.3.1). ˆ Addressee the address of the parcel recipient (including the country code). If the service VM is used, will be used pickup point address. ˆ Insurance value (amount) of the insurance provided the specific parcel is insured. ˆ EXW this field includes the text Yes, if the costs of the parcel delivery are to be paid by the recipient. In case of a mass shipment, where the delivery costs are paid by the recipient the word Yes has to be given for each parcel. The column is obligatory even when the client does not use the service Ex Works. 6 All data given in the handover protocol preview as annexed are obligatory. 21

30 GEIS Group 2.3 Handover protocol structure ˆ Cash on delivery (COD) a value (amount) of the cash if the parcel is to be delivered against cash payment upon delivery. The cash on delivery amount is always specified in the currency of the country with the accuracy of two decimal points (hellers, cents etc.). In case of a COD mass shipment, the total amount of cash to be paid upon delivery is to be specified for the superior parcel of the shipment (i.e. the parcel with identical parcel and shipment number). It must not be specified for other parcels so that the total sum could match. ˆ Variable symbol a payment identifier (it consists of digits, only). It is an obligatory item for COD. It may be specified for superior parcels, only, in case of combined shipments. If specified for non-cod shipments, it is not transmitted for the shipment. ˆ Note fill in the text of the remark for the driver. The same text is given also in the record for the corresponding parcel in the export file (see the block No. 32 in the table 4 Structure of Records in the Parcel Export File ). Total number of files: The total number of files is to be specified below the list of parcels at the left-hand edge. Total COD sum: The total sum of COD is to be provided below the parcel table at the column position Cash on delivery (COD). If the protocol includes COD parcels to several countries, the sum of COD amount is only numeric (i.e. add only EUR and CZK without the conversion to a common currency). Signatures: : The bottom part of the protocol has to include signatures of the driver and the sender together with the text: The above shipments were delivered without any damage. Footing: The footing text is given in the preview in the annex Parcel Handover Protocol. Caution: The text of the footing in the parcel protocol differs from the cargo protocol. Combined (mass) shipments are not highlighted in the handover protocol in any way Bar code The bar code is to be provided on the handover protocol, it includes the parcel number including the check digit (see 1.4 Check digit ). The bar code is subject to the standard Interleaved 2 of 5 (referred to as I2/5, too). If, for example, the parcel number is and the check digit is 2, the bar code will represent the number Bar code readability When preparing the protocol, measures have to be taken to keep the bar codes readable. The figure 3, left-hand side, shows as example of unreadable bar code (the code is too 22

31 GEIS Group 2.3 Handover protocol structure narrow). The bar code will always be readable when its width is at last 3.5 cm, see the example at the right-hand side. Also the distance between the bar code and the table grid is to be at least 2 mm. Figure 3: Example unreadable (left) and correct (right) bar code 23

32 GEIS Group 2.4 Label printing specification 2.4 Label printing specification Every parcel shall be provided with a label according to the general business terms and conditions representing offered transport services (for service details see the section 2.5). A printer supporting EPL language is recommended for the printing of labels. The labels may be printed using a laser printer, too. However, the output must match below specified parameters (size, content, legible bar codes etc.). The ZIP archive attached to this manual includes a template (in the directory Parcel file Parcel Label EPL.txt)for the printing with an EPL printer with the printing head resolution of 203dpi. In the template, just replace the expressions %%VAR NAME%% with actual values specified for given parcels. What is available in the file EPL2 Programming Manual.pdf 7 is the EPL2 language manual use for the preparation of the template. The following figure 4 shows the layout of the content on the label with explanatory notes given in the list behind it. In the template we have defined texts are printed without diacritics and therefore it is necessary to enter text chains without diacritics. The diacritics support is possible when defining the template itself, see the attached EDP manual. 1. The logo is available in the attached archive file loga/geis.pcx. In the template for the EPL printer is its printing provided for by the setting GG630,20,"geis" on the line 63. The logo has to be uploaded to the printer, only after that it may be printed. In the attached archive in the directory loga you will find the file Geis logo printer.zip with the instruction describing how to upload the logo to the EPL printer. data. 2. Address and contact of the collection depot. For this information go to after striking the link Balíkové přepravy. Replace the following expression with adequate values in the template. %%SEND DEPOT STREET%% on the line 93 street, %%SEND DEPOT POSTALCODE%% on the line 94 Post code, %%SEND DEPOT CITY%% on the line 94 city, %%SEND DEPOT PHONE%% on the line 95 phone number, %%SEND DEPOT FAX%% on the line 96 phone number for FAX. 3. Service identification strip. If no supplementary transport services are required for the parcel, the strip is to be left blank (see the model label in the picture 8 in the annex to the manual). Otherwise black backlighted service abbreviations are provided in the strip divided by comma (see the model label in the figure 10 in the 7 The manual needs not be studied as it has been attached for those who wish to get insight in printed 24

33 GEIS Group 2.4 Label printing specification 154cm f Geis4Parcel4CZ4s.r.o. U4Cementárny41183, Ostrava y Tel.: Fax: mm 554mm 6 104cm u Prijemce: FirmajABCjsErEoE JanjNovak fu Lidickaj9u Ejpovice CZjjjjuu7Of f- Pozn:jtextjprojprijemce fm Tel:js-yO9Mffyufyu Odesilatel: f8 NazevjfirmyjsErEoE NejakajulEj9My CZjjjj7u8OyjFrydekdMistek Tel:js-yOuMMOOO7MM f9 f7 KS:fZf f6 VS:jfyffOf798 77O9OOfOOy- M yo yofu mm - M 454mm fueoueyofufo fjkgff uu7offy 9 Figure 4: Label layout for parcel 25

34 GEIS Group 2.4 Label printing specification annex to the manual). They are to be shown only for the following services: Phone notification ( AVI ), Cash on delivery ( COD ), Delivery until 12 o clock ( D12 ), Delivery to a natural person ( B2C ), Ex Works ( EXW ), Guaranteed delivery ( GAR ) and Pickup point ( VM-1234 ). For a more detail description of service see the section 2.5. In the printing template, replace the expression %%SERVICES%% on the line 75 with a text that specified required services (e.g., for the label given in the figure 10 the line 75 will read B2C,COD,EXW). 4. Parcel No. What is to be given at this position is the 11 digit number of the parcel (see the section 1.3 Numeric series ). Replace the line 123 in the printing template the expression %%TRANSPORT ID%% with it. 5. Check digit. A parcel number check digit (see the section 1.4 Check digit ). is given at this place. In the printing template replace the expression %%TRANSPORT CHKSUM%% on the line 124 with it. 6. Parcel number bar code. The bar code is subject to the standard Interleaved 2 of 5 and it contains both the parcel number and the check digit (i.e. a 12 digit number) Replace in the printing template the following expressions with adequate values and the bar code will be generated automatically when printing. %%TRANSPORT ID%% na řádku 100 parcel number, %%TRANSPORT CHKSUM%% také na řádku 100 check digit. 7. Delivery depot number. Fill in the number of the depot that will deliver the given parcel (shipment) to the recipient. It may be found based on the post code of the recipient (see the section 1.5 Routing ). Replace in the printing template the expression %%DEPOT%% on the line 118 with a value taken from the routing table. 8. Delivery route number. The number of the delivery route is to be found based on the post code of the recipient (see the section 1.5 Routing ). Replace in the printing template the expression %%ROUTE%% on the line 120 with value taken from the routing table. 9. Route number bar code. The bar code is subject to the standard Code 39 and it contains the number of the delivery route. Replace in the printing template the expression %%ROUTE%% on the line 120 (see the point 8 of this list) and the bar code will be generated automatically when printing. 10. Collection date. The parcel collection date to our depot is to be filled in at this place. In the template replace the expression %%LOAD%% on the line 117 with the adequate date in the format DD.MM.YYYY. 11. Parcel weight. If not weighed, the parcel value will be specified as 1 kg. In the template replace the expression %%PACKEGE WEIGHT%% on the line 122 with the actual value. 26

35 GEIS Group 2.4 Label printing specification 12. Post code of the recipient. Here specify the post code of the recipient. If the service VM is used, will be used post code of pickup point. In the template replace the expression %%RECIPIENT POSTALCODE%% on the line 121 with adequate post code (without any spaces). 13. Recipient s address. If the service VM is used, will be used pickup point address, only the contact person will be recipient. Replace the following expression with adequate values in the template. %%RECIPIENT NAME%% on the line 111 juridical/natural person s name, %%RECIPIENT PERSON%% on the line 112 contact person s name, %%RECIPIENT STREET%% on the line 113 recipient s street, %%RECIPIENT CITY%% on the line 115 recipient s city, %%RECIPIENT STATE%% on the line 126 country code (for all values valid for the shipment parcel see the annex Country Code Table subject to ISO-3166 ), %%RECIPIENT POSTALCODE%%on the line 114 post code with the same value as given in the item Remark for the recipient. Here fill in the remark for the recipient identical to the text of the in the block Remark for the recipient in the export file. If the service VM is used, will be in note recpient s address (Address, City, Post code). Replace in the template the expression %%NOTE RCPT%% on the line 143 with corresponding text. 15. Recipient s phone number. This data is not obligatory, nevertheless it is recommended to be filled in. Otherwise, phone number is obligatory for services B2C, AVI and VM. In template replace the expression %%RECIPIENT PERSON PHONE%% on the line 128 with the corresponding value, if the service VM is used, it will be used phone number of real recipient. 16. Variable symbol. This data is obligatory for COD parcels. In the template replace the expression %%VS%% on the line 110 with the corresponding number. 17. Parcel order. Fill in information on the order of the parcel and the total number of parcel included to the shipment. Replace the following expression with adequate values in the template. %%PACKAGE NR%% on the line 146 order of the package in the shipment, %%PACKEGE COUNT%% also on the line 146 number of packages in the shipment. Both pieces of data have to be separated by a slash ( / ). A shipment containing one only parcel shall have the resulting value 1/1. A mass shipment containing several parcels (e.g. 3) to a single recipient shall have on individual labels 1/3, 2/3 and 3/3. 27

36 GEIS Group 2.4 Label printing specification 18. Sender s address. Replace the following expression with adequate values in the template. %%SENDER NAME%% on the line 105 sender s company name, %%SENDER STREET%% on the line 107 street, %%SENDER STATE%% on the line 108 country code, %%SENDER POSTALCODE%% also on the line 108 Post code, %%SENDER CITY%% also on the line 108 city. 19. Sender s phone number. This data is not obligatory, nevertheless it is recommended to be filled in. In template replace the expression %%SENDER PERSON PHONE%% on the line 145 with the corresponding value. All data on the label have to agree with data given in the export file and in the handover protocol. 28

37 GEIS Group 2.5 Shipment parcel transport services 2.5 Shipment parcel transport services In this section, there is a brief description 8 of all supplementary services provided in connection with the transport of parcel shipments. Information is included for individual services whether they are not incompatible with other services, how they are to be marked on labels and how they are to be referred to in export data. The use of supplementary services is subject to agreement between the client and the sales manager of Geis Parcel. The availability of individual services differs for Czech and Slovak clients. The availability of services also differs in the dependence on the type of the transport according to the destination country of the shipment recipient - for explanation see the section Service CZ - Inland CZ - Export SK - Inland SK - Export EXW Yes COD Yes SK only Yes CZ and HU only B2C Yes SK only Yes CZ only SMS Yes Yes AVI Yes Yes GAR Yes Yes POJ Yes Yes Yes Yes D12 Yes Yes ADZ Yes Yes APZ Yes Yes POD Yes Yes CZ only CDR Yes SK only Yes CZ only VM Yes Table 6: Accessibility of services by type of transport - parcel Notification on the delivery of the shipment ADZ The notification is sent by or SMS and confirms the successful delivery of the shipment. The address or phone number to which the information is to be sent is provided in the export file in the block 37 (see the table 4 in the section 2.2.1). This service is not marked in the handover protocol and labels. Should the shipment be combined, fill in the address or phone number in the export file for all parcels.. This service may be combined with all other services. 8 For the full description of all supplementary transport services see the general Business Terms and Conditions This document contains just their brief definition. 9 In case of chosen export destinations, other supplementary services may be provided above the framework of services specified in this document. For details contact the Geis sales manager. 29

38 GEIS Group 2.5 Shipment parcel transport services POD services This service provides for the automatic dispatch of the confirmed delivery note to the specified address. address is given in the export filein the block 39 (see the table 4 in the section 2.2.1). This service is not marked in the handover protocol and labels. The address is given in the export file for all parcels included to a combined shipment. This service may be combined with all other services, without Pickup point service Notification on a problematic shipment APZ This service resides in the sending of an or SMS containing the information that the shipment could not be delivered or a specific reason. The address or phone number to which the information is to be sent is given in the export file in the block 36 (see the table 4 in the section 2.2.1). This service is not marked in the handover protocol and labels. Should the shipment be combined, fill in the address or phone number in the export file for all parcels. This service may be combined with all other services SMS notification on the dispatch of the shipment SMS This service resides in the sending of a SMS to a specified number. The text of the SMS informs on the fact that the shipment was taken over for delivery. The phone number to which the information is to be sent is given in the export file in the block 40 (seethe table 4in the section 2.2.1). This service is not marked in the handover protocol and labels. Should the shipment be combined, the phone number is given in the export file for the first (superior) parcel, only. This service cannot be combined with the service Delivery to a natural person (B2C service) as in the framework of the B2C service the SMS addressee is sent the notification as a part of the price of the B2C service (to the phone number specified for the B2C service) and Pickup point service. It may be combined with other services Telephonic notification AVI This service resides in the telephonic notification of the time of the arrival to the destination address with the shipment recipient. The phone number is given in the export 30

39 GEIS Group 2.5 Shipment parcel transport services file in the block 31 (see the table 4 in the section 2.2.1). This service is not marked in the handover protocol in any way. On labels, it is marked using text AVI in the service strip (for details see the section 2.4 Label Print Specifications ). In case of a combined shipment, the phone number is given in the export file only for the first (superior) parcel. The denomination AVI is given on labels of all parcels. This service cannot be combined with the service Delivery to a natural person (B2C service) and Pickup point. It may be combined with other services Cash on delivery COD The COD service is to be given in the export file in the block 20 (see the table 5) at records on COD parcels. In addition to the denomination in the block 20, the block 23 has to include the information on the amount of the COD and the block 26 has to include the variable symbol. In case of a combined (mass) shipment, the COD is marked in the export file only for the first parcel. The COD value is given also for the first parcel. On the other hand, the variable symbol has to be given for each parcel included to a combined shipment. What is to be given in the handover protocol is the value of the COD in the COD column and the variable symbol in the column Variable symbol.in case of a combined COD shipment, specify the total COD amount or the shipment at the first shipment parcel; it must not be specified for other parcels in order to match to the sum. The variable symbol is given for all parcels of a combined shipment in the same way as in the export file. Mark the COD on labels by a text COD in service strip. Moreover, the label has to include the variable symbol (for details see the section 2.4 Label Printing Specifications and an example of a label in the figure 9 in the annex to the manual). In case of a combined shipment, mark the COD COD together with the variable symbol on labels of all parcels. This service may be combined with all other services Delivery until 12 o clock D12 This service envisages the delivery of the shipment until 12 o clock of the day following the takeover of the shipment from the sender. This service is given in the export file in the block 20 (see the table 5). In case of a combined shipment, this service is marked in the export file of all parcels. This service is not mentioned in the handover protocol. The service can only be used for particular Post Code range, where the Geis company is able to guarnteed delivery until 12 o clock. The current range of postcode is available at in Balíkové přepravy / Vnitrostátní přeprava / Firemní adresy B2B for national shipments in the Czech Republic. Postcode list for national shipments at 31

40 GEIS Group 2.5 Shipment parcel transport services Slovak territory shall provide the Geis business manager for this service. It is marked using text on labels D12 in the service strip (for details see the section 2.4 Label Printing Specification ). In case of combined shipment, it is to be marked for all parcels. This service cannot be combined with the service Guaranteed delivery, B2C and Pickup point Delivery to a private address B2C This service provides the delivery of shipments to private addresses within the Czech and Slovak Republic. Fill in the export file in the block 20 (see table 5) for parcels to which the service is to be applied. Moreover, in the block 31 fill in the phone number of the recipient. In case of a combined shipment, the export file has to include the denomination of the B2C service and the phone number for all shipments. This service is not mentioned in the handover protocol. Service is marked using text on labels B2C in the service strip (for details see the section 2.4 Label Printing Specification ). It is to be marked for all parcels where the service is specified in the export file. This service cannot be combined with the services SMS notification, Phone notification, Delivery until 12 o clock, Guaranteed delivery and Pickup point Ex Works EXW This service safeguards that the parcel delivery costs will be paid by the recipient. It is to be filled in the export file in the block 20 (see table 5) at records for parcels where the delivery costs are to be paid by the recipient. In case of a combined shipment, this service is to be specified for all parcels. Fill in the handover protocol the text Yes in the EXW column. In case of combined shipment, the word Yes has to be given for all shipment parcels. It is marked using text on labels EXW in the service strip (for details see the section 2.4 Label Printing Specification ). It is to be marked for all parcels where the service is specified in the export file. This service may be combined with all other services, without Pickup point service Guaranteed delivery GAR The delivery including this service means the guaranteed delivery of the shipment on the Czech territory on the day following the collection of the shipment from the sender. Fill 32

41 GEIS Group 2.5 Shipment parcel transport services in the export file in the block 20 (see table 5). In case of a combined shipment, fill in the export file the denomination of the guaranteed delivery for all shipments. This service is not mentioned in the handover protocol. It is marked using text on labels GAR in the service strip (for details see the section 2.4 Label Printing Specification ). It is to be marked for all parcels where the service is specified in the export file. This service cannot be combined with the service Delivery to a natural person (B2C service), Delivery until 12 o clock and Pickup point Insurance POJ The parcel insurance is specified in the export file in the block 20 (see the table 5).In addition to the denomination in the block 20, the insurance value has to be specified in the block 31. In case of a combined shipment, the insurance is specified in the export file only for those parcels that are insured. The insurance value is to be filled in in the handover protocol in the column Insurance. In case of a combined shipment, the insurance has to be referred to for each parcel that has this reference in the export file. This service is not to be marked on labels. This service may be combined with all other services, without Pickup point service Card payment CDR The card payment service is specified in the export file in the block 21 (see table 5). The value 0 means that card payment possibility is not required for the shipment, the value 1 means that the card payment possibility is required. This data block is obligatory and it has to be included to the data file anytime. In case of combined shipment s, it is specified only for the shipment superior parcel (i.e. the parcel that has the same shipment and parcel number). The use of service is subject to previous agreement with the sales manager of Geis. The service is not to be mentioned in the handover protocol and on labels. It makes sense to require this service only in connection with the COD service included to the shipment Pickup point VM This service provides the delivery of shipments to Pickup points addresses within the Czech Republic. Delivery of the shipment on the pickup point can be specified in the data file by sender, but the shipment can be redirected on pickup point by recipient. 33

42 GEIS Group 2.6 Verification parcel This document describe possibility, when delivery of the shipment is specified by sender - customer Geis on the pickup point. More details about service VM are at in section balíkové přepravy - vnitrostátní přeprava - výdejní místa Geispoint. List of pickup points is available at To find pickup point can be used plug-in, via document Geis Point Plugin on support website Fill in the export file in the block 20 (see table 5) for parcels to which the service VM is to be applied. Moreover, in the block 31 fill in the phone number of the recipient and in the block 24 fill pickup point code. The code must have following format: VM-nnnn, VMnnnn or nnnn (where nnnn is pickup point code). This service is not mentioned in the handover protocol. Service conditions: ˆ Shipment must contain only one parcel (musn t be superior parcel) ˆ Shipment s maximum weight can be 15 kg If won t be all data for sevice VM (Recipient, Phone number, Valid Pickup point code), the shipment will be specified without service VM. Recipient s phone number must be present in international format and must be registered within Czech republic (phone number starts with prefix +420). Service is marked using text on labels VM-1234 in the service strip (for details see the section 2.4 Label Printing Specification ). It is to be marked for all parcels where the service is specified in the export file. The use of service is subject to previous agreement with the sales manager of Geis. This service can be combined only with the services COD. 2.6 Verification parcel The correctness (i.e. adherence to the format and consistency of information according to this manual) of export data, handover protocol and labels is the responsibility of the client. When all such underlying documents match the specification described in this document and the data file is successfully checked by the data validator, the client will send their preview by to the respective sales manager of Geis. The sales manager shall handover the underlying documents internally to the Geis IT department and any possible deficiencies shall be communicated immediately with the technical contact of the client. Never send testing data directly to the FTP server! If not specified otherwise, the client s underlying documents are subject to the following requirements: 34

43 GEIS Group 2.6 Verification parcel ˆ They consist of an export file associated with the handover protocol and labels for all parcels. These labels have to be printed on an EPL or laser printer and scanned to be available ideally in the PDF format. ˆ They include at least one combined and one jedno-balíkovou shipment. ˆ They include only shipments with those services (COD, notification etc.) as agreed between the client and Geis sales manager in the framework of the contract with Geis. ˆ They have been checked according to the annex Checklist for Underlying Documents Parcel. Parcel numbers (respectively the numerical series) is to be chosen by the client on random basis. What is important is that the numbers are 11 digit numbers and data in the export files are consistent with data in the handover protocol and on labels. The collection address number to be chosen by the client as an 8 digit number (e.g ). The client s ID for the compilation of the export file name is to be chosen by the client as a three character number (e.g. TST). After the verification of the correctness of testing data, actual identifiers are assigned in the followings cope: ˆ Client s number (eight digit number) ˆ ID of the client (three character, it is added to the file name) ˆ Numeric series (one scope for inland shipments and another for international shipments) What follows is an integration test of sharp data with identifiers assigned to the client by Geis. This test is described in the next chapter. Data integration test The data integration test in the Geis system is executed after the validation of the correctness of all underlying documents and assignment of identifiers. During the test, the client proceeds identically to the procedure of the actual operation (see the section 2.7 Go live ). Thus, the client creates actual shipments in his IS. That means that numbers from the assigned numeric series will be used for the parcels. The export file generated by the client s IS will include the assigned client s number and the client s assigned ID will be integrated to the name of the generated file. The client shall send the export file (see the section 2.7 Go live ). to the Geis FTP server. Moreover, he will send to the Geis sales manager and IT department numbers of all 35

44 GEIS Group 2.7 Go live parcels from this export parcel by . Thus, the shipment will be actual, nevertheless only in terms of data as they will not be dispatched physically. Numbers that could not be used for testing parcels cannot be used again any further in future for other parcels! 2.7 Go live What is optimal during the go live procedure is to send the export file when printing the handover protocol (it may be automated), however, no later than immediately after the departure of our collection vehicle to our depot. What is important is to import data to our IS no later than at the moment when the collection vehicle arrives to the depot. The export file may be sent either to the FTP server or to the address We prefer the FTP, is a backup solution in case the FTP server failed for any reason whatsoever. Below see the addresses and login data. FTP server: User: Password: Directory: ftp1.geis.cz ftp objednavky ftp194obj objednavky data@geis.cz What is anticipated is the sending of a single file per day, but as shown in the section 2.2.2, it is possible to send more files. 36

45 GEIS Group 3. Cargo 3 Cargo This part of the manual describes all requisites concerning the clients integration who make use of our services of the palette (cargo) shipments. 3.1 EDI format specification What is used for the import of data on the transport of cargo shipments to our IS is the electronic exchange of structured text files in the logistic format of the electronic data exchange system KDDS128, coding windows The data transmission file has the structure of records. Each record has its own meaning, individual records are described in the figure 6. The structure of the export file with shown data records is given in the figure 5. 37

46 GEIS Group 3.1 EDI format specification Figure 5: Scheme records in the format KDDS128 38

47 GEIS Group 3.1 EDI format specification Figure 6: Description of records in the format KDDS Records structure Below see the data structure of individual records of the data file KDDS128. The records order has to be preserved (see the scheme in the figures 5 and 6) and all obligatory records for each shipment have to be included. The heading record (A) and summary record (L) are included to each data file once, only. Note to the F record: The F record may include loading items of the shipment either in the form 1 line = 1 shipment item (i.e. without the grouping to handling units) or in the form of 1 line = n items of the shipment of the same handling unit (i.e. grouping in handling units). The frequency of the occurrence of the F records for one shipment depends on the chosen grouping method. Example: Let s have a shipment consisting of 2 items of a handling unit EUR palette (FP) of the total weight of 150 kg and 3 items of the handling unit Barrel (FA) of the total weight of 90 kg, thus, this shipment consists of 5 loading items including two various handling units. ˆ Should the handling items be grouped based on handling units, the F record of this shipment will be given twice: once for the handling unit FP (in the F record data, there will be the number of items = 2, weight = 150) and once for the handling unit FA (in the F record data, there will be the number of items = 3, weight = 90). ˆ Should the loading items be not grouped based on handling units, the F record of this shipment will be given five times: twice for the handling unit FP (each F record will include in the data the number of items = 1, weight = actual weight of the given item or 75) and three times for the handling unit FA (each F record data will include the number of items = 1, weight = actual weight of the given item or 30). 39

48 GEIS Group 3.1 EDI format specification Record A transmission heading (once in the data transmission) obligatory # Name Position Length Data type Remark 1 Fixed value A 1 1 AN Fixed A 2 Fixed value CC Fixed Transmission No AN Unique number of the EDI transmission 4 File date 23 6 KD Date of the creation of EDI data (format DDMMYY) 5 Transport mode 29 1 AN Fixed L 6 Blank 30 2 AN 7 Payer s number CP Assigned by GEIS 8 Blank AN 9 Electronic data CC Fixed 1 Record B data on the sender 1 (for each shipment) obligatory # Name Position Length Data type Remark 1 Fixed value B 1 1 AN Fixed B 2 Position in the transmission 2 3 CC Serial number in the data file 3 Name AN Company name / sender s name 4 Name AN Addition to the sender s name 5 Street ad number AN Sender s street including building number 6 Country code AN Sender s country code 7 Post Code CP Sender s post code (without spaces) Record C data of the sender 2 (for each shipment) obligatory # Name Position Length Data type Remark 1 Fixed value C 1 1 AN Fixed C 2 Position in the transmission 2 3 CC Serial number in the data file 3 City 5 35 AN Sender s city 4 Blank AN 5 Variable symbol CL Variable symbol for a COD shipment* 6 Client s number CP Assigned by GEIS * Should the shipment be a COD shipment, this data is obligatory If given for non-cod shipments, the data is not transmitted for the shipment Record D data of the recipient 1 (for each shipment) obligatory # Name Position Length Data type Remark 1 Fixed value D 1 1 AN Fixed D 2 Position in the transmission 2 3 CC Serial number in the data file 3 Name AN Company name / recipient name 4 Name AN Addition to the recipient s name 40

49 GEIS Group 3.1 EDI format specification Record E data of the recipient 2 (for each shipment) obligatory # Name Position Length Data type Remark 1 Fixed value E 1 1 AN Fixed E 2 Position in the transmission 2 3 CC Serial number in the data file 3 Street ad number 5 35 AN Recipient s street including building number 4 Country code 40 3 AN Recipient s country code* 5 Post Code 43 9 CP Recipient s post code (without spaces) 6 City AN Recipient s city * values valid for cargo shipments re given in the annex uvtables of Country Codes subject to ISO-3166 Record F data on shipment items (for each used handling unit in the shipment) obligatory # Name Position Length Data type Remark 1 Fixed value F 1 1 AN Fixed F 2 Position in the transmission 2 3 CC Serial number in the data file 3 Number of items 5 4 CC Number of loading items of the same handling unit 4 MJ code 9 2 AN Handling unit code* 5 Blank 11 6 AN 6 Goods description AN Description of the shipment content (it may be given using for instance the handling unit code) 7 References AN Reference (visible on the invoice and delivery note) 8 Weight 57 5 CP Weight of all items in kg in the given F record** * MJ = handling unit, e.g. KT cardboard crate, FP EUR palette etc. For a list of permitted handling units see the end of this document. ** Sum of the weight of all loading items from the same MJ as specified in the given F record. 41

50 GEIS Group 3.1 EDI format specification I record shipment summary data (for each shipment) obligatory # Name Position Length Data type Remark 1 Fixed value I 1 1 AN Fixed I 2 Position in the transmission 2 3 CC Serial number in the data file 3 Shipment # 5 16 CS Number from the assigned scope (+ 000 at the end) 4 Weight 21 5 CP Weight in kg of all shipment items 5 Blank 26 5 AN 6 Volume 31 5 CC Shipment volume in dm3 7 Blank 36 7 AN 8 Delivery terms 43 2 CC Code 30 (DAP), 20 (EXW) 9 Blank 45 2 AN 10 Service CC Service code (for services in the regime Service 1) 11 Term delivery time 49 4 KC Delivery time HHMM (for DTR services, only) 12 Blank AN 13 Term delivery date 79 6 KD Delivery date DDMMYY (for DTR services, only) 14 Service CC Service code (for services in the regime Service 2) 15 Phone number service TC Phone number for regime 2 services 16 Service CC Service code (for service in the service 3 regime) Record J supplementary data on the shipment (for each shipment) optional # Name Position Length Data type Remark 1 Fixed value J 1 1 AN Fixed J 2 Position in the transmission 2 3 CC Serial number in the data file 3 Remark for consignee 5 62 AN Remark on the delivery note (it may be used instead of delivery note) 4 Remark for driver AN Remark on the delivery note (it may be used instead of delivery note) Record K shipment COD (for each shipment) obligatory for COD # Name Position Length Data type Remark 1 Fixed value K 1 1 AN Fixed K 2 Position in the transmission 2 3 CC Serial number in the data file 3 Blank 5 18 AN 4 COD value 23 9 CC COD values in hellers (cents) 5 Blank AN 6 COD currency 74 3 AN COD currency code (CZK or EUR) 42

51 GEIS Group 3.1 EDI format specification Record L transmission check sums (once in the data transmission) obligatory # Name Position Length Data type Remark 1 Fixed value L 1 1 AN Fixed L 2 Fixed value CC Fixně Total number of shipmentted 5 5 CC Number of shipments transmit- in the data file 4 Total number of items 10 5 CC Sum of all items in shipments 5 Total weight 15 5 CC Weight of all shipments in kg 6 Blank AN 7 Total CODs 38 9 CC Sum of all CODs in hellers 8 Blank AN 9 Number of MJs of the FP 71 3 CC Number of MJ items of the FP type See the attached ZIP archive in the directory Cargo for an example of the export file Cargo Data ftp txt that is in compliance with the handover protocol available in the annex Cargo Handover Protocol. The file includes five shipments with three various handling units. 43

52 GEIS Group 3.1 EDI format specification Convention regulating the process of assigning of names to export files The name of the cargo export file consists of several parts: ftp, nnnnnnnn and txt. Their position in the file name is as follows: ftpnnnnnnnn.txt ftp fixed letters ftp. nnnnnnnn client s number. The client s number may have max. eight digits and it is assigned by Geis after the verification of the data correctness, see the section 3.5. Should the number have less than 8 positions, nothing else will be added to the file s name. txt suffix to the export file, fixed txt. Example: Name of the cargo export file sent by the client with the assigned number : ftp txt Example: Named of the cargo export file sent by the client with assigned number : ftp txt 44

53 GEIS Group 3.2 Handover protocol structure 3.2 Handover protocol structure The handover protocol serves as a confirmation on the takeover of shipment for transport and it has precisely specified layout of individual parts. It is to be produced in two copies one for the driver and one for the sender. At the end of the document attached to the Cargo handover Protocol there is a preview check it thoroughly. The protocol has the following obligatory parts 10. Contact to the sender: The full address of the client has to be filled in the left-hand upper corner. It is recommended to include the phone contact at this place, but it is not obligatory. Collection date: In the centre of the upper part of the sheet there should be the below specified shipments collection date specified that is identical to the date given in the export file. Contact to the depot: In the upper right-hand corner, there should be the logo, address and phone contact to the collection depot. Find the contact to your collection depot at striking the link Paletové přepravy. For the logo go to the attached ZIP archive in the directory loga. Number of pages: Each page of the protocol has to include the page number and the total number of pages. List of shipments: The list of all shipments handed over for delivery is provide din the central part. The following data shall be given for the shipments: ˆ Position a value specifying the order of the shipment in the protocol. The initial value is 1 and it gradually grows for each other shipment. ˆ Shipment number this way marked field has to contain the shipment number (see the section 1.3). ˆ Recipient, contact address of the shipment recipient (including the country code). ˆ Items number of items per shipment. ˆ Weight total shipment weight in kg. ˆ EXW this field includes the text Yes if costs of the shipment delivery are to be paid by the recipient. The column is obligatory even when the client does not use the service Ex Works. ˆ Cash on delivery (COD) a value (amount) of the COD if the shipment is COD. The cash on delivery amount is always specified in the currency of the country with the accuracy of two decimal points (hellers, cents etc.). ˆ Reference a client s reference, for instance the order number. This field serves mainly to senders who may fill in here their shipments registration numbers according to which they can trace the shipments. Enumeration of handling units: Below the list of shipments, at left hand edge, there is an enumeration and number of handling units. Total number of items: Below the enumeration of shipments at the Ks column position, there is the total number of items to be filled in. Total weight: : The total weight of all shipments in kg is to be filled in below the enumeration of shipments at the position of the column Weight. Total COD sum: The total COD sum is to be provided below the enumeration of shipments at the position of the column Cash on delivery (COD). Should the protocol include COD shipments to be delivered to several countries, the sum of CODs is only numeric (i.e. EUR and CTZK are added without conversion to a common currency). 10 All data given in the handover protocol preview as annexed are obligatory. 45

54 GEIS Group 3.3 Label printing specification Signatures: The bottom part of the protocol has to include signatures of the driver and the sender together with the text: The above shipments were delivered without any damage. Footing: The footing text is given in the preview in the annex Cargo Handover Protocol. Caution: The footing text in the cargo protocol differs from the parcel protocol. 3.3 Label printing specification Each shipment shall be provided with a label according to the general business terms and conditions. What is recommended for the printing of labels is a printer supporting the EPL language or labels may be printed using a laser printer. However, the output must match below specified parameters (size, content, legible bar codes etc.). The ZIP archive attached to this manual includes a template (in the directory Cargo file Cargo Label EPL.txt) for the printing using the EPL printer with the printer head resolution 203dpi. In the template just replace expressions %%VAR NAME%% with actual values for given shipments. What is also available in the file EPL2 Programming Manual.pdf 11 is the EPL2 language manual where the template was created. The figure 7 shows the layout of the content on the label and in the list behind it, there are explanatory notes provided. The template defined by us is used for the printing of text without diacritics, therefore enter text chains without any diacritics. When defining an own template, the diacritics support is possible, see the attached EPL manual. 60pmm 10pcm P PjjczzzzzpcPjyyzj p KOLLI: jip AbsenderiOdesilatel: Nazevyfirmyysdrdod Nejakayuldy9cu PuRyzzyPlzen Tel:yCpuzPEEjuPpcR EmpfangeriPrijemce: Novakylysynysdrdod JosefyNovak Tel:yCpuzc9R9gERcp je StrmayjpEuiuE CZyyEzczzyyOstrava E p jr c jp jc R 15pmm GeispCZps.r.o. Zemskap211/I 337p01pEjpovice Tel.:p+420p951p220p521 Fax:p+420p951p220p109 jj VS:y9gERcpPujz Ref:yreferenceyodesilatele jp Pozn:ypoznamkayproyprijemce u DATUM:yyyRdjuduzjP CZEz 9 EzzP j jz g CZyyEzczz ju 15pcm Figure 7: Label layout for cargo 11 The manual needs not be studied as it has been attached for those who wish to get insight in printed data. 46

55 GEIS Group 3.3 Label printing specification 1. The logo is available in the attached archive file loga/geis.pcx. In the template for the ELP language printer its printing is safeguarded by the setting GG15,50,V27 on the line 71 (and the V27 variable value is "geis"). The logo has to be uploaded to the printer, only after that it may be printed. See the attached archive and the directory loga soubor Geis logo printer.zip where you find the instruction how to upload the logo to the EPL printer. 2. Address and contact of the collection depot. For this information go to after striking the link Paletové přepravy. Replace the following expression with adequate values in the template. %%SEND DEPOT STREET%% on line 125 street, %%SEND DEPOT POSTALCODE%% on the line 126 post code, %%SEND DEPOT CITY%% on the line 127 city, %%SEND DEPOT PHONE%% on the line 128 phone number, %%SEND DEPOT FAX%% on the line 129 phone number for FAX. 3. Shipment number bar code. What is used for the bar code is the standard Interleaved 2 of 5 and it includes both the shipment number 13 characters) and the serial number of the loading item (2 characters)and the check digit (1 character, altogether a 16 character number). In the printing template replace the following expressions with corresponding values and the bard code will be generated automatically when printing. %%TRANSPORT ID%% on the line 106 shipment number, %%PACKAGE NR0%% on the line 106 parcel number, %%TRANSPORT CHKSUM%% also on the line 106 check digit. 4. Shipment number. What is be filled in to this position is a 13 digit number of the shipment (see 1.3 Numeric series ). Replace with it the expression %%TRANSPORT ID%% in the printing template on the line Loading item number. What is to be filled in this position is the serial number of the loading item (palette, cardboard crate, bag, can... ). The shipment may be com posed of max. 99 loading items. The loading item number is entered including the initial zero (e.g. 03) so that the number could always have two digits. Replace with it the expression %% PACKAGE NR0%% in the printing template on the line Check digit. What is to be filled in at this place is the check digit for the shipment number (see 1.4 Check digit ). Replace with it the expression %%TRANSPORT CHKSUM%% in the printing template on the line The order (number) of the loading item (so called kolli ). Information on the order of the given loading item and total number of loading items included to the shipment is to be provided here. Replace in the printing template the following expressions with corresponding values. %%PACKAGE NR%% on the line 108 items order in the shipment, %%PACKEGE COUNT%% also on the line 108 number of items in the shipment. oth pieces of data have to be separated by a slash ( / ). The resulting value of a shipment with one only loading item will be 1/1. Shipments with several loading items (e.g. 3) will have on individual labels the values 1/3, 2/3 and 3/3. 8. Collection date Fill in the date of the shipment collection to our depot at this place. Replace in the template the expression %%LOAD%% on the line 107 with the adequate date in the format DD.MM.YYYY. 47

56 GEIS Group 3.3 Label printing specification 9. Denomination of the delivery depot. The denomination may be found out from the post code of the recipient (according to routing tables, see the section 1.5 Routing ). The denomination consists of the country code (2 positions) and depot number (2 positions without the initial zero). The country code is always CZ, only if the shipment is sent to a recipient from the following countries: SK, RO, MJ, the country code will be SK. Example 1: The sender is in the Czech Republic. The recipient s post code is and the recipient s country is CZ. Thus, it is an inland shipment. It may be found in the routing table Cargo PSC CZ Vnitro.txt that the scope covering the specified post code matches the following record: NT061CZ Thus, the depot number is 061, the country code is CZ. In order to create the depot denomination data, let s skip the initial zero in the depot number and compose both pieces of data in the following order: country code, depot code: CZ61 Example 2: The sender is in the Czech Republic, the recipient s post code is and the recipient s country is MJ. It is an international shipment. It may be found in the routing table Cargo PSC CZ Export.txt that the scope and country covering the specified post code matches the following record: NT083HU SK Thus, the depot number is 083, the country code in this case is SK (because the recipient is in one of the countries SK, RO, MJ). In order to create the depot denomination data, let s skip the initial zero in the depot number and compose both pieces of data in the following order: country code, depot code: SK83 Example 3: The sender is in the Czech Republic, the recipients post code is and the recipient s country is DE. It is an international shipment. It may be found in the routing table Cargo PSC CZ Export.txt that the scope and country covering the specified post code matches the following record: NT041DE CZ Thus, the depot number is 041, the country code is in this case CZ. In order to create the depot denomination data, let s skip the initial zero in the depot number and compose both pieces of data in the following order: country code, depot code: CZ41 Replace in the printing template the expression %%DEPOT%% on the line 113 with the value defined using the above described procedure. 10. Delivery route number. This number may be found based on the post code of the recipient s (see the section 1.5 Routing ). For the post code of the recipient as given in the example 1 above the delivery route number will be 6119 For the post code of the recipient as given in the example 2 above the delivery route number will be SK83 For the post code of the recipient as given in the example 3 above the delivery route number will be CZ41 Replace in the printing template the expression %%ROUTE%% on the line 116 with the value taken from the routing table. 11. Recipient s country. Fill in the recipient s country. The value has to be the same as the value of the country as given in the point No. 17 (recipient s address). In the printing template replace the expression %%RECIPIENT STATE%% on the line Post code of the recipient. Fill in the recipient s post code. The value has to be the same as the post code value given in the pint No. 17 (recipient s address). The post code is to be entered without spaces. Replace in the printing template the expression %%RECIPIENT POSTALCODE%% on the line

57 GEIS Group 3.3 Label printing specification 13. Variable symbol. This data is obligatory for COD shipments. Replace in the template the expression %%VS%% on the line 124 with the corresponding number. 14. References. This data is used for later identification of the shipment by the sender, the value filled in is identical to the text as in the block References in the export file. Replace in the template the expression %%REFERENCE%% on the line 118 with corresponding text. 15. Remark for the recipient. Here fill in remarks for the recipient identical to the text as in the block remark for recipient in the export file. Replace in the template the expression %%NOTE RCPT%% on the line 119 with adequate text. 16. Sender s address. Replace in the printing template the following expressions with adequate values. %%SENDER NAME%% on the line 98 sender s company name, %%SENDER STREET%% on the line 99 sender s street including the descriptive and/or orientation number (e.g. Modřínová 1740/6, where 1740 is the descriptive number. Or Jasanová 8, if only the orientation number is given), %%SENDER POSTALCODE%% on the line 100 sender s post code, %%SENDER CITY%% also on the line 100 senders city. 17. Recipient s address Replace in the printing template the following expressions with adequate values. %%RECIPIENT NAME%% on the line 101 company name (in the export file, block Name 1), %%RECIPIENT PERSON%% on the line 121 contact person name (in the export file of the block Name 2), %%RECIPIENT STREET%% on the line 102 recipient s street including the descriptive and/or orientation number (e.g. Modřínová 1740/6, where 1740 is the descriptive number). Or Jasanová 8, if only the orientation number is given), %%RECIPIENT CITY%% on the line 103 recipients city, %%RECIPIENT STATE%% on the line 104 country code (valid cargo shipment conventions are given in the annex Table of Country Codes subject to ISO-3166 ), with the same value as in the point 11 (of course, it will suffice to enter the value once, only), %%RECIPIENT POSTALCODE%% on the line 105 post code with the same value as in the point 12 (of course, it will suffice to enter the value once, only). All data given on the label has to be identical to data given in the export file and in the handover protocol. 49

58 GEIS Group 3.4 Transport services for cargo shipments 3.4 Transport services for cargo shipments This section describes supplementary services provided together with cargo transport services. The use of supplementary services has to be contracted in advance with Geis. The method of specification in export data is given for individual services. For detailed specifications of supplementary services contact the Geis sales manager. Name of service Abbreviation Mode Record Position Service code EXW (Payment by the recipient) EXW I 43 Cash on delivery COD K 23 Specified delivery time DTR Service 1 I DL backwards VDL Service 1 I Contracts back VSM Service 1 I B2C (Private address) B2C Service 2 / Service 3 I 85 / SMS notification SMS Service 2 / Service 3 I 85 / Phone notification AVI Service 2 / Service 3 I 85 / B2C Assisted delivery B2P Service 2 / Service 3 I 85 / B2C Delivery of an appliance B2S Service 2 / Service 3 I 85 / VIP delivery VIP Service 2 / Service 3 I 85 / Table 7: Additional services for cargo export file The availability of individual services differs for Czech and Slovak clients. The availability of services differs also dependent on the transport type according to the shipment recipient s destination country - for explanation see the section Service CZ - Inland CZ - Export SK - Inland SK - Export EXW Yes Yes COD Yes SK only Yes CZ only DTR DE only DE only VDL Yes Yes VSM Yes DPC Yes B2C Yes SK only Yes CZ only SMS Yes SK only Yes CZ only AVI Yes SK only Yes CZ only B2P Yes SK only Yes CZ only B2S Yes SK only Yes CZ only VIP Yes Yes Table 8: Accessibility of services by type of transportation - cargo SMS notification SMS This service resides in the sending of a SMS to a specified number. The SMS text informs the recipient that the shipment was taken over for its delivery and time of future delivery. Should this service be 12 In case of chosen export destinations, other supplementary services may be provided above the framework of services specified in this document. For details contact the Geis sales manager. 50

59 GEIS Group 3.4 Transport services for cargo shipments required for the shipment, fill in the service code 48 in the record I, position 85 (service 2) or 117 (service 3, if another service is already specified on the position 85. The phone number to which the information is to be sent is given in the export file in the record I, position 87. This service is not marked in the handover protocol in any way Phone notification AVI This service resides in the phone specification of exact time of the arrival of the driver to the place of delivery for the shipment recipient. Should the service be required for the shipment, fill in the code of the service 01 in the record I, position 85 (Service 2) or 117 (Service 3) if the position 85 includes already another service. The phone number to which the driver should call is to be given in the export file in the record I, position 87. This service is not marked in the handover protocol in any way Cash on delivery COD The COD service is to be given in the export file in the record K position 23 COD amount (in hellers of cents) and on the position 74 COD currency (see the table 7). In addition to the COD amount and Cod currency in the record J, fill in also the variable symbol in the record J, position 77. What is to be given in the handover protocol is the value of the COD in the COD column and the variable symbol in the column Variable symbol Specified delivery time DTR This service envisages the delivery of the shipment on a specified day as required by the sender. Should the service be required for the shipment, fill in the service code 14 in the record I on the position 47 (Service 1). This service is not mentioned in the handover protocol. The delivery date is specified in the format DDMMYY in the record I on the position 79. The delivery time is specified in the format HHMM in the record I on the position 49. This service is not marked in the handover protocol in any way B2C (Private address) This service resides in the delivery of shipments in the Czech and Slovak Republic to private addresses. Should the service be required for the shipment, fill in the service code 02 in the record I on the position 85 (Service 2) or 117 (Service 3) if the position 85 includes already another service. The phone number to which the driver should call is to be given in the export file in the record I, position 87. This service is not marked in the handover protocol in any way EXW (Payment by the recipient) This service envisages the payment of the transport costs by the recipient. The service is specified in the export file in the record I on the position 43 by the reference to the delivery condition EXW by 51

60 GEIS Group 3.5 Verification cargo means of the code 20. For the standard delivery when the transport costs are paid by the sender fill in the code 30 (see the table 7). Fill in in the handover protocol the text Yes in the EXW column DL backwards VDL This service resides in the scanning of delivery notes signed by the recipient and making them available to the sender (either online using Track&Trace or by reverse delivery to the sender). Should the service be required for the shipment, fill in the service code 40 in the record I on the position 47 (Service 1) Contracts back VSM This service provides for the sending of contract signed by the recipient back to the sender. Should the service be required for the shipment, fill in the service code 41 in the record I on the position 47 (Service 1) B2C Assisted delivery B2P This service provides for the delivery to a private address where the shipment will be delivered to a deliver address specified by the recipient with active assistance of the recipient. Should the service be required for the shipment, fill in the service code 30 on the position 85 (Service 2) or 117 (Service 03), if another service is already specified in on the position B2C Delivery of an appliance B2S This service provides for the collection of (an old) appliance from the private address of the recipient to which a shipment was delivered (e.g. a new appliance). Should the service be required for the shipment, fill in the service code 31 on the position 85 (Service 2) or 117 (service 3) provided another service has already been specified on the position VIP delivery VIP This service is provided exclusively for inland shipments and it provides for comfort delivery to the recipient. Should the service be required for the shipment, fill in the service code 32 on the position 85 (Service 2) or 117 (service 3) provided another service has already been specified on the position Verification cargo The correctness (i.e. adherence to the format and consistency of information according to this manual) of export data, handover protocol and labels is the responsibility of the client. When all such documents match the specification given in this document, the client shall send an with their preview to the assigned Geis sale manager. The sales manager shall handover the underlying documents internally to the Geis IT department and any possible deficiencies shall be communicated immediately with the technical contact of the client. Never send testing data directly to the FTP server! If not specified otherwise, the client s underlying documents are subject to the following requirements: 52

61 GEIS Group 3.5 Verification cargo ˆ They consist of an export file related to the handover protocol and labels to all shipments. These labels have to be printed on an EPL or laser printer and scanned to be available ideally in the PDF format. ˆ They include at least three shipments out of which at least one consists of several items and several handling units. ˆ They include shipments with those services, only (COD, etc.) that have been agreed between the client and the sales manager in the contract with Geis. ˆ They were checked according to the annex Checklist for Underlying Documents Cargo. Shipment numbers (resp. numeric series) are chosen by the client on random basis. It is important that the number had 13 digits and data in the export files were consistent with data given in the handover protocol and on labels. The payer and client number is to be chosen by the client as an eight digit number (e.g ) The payer and client number will be always the same. After the verification of the correctness of testing data, actual identifiers are assigned in the followings cope: ˆ Client s number (eight digit number) ˆ The numeric series (the same scope for inland and international shipments) What follows is an integration test of sharp data with identifiers assigned to the client by Geis. This test is described in the next chapter. Data integration test The data integration test in the Geis system is executed after the validation of the correctness of all underlying documents and assignment of identifiers. During the test, the client proceeds in same way as in the go live procedure (see the section 3.6 Go live ). Thus, the client creates actual shipments in his IS. That means that numbers from the assigned numeric series will be used for the shipments. The assigned client s number will be given in the export file generated by the client s IS. The client shall send the export file (see the section 3.6 Go live ). to the Geis FTP server. Moreover, he will send all shipment numbers from the first export file by mail to the Geis sales manager and IT department. Thus, the shipment will be actual, nevertheless only in terms of data as they will not be dispatched physically. Numbers used for the testing shipments cannot be used again any further in future for other shipments! 53

62 GEIS Group 3.6 Go live 3.6 Go live What is optimal during the go live procedure is to send the export file when printing the handover protocol (it may be automated), however, no later than immediately after the departure of our collection vehicle to our depot. What is important is to import data to our IS no later than at the moment when the collection vehicle arrives to the depot. The export file may be sent either to the FTP server or to the address We prefer the FTP, is a backup solution in case the FTP server failed for any reason whatsoever. Below see the addresses and login data. FTP server: User: Password: Directory: ftp1.geis.cz ftp objednavky ftp194obj objednavky data@geis.cz What is anticipated is the sending of a single file per day but as specified in the section 3.1.2, several files may be sent. 54

63 Symbols and abbreviations List of the documents used or generally used symbols and abbreviations AN Alphanumeric value (see the section ) CC Integer value (see the section ) COD Cash of delivery EDI Electronic Data Interchange EXW Costs and risks associated with the delivery of goods are assigned to the recipient FP Numeric values with decimal points (see the section ) IS Information system KD Calendar date (see the section ) KOLLI Two-digit number describing the order of the loading item I the cargo shipment POD Confirmed delivery note TC Phone number (see the section ) 55

64 Vzor - předávací protokol PARCEL PŘéžÁVH6ÍfPROTOKOL Příkazcef9odesílatel5X Názevffirmyfs0r0o0 Nějakáful0fš1M BSpýMf Irýdek8Místek žatumx StranaX -S0ýS0Mý-S -fff- UeisfParcelf6Zfs0r0o0 Uf6ementárnyf--pS3fBýýfSýfOstrava Tel0Xf97nMý5fš1-fMBBfBBB3 IaxXf97nMý5fš1-fMBýf-1š Poz0 Galíkfčíslo Hdresát Připojištění éxw žob096ož5 Var0fsymbol Poznámka - M S n 1 ýý-m--ý-pý- M ýý-m--ý-pýý 1 ýý-m--ý-pýb n ýý-m--ý-bšš M ýý-m--ý-bšp 1 Prvnífstavebnífs0r0o0 6hodskáf-SnnF1M 6ZfSSšý-fKlatovyf8fLubyff Potrebyfprofchovatelefv0o0s0 Uercenovaf-/MF1 SKfp1-ý-fPetržalka Potrebyfprofchovatelefv0o0s0 Uercenovaf-/MF1 SKfp1-ý-fPetržalka LojzafNovák LidickáfšS 6ZfSSý--fTřemošná HlenafKrátká NafLibušifSSS 6ZfSš-/1fGechyně ý3ýý ý3ýý +odinufpředemfvolat ý3ýý M-B3ýý -M--ý-pýý Manipulovatfopatrně ý3ýý ý3ýý Manipulovatfopatrně ý3ýý ý3ýý ý3ýý --/-3ýý -M--ý-Bšp 6elkemfbalíkůXf1 6elkemf6OžXf -SBp3ýý Podpisfřidiče Výšefuvedenéfzásilkyfbylyfpředányfbezfpoškození0 Podpisfodesílatele PřepravyfsefuskutečňujífdlefVšeobecnýchfobchodníchfpodmínek3faktuálnífstavfUéxSfPHR6éLf6Z3fspol0fsfr0o03fxČOXf/SýBBý1-0 SpolečnostfjefzapsánafvfobchodnímfrejstříkufvedenémfKrajskýmfsoudemfvfPlzni3foddílf63fčíslofvložkyfš1ýS0

65 zor - předávací protokol CARGO Příkazcef9odesílatel5b PŘpžÁVé6ÍfPROTOUO+ Názevffirmyfs0r0o0 Nějakáful0fW1M,SXýMf grýdek8xístek žatumb -S0ýS0Mý-S Zeisf6Zfs0r0o0 Uf6ementárnyf--XS3f,ýýfSýfOstrava Tel0bf97nMý5fW1-fM,,f,,,3 BČbf-MSýýý,X Stranab -fff- gaxbf97nmý5fw1-fm,ýf-1w3fw1-fm,-fwnwf9+ogistika5 Poz0 Číslofzásilky Příjemce3fkontakt Us šmotnost pxw žob096ož5 Reference -,ý,1sýýý-mýým Ioseff6horý Štúrovaf-SnnF1M SUfWnWý-fNitra8Staréfxesto - -1ý ý3ýý -nýýms M,ý,1Sýýý-MýýS StavebninyfSTVfs0r0o0 Zercenovaf-/MF1 SUfX1-ý-fPetržalka M nxý M-,ý3ýý -nýýmn S,ý,1Sýýý-Mýýn SuperfPneufs0r0o0 UollárovafSMMFX SUfX1-ý-fPetržalka - Mý ý3ýý -nýý1- n,ý,1sýýý-mýý1 égrofézfs0r0o0 +idickáfws 6ZfSSý--fTřemošná - -n éno ý3ýý --ýýns 1,ý,1Sýýý-Mýý/ pleftrofs0r0o0 Naf+ibušifSSS 6ZfSW-/1fGechyně n XS --/-3ýý -nýý1m gpf8f6elkemfpuropalet S WfUs,n,fUg 6OžbffSSS-3ýýf ppf8f6elkemfjednocestnýchfpalet M UTf8f6elkemfkartonů M špf8f6elkemfpůlpalet ý Ušf8f6elkemfpolopalet ý žpf8f6elkemfdvojpalet - 6elkemfostatnífnákladovéfkusy - Podpisfřidiče Výšefuvedenéfzásilkyfbylyfpředányfbezfpoškození0 Podpisfodesílatele PřepravyfsefuskutečňujífdlefVšeobecnýchfobchodníchfpodmínek3faktuálnífstavfZpBSf6Z3fspol0fsfr0o03fBČObfnn1/,S1W0 SpolečnostfjefzapsánafvfobchodnímfrejstříkufvedenémfUrajskýmfsoudemfvfPlzni3foddílf63fčíslofvložkyf-nn,10

66 Vzor - předávací protokol PARCEL (slovenská verzia) POTVRjéN+ékOkPRéVZGTÍkZÁS+éLOKkNGkPRéPRGVU Odosielateľ(( úén+xkslovenskoksyryoy +liašskákcestakwí bp/mzkkkkkžanskákžystrica játum( Strana( 12ym2y3m12 1kuk1 ýeiskparcelkskksyryoy Trňanskákí5kbímkm1kZvolen Tely(k90/317k1Wk1W1 úax(k90/317k/zkzzzk3m3b Pozy žalíkkčíslo Gdresát Pripoistenie éxw joby9moj7 Varyksymbol Poznámka / z mm1311m1wm1 3 mm1311m1wmm z mm1311m1wmp / mm1311m1pbb 3 mm1311m1pbw z Prvníkstavebníksyryoy Mhodskák12//uz3 MZk22bm1kKlatovykBkLubykk Potrebykprokchovatelekvyoysy ýercenovak1í3uz SKkWz1m1kPetržalka Potrebykprokchovatelekvyoysy ýercenovak1í3uz SKkWz1m1kPetržalka LojzakNovák Lidickákb2 MZk22m11kTřemošná GlenakKrátká NakLibušik222 MZk2b1ízkžechyně m5mm m5mm godinukpředemkvolat m5mm 31p5mm 1311m1Wmm Manipulovatkopatrně m5mm m5mm Manipulovatkopatrně m5mm m5mm m5mm 11í15mm 1311m1pbW Melkomkbalíkov(kz MelkomkMOj(kkk12pW5mm Podpiskvodiča Vyššiekuvedenékzásielkykbolikprevzatékbezkpoškodeniay Podpiskodosielateľa PrepravyksakuskutočňujúkpodľakVšeobecnýchkobchodnýchkpodmienok5kaktuálnýkstavkýeiskParcelkSK5kspolykskryoy5k+ČO(k/í/Wbzb3y SpoločnosťkjekzapísanákvkobchodnomkregistrikOkresnéhoksúdukžanskákžystrica5kvložkakčíslok31zm2uSy