System Integration Manual

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "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: 2017/01 Valid From: April Last revision: August 31, 2018 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 gures List of tables v vi vii vii 1 General information Modication of customer's information system Transport types Sequences Checksums Package routing Description of blocks in routing le National routing International routing International routing for cargo Poland 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) i

3 1.8.4 Integer values, the number is aligned to the left (CL) Integer values, the number is completed with the xed value (CS) Calendar dates (KD) Time data (KC) Phone numbers (TC) Data validator Parcel Combined (mass) shipment EDI format specication Records structure Export le denomination convention Handover protocol structure Bar code Label printing specication Shipment parcel transport services Notication on the delivery of the shipment ADZ POD services Notication on a problematic shipment APZ SMS notication on the dispatch of the shipment SMS Telephonic notication AVI Cash on delivery COD Individual account COD Delivery until 12 o clock D Delivery to a private address B2C Ex Works EXW Guaranteed delivery GAR Insurance POJ Card payment CDR ii

4 Pickup point VM Electronic shipment documents - EDL Notication before collection by SMS - SAS Notication before collection by phone - SAT COD Express - CDE Nonstandard packaging - DON Reverse shipment - BCK Verication parcel Go live Cargo EDI format specication Records structure Convention regulating the process of assigning of names to export les Handover protocol structure Label printing specication Transport services for cargo shipments SMS notication SMS Phone notication AVI Cash on delivery COD Specied 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 Electronic shipment documents - EDL iii

5 3.5 Verication cargo Go live Symbols and abbreviations 61 Attachments 62 Handover protocol for parcel Handover protocol for cargo P edávací protokol pro parcel P edávací protokol pro cargo Previews of parcel labels 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 le 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 denes the rules for transferring data into Geis Group information system, denes which data should be transferred, which data formats and types are used, and also provides specication of stickers and handing-over certicates for parcel and cargo transport. Prepared by IT department Last revision: August 31, 2018 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) 2018/ Change of pickup point format / Modied routing - description of blocks 1.5 New chapter added - International routing for cargo Poland Service BCK - Reverse shipment added / National routing - Depot number Modied data block table - record 22, 44, New additional services for Poland - CDE, DON, SAS, SAT Modied specications of labels 2.4 Descriptions of new services for Poland CDE, DON, SAS, SAT Modied positions of data blocks in text - Modied positions of variables for labels / EDL service specication , 3.4, Adding Pickup point service for SK / Change of service availability for countries 2.5 (CDR) 2014/ Added Pickup point service 2.5 Added Slovak version of Handover protocol Attachments 2014/ Added Payment by card service 2.5 Dierentiation of packages from transport 1.2 subjects' perspective Added information about data validator 1.9 Barcode size specied 2.4, 3.3 Change of order of introductory chapters v, vi, vii Correction of typos and mistakes Modied availability of cargo services 3.4 abroad 2014/ Initial issue of documentation Publication on technical support website Revised Parcel specication Completed Cargo specication Table 1: Overview of documentation modications vi

8 List of Figures 1 Simplied scheme of EDI format for parcel Export le 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 modications vi 2 Structure of records in routing table for national Structure of records in routing table for international Structure of records in routing table for Polish cargo export Records structure in a parcel export le Denomination of supplementary services in the parcel export le Denomination of supplementary services II. in the parcel export le Accessibility of services by type of transport - parcel Additional services for cargo export le Accessibility of services by type of transportation - cargo vii

9 GEIS Group 1. General information 1 General information The manual includes ZIP archive containing les 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 Modication of customer's information system 1.1 Modication of customer's information system Implementation of integrated data communication with Geis systems frequently requires modications of customer's information system. When ordering these modications, 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 modications 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 les, handover protocols, stickers, supplementary services, routing tables, etc.) are dierent 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 dened in dierent 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; dierent 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 dened 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 dierent 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 dierent prex 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 suces for packages. The rst 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 dierent 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 rst 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 dierence between next "ten" and the result of previous step (marked blue). 54 and complement to next "ten" (60) = 6 Parcel Checksum of parcel 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 dierence 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 dened by routing tables. Sections 1.5.2, 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. Dierent routing tables are used to route parcel packages and cargo packages. Dierent structure of routing tables is used for national and international transport, described in sections National routing, International routing and International routing for cargo Poland. Appended archive and also FTP server lists them in directories Parcel and Cargo. More information about naming of les can be found in section Description of blocks in routing le Routes are stored at separate lines within the les. Each line contains dierent information, at positions listed in tables 2, 3 and 4. The following list describes all information items. Fixed value: The rst information in a record is so-called Fixed value. This block is always NT and need not be processed.. Delivery 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 specied extent. The depot number in le is a three-digit number, and the rst or last digit is skipped, it depends on country where depot is, if it is Czech Republic, the rst digit is skipped, and for other countries will be skipped the last digit. For example, if used depot number in le for Czech Republic is 088, 88 will be used as nal depot number. If 120 is a number used for Slovakia as a depot number, 12 will be used. 3 They are also sent to client's contact s. 5

14 GEIS Group 1.5 Package routing 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 elds are left free they are lled 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 eld 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 eld includes the upper limit of the Post code scope. The value is aligned from the left 4. Delivery route number: This number denes 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. Number of sending depot This number denes sending depot of shipment National routing Directory Parcel in appended archive contains the following les: ˆ 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 les: ˆ 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 les. Each line contains dierent information, at positions listed in table 2. The table 2 denes positions of values described in the line, their length and data type (for more information on data types see the section 1.6). 4 Both border digits belong to the interval. 5 This is used only in international cargo routing for Poland 6

15 GEIS Group 1.5 Package routing # Name of block Position Lenght Data type 1 Fixed value NT 1 2 AN 2 Delivery 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 International routing The following les 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 nd the following les 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 dierence being the positions and length of some values as you it is apparent in the table International routing for cargo Poland You will nd the following le in the Cargo directory: ˆ Cargo_PSC_PL_Export - routing table for international cargo shipments of clients from Poland. The international transport operations routing table for Poland includes information on lines identical to the inland transport operations routing table, the only dierence is that it has Number of sending depot in last part of routing. You can see it in the table 4. 7

16 GEIS Group 1.5 Package routing # Name of block Position Lenght Data type 1 Fixed value NT 1 2 AN 2 Delivery 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. # Name of block Position Lenght Data type 1 Fixed value NT 1 2 AN 2 Delivery 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 6 CC 11 Number of sending depot 33 3 AN Table 4: Structure of records in routing table for Polish cargo export. 8

17 GEIS Group 1.6 Data types 1.6 Data types Individual data (values) have to be formatted in data les and routing tables based on the specication. The data type denes 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 les for cargo and parcel operations dier 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 lled with spaces across the entire length of the eld. Example: Name of the Recipient Lojza Novák in a 20 character eld: Lojza Novák Integer values (CC) Integer value elds may include only digits. The number has to be aligned to the right and all empty spaces have to be lled with zero characters. Example: Parcel weight gr in a 10 digit eld: 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 lled with zero characters. Example: Cash on delivery CZK in the 10 digit eld: Example: Cash on delivery EUR 99.- in the 10 digit eld: 9

18 GEIS Group 1.8 Data types valid for cargo Example: Cash on delivery 0.- in the 10 digit eld: Calendar dates (KD) The date is written to the integer eld. 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 elds and have a strictly dened 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 lled with spaces across the entire length of the eld. 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 eld: 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 eld: Lojza Novák 10

19 GEIS Group 1.8 Data types valid for cargo Integer values (CC) Integer value elds may include only digits. The number has to be aligned to the right and all empty spaces have to be lled with zero characters. If the eld contains no data, it remains blank (e.g. for supplementary services). Example: Parcel weight 15 kg in a 10 digit eld: Integer values, the number is to be aligned to the right (CP) Integer value elds may include only digits. The number has to be aligned to the right and empty places (until the end of the eld length) have to be lled with spaces. Example: The sender s Post code is in a 9 digit eld: Integer values, the number is aligned to the left (CL) Integer value elds may include only digits. The number has to be aligned to the left and empty places (until the end of the eld length) behind the number have to be lled with spaces. Example: The shipment variable symbol is in 10 digit eld: Integer values, the number is completed with the xed value (CS) Integer value elds may include only digits. A xed 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 eld. The cargo date format is DDMMYY. 11

20 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 elds and have a strictly dened 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 lled with spaces across the entire length of the eld. 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 eld:

21 GEIS Group 1.9 Data validator 1.9 Data validator A data validator is available for the verication of the correctness of data in data les. The validator checks the following: ˆ Data le coding ˆ Data le 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 les. This validator is recommended to be used as early as prior to the rst 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). 13

22 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 specication Electronic exchange of structured text les 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 le 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 g. 1. The preview of the export le with data blocks is shown on the g. 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: Simplied scheme of EDI format for parcel Export EDI data file H H H H H... Figure 2: Export le view for parcel. 14

23 GEIS Group 2.2 EDI format specication Records structure Individual data blocks have a xed position (sequence), length and data format (see the section 1.7 Data types). Some blocks have strictly dened value or enumeration of valid values. All this information is described in the list and table 5 Structure of records in the export le 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 rst of all positions, lengths and data types of blocks. Fixed value: The rst block in the record is so called xed value. This block has a dened xed 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 rst (so called superior) parcel in the combined shipment. This record will appear in the export le as rst and will have the same values in the blocks shipment number and parcel number. Parcel number: It has to be specied 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 identication number. It will be assigned to the client after the validation of the correctness of the export le. 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 specied. business day 6 after the collection date. If specied, 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 specied. It may be found based on the post code of the shipment Recipient (see the section 1.5 Routing).It must be given anytime. 6 Both weekends and public holidays have to be taken into account. 15

24 GEIS Group 2.2 EDI format specication Blank: This way marked data blocks have to be left empty they should be lled 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 lled 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 lled 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 Country Code Table subjects to 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 at rate of 1 kg may be specied 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 specied. Supplementary services coding: Required supplementary services are to be dened in this block using the symbol 1 on respective positions for details see the table 6 below in this section and the section 2.5). Services are dened for the superior combined shipment parcel, only. Card payment: Card payment (CDR) is to be dened 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 specied 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 specied 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 specied for the shipment superior parcel (i.e. the parcel that has the same number of the shipment and the parcel). It must not be specied for other parcels so that the total sum could match. According to the business 16

25 GEIS Group 2.2 EDI format specication 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 is to be dened 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. Supplementary services II coding: Required supplementary services are to be de- ned in this block using the symbol 1 on respective positions for details see the table 7 below in this section and the section 2.5). For combined shipments, services are dened as specied in services details. Variable symbol: If a parcel is cash on delivery shipment, this information is obligatory. It may specied only for the superior parcel in case of combined shipment s. Number of parcels in the shipment: This block species the number of parcels in the shipment and it is obligatory. The number of parcels in combined shipment s is to be specied for each parcel. References: This block includes clients references, for instance order numbers. This led 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 specied 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 specied 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 specied 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. Notication 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. 17

26 GEIS Group 2.2 EDI format specication Notication 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 notication: 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. POD service: Enter the address to which the conrmed delivery note is to be sent. SMS notication on the dispatch of the shipment: Here enter the phone number to which the shipment dispatch message is to be sent. Recipient for notication: Here enter the recipient to which the shipment dispatch message is to be sent. 18

27 GEIS Group 2.2 EDI format specication # 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 Individual account COD CC No 23 blank AN 24 COD value FP Yes* 25 Pickup point code AN Yes* 26 blank AN 27 Supplementary services II. denom CC Yes 28 Variable symbol AN Yes* 29 blank AN 30 Number of parcels per shipment CC Yes 31 References AN No 32 blank AN 33 Phone notication/private address TC Yes* 34 Insurance FP Yes* 35 Remark for driver AN No 36 Remark for consignee AN No 37 EDL documents specication AN Yes* 38 Notication of problematic shipment AN/TC No 39 Notication of delivered shipment AN/TC No 40 Notication of damaged shipments AN/TC No 41 POD service AN No 42 SMS notication of the dispatch TC No 43 Recipient for notication AN No 44 IBAN Account number AN No 45 Sender's telephone number TC Yes* 46 Reverse shipment number CC Yes* * 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 5: Records structure in a parcel export le. 19

28 GEIS Group 2.2 EDI format specication Service name Abbreviation Position Length Value Specication 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 6: Denomination of supplementary services in the parcel export le. Service name Abbreviation Position Length Value Specication in the block No. 27 Service EDL EDL / Service CDE CDE / Service DON DON / Service SAS SAS / Service SAT SAT / Service BCK BCK / Table 7: Denomination of supplementary services II. in the parcel export le. Specifying the phone number in the respective data block for service of the type of notication 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 le Parcel_Data_CTST108c.001 that complies with the handover protocol provided in the annex Parcel Handover Protocol. The le includes ve 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 le denomination convention The parcel export le number consists of several parts: xxx, dd, m a yyy. Their position in the le name is as follows: 20

29 GEIS Group 2.2 EDI format specication Cxxx1ddm.yyy xxx an assigned three digit clients ID. It may include digits and alphabet characters. dd day when the le was exported (sent to Geis Parcel CZ s.r.o.). m month when the le was exported. Months are coded using alphabet letters (January a, February b, March c etc. to December l). yyy export le sux. Should the dates be sent once a day, only or after at last 30 minutes, it is always possible to send the le with the sux 001. Otherwise, it will be necessary to make sure that the sux number grows by one with each sent le (i.e. 001, max. 999 les per day). Example: The name of the parcel export le sent on March 2 by the client is ID 565: C565102c.001 Caution: The name of the le C565102c.001 a C565102c.001.txt is not the same. Caution: No mass shipment may be divided to several les (e.g. between *.001 a *.002). Export les sent later in a single day (e.g. the le C565102c.002 or C565102c.003 etc.) may, but need not necessarily, contain records for parcels exported in previous le sin the same day. That means that data exported in the le C565102c.001 need not be contained in les C565102c.002 and C565102c.003. If the exported records are contained again in follow up les and shipment data diers (e.g. another recipient), such records will not be imported/updated any further. 21

30 GEIS Group 2.3 Handover protocol structure 2.3 Handover protocol structure The handover protocol serves as a conrmation on the takeover of shipment for transport and it has precisely specied 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 7. Contact to the sender: The full address of the client has to be lled 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 specied shipments collection date specied that is identical to the date given in the export le. 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 eld 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 specic parcel is insured. ˆ EXW this eld 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. ˆ 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 specied in the currency of the country with the accuracy 7 All data given in the handover protocol preview as annexed are obligatory. 22

31 GEIS Group 2.3 Handover protocol structure 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 specied for the superior parcel of the shipment (i.e. the parcel with identical parcel and shipment number). It must not be specied for other parcels so that the total sum could match. ˆ Variable symbol a payment identier (it consists of digits, only). It is an obligatory item for COD. It may be specied for superior parcels, only, in case of combined shipments. If specied for non-cod shipments, it is not transmitted for the shipment. ˆ Note ll 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 le (see the block No. 32 in the table 5 Structure of Records in the Parcel Export File ). Total number of les: The total number of les is to be specied 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 diers 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 gure 3, left-hand side, shows as example of unreadable bar code (the code is too 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. 23

32 GEIS Group 2.3 Handover protocol structure Figure 3: Example unreadable (left) and correct (right) bar code 24

33 GEIS Group 2.4 Label printing specication 2.4 Label printing specication Every parcel shall be provided with a label according to the general business terms and conditions representing oered 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 specied parameters (size, content, legible bar codes etc.). The ZIP archive attached to this manual includes a template (in the directory Parcel le 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 specied for given parcels. What is available in the le EPL2_Programming_Manual.pdf 8 is the EPL2 language manual use for the preparation of the template. The following gure 4 shows the layout of the content on the label with explanatory notes given in the list behind it. In the template we have dened texts are printed without diacritics and therefore it is necessary to enter text chains without diacritics. The diacritics support is possible when dening the template itself, see the attached EDP manual. data. 1. The logo is available in the attached archive le _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 nd the le Geis_logo_printer.zip with the instruction describing 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 Balíkové p epravy. Replace the following expression with adequate values in the template. %%SEND_DEPOT_STREET%% on the line 92 street, %%SEND_DEPOT_POSTALCODE%% on the line 93 Post code, %%SEND_DEPOT_CITY%% on the line 93 city, %%SEND_DEPOT_PHONE%% on the line 94 phone number, %%SEND_DEPOT_FAX%% on the line 95 phone number for FAX. 3. Service identication 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 gure 10 in the 8 The manual needs not be studied as it has been attached for those who wish to get insight in printed 25

34 GEIS Group 2.4 Label printing specication 15 cm 1 Geis Parcel CZ s.r.o. U Cementárny 1183, Ostrava 2 Tel.: Fax: mm 55 mm 6 10 cm 3 Prijemce: Firma ABC s.r.o. Jan Novak 13 Lidicka 93 Ejpovice CZ Pozn: text pro prijemce 15 Tel: Odesilatel: 18 Nazev firmy s.r.o. Nejaka ul. 952 CZ Frydek-Mistek Tel: KS:1/1 16 VS: CZ mm mm kg

35 GEIS Group 2.4 Label printing specication annex to the manual). They are to be shown only for the following services: Phone notication ( 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 ( GP ). For a more detail description of service see the section 2.5. In the printing template, replace the expression %%SERVICES%% on the line 73 with a text that specied required services (e.g., for the label given in the gure 10 the line 73 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 122 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 123 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 99 parcel number, %%TRANSPORT_CHKSUM%% také na ádku 99 check digit. 7. Abbreviation (code) of recipient country and number of depot which delivers the consignment. Valid values of a country code for parcel shipments are given in the annex Country Code table subjects to ISO 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 117 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 119 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 119 (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 lled in at this place. In the template replace the expression %%LOAD%% on the line 116 with the adequate date in the format DD.MM.YYYY. 27

36 GEIS Group 2.4 Label printing specication 11. Parcel weight. If not weighed, the parcel value will be specied as 1 kg. In the template replace the expression %%PACKEGE_WEIGHT%% on the line 121 with the actual value. 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 120 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 110 juridical/natural person s name, %%RECIPIENT_PERSON%% on the line 111 contact person s name, %%RECIPIENT_STREET%% on the line 112 recipient s street, %%RECIPIENT_CITY%% on the line 114 recipient s city, %%RECIPIENT_STATE%% on the line 125 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 113 post code with the same value as given in the item Remark for the recipient. Here ll in the remark for the recipient identical to the text of the in the block Remark for the recipient in the export le. 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 142 with corresponding text. 15. Recipient s phone number. This data is not obligatory, nevertheless it is recommended to be lled in. Otherwise, phone number is obligatory for services B2C, AVI and VM. In template replace the expression %%RECIPIENT_PERSON_PHONE%% on the line 127 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 109 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 145 order of the package in the shipment, %%PACKEGE_COUNT%% also on the line 145 number of packages in the shipment. 28

37 GEIS Group 2.4 Label printing specication 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/ Sender s address. Replace the following expression with adequate values in the template. %%SENDER_NAME%% on the line 104 sender s company name, %%SENDER_STREET%% on the line 106 street, %%SENDER_STATE%% on the line 107 country code, %%SENDER_POSTALCODE%% also on the line 107 Post code, %%SENDER_CITY%% also on the line 107 city. 19. Sender s phone number. This data is not obligatory, nevertheless it is recommended to be lled in. In template replace the expression %%SENDER_PERSON_PHONE%% on the line 144 with the corresponding value. All data on the label have to agree with data given in the export le and in the handover protocol. 29

38 GEIS Group 2.5 Shipment parcel transport services 2.5 Shipment parcel transport services In this section, there is a brief description 9 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 diers for Czech and Slovak clients. The availability of services also diers 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 PL Inland PL Export EXW Yes COD Yes only SK and PL Yes only CZ and HU Yes only CZ and SK B2C Yes only SK and PL Yes only CZ and PL Yes only CZ and SK SMS Yes only SK Yes only CZ Yes AVI Yes only SK and PL Yes only CZ and PL Yes only CZ and SK GAR Yes Yes Yes POJ Yes Yes Yes Yes Yes D12 Yes Yes Yes ADZ Yes Yes Yes APZ Yes Yes Yes POD Yes Yes only CZ Yes CDR Yes only SK and PL Yes only CZ and PL Yes only CZ and SK VM Yes only SK Yes only CZ Yes EDL Yes only SK Yes only CZ Yes SAS Yes SAT Yes CDE Yes DON Yes BCK Yeso Yes Yes Table 8: Accessibility of services by type of transport - parcel Notication on the delivery of the shipment ADZ The notication is sent by or SMS and conrms the successful delivery of the shipment. The address or phone number to which the information is to be sent is provided in the export le in the block 39 (see the table 5 in the section 2.2.1). This service is not marked in the handover protocol and labels. Should the shipment be combined, ll in the address or phone number in the export le for all parcels.. 9 For the full description of all supplementary transport services see the general Business Terms and Conditions This document contains just their brief denition. 10 In case of chosen export destinations, other supplementary services may be provided above the framework of services specied in this document. For details contact the Geis sales manager. 30

39 GEIS Group 2.5 Shipment parcel transport services This service may be combined with all other services POD services This service provides for the automatic dispatch of the conrmed delivery note to the specied address. address is given in the export lein the block 41 (see the table 5 in the section 2.2.1). This service is not marked in the handover protocol and labels. The address is given in the export le for all parcels included to a combined shipment. This service may be combined with all other services, without Pickup point service Notication 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 specic reason. The address or phone number to which the information is to be sent is given in the export le in the block 38 (see the table 5 in the section 2.2.1). This service is not marked in the handover protocol and labels. Should the shipment be combined, ll in the address or phone number in the export le for all parcels. This service may be combined with all other services SMS notication on the dispatch of the shipment SMS This service resides in the sending of a SMS to a specied 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 le in the block 42 (seethe table 5in 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 le for the rst (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 notication as a part of the price of the B2C service (to the phone number specied for the B2C service) and Pickup point service. It may be combined with other services 31

40 GEIS Group 2.5 Shipment parcel transport services Telephonic notication AVI This service resides in the telephonic notication of the time of the arrival to the destination address with the shipment recipient. The phone number is given in the export le in the block 33 (see the table 5 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 Specications ). In case of a combined shipment, the phone number is given in the export le only for the rst (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 32

41 GEIS Group 2.5 Shipment parcel transport services Cash on delivery COD The COD service is to be given in the export le in the block 20 (see the table 6) at records on COD parcels. In addition to the denomination in the block 20, the block 24 has to include the information on the amount of the COD and the block 28 has to include the variable symbol. In case of a combined (mass) shipment, the COD is marked in the export le only for the rst parcel. The COD value is given also for the rst 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 rst shipment parcel; it must not be specied 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 le. COD value is specied in domestic currency of recipient's state. 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 Specications and an example of a label in the gure 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 Individual account COD This option permits use of international bank account number IBAN (ISO ) for COD, on this account will be sent the amount of COD on shipment. For individual account COD is necessary to insert value 1 in block 22 (Individual account COD ) of export le, and also to have in the export le in block 44 (Account number IBAN ) account number in IBAN format (Bank account number in international format) - without spaces, dashes, and other additional characters. An example of the correct value in block 44: CZ PL 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 le in the block 20 (see the table 6). In case of a combined shipment, this service is marked in the export le of all parcels. This service is not mentioned in the handover protocol. 33

42 GEIS Group 2.5 Shipment parcel transport services 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 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 Specication ). 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 le in the block 20 (see table 6) for parcels to which the service is to be applied. Moreover, in the block 33 ll in the phone number of the recipient. Optionally in block 43 recipient address can be specied. In case of a combined shipment, the export le 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 Specication ). It is to be marked for all parcels where the service is specied in the export le. This service cannot be combined with the services SMS notication, Phone notication, 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 lled in the export le in the block 20 (see table 6) 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 specied 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 Specication ). It is to be marked for all parcels where the service is specied in the export le. This service may be combined with all other services, without Pickup point service. 34

43 GEIS Group 2.5 Shipment parcel transport services 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 in the export le in the block 20 (see table 6). In case of a combined shipment, ll in the export le 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 Specication ). It is to be marked for all parcels where the service is specied in the export le. 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 specied in the export le in the block 20 (see the table 6).In addition to the denomination in the block 20, the insurance value has to be specied in the block 34. In case of a combined shipment, the insurance is specied in the export le only for those parcels that are insured. The insurance value is to be lled 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 le. 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 specied in the export le in the block 21 (see table 6). 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 le anytime. In case of combined shipment s, it is specied 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. 35

44 GEIS Group 2.5 Shipment parcel transport services Pickup point VM This service provides the delivery of shipments to Pickup points addresses within the Czech and Slovak Republic. Redirection of the shipment to pickup point can be specied in the data le by sender, or the shipment can be redirected to pickup point by recipient. Redirection to pickup point is available only to pickup point in the country equal to recipient coutry. This document describe possibility, when delivery of the shipment is specied by sender - customer Geis on the pickup point. More details about service VM are at and in section balíkové p epravy - vnitrostátní p eprava - výdejní místa Geispoint. List of pickup points is available at To nd pickup point can be used plug-in, via document Geis Point Plugin on support website and Fill in the export le in the block 20 (see table 6) for parcels to which the service VM is to be applied. Moreover, in the block 32 ll in the phone number of the recipient and in the block 25 ll pickup point code.this service is not mentioned in the handover protocol. The code must have following format: GPnxxxxxxx. n - In this value, you must ll code of the country. CZ=1, SK=2, PL=3 xxxxxxx - In this value, you must ll code of the pickup point. Service conditions: ˆ Shipment must contain only one parcel (must not 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) specied, or shipment doesn't meet coditions for redirection to pickup point, the shipment will be specied without service VM. Recipient's phone number must be present in international format and must be registered within Czech or Slovak Republic (phone number starts with prex +420 or +421). Service is marked using text on labels GP in the service strip (for details see the section 2.4 Label Printing Specication ). It is to be marked for all parcels where the service is specied in the export le. 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. 36

45 GEIS Group 2.5 Shipment parcel transport services Electronic shipment documents - EDL This service means an option to attach electronic documents to shipment in PDF format, that are sent to FTP server as well as shipment EDI les. These documents are printed out before delivery and hand over to delivering driver. The documents are of two types - returnable and non-returnable. Returnable documents are conrmed (signed) by recipient by shipment delivery, later scanned and saved on Track & Trace web. If recipient refuses to conrm these documents, shipment won't be delivered. Non-returnable documents are handed-over to recipient with shipment delivery. EDL documents types: V = returnable document, e.g. document, that needs to be conrmed by recipient within shipment delivery and returned to driver N = non-returnable document, e.g. document, that is left by recipient within shipment delivery X = combined document, where rst half of pages is considered as returnable and second half as non-returnable - if odd number of pages in document, returnable pages are calculated as (n+1)/2 Y = combined document, where each odd page is returnable and even page non-returnable Fill in the export le in the block 27 (see table 6) for parcels to which the service EDL is to be applied. Moreover it is required to ll in additional information with document quantity in the block 37. Document quantity is recorded as VmmnnNmmnnXmmnnYmmnn, (mm means document quantity of given document type - required, nn means total number of pages in all les of given document type - not requred, 00 = not specied). Example of additional information for EDL: V0104N0000X0000Y0200 = there will be 1 returnable document of type V, with totally 4 pages, and two les - documents of type Y with number of pages not specied. This information must contain exactly 20 chars. Service conditions: ˆ Electronic documents in PDF format, sized A4 or Letter ˆ PDF les meet ISO standard, are not ciphered, password protected and opened for editing ˆ All fonts used in EDL document must be included in PDF les. If not, Geis cannot guarantee correct and readable printouts (especially important for barcode fonts) ˆ File names must meet structure EDL_<document type>_<shipment number>_<le number>, example EDL_N_ _01.pdf ˆ Documents are stored on FTP server using similar login information as for EDI les, into edl subfolder ˆ Documents are stored latest at 3:00 a.m. of the provisioned delivery day (usually next business day after shipment collection) 37

46 GEIS Group 2.5 Shipment parcel transport services ˆ Document header of size 2,7 cm must remain clear from any text for adding document identication ˆ Document is valid for shipment, in case of merged (combined) shipments on each shipment, where this service is required If documents to consignment with service EDL (service have to be given in block 27) are not present on FTP by 3:00 AM of the delivery, documents are incomplete (due to information in block 37 is not correct, or missing), then EDL service will be automatically removed. This service is not present in hand-over protocol. The use of service is subject to previous agreement with the sales manager of Geis. This service cannot be combined with the service VM Notication before collection by SMS - SAS Service available only in Poland. This service informs the sender via SMS that the shipment will be collected. The phone number is given in the export le in block Notication before collection by phone - SAT Service available only in Poland. This service informs the sender by phone in advance before shipment collection. The phone number is given in the export le in block COD Express - CDE Service available only in Poland. If this service is entered, the amount of COD will be transferred faster than stadnard COD, within the deadline agreed under a contract with the company Geis. Service is only possible in combination with the COD Nonstandard packaging - DON Service available only in Poland. By entering this service the sender species that the shipment has nonstandard packaging, that exceeds the standard dimensions of the consignment according to the General 38

47 GEIS Group 2.5 Shipment parcel transport services business conditions. If this service is specied, any fees for oversized shipment will not be charged Reverse shipment - BCK By entering this service the sender species, that the shipment recipient is allowed to send reverse shipment to sender on costs of sender. If sender includes the transport label for reverse shipment into package, the number of reverse shipment must be specied in the block 46. Service is marked using text on labels with text BCK in the service strip (for details see the section 2.4 Label Printing Specication ). It is to be marked for all parcels, if the shipment is combined. 39

48 GEIS Group 2.6 Verication parcel 2.6 Verication 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 specication described in this document and the data le 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 deciencies shall be communicated immediately with the technical contact of the client. Never send testing data directly to the FTP server! If not specied otherwise, the client s underlying documents are subject to the following requirements: ˆ They consist of an export le 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, notication 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 les 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 le name is to be chosen by the client as a three character number (e.g. TST). After the verication of the correctness of testing data, actual identiers are assigned in the followings cope: ˆ Client s number (eight digit number) ˆ ID of the client (three character, it is added to the le name) ˆ Numeric series (one scope for inland shipments and another for international shipments) What follows is an integration test of sharp data with identiers assigned to the client by Geis. This test is described in the next chapter. 40

49 GEIS Group 2.7 Go live 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 identiers. 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 le 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 le. The client shall send the export le (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 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 le 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 le 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 What is anticipated is the sending of a single le per day, but as shown in the section 2.2.2, it is possible to send more les. 41

50 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 specication What is used for the import of data on the transport of cargo shipments to our IS is the electronic exchange of structured text les in the logistic format of the electronic data exchange system KDDS128, coding windows The data transmission le has the structure of records. Each record has its own meaning, individual records are described in the gure 6. The structure of the export le with shown data records is given in the gure 5. 42

51 GEIS Group 3.1 EDI format specication Figure 5: Scheme records in the format KDDS128 43

52 GEIS Group 3.1 EDI format specication Figure 6: Description of records in the format KDDS Records structure Below see the data structure of individual records of the data le KDDS128. The records order has to be preserved (see the scheme in the gures 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 le 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 ve 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). 44

53 GEIS Group 3.1 EDI format specication 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 le 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 le 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 le 3 Name AN Company name / recipient name 4 Name AN Addition to the recipient s name 45

54 GEIS Group 3.1 EDI format specication 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 le 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 le 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 specied in the given F record. 46

55 GEIS Group 3.1 EDI format specication 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 le 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 EDL documents specication AN Quantity and types of EDL documents 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 le 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 le 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* (example CZK, EUR) * COD value is denominated in domestic currency of recipient's state. 47

56 GEIS Group 3.1 EDI format specication 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 le 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 le Cargo_Data_ftp txt that is in compliance with the handover protocol available in the annex Cargo Handover Protocol. The le includes ve shipments with three various handling units. 48

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

58 GEIS Group 3.2 Handover protocol structure 3.2 Handover protocol structure The handover protocol serves as a conrmation on the takeover of shipment for transport and it has precisely specied 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 11. Contact to the sender: The full address of the client has to be lled 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 specied shipments collection date specied that is identical to the date given in the export le. 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 eld 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 eld 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 specied 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 eld serves mainly to senders who may ll 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 lled in. Total weight: : The total weight of all shipments in kg is to be lled 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). 11 All data given in the handover protocol preview as annexed are obligatory. 50

59 GEIS Group 3.3 Label printing specication 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 diers from the parcel protocol. 3.3 Label printing specication 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 specied parameters (size, content, legible bar codes etc.). The ZIP archive attached to this manual includes a template (in the directory Cargo le 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 le EPL2_Programming_Manual.pdf 12 is the EPL2 language manual where the template was created. The gure 7 shows the layout of the content on the label and in the list behind it, there are explanatory notes provided. The template dened by us is used for the printing of text without diacritics, therefore enter text chains without any diacritics. When dening 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 12 The manual needs not be studied as it has been attached for those who wish to get insight in printed data. 51

60 GEIS Group 3.3 Label printing specication 1. The logo is available in the attached archive le _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 nd 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 lled 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 lled 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 lled 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. 52

61 GEIS Group 3.3 Label printing specication 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 specied 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 specied 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 specied 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 dened 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

62 GEIS Group 3.3 Label printing specication 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 identication of the shipment by the sender, the value lled in is identical to the text as in the block References in the export le. Replace in the template the expression %%REFERENCE%% on the line 118 with corresponding text. 15. Remark for the recipient. Here ll in remarks for the recipient identical to the text as in the block remark for recipient in the export le. 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 le, block Name 1), %%RECIPIENT_PERSON%% on the line 121 contact person name (in the export le 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 suce 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 suce to enter the value once, only). All data given on the label has to be identical to data given in the export le and in the handover protocol. 54

63 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 specication in export data is given for individual services. For detailed specications 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 Specied 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 notication SMS Service 2 / Service 3 I 85 / Phone notication 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 / EDL service EDL Service 2 / Service 3 I 85 / Table 9: Additional services for cargo export le The availability of individual services diers for Czech and Slovak clients. The availability of services diers 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 EDL Yes SK only Yes CZ only Table 10: Accessibility of services by type of transportation - cargo 13 In case of chosen export destinations, other supplementary services may be provided above the framework of services specied in this document. For details contact the Geis sales manager. 55

64 GEIS Group 3.4 Transport services for cargo shipments SMS notication SMS This service resides in the sending of a SMS to a specied 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 required for the shipment, ll in the service code 48 in the record I, position 85 (service 2) or 117 (service 3, if another service is already specied on the position 85. The phone number to which the information is to be sent is given in the export le in the record I, position 87. This service is not marked in the handover protocol in any way Phone notication AVI This service resides in the phone specication 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, ll 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 le 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 le in the record K position 23 COD amount (in hellers of cents) and on the position 74 COD currency (see the table 9). In addition to the COD amount and Cod currency in the record J, ll 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 Specied delivery time DTR This service envisages the delivery of the shipment on a specied day as required by the sender. Should the service be required for the shipment, ll 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 specied in the format DDMMYY in the record I on the position 79. The delivery time is specied 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, ll 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 le in the record I, position 87. This service is not marked in the handover protocol in any way. 56

65 GEIS Group 3.4 Transport services for cargo shipments EXW (Payment by the recipient) This service envisages the payment of the transport costs by the recipient. The service is specied in the export le in the record I on the position 43 by the reference to the delivery condition EXW by means of the code 20. For the standard delivery when the transport costs are paid by the sender ll in the code 30 (see the table 9). 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, ll 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, ll 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 specied by the recipient with active assistance of the recipient. Should the service be required for the shipment, ll in the service code 30 on the position 85 (Service 2) or 117 (Service 03), if another service is already specied 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, ll in the service code 31 on the position 85 (Service 2) or 117 (service 3) provided another service has already been specied 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, ll in the service code 32 on the position 85 (Service 2) or 117 (service 3) provided another service has already been specied on the position Electronic shipment documents - EDL This service means an option to attach electronic documents to shipment in PDF format, that are sent to FTP server as well as shipment EDI les. These documents are printed out before delivery and hand over to delivering driver. The documents are of two types - returnable and non-returnable. Returnable 57

66 GEIS Group 3.5 Verication cargo documents are conrmed (signed) by recipient by shipment delivery, later scanned and saved on Track & Trace web. If recipient refuses to conrm these documents, shipment won't be delivered. Non-returnable documents are handed-over to recipient with shipment delivery. EDL documents types: V = returnable document, e.g. document, that needs to be conrmed by recipient within shipment delivery and returned to driver N = non-returnable document, e.g. document, that is left by recipient within shipment delivery X = combined document, where rst half of pages is considered as returnable and second half as non-returnable - if odd number of pages in document, returnable pages are calculated as (n+1)/2 Y = combined document, where each odd page is returnable and even page non-returnable If this service is required, ll in the service code 52 on the position 85 (Service 2) or 117 (Service 3) provided another service has already been specied on the position 85. Moreover it is required to ll in additional information with document quantity in segment I on position 53. Document quantity is recorded as VmmnnNmmnnXmmnnYmmnn, (mm means document quantity of given document type - required, nn means total number of pages in all les of given document type - not requred, 00 = not specied). Example of additional information for EDL: V0104N0000X0000Y0200 = there will be 1 returnable document of type V, with totally 4 pages, and two les - documents of type Y with number of pages not specied. This information must contain exactly 20 chars. Service conditions: ˆ Electronic documents in PDF format, sized A4 or Letter ˆ PDF les meet ISO standard, are not ciphered, password protected and opened for editing ˆ File names mmet structure EDL_<document type>_<shipment number>_<le number>, example EDL_N_ _02.pdf ˆ Documents are stored on FTP server using similar login information as for EDI les, into edl subfolder ˆ Documents are stored latest at 3:00 a.m. of the provisioned delivery day (usually next business day after shipment collection) ˆ Document header of size 2,7 cm must remain clear from any text for adding document identication If les are not present on FTP server till 3:00 a.m. of delivery day, les are not complete (against additional information in segment I on position 53) or segment I on position 53 is empty or not in correct format, EDL service is removed from shipment automatically. This service is not present in hand-over protocol. The use of service is subject to previous agreement with the sales manager of Geis. 3.5 Verication 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 specication 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 58

67 GEIS Group 3.5 Verication cargo to the Geis IT department and any possible deciencies shall be communicated immediately with the technical contact of the client. Never send testing data directly to the FTP server! If not specied otherwise, the client s underlying documents are subject to the following requirements: ˆ They consist of an export le 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 les 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 verication of the correctness of testing data, actual identiers 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 identiers 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 identiers. 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 le generated by the client s IS. The client shall send the export le (see the section 3.6 Go live). to the Geis FTP server. Moreover, he will send all shipment numbers from the rst export le 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! 59

68 GEIS Group 3.6 Go live 3.6 Go live What is optimal during the go live procedure is to send the export le 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 le 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 What is anticipated is the sending of a single le per day but as specied in the section 3.1.2, several les may be sent. 60

69 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 Conrmed delivery note TC Phone number (see the section ) 61

70 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

71 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

72 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