InterfazPlatino-Version 1 41

Point Of Sale
Interface Specification
for Back Office third parties
Version 1.41
Last modification: Junio 2015
Copyright Gilbarco Latin America

All Rights Reserved
PLatino POS
Interface Specification PLatino and Back Office third parties
Table of Contents
1
2
Version Control.................................................................................................................. 5
Introduction ........................................................................................................................ 6
2.A
A Brief introduction ............................................................................................................................... 6

2.A.1 Purpose and scope ..................................................................................................................... 6
2.A.2 XML Background and references ................................................................................................ 6
2.A.3 XML vs. TXT size ........................................................................................................................ 6
XML Operations ..................................................................................................................................... 8
2.B.1 Data export ................................................................................................................................. 8
2.B.2 Data import ................................................................................................................................. 8
2.B.3 Error manipulation for input files .................................................................................................. 8
2.B.3.1 Error file ......................................................................................................................... 8
2.B.4 File names .................................................................................................................................. 9
2.B.5 Share folders .............................................................................................................................. 9
2.B
XML file specification ..................................................................................................... 12
3.A
Data Types ........................................................................................................................................... 14
Output files: POS to BO.................................................................................................. 15
4.A
Sales transactions ............................................................................................................................... 15

4.A.1 Pos_information ........................................................................................................................ 15
4.A.2 trans ......................................................................................................................................... 15
4.A.2.1 item .............................................................................................................................. 17
4.A.2.1.1 tax.................................................................................................................................. 18
4.A.2.2 tender........................................................................................................................... 19
4.A.2.2.1
4.A.2.2.2
4.A.2.2.3
4.A.2.2.4
4.A.2.2.5
4.A.2.2.6
4.A.2.2.7
4.A.2.2.8
4.A.2.2.9
4.B
4.C
4.D
4.E
4.F
4.G
check ............................................................................................................................. 19
account.......................................................................................................................... 19
credit_card..................................................................................................................... 19
efleet.............................................................................................................................. 20
axion_card ..................................................................................................................... 20
delivery_notes ............................................................................................................... 21
total_tax......................................................................................................................... 21
customer_tax_config ..................................................................................................... 21
additional_data .............................................................................................................. 21
Cash Drop ............................................................................................................................................ 24

4.B.1 Pos_information ........................................................................................................................ 24
4.B.2 drop .......................................................................................................................................... 24
4.B.2.1 detail ............................................................................................................................ 24
Filling Detail ......................................................................................................................................... 26
4.C.1 Pos_information ........................................................................................................................ 26
4.C.2 filling ......................................................................................................................................... 26
4.C.2.1 tank .............................................................................................................................. 27
Filling Summary................................................................................................................................... 28
4.D.1 Pos_information ........................................................................................................................ 28
4.D.2 filling ......................................................................................................................................... 28
4.D.2.1 data .............................................................................................................................. 28
Tank Product Inventory ....................................................................................................................... 30
4.E.1 Pos_information ........................................................................................................................ 30
4.E.2 tank........................................................................................................................................... 30
Cashier Statistics ................................................................................................................................ 31
4.F.1 pos_information ........................................................................................................................ 31
4.F.2 cashier ...................................................................................................................................... 31
Endings ................................................................................................................................................ 33
4.G.1 Pos_information ........................................................................................................................ 33
4.G.2 endings ..................................................................................................................................... 33
Input files: BO to POS ..................................................................................................... 35
5.A
Customers ........................................................................................................................................... 35
5.A.1 update ...................................................................................................................................... 35
Version 1.41
Page 2 of 91
PLatino POS
5.B
5.C
5.D
5.E
5.F
5.A.1.1 tax_config ..................................................................................................................... 36

5.A.1.2 patent_config ................................................................................................................ 36
5.A.2 delete........................................................................................................................................ 37
Products............................................................................................................................................... 38
5.B.1 single ........................................................................................................................................ 38
5.B.1.1 barcode ........................................................................................................................ 39
5.B.1.2 tax ................................................................................................................................ 39
5.B.2 combo....................................................................................................................................... 39
5.B.2.1 barcode ........................................................................................................................ 40
5.B.2.2 item .............................................................................................................................. 41
5.B.3 grouped .................................................................................................................................... 41
5.B.3.1 item .............................................................................................................................. 42
5.B.4 fuel ........................................................................................................................................... 42
5.B.4.1 tax ................................................................................................................................ 43
5.B.4.2 Manual Fuels ................................................................................................................ 44
5.B.5 Telephone_pin .......................................................................................................................... 44
5.B.5.1 tax ................................................................................................................................ 45
5.B.6 Motorway/Freeway Unique Daily Pass ...................................................................................... 45
5.B.6.1 tax ................................................................................................................................ 47
5.B.7 enable....................................................................................................................................... 47
5.B.8 disable ...................................................................................................................................... 47
5.B.9 delete........................................................................................................................................ 47
Concepts.............................................................................................................................................. 48
5.C.1 paid_in_out ............................................................................................................................... 49
5.C.2 credit_debit ............................................................................................................................... 50
5.C.2.1 tax ................................................................................................................................ 50
5.C.3 enable....................................................................................................................................... 51
5.C.4 disable ...................................................................................................................................... 51
Categories............................................................................................................................................ 52
5.D.1 update ...................................................................................................................................... 52
5.D.2 delete........................................................................................................................................ 52
Price Changes ..................................................................................................................................... 55
5.E.1 product ..................................................................................................................................... 55
5.E.1.1 combo_item .................................................................................................................. 55
5.E.1.2 price_level .................................................................................................................... 56
Special Price List ................................................................................................................................. 57
5.F.1 update ...................................................................................................................................... 57
5.F.1.1 special_price ................................................................................................................ 57
5.F.1.1.1
5.F.1.1.2
5.F.2
delete........................................................................................................................................ 60
5.F.2.1 special_price ................................................................................................................ 60
5.F.2.1.1
5.F.2.1.2
5.G
product .......................................................................................................................... 59
category......................................................................................................................... 60
product .......................................................................................................................... 60
category......................................................................................................................... 61
Bonus Buy Promotions ....................................................................................................................... 64

5.G.1 TransmissionHeader ................................................................................................................. 64
5.G.2 ComboMaintenance .................................................................................................................. 64
5.G.2.1 CBTDetail ..................................................................................................................... 64
5.G.2.1.1 Promotion ...................................................................................................................... 65
5.G.2.1.2 ComboList ..................................................................................................................... 65
5.G.2.1.2.1 ComboItemList ................................................................................................ 65

5.G.3
ItemListMaintenance ................................................................................................................. 66
5.G.3.1 ILTDetail ....................................................................................................................... 66
5.G.3.1.1 ItemListEntry ................................................................................................................. 67
5.G.3.1.1.1 ItemCode .......................................................................................................... 67

5.G.4
MixMatchMaintenance .............................................................................................................. 67
5.G.4.1 MMTDetail .................................................................................................................... 68
5.G.4.1.1 Promotion ...................................................................................................................... 68
Version 1.41
Page 3 of 91
PLatino POS
5.G.4.1.2 MixMatchEntry ............................................................................................................... 68
5.H
5.I
Special Price List (backward compatibility) ....................................................................................... 69

5.H.1 update ...................................................................................................................................... 69
5.H.1.1 product ......................................................................................................................... 69
5.H.2 delete........................................................................................................................................ 71
Tax by Province ................................................................................................................................... 72
5.I.1
update ...................................................................................................................................... 72
5.I.1.1 data .............................................................................................................................. 72
5.I.1.1.1
5.J
5.K
Variant ........................................................................................................................... 72
Account................................................................................................................................................ 74
5.J.1 update ...................................................................................................................................... 74
5.J.1.1 subaccount ................................................................................................................... 74
5.J.2 new_balance............................................................................................................................. 75
5.J.2.1 subaccount ................................................................................................................... 75
5.J.3 new_balance (backward compatibility with Version 1-16-5)........................................................ 75
5.J.4 disable ...................................................................................................................................... 76
5.J.4.1 subaccount ................................................................................................................... 76
Transactions ........................................................................................................................................ 77
5.K.1 update ...................................................................................................................................... 77
5.K.1.1 item .............................................................................................................................. 78
5.K.1.1.1 tax.................................................................................................................................. 78
5.K.1.2 tender........................................................................................................................... 79
5.K.1.2.1 account.......................................................................................................................... 79
5.L
5.M
5.N
5.O
Account-Product Restriction .............................................................................................................. 80

5.L.1 update ...................................................................................................................................... 80
5.L.1.1 product ......................................................................................................................... 80
5.L.2 delete........................................................................................................................................ 80
5.L.2.1 product ......................................................................................................................... 80
Currency Rate ...................................................................................................................................... 82
5.M.1 update ...................................................................................................................................... 82
Banks ................................................................................................................................................... 82
5.N.1 update ...................................................................................................................................... 82
Payments eFleet .................................................................................................................................. 83
5.O.1 insert......................................................................................................................................... 83
Apendix A: Table of Constant Values ................................................................................... 84

A.1
Modules ............................................................................................................................................... 84
Apendix B: Combo Examples ................................................................................................ 85

B.1
B.2
B.3
Saletrans .............................................................................................................................................. 85
Products............................................................................................................................................... 87
Price Changes ..................................................................................................................................... 87
Apendix C: NAXML Promotions Examples .......................................................................... 88

C.1
C.2
Combo Promotion ............................................................................................................................... 88

NAXML Mix & Match Promotion.......................................................................................................... 90
Version 1.41
Page 4 of 91
PLatino POS
1 Version Control
Date
27/03/2014
18/06/2014
01/07/2014
13/03/2015
16/06/2015
Version 1.41
Document Version
1.37
1.38
1.39
1.40
1.41
Actual Platino Version

6.0.0.3
6.0.7
1.0.3
7.0
7.0
Version from Platino

Corporate 5
Corporate 6
AXION PY
Axion Main
Axion Main
Page 5 of 91
PLatino POS
2 Introduction
2.AA Brief introduction
2.A.1 Purpose and scope
The goal of this document is to specify the Gilbarco Latin America standard unique interface
specification between PLatino POS and any Back Office third parties.
This document includes the XML file specifications with its corresponding data for the PLatino/Back
Office interface.
This document does not include any program or parser specification to read the XML files.
2.A.2 XML Background and references

XML is the Extensible Markup Language. It is designed to improve the functionality by providing more
flexible and adaptable information identification. It is called extensible because it is not a fixed format like HTML
(a single, predefined markup language). Instead, XML is actually a metalanguage, in other words, a language
for describing other languages that lets you design your own customized markup language for limitless different
types of documents.
The following are some advantages by using XML:
New standard for interfaces

Is platform and system independent
Easy to understand (it is human-legible and clear)
It allows you to define your own data structure
Many existing tools and parsers to manage it
It is easier to exchange documents among users and applications
Supports advanced searching
Backward Compatibility New version support
XML applications support many document encoding (Unicode)
For more information about XML you can visit the following sites:
http://www.xml.org
http://www.xml.com
http://www.w3.org
2.A.3 XML vs. TXT size

In order to show the different file sizes between these two kinds of formats, many tests have been done
using the products file specification with common data.
It has taken a TXT file format with a fixed length record.
The first test has been performed with 100 products for each case:
The size of the uncompressed TXT file is 21300 bytes

The size of the uncompressed XML file is 20821 bytes
In this case the XML size is less than the TXT file, but it could occur the inverse.
Version 1.41
Page 6 of 91
PLatino POS
The XML file compressed with WinZip (normal compression) resulted in 386 bytes. The compression
ratio was 98.15 %, i.e. the new zip file occupied 1.85 % of the original XML file.
The second test has been performed with 50 transactions (the most typical) for each case:
The size of the uncompressed TXT file is 37898 bytes

The size of the uncompressed XML file is 40726 bytes
In this case the TXT size is less than the XML file, but it could occur the inverse.
The XML file compressed with WinZip (normal compression) resulted in 857 bytes. The compression
ratio was 97.90 %, i.e. the new zip file occupied 2.10 % of the original XML file.
The conclusion is that there is not much difference respecting the size between an XML and a TXT file.
Besides, the compression ratio is always big enough to reduce considerably the whole file size.
Version 1.41
Page 7 of 91
PLatino POS
2.B XML Operations

2.B.1 Data export
There is an active process to export data that will write the XML files at a predefined moment.
2.B.2 Data import

There is an active process to import data that will be checking for new files. Depending on file type, the import
process could have different treatment, which allows records to be updated individually. It is possible to create,
delete or modify a record depending on the XML file specified. Some files do not allow a delete action, but in
some cases they allow data to be enabled or disabled.
The import files are not differentiated as master or update files. The actions to be performed are for
individual records (or elements) and are described by the element names:
update: This action will create a new data record in the database if it does not exist in the system.
This action will modify a data record in the database if it does exist in the system.
delete: This action will delete a data record in the database.
enable: This action will enable a data record in the database.
disable: This action will disable a data record in the database.
2.B.3 Error manipulation for input files

During the import process at the POS, it is possible that some error can occur. When this happen, an error file
is generated for each import file that caused an error.
When one of the following cases occurred, an XML error file is generated:
A required attribute does not appear in the XML file.

An attribute name does not match the specification.
An attribute value is incorrect or does not correspond with the type or size specified.
It is worth noting that if the first error is encountered for one element in the file, the whole record will be
rejected. Therefore, if there exists more than one error for the same element (e.g. two incorrect attributes
names), only the first error will be considered.
2.B.3.1
Error file
The error file is compound by:
A root element with the name errores.

Elements that are copies of the elements that caused the errors. Each of these elements has added a
new attribute named error where its content is the error description.
This is an example of an error file for categories:
<errores>
<update id=101 desc=Drinks level=5 error =Invalid level. It is allowed between 1 and 4. />
</errores>
Version 1.41
Page 8 of 91
PLatino POS
2.B.4 File names

Both input and output files must have unique names. For this purpose, it was defined in the following way:
Input File: NNNN_XXXXXXXXCCCYYYYMMDDHHMMSS.xml
Output File: XXXXXXXCCCYYYYMMDDHHMMSSVVV.xml
NN..NNN
_
XXXXXXXX
CCC
YYYYMMDD
HHMMSS
VVV
= Store identifier (variable character length), this must be the Platino Local Store.
= Seperator
= Data type name to distinguish the information that will be processed (8 characters)
= These 3 characters are for possible recognition of different vendors.
= Date creation (YYYY = Year, MM = Month, DD = Day) (8 characters)
= Time creation (HH=Hour, MM=Minutes, SS=Seconds) (6 characters)
= These 3 characters are for possible recognition of different version.
Note:
Creation Date & Time will be used to validate the moment of the importation to Platino.
To be imported Creation date & time should be smaller than the current date & time set in Site Master Server.
2.B.5 Share folders

PLatino POS will have two folders to receive and transmit files with a Back Office: Input and Output.
In \ZeusData\Input\ folder the POS application will be waiting for input files deposited by the Back
Office. In \ZeusData\Output\ folder the POS application will be writing the output files to be taken by the Back
Office. These folders must be shared with the Back Office.
The structure within the Input directory is depicted in the figure:
Version 1.41
Page 9 of 91
PLatino POS
Platino has the opcion to expect a ZIP file with all the input
files.
Input
In that case when the ZIP file is left, Platino will detect it
automatically and move it to a temporary folder
\Input\Pendientes
where
the
xmls
should
be
decompressed in the \Input folder and the zip file should
be moved to \Input\Zip in its corresponds YYYYMM folder.
Procesados
200502
If this option is not set, the Back Office should leave all the
input xmls files in the \Input folder together.
Then the xmls are processed with a logical order as it is
today.
200503
Originales
When a xml is processed, any of these possibilities can take

place:
200502
1) The xml file has no error

The original file is moved to the \Input\Originales
folder in its corresponds YYYYMM folder
A New file is created in \Input\Procesados folder in
its corresponds YYYYMM folder.
200503
Errores
2) The input file has some elements with errors and others
without errors
A new file is created in \Input\Procesados folder in
its corresponds YYYYMM folder
A new file is created in \Input\Errores It contains the
original elements that caused an error during the
import process, where each element has a new
subelement error with a message(added by the
interface)
3) The input file has only elements with errors
A new file is created in \Input\Errores It contains the
original elements that caused an error during the
import process, where each element has a new
subelement error with a message(added by the
interface)
200502
200503
Pendientes
ZIP
200502
200503
In case of using the ZIP file option the mask of the ZIP file will be:
XXXXXXXXCCCYYYYMMDDHHMMSS.ZIP
Where:
XXXXXXXX ="ZIPINPUT"
CCC
= Vendor "SAP"
YYYYMMDD
= Creation Date
HHMMSS
= Creation Time
Example:
ZIPINPUTSAP20050321080912.ZIP
Version 1.41
Page 10 of 91
PLatino POS
Directories:
Procesados: It contains files with elements that were processed ok.
Original: It contains exactly the files that were putted into the Input directory.
Errores: It contains files with elements that were processed with errors.
The structure within the output directory is depicted in the figure:
Each output interface (sales, cashier statistics, cash
drop, so on) is generated through a specific batch
process set in Platino.
Output
Each process is executed after other in a specific

dependence. (i.e. first sale, then cashier statistis, then
cash drop and so on).
XMLS
200502
200503
The ZIP process should be a new one which depends

on the last interface executed in one moment.
It is understood that one moment could be a shift or a
day close.
The ZIP file should be generated in \Output and then the XMLS should be moved \Output\XMLS folder in its
corresponds YYYYMM folder
The mask of the ZIP file should be:
XXXXXXXXCCCYYYYMMDDHHMMSS.ZIP
Where:
XXXXXXXX ="ZIPOUPUT"
CCC
= Vendor "SAP"
YYYYMMDD
= Creation Date
HHMMSS
= Creation Time
Example:
ZIPOUTPUTSAP20050321080912.ZIP
Version 1.41
Page 11 of 91
PLatino POS
3 XML file specification

The following is a description for an XML file specified in this document. It can be taken like an example.
/------------------------------------------------------------ BEGINNING -------------------------------------------------------------------\
1.C A Subject to understand the data information in the file

File: name
(This word will be replaced in the XXXXXXXX part of the file name.
See section File names )
Root element: root_name
(This word is the name of the root element of the XML file)
1.C.1 Element
(This word is the tag of an element of the first level)
Attribute Name
Type /
Size
Possible Values
Description
attribute_name1
attribute_nameN
Amount of elements: (Indicates how many elements can be repeated)
Validation: (Indicates that the POS will check the data described in this sentence)
\----------------------------------------------------------------- END ------------------------------------------------------------------------/
The following is the meaning of each column showed above.
Attribute Name: Is the name of the attribute in the element. The keys are represented in bold format.
A key is the attribute that uniquely identifies data.
Type/Size: Is the type and size of the attribute value. See section Data Types.
Possible Values: Values allowed for the attribute. The word Any means that any value for the
corresponding attribute type and size is permitted.
Description: A short description of the attribute meaning.
Notes:
There is a column named Required? in each element specification to inform whether the attribute is
optional (value No) or mandatory (value Yes). This is only valid for input files.
Version 1.41
Page 12 of 91
PLatino POS
Certainly, some files contain sub-elements for some elements. Therefore, a sub-element is specified in
the same way as the element depicted above but incrementing the index level number, which indicates
the level it occupies in a tree hierarchy.
An attribute can appear in any position inside the element. This means that the attributes position is
unordered.
An element without sub-elements can appear in two ways:

1. The element is closed by one slash at the end (before > sign).
Example: <example attribute1=test attribute2=testing / >
2. The element is closed like an element with sub-elements.
Example: <example attribute1=test attribute2=testing >
</example>
Therefore, the parser can be prepared to manipulate an element without sub-elements in both ways.
Version 1.41
Page 13 of 91
PLatino POS
3.A Data Types

To determine the information that can be used in this interface and also to avoid data errors, it has
defined the list of data type with its corresponding values to be used.
Padding of blanks or zeros is not necessary.
Data Type
Letter to
represent
data type in
the element
specification
Length
Type
Description
An integer number with sign.

Integer
Variable
A type I n mean an integer number with

a maximum of n digits.
Examples
I 4: 0
I 4: -1
I 4: 8371
A real number with sign. It has both an

integer and decimal part.
Real
Variable
R 1,2: 0
A type R n,m mean a real number with a R 1,2: 1.83
R 8,3: 45.912
maximum of n digits for the integer part
R 3,3: -120
and a maximum of m digits for the
decimal part.
A chain of alphanumeric characters.

The same as String.
Alphanumeric
Variable
A type A n mean a string with a
maximum of n characters.
A 11: Hello
A 11:Hello world
Date
Fixed
(10 characters)
A date with format DD/MM/YYYY

D 10: 27/10/2001
(DD = Day, MM = Month, YYYY = Year) D 10: 01/12/2005
Time
Fixed
(6 characters)
A time with format 24 hour HHMMSS

(HH=Hour, MM=Minutes, SS=Seconds)
T 6 : 235959
T 6 : 000001
Fixed
(1 character).
A logical value.
The attribute can be thought as a
question. For example an attribute
named cancelled, think as Is
cancelled ?
There are two possible values: Y or N.
A value of Y means Yes or True.
A value of N means No or False.
L 1: Y
L 1: N
Logical
Version 1.41
Page 14 of 91
PLatino POS
4 Output files: POS to BO

4.A Sales transactions
This file contains the sales transactions.
Each transaction always includes all the hierarchy of products that depends on the main products sold
(which are showed in the ticket), i.e. every product with its components, and the components of the component,
and so on.
If the transaction were cancelled (attribute cancelled = Y), then both elements item and tender would not
appear in the trans element. Therefore, it will only be compound by trans element attributes. The total_amount
attribute will be equal to 0 (zero).
File: saletran
Root element: sales_transactions
4.A.1 Pos_information
Attribute Name
Pos_version
Type /
Size
A 30
Possible Values
Description
Platinos version
Any
Amount of elements: one
4.A.2 trans
These attributes have general transaction information.
Attribute Name
Node
Id_trans
pos
trans_type
business_date
gen_date
gen_time
Version 1.41
Type /
Size
A 15
I 18
I5
A 10
D 10
D 10
T6
Possible Values
Any
1 999999999999999999
1 99999
sale
refund
delivnote
paidin
paidout
debit
credit
invoicedelivery
invoicedelivery_flt
billingInAdvance
refundUnAdvance
payments
refund_delivnote
refund_paidin
refund_paidout
Any valid date
Any valid date
Any valid time
Description
Store identifier
Transaction identifier. It is unique by POS.
POS identifier
Indicates what type of transaction it is.
Date for the business

Date at the moment of end transaction
Time at the moment of end transaction
Page 15 of 91
PLatino POS
id_cashier
A 15
Any
cashier_name
id_issuer
A 30
A 10
Any
Any
fiscal_doc_type
A 10
series_num
fiscal_doc_num
A 15
I 18
See table
Fiscal document
Any
1 999999999999999999
0,0 99999999999999,9999
0,0 99999999999999,9999
0,0 99999999999999,9999
net_amount
total_amount
total_tax
cashier_relative_shift_id
R 14,4
R 14,4
R 14,4
I5
cashier_absolute_shift_id
I5
Any
main_group_abs
I5
Any
main_group_rel
I5
Any
id_initial_day
I 18
Any
id_initial_day_abs
I 18
Any
voided
L1
Y, N
cancel_conc_id
I 10
0 9999999999
cust_num
I 18
1 999999999999999999
cust_comm_name
tic
A 50
A 20
Any
tic_type
A5
See Table TIC Type
tax_payer
A4
See table Tax Payer
origin
A 20
pos
Version 1.41
Any
Any
Store operator identifier (system user id) who

made the transaction
Store operator name (system user name)
Issuer number. It is the POS identification
number issued by the Tax Bureau Agency of the
country.
Fiscal document type
Number Series Fiscal documente Type
Fiscal document number. It depends on
fiscal_doc_type.
It can never be zero, even though the
transaction had been cancelled.
Important: this number can be repeated for a
fiscal_doc_type (certainly, for different
fiscal_doc_type too).
This is possible if any of the following happen:
1) The printers fiscal memory is filled and
must be changed.
2) The fiscal printer must be replaced.
= Total_amount Total_tax Exempt_amount
Total amount of the transaction
Total tax for the transaction
Cashier Shift ID relative to the current Business
day (Cashier Module Ending)
Unique shift ID for Cashier (Cashier Module
Ending)
Unique shift ID for Main Group (Shop Module
Ending)
Main Group Shift ID relative to the current
Business day (Shop Module Ending)
Shop DAY period ID relative to the current
Month (Shop Module Ending)
Unique shop DAY period ID (Shop Module
Ending)
Notifies whether the transaction was voided or
not.
Values:
Y = transaction voided
N = transaction not voided
Cancellation concept identifier, which
corresponds to the id attribute in the Concepts
file
Unique customer identifier in the whole system.
In case of Temporal Customer then value = -1
Customer name or commercial name
Tributary identifier code of the customer
It is recommended to use customer_tax_config
tag instead of.
Tributary identifier Type.
tag instead of.
Tax payer.
tag instead of.
Indicates who generated the transaction.
Page 16 of 91
PLatino POS
compl_inv_close
auto_invoice_maker
manual
L1
Y, N
cash_drawer
rev_trans
I5
I 18
1 99999
1 999999999999999999
Values:
pos: it was generated by a normal sale at the
pos.
compl_inv_close: it was generated by a period
close. It is a complement invoice.
auto_invoice_maker: It was generated by the
auto invoice maker.
Notifies whether the transaction was manual or
automatic
Cash Drawer Identifier
Transaction identifier reverse
rev_pos
I5
1-99999
Pos identifier reverse
split_category
I1
Any
BOS/HOS category to split sales transactions.
fiscal_auth
A 30
Any
fiscal_auth_expire
D 10
Any valid date
Depending on the fiscal document type and tax

regulations
Fiscal authorization code (ARG -> CAI )
Depending on the fiscal document type and tax
regulations
Fiscal authorization code expire date
Customer address steet
Customer address city
Total Exempt Amount for the transaction, these
are the tax free items
Control Code of transactions, if request by any
country. Fiscal code to be printed in the ticket.
Car Number Patent
Nationality of the Car
cust_address_street
cust_address_city
exempt_amount
A 50
A 50
R 14,4
Any
Any
control_code
A 20
Any
patent
nationality_car
A 15 Any
A 50 Any
0,0 99999999999999,9999
Amount of elements: There is no specified limit

4.A.2.1
item
This is the information of the product sold. If the product type is combo, there will not be any tax element.
Attribute Name
id
type
Type /
Size
A 16
A1
Possible Values
Any
S, C, G, F, P, O
seq_number
I5
Any
parent_seq_number
I5
Any
Version 1.41
Description
Product (or item) identifier
Product type
Values:
S = Single
C = Combo
G = Grouped
F = Fuel Automatic
P = PaidIn or PaidOut
O = Credit / Debit
Sequential number assigned to each item
included in the transaction
0 the product belongs to the first level, which
are printed in the ticket
<> 0 the product is a component of the
Page 17 of 91
PLatino POS
quantity
price_orig
R 18,6
R 18,4
Any
Any
price
line_amount
tax_amount
R 18,4
R 18,4
R 18,8
Any
Any
Any
0 - 99999999999999999999
barcode
A 20
desc
A 50
Any
exempt_amount
R 18,8
Any
total_tax_amount
R 18,8
Any
net_amount
R 18,8
Any
I5
Any
A 15
Any
R 18,4
Any
special_price_list_id
promotion_id
discount_amount
manual_fuel_selected
A3
discount_reason_code A16
YES / NO
Any
product associated with the parent_seq_number

Quantity of sold products
Price original per unit of the product with tax
included
Price per unit of the product with tax included
(price * quantity)
It is the sum of all taxes(per unit) applied to the
item.
It is equal to the sum of the amount attribute of
all tax subelements related with this item
(through the sequence number).
Barcode number used to identify the product.
It is empty in case that no barcode was entered
to find the product.
Barcode description for the item If the product
was selected through a barcode number.
Otherwise, it is the product description that is
shown on the POS.
Total Exempt Amount for the transaction, these
are the tax free items
It is the sum of all taxes applied to the item.
It is equal to the sum of the total_amount
attribute of all tax subelements related with this
item (through the sequence number).
= line_amount total_tax_amount
exempt_amount
Special Price list identifier applied to the item
into the transaction. (if any)
One special price list can have more than one
promotions
This id is the promotion id linked to the special
price list id applied to the item into the
transaction
Value of the discount applied to the item into the
transaction
No => fuel data input was provided by Pump
Controller Online output.
Yes => fuel data input was provided manually by
POS operator. This does not mean that Pump
Controller was OFFLINE.
It is the discount reason code.
4.A.2.1.1 tax
Taxes are only applied to single or fuel products.
Attribute Name
Id
amount
taxable_amount
total_amount
Version 1.41
Type /
Size
A5
R 18,8
R 18,8
R 18,4
Possible Values
See table Tax types
Any
Any
Any
Description
Tax identifier
Tax amount per unit for the item
Taxable amount
Total amount for the Item rounded to the local
Page 18 of 91
PLatino POS
currencys fraction digits.

Amount of elements: One element per tax identifier.
Note:
4.A.2.2
If an item is exempt (it has no taxes), the tax element will not be present for the item.
In case that the transaction had only exempt items, both net_amount and total_amount attributes will
be equal.
tender
Attribute Name
type
currency
amount
amount_not_returned
rate
Type /
Size
A 10
A 15
R 14,4
Possible Values
Description
See table Tender type
Tender type identifier

Currency.
Total amount of the transaction for this tender
type
Amount not returned to type of payment that not
accept cash back.
Value that corresponds to a unit (one) in the
local currency.
See Table Currency

Any
R1
Any
R 14,4
Any
4.A.2.2.1 check
This element will only appear if the tender type is a check.
Attribute Name
number
bank
issue_date
payable_date
Type /
Size
A 16
A 15
D 10
D 10
Possible Values
Any
See table Banks
Any valid date
Any valid date
Description
Check number
Bank code
Issue date
This attribute will come if configured on the POS
4.A.2.2.2 account
This element will only appear if the tender type is a local/global account.
Attribute Name
subaccount
Type /
Size
R 4,0
Possible Values
Any
Description
Subaccount ID

4.A.2.2.3 credit_card
This element will only appear if the tender type is a credit card.
Attribute Name
type
Version 1.41
Type /
Size
A 50
Possible Values
Any
Description
Type of credit card: VISA, AMEX.
Page 19 of 91
PLatino POS
number
A 50
batch_id
I4
1 - 9999
voucher_num
I6
1 999999
terminal_id
card_acceptor_code
A 30
A 30
Any
Any
Any
This information is provided by the Card

Processor
number credit card. This information is provided
by the Card Processor
Batch id from where the credit card transaction
belongs to.
Processor.
Credit card ticket number.
Processor.
Terminal id
Card acceptor code code

4.A.2.2.4 efleet
This element will only appear if the tender type is a efleet.
Attribute Name
id_contract
Type /
Size
I5
Possible Values
Description
1 - 99999
Identification number of contract
id_account
I5
1 -99999
Identification number of account
device_type
A1
A, T
Device Type
Values
A = Anillo
T = Tarjeta
id_device
A 30
Any
Device Number
odometer
A10
Any (accept null)
Odometer
license_plate
A15
Any (accept null)
License Plate
4.A.2.2.5 axion_card
This element will only appear if the tender type is an axion card.
Attribute Name
Type
Type /
Size
A 50
Pan
A 50
Any
authorization_code
A 50
Any
(Ex: 123456 B)
Voucher
A 30
Any
(Ex: 638)
terminal_id
I 18
descripcion_cliente
A 50
Any
(Ex: 2)
Any
Version 1.41
Possible Values
AXIONCARD
Description
This description is equal to system description of
payment in Platino.
number Axion card. This information is provided
by the Card Processor, but only itll save the last
4 numbers.
Authorization code where the credit card
transaction is approved.
Processor.
Axion card ticket number.
Processor.
Terminal id
Processor.
Page 20 of 91
PLatino POS
direccion_cliente
A 50
Any
cuit_cliente
A 50
Any

Processor.
Processor.
4.A.2.2.6 delivery_notes
Attribute Name
Node
Pos
id_trans
Type /
Size
A 15
I5
I 18
fiscal_doc_type
A 10
id_issuer
A 10
fiscal_doc_num
I 18
Possible Values
Any
1 99999
1
999999999999999999
See table
Fiscal document
Any
1
999999999999999999
Description
Node identifier. It is unique by HO
POS identifier
country.
fiscal_doc_type.
4.A.2.2.7 total_tax
Transaction Tax Summary
Attribute Name
Id
total_amount
Type /
Size
A5
R 18,4
Possible Values
See table Tax types
Any
Description
Tax identifier
Total amount for the transaction
4.A.2.2.8 customer_tax_config
This is the tax configuration for the customer.
Attribute Name
fiscal_group
tax_payer
id_fiscal_number
tic_type
Type /
Size
A 15
A4
A 30
A5
Possible Values
See table Fiscal group
See table Tax Payer
Any
See Table TIC Type
Description
Fiscal group
Tax payer identifier
Fiscal identifier number
Tributary identifier Type
4.A.2.2.9 additional_data
Attribute Name
Odometer
Version 1.41
Type /
Size
A 50
Possible Values
Any
Description
Odometer
Page 21 of 91
PLatino POS
license_plate
Driver
Observations
pago_facil_session_id
printer_serie
es_dest_propio
es_trans_propio
es_transporte
nombre_chofer
Patente
Referencia
Reffecha
Reffolio
Reftipocomp
rut_conductor
Vehiculo
A 50
A 50
A 10
A8
A 10
A 50
A 50
A 50
A 30
A6
A 50
A 50
A 15
A 50
A 10
A 50
Any
Any
Any
Any
Any
Any
Any
Any
Any
Any
Any
Any
Any
Any
Any
Any
License plate
Observations
Session Id sent by Pago Facil
Printer Number Series
Destination
Own transport
Buying transport
Driver Name
License plate
Reference code
Reference Date
Reference - Folio Number
Reference Type of receipt
Driver rut
Vehicle type
Examples:
<sales_transactions>
<pos_information Pos_Version="Platino-EM-3.3bG.1.1" />
<trans node="0001" id_trans="174" pos="10" trans_type="sale" business_date="20/10/2005"
gen_date="20/10/2005" gen_time="125731" id_cashier="4001" cashier_name="Cajero - Turno 1" id_issuer="0010"
fiscal_doc_type="TFA" fiscal_doc_num="1" net_amount="3.12" total_amount="5.0" total_tax="1.88"
cashier_relative_shift_id="1" cashier_absolute_shift_id="40" main_group_abs="67" main_group_rel="1"
id_initial_day_abs="232" id_initial_day="2" voided="N" cancel_conc_id="" cust_num="17"
cust_comm_name="Transp. y Serv. La Fusta Ltda." tic="50546101700" tic_type="CU" tax_payer="RI" origin="pos"
manual="N" cash_drawer="10" rev_trans="" rev_pos="" split_category="" fiscal_auth="" fiscal_auth_expire=""
cust_address_street="Ruta 57 KM 12.5" cust_address_city="Colina" exempt_amount="0.0" control_code=2H-3J6S-8J patent="1212AER" nationality_car=" Argentina" />
<item id="5" type="F" seq_number="1" parent_seq_number="0" quantity="4.332756" price_orig="1.154"
price="1.154" line_amount="5" tax_amount="0.43428674" barcode="" desc="Esso GasOli"
exempt_amount="0.0" total_tax_amount="1.88" net_amount="3.12" manual_fuel_selected="NO">
<tax id="ITCGASOIL" amount="0.15" taxable_amount="0.71971326" total_amount="0.65" />
<tax id="ITVGASOIL" amount="0.13314695" taxable_amount="0.71971326"
total_amount="0.58" />
<tax id="IVATG" amount="0.15113978" taxable_amount="0.71971326" total_amount="0.65" />
</item>
<tender type="1" currency="PESOS_ARG" amount="5" rate="1" />
<total_tax id="ITCGASOIL" total_amount="0.65" />
<total_tax id="ITVGASOIL" total_amount="0.58" />
<total_tax id="IVATG" total_amount="0.65" />
<customer_tax_config fiscal_group="IVA" tax_payer="RI" id_fiscal_number="50546101700"
tic_type="CU" />
<additional_data patente="AA2123" />
<additional_data rut_conductor="78299930-3" />
<additional_data vehiculo="MOTO" />
</trans>
</sales_transactions>
<trans node="0001" id_trans="177" pos="10" trans_type="sale" business_date="20/10/2005"
gen_date="20/10/2005" gen_time="130327" id_cashier="4001" cashier_name="Cajero - Turno 1" id_issuer="0010"
Version 1.41
Page 22 of 91
PLatino POS
fiscal_doc_type="TFB" fiscal_doc_num="136" net_amount="6.01" total_amount="7.27" total_tax="1.26"
cashier_relative_shift_id="1" cashier_absolute_shift_id="40" main_group_abs="67" main_group_rel ="1"
id_initial_day_abs="298" id_initial_day="2" voided="N" cancel_conc_id="" cust_num="50000"
cust_comm_name="Cliente Annimo" tic="" tic_type="" tax_payer="CF" origin="pos" manual="N"
cash_drawer="10" rev_trans="" rev_pos="" split_category="" fiscal_auth="" fiscal_auth_expire=""
cust_address_street="" cust_address_city="" exempt_amount="0.0" >
<item id="302" type="S" seq_number="1" parent_seq_number="0" quantity="1" price_orig="5.2"
price="5.2" line_amount="5.2" tax_amount="0.90247934" barcode="" desc="A3 LIMPIA TAPIZADO
450cc" exempt_amount="0.0" total_tax_amount="0.9" net_amount="4.3" manual_fuel_selected="NO">
<tax id="IVAT21GD" amount="0.90247934" taxable_amount="4.29752066" total_amount="0.9"
/>
</item>
<item id="303" type="S" seq_number="2" parent_seq_number="0" quantity="1" price_orig="2.3"
price="2.07" line_amount="2.07" tax_amount="0.359256198" barcode="" desc="LAMPARAS P/AUTO
3893 x 2u" exempt_amount="0.0" total_tax_amount="0.36" net_amount="1.71" special_price_list_id="0"
promotion_id="US02XX000002" discount_reason_code=combinationOffer discount_amount="0.23"
manual_fuel_selected="NO">
<tax id="IVAT21GD" amount="0.359256198" taxable_amount="1.710743802"
total_amount="0.36" />
</item>
<tender type="39" currency="PESOS_ARG" amount="7.27" rate="1" />
<total_tax id="IVAT21GD" total_amount="1.26" />
<customer_tax_config fiscal_group="IVA" tax_payer="CF" id_fiscal_number="" tic_type="" />
<additional_data rut_conductor="78299930-3" />
<additional_data vehiculo="AUTOMOTORA" />
</trans>
See Apendix B for a Combo sale example.

Example of transaction invoice delivery efleet
<trans node="00000" id_trans="2650180" pos="1" trans_type="invoicedelivery_flt" business_date="16/09/2003"
gen_date="06/03/2013" gen_time="103208" id_cashier="7001" cashier_name="Administrativo HE"
id_issuer="0001" fiscal_doc_type="FAC_FLT" series_num="" fiscal_doc_num="27" net_amount="0.0"
total_amount="251.17" total_tax="0.0" cashier_relative_shift_id="1" cashier_absolute_shift_id="1"
main_group_abs="1" main_group_rel="1" id_initial_day="1" id_initial_day_abs="1" voided="N" cancel_conc_id=""
cust_num="2232" cust_comm_name="Rent a Car Panamea, S.A. (Avis Rent a Car)" tic="" tic_type=""
tax_payer="CF" origin="n/a" manual="N" cash_drawer="1" rev_trans="" rev_pos="" split_category=""
fiscal_auth="" fiscal_auth_expire="" cust_address_street="" cust_address_city="" exempt_amount="251.17">
<item id="2" type="F" seq_number="1" parent_seq_number="0" quantity="14.5689" price_orig="3.9900"
price="3.9900" line_amount="58.1300" tax_amount="0.00000000" barcode="" desc="Gasolina Mxima
91" exempt_amount="58.13" total_tax_amount="0.0" net_amount="0.0" special_price_list_id=""
promotion_id="" discount_amount="0.0000" manual_fuel_selected="NO"/>
<tender type="21" currency="DOLAR" amount="251.17" rate="1" amount_not_returned="0"/>
<customer_tax_config fiscal_group="IVAPA" tax_payer="CF" id_fiscal_number="" tic_type=""/>
<delivery_notes node="00000" pos="1" id_trans="1655" fiscal_doc_type="DELIVERY_FLT"
fiscal_doc_num="230331" id_issuer="9100" />
</trans>
Version 1.41
Page 23 of 91
PLatino POS
4.B Cash Drop

This file contains the cash drop(safe drop) made by the cashiers.
File: cashdrop
Root element: cash_drop
4.B.1 Pos_information
Attribute Name
Pos_version
Type /
Size
A 30
Possible Values
Any
Description
Platinos version
4.B.2 drop
These attributes have general cash drop information.
Attribute Name
node
id
Type /
Size
A 15
I 18
Possible Values
Any
1
999999999999999999
id_shift
I5
Any
pos
cash_drawer
envelope
I5
I5
I 10
1 99999
1 99999
1 - 9999999999
business_date
date
time
id_cashier
D 10
D 10
T6
A 15
Any valid date

Any valid date
Any valid time
Any
cashier_name
total_amount
A 30
R 14,4
Any
I5
Any
cashier_relative_shift_id
0,0
99999999999999,9999
Description
Store identifier
Cash drop identifier. It is unique by POS.
Unique number to identify the shift
This number is by POS.
POS identifier
Cash Drawer Identifier
Envolope identifier where the cash was
dropped.
Date at the moment of the cash drop.
Time at the moment of the cash drop.
Store operator identifier (system user id) who
made the transaction
Store operator name (system user name)
type
Cashier Shift ID relative to the current Business
day

4.B.2.1
detail
Attribute Name
currency
cashier_value
Type /
Size
A 15
A 15
Possible Values
See Table Currency
See Table
Cashier_Value
Version 1.41
Description
Currency.
Cashier_Value, these are different
representations of the currency, for example in
Page 24 of 91
PLatino POS
amount
R 14,4
rate
R 14,4
0,0
99999999999999,9999
0,0
99999999999999,9999
Argentina the Peso can be represented as

Pesos or as Patacones.
Amount dropped.
local currency.

Example:
<cash_drop>
<drop node= GLA0002 id="1" id_shift=1 pos="0" cash_drawer=1 envelope="545464"
business_date=13/06/2002 date="13/06/2002" time="15:05:43" id_cashier="ADMIN" cashier_name="ADMIN"
total_amount="300.0" cashier_relative_shift_id =7>
<detail currency="PESOS_ARG" cashier_value=PESOS amount="300.0" rate="1.0"/>
</drop>
<drop node=GLA0002 id="2" id_shift=2 pos="0" cash_drawer=1 envelope="545465"
business_date="13/06/2002" date="13/06/2002" time="15:32:24" id_cashier="ADMIN" cashier_name="ADMIN"
total_amount="384.0" cashier_relative_shift_id =8>
<detail currency="PESOS_ARG" cashier_value=PESOS amount="300.0" rate="1.0"/>
<detail currency="DOLAR" cashier_value=DOLARES amount="30.0" rate="2.8"/>
</drop>
</cash_drop>
Version 1.41
Page 25 of 91
PLatino POS
4.C Filling Detail

This file contains the details about the fillings made by the pumps.
Data would not have associated one-to-one to a sale transaction in transactions file due to many
uncontrolled sale could be a unique sale transaction.
File: filldeta
Root element: filling_detail
4.C.1 Pos_information
Attribute Name
Pos_version
Type /
Size
A 30
Possible Values
Any
Description
Platinos version
4.C.2 filling
Attribute Name
node
id
Type /
Size
A 15
I 18
Possible Values
Any
1
999999999999999999
shift_date
shift_time
business_date
date
time
pump
hose
product
type
D 10
T6
D 10
D 10
T6
I2
I1
A9
A1
Any valid date

Any valid time
Any valid date
Any valid date
Any valid time
1 99
09
Any
N, U, P
ppu
R 6,3
0,0 999.999,999
amount
volume
R 6,3
R 6,3
0,0 999.999,999
0,0 999.999,999
ini_vol_totalizer
fin_vol_totalizer
ini_amount_totalizer
fin_amount_totalizer
prepaid
R 6,3
R 6,3
R 6,3
R 6,3
L1
0,0 999.999,999
0,0 999.999,999
0,0 999.999,999
0,0 999.999,999
Y, N
Version 1.41
Description
Store identifier
Sale identifier.
This value starts from 1 for each shift
Date on which the shift started
Time on which the shift started
Date on which the sale occurred
Time on which the sale occurred
Pump identifier
Hose identifier
Product identifier
Sale type
Values:
N = Normal sale
U = Uncontrolled sale
R = Pump test with return
P = Pump test without return
Price per unit of the product.
If the type is U, the ppu could be different to the
transaction ppu.
Sale amount
This value must be equal to the sum of all
volumes in each tank sub-element
Total volume initial from dispenser meter
Total volume final from dispenser meter
Total amount initial from dispenser meter
Total amount final from dispenser meter
Notify whether the sale was prepaid or not
Page 26 of 91
PLatino POS
id_trans
I 18
id_cashier
cashier_name
A 10
A 10
1
999999999999999999
Any
Any
Values:
Y = It is prepaid
N = It is not prepaid
Transaction identifier.
It is unique by POS.
Id user
Name user

4.C.2.1
tank
Attribute Name
id
volume
product
Type /
Size
A2
N 6,3
I 15
Possible Values
1 99
0,0 999.999,999
0 999999999999999
Description
Tank identifier which was used to sell
Volume pulled from this tank
Product identifier
Example:
<filling_detail>
<filling node= GLA0002 id=10 shift_date=26/01/2001 shift_time=102000 business_date=26/01/2001
date=26/01/2001 time=091255 pump=1 hose=1 product=1 type=N ppu=1.00 amount=10.00
volume=10.00 ini_vol_totalizer=30728 fin_vol_totalizer=30738 ini_amount_totalizer=25290
fin_amount_totalizer=25300 prepaid=N id_trans=27262 id_cashier=1002 cashier_name=Cashier1>
<tank id=1 volume=5.00 product=21 />
</filling>
<filling node=GLA0002 id=11 shift_date=26/01/2001 shift_time=102000 business_date=26/01/2001
date=26/01/2001 time=091257 pump=1 hose=1 product=2 type=N ppu=0.5 amount=5.00
volume=10.00 ini_vol_totalizer=11230 fin_vol_totalizer=11235 ini_amount_totalizer=25290
fin_amount_totalizer=25300 prepaid=N id_trans=27263 id_cashier=1002 cashier_name=Cashier1>
</filling>
</filling_detail>
Version 1.41
Page 27 of 91
PLatino POS
4.D Filling Summary

This file contains the summary about the fillings made by the pumps.
File: fillsuma
Root element: filling_summary
4.D.1 Pos_information
Attribute Name
Pos_version
Type /
Size
A 30
Possible Values
Any
Description
Platinos version
4.D.2 filling
Attribute Name
node
pump
hose
main_group_abs
main_group_rel
Type /
Size
A 15
I2
I1
I5
I5
Possible Values
Any
1 99
09
Any
Any
shift_date
shift_time
product
business_date
total_volume
D 10
T6
A9
D 10
R 6,3
Any valid date

Any valid time
Any
Any valid date
0,0 999.999,999
total_amount
R 6,3
0,0 999.999,999
ini_vol_totalizer
fin_vol_totalizer
ini_amount_totalizer
fin_amount_totalizer
R 6,3
R 6,3
R 6,3
R 6,3
0,0 999.999,999
0,0 999.999,999
0,0 999.999,999
0,0 999.999,999
Description
Store identifier
Pump identifier
Hose identifier
Unique shift ID for Main Group
Main Group Shift ID relative to the current
Business day
Fuel product identifier
Total volume for the shift, pump and hose.
It is the sum of all volumes of the data element.
Total amount for the shift, pump and hose.
It is the sum of all amounts of the data element.
Total volume initial from dispenser meter
Total volume final from dispenser meter
Total amount initial from dispenser meter
Total amount final from dispenser meter
Amount of elements: There is no specified limit.
4.D.2.1
data
Attribute Name
type
Version 1.41
Type /
Size
A1
Possible Values
N, U, P
Description
Sale type.
Values:
N = Normal sale
U = Uncontrolled sale
R = Pump test with return
P = Pump test without return
Page 28 of 91
PLatino POS
amount
volume
R 6,3
R 6,3
0,0 999.999,999
0,0 999.999,999
Sale amount
Sale volume
Amount of elements: No more than three with different types.

Example:
<filling_summary>
<filling node= GLA0002 pump=1 hose=1 main_group_abs=1 main_group_rel=1 shift_date=26/01/2001
shift_time=102000 product=342 business_date=26/01/2001 total_volume=4.50 total_amount=10.00
ini_vol_totalizer=30722 fin_vol_totalizer=30726.50 ini_amount_totalizer=25290 fin_amount_totalizer=25300 >
<data type=N amount=5.00 volume=3.00 />
<data type=U amount=5.00 volume=1.50 />
</filling>
</filling_summary>
Version 1.41
Page 29 of 91
PLatino POS
4.E Tank Product Inventory

This file contains the tank product inventory.
File: tankinvt
Root element: tank_product_inventory
4.E.1 Pos_information
Attribute Name
Pos_version
Type /
Size
A 30
Possible Values
Any
Description
Platinos version
4.E.2 tank
Attribute Name
node
id
product
shift_date
shift_time
business_date
fuel_volume
Type /
Size
A 15
A2
A9
D 10
T6
D 10
R 6,3
Possible Values
Any
1 99
Any
Any valid date
Any valid time
Any valid date
0,0 999.999,999
water_volume
R 6,3
0,0 999.999,999
date
time
reading_date
reading_time
D 10
T6
D 10
T6
Any valid date

Any valid time
Any valid date
Any valid time
Description
Store identifier
Tank identifier
Fuel product identifier
Measured volume of fuel (in liters/gallons)
calculated by the system depending on the tank
calibration
Measured volume of water (in liters/gallons)
calculated by the system depending on the tank
calibration
Date of volume calculation
Time of volume calculation
Date of measures readings
Time of measures readings
Example:
<tank_product_inventory>
<tank node= GLA0002 id=1 product=7 shift_date=23/01/2001 shift_time=200000 business_date=23/01/2001
fuel_volume=1533.862 water_volume=12.036 date=23/01/2001 time=221034 reading_date=23/01/2001
reading_time=210830 />
<tank node=GLA0002 id=2 product=8 shift_date=23/01/2001 shift_time=200000 fuel_volume=2177.000
water_volume=17.330 date=23/01/2001 time=221034 reading_date=23/01/2001 reading_time=211530 />
</tank_product_inventory>
Version 1.41
Page 30 of 91
PLatino POS
4.F Cashier Statistics

This file contains the information about cashier statistics.
File: cashstat
Root element: cashier_statics
4.F.1 pos_information
Attribute Name
Pos_version
Type /
Size
A 30
Possible Values
Description
Platinos version
Any
4.F.2 cashier
Attribute Name
Type /
Size
A 15
A 15
Any
Any
cashier_name
A 30
Any
business_date
shift_date
D 10
D 10
Any valid date

Any valid date
shift_time
T6
Any valid time
sale_cancellation_qty
I 18
0 999999999999999999
node
id
sale_cancellation_amount
voided_qty
R 14,4
I 18
Possible Values
0,0 99999999999999,9999
0 999999999999999999
voided_amount
refund_qty
R 14,4
I 18
0,0 99999999999999,9999
0 999999999999999999
refund_amount
R 14,4
0,0 99999999999999,9999
items_deteled_qty
items_deleted_amount
trans_qty
trans_amount
manual_discounts_qty
Version 1.41
I 18
R 14,4
I 18
R 14,4
I 18
0 999999999999999999
0,0 99999999999999,9999
0 999999999999999999
0,0 99999999999999,9999
0 999999999999999999
Description
Store identifier
Store operator identifier
(system user id)
Store operator name
(system user name)
Date of the shift closed.
Zeros if it is generated at
the day end
Time of the shift closed.
Zeros if it is generated at
the day end
Number of cancellations
before ends
Amount in cancellations
before ends
Number of sales
transactions cancelled
Amount of sales cancelled
Number of refunds
transactions
Amount of refunds
transactions
Number of items deleted
before transaction ending
Amount of items deleted
Total quantity of sales
transactions
Total amount of sales
transactions
Times the cashier granted
Page 31 of 91
PLatino POS
manual_discounts_amount
drawer_open
R 14,4
I 18
drawer_open_amount
R 14,4
manual_overprice_qty
I 18
0,0 99999999999999,9999
0 999999999999999999
0,0 99999999999999,9999
0 999999999999999999
manual_overprice_amount
R 14,4
0,0 99999999999999,9999
safe_drop_qty
safe_drop_amount
cash_short_qty
cash_short
I 18
R 14,4
I 18
R 14,4
0 999999999999999999
0,0 99999999999999,9999
0 999999999999999999
0,0 99999999999999,9999
authorize_duplicate_safe_drop_qty
I 18
0 999999999999999999
authorize_duplicate_safe_drop_amount
R 14,4
0,0 99999999999999,9999
cash_over_qty
cash_over
I 18
R 14,4
0 999999999999999999
0,0 99999999999999,9999
a discount manually from

the POS
Amount of discount granted
manually from POS
Times that drawer was
opened and it was not a
sale
Amount of drawer was
opened and it was not a
sale
Times the cashier rised the
price manually from the
POS
Amount of manual
overprice collected from
POS
Safe drop quantity
Safe drop amount
Times of cash sort
Cash_short
To get this functionality a
login by transaction is
required but it will work if
only one generic user is
used and it is loged during
the whole period
Last cash drop functionality
should be used if not this
values will be always ceros
Times of authorize
duplicate safe dropeleted
Amount of authorize
duplicate safe dropeleted
Times of cash over
Cash over.
To get this functionality a
login by transaction is
required but it will work if
only one generic user is
used and it is loged during
the whole period
Last cash drop functionality
should be used if not this
values will be always ceros

Example:
<cashier_statics>
<cashier node="1" id="1001" cashier_name="Bombero Playa 1" business_date="27/11/2008" shift_date=""
shift_time="" sale_cancellation_qty="0" sale_cancellation_amount="0" voided_qty="0" voided_amount="0"
refund_qty="0" refund_amount="0" items_deleted_qty="0" items_deleted_amount="0" trans_qty="0"
Version 1.41
Page 32 of 91
PLatino POS
trans_amount="0" manual_discounts_qty="0" manual_discounts_amount="0" drawer_open="0"
drawer_open_amount="0" manual_overprice_qty="0" manual_overprice_amount="0" safe_drop_qty="0"
safe_drop_amount="0" cash_short_qty="0" cash_short="0" authorize_duplicate_safe_drop_qty="0"
authorize_duplicate_safe_drop_amount="0" cash_over_qty="0" cash_over="0" />
</cashier_statics>
4.G
Endings
This file contains the information about shift, day, month and year endings.
Only the SHOP module will inform Day, Month and Year endings. Other modules will refer to independent
terminal shift endings.
A Shop module shift ending refers to the event of a terminal group ending.
File: endingss
Root element: endings
4.G.1 Pos_information
Attribute Name
Pos_version
Type /
Size
A 30
Possible Values
Any
Description
Platinos version
4.G.2 endings
Attribute Name
node
type
Type /
Size
A 15
A1
Possible Values
Any
S, D, M o Y
module
terminal
id
number
day_id
A15
I5
I5
I5
I5
month_id
I5
1 99999
year_id
I5
1 99999
depending_id
business_date
open_date
open_time
end_date
end_time
operator
Version 1.41
I5
D 10
D 10
T6
D 10
T6
A15
Any valid Modules

1 99999
1 99999
1 99999
1 99999
1 99999
Any valid date
Any valid date
Any valid time
Any valid date
Any valid time
Any valid operator
Description
Store identifier
Operator (S)hift, (D)ay end, (M)onth end, (Y)ear
end
Terminal ID
End ID
Turn counter in the current period
Corresponding day period counter id, present
for type=SHIFT
Corresponding Month period counter id, present
for type=SHIFT or DAY
Corresponding Year period counter id, present
for type<>YEAR
End ID of the super period
Business Date
End opening date
End opening time
End close date
End close time
Present for Module CAJA in the case of a
Billetera
Page 33 of 91
PLatino POS

Example:
<endings>
<endings node= GLA0002 type="S" module=PLATINO terminal="5" id=23 number="2" day_id=5
month_id=3 year_id=1 depending_id="5" business_date="05/03/2003" open_date="05/03/2003"
open_time="060218" end_date="05/03/2003" end_time="150520" operator=Peter />
</endings>
Version 1.41
Page 34 of 91
PLatino POS
5 Input files: BO to POS

5.A Customers
This file contains the customers to be created, deleted or modified at the store.
File: customer
Root element: customers
5.A.1 update
This is the customer information. If the customer doesnt exist in the POS system, it will be created. Otherwise,
it will be modified.
Attribute Name
cust_number
Type /
Size
E 18
Possible Values
Required?
Description
1
999999999999999999
Yes
Customer identifier
Yes
Customer category
Yes
Customer last name or commercial

name
Customer first name
Country on which the customer was
born.
Customer commercial activity
category
A 15
last_name
A 50
See table Customer

Category
Any
first_name
nationality
A 50
A 15
Any
See table Country
No
Yes
activity_code
A 15
No
doc_type
A 50
See table Activity

Code
See table Document
Type
doc_number
birth_date
phone
A 50
D 10
I 18
Any
Any valid date
No
No
No
Document type. If the field doc_type

sent, should sent the field
doc_number also.
Document number
Birth date
Telephone number
fax
I 18
No
Fax number
address_type
A1
C, P
No
street
A 50
Any
No
Address type.
Values:
C = Commercial address
P = Particular address
Default value: P
Street name.
See note.
Street number.
See note.
Apartment floor.
See note.
Department.
See note.
Zip code.
See note.
Division name for level 3.
Example of division3 can be Locality.
0
999999999999999999
0
999999999999999999
No
number
I5
0 99999
No
floor
I3
0 999
No
department
A5
Any
No
zipcode
A 10
Any
No
division3
A 20
Any
No
Version 1.41
Page 35 of 91
PLatino POS
division2
A 20
Any
No
division1
A 15
See Table Province
No
country
A 15
See table Country
Yes
observation
special_price_list
A 200
I5
Any
0 99999
No
No
Y, N
No
enable
L1

Example of division2 can be City .
Examples of division1 can be
Province or State.
Country on which the customer
belongs to
Observations
Price list identifier.
Each customer may have one special
price list.
Values:
0 = Its a General list for any
customer.
1 99999 = Its a Special list.
Enable customer

Validation:
The price list special_price_list must exist in the system
Both doc_type and doc_number must be empty or not empty toghether.
If the attributes doc_type and doc_number are not empty, the nationality must not be empty.
Note:
Both division1 and country attributes are not required, but if one of them has value and the other has
not value, then an error will be informed. This means that both attributes must appear together with valid
values.
Besides, only when both division1 and country attributes have values, anyone of street, number, floor,
department, city and zipcode will be considered.
5.A.1.1
tax_config
This is the tax configuration for the customer.

Attribute Name
fiscal_group
tax_payer
id_fiscal_number
Type /
Size
A 15
A4
A 30
Possible Values
Required?
See table Fiscal group

See table Tax Payer
Any
Yes
Yes
No
Description
Fiscal group
Tax payer identifier
Fiscal identifier number
Amount of elements: At least one

Validation:
The attributes values of fiscal_group and tax_payer must be consistent with the table Tax Payer
5.A.1.2 patent_config
Attribute Name
cust_number
Type / Size
E 18
patent
A 15
Version 1.41
Possible Values
1 999999999999999999
Any
Any
Description
Customer identifier
Patent of the Car
Page 36 of 91
PLatino POS
nationality_car
A 50
Any
Nationality of the Car
5.A.2 delete
This customer will be deleted from the database.
Attribute Name
cust_number
country
Type /
Size
I 18
A 15
Possible Values
Required?
Description
1
999999999999999999
Yes
Customer identifier to be disabled.
See table Country
Yes
Country on which the customer

belongs to

Validation:
In eliminating customer will validate if exits patent and nationality associated. If exists one or more
patents and nationalities will eliminate all the registers.
Example:
<customers>
<update cust_number=100 category=DEFAULT last_name=Perez first_name=Juan nationality=ARG
activity_code=1 doc_type=DNI doc_number=21190283 birth_date=26/05/1970 phone=3456789 fax=
address_type=C street=Corrientes number=345 floor=2 department=A zipcode=1043 division3=San
Nicolas division2=Buenos Aires division1=BSAS country=ARG observation= special_price_list= >
<tax_config fiscal_group=IVA tax_payer=RI id_fiscal_number=12345678 enable=Y />
<tax_config fiscal_group=IB tax_payer=RI id_fiscal_number=9019115109 />
<patent_config cust_nubmer=1000 patent=1212AER nationality_car=Argentina />
<patent_config cust_nubmer=1000 patent=3456TY nationality_car=Chile />
</update>
<delete cust_number=309 country=ARG />
<delete cust_number=315 country=ARG />|
</customers >
Version 1.41
Page 37 of 91
PLatino POS
5.B Products
This file contains the products to be created, deleted or modified at the store.
File: products
Root element: products
5.B.1 single
This element defines the product to be updated.
If the product does not exist in the POS system, it will be created. Otherwise, it will be modified.
Attribute Name
id
desc
Type /
Size
A 16
A 50
Possible Values
Required?
Description
0 999999999999999
Any
Yes
Yes
ticket_desc
A 15
Any
Yes
id_tax
A 15
See table Tax

Configuration
No
price
R 14,4
Yes
cost
R 14,4
0,0
99999999999999,9999
0,0
99999999999999,9999
Product identifier
Product description to be shown on the
POS
ticket
Tax identifier that represents a group of
taxes.
Product price per unit
No
Product Cost
sale_enable
L1
Y, N
Yes
consig_indic
I 18
No
eft_code
I 15
0
999999999999999999
0 999999999999999
Enable or disable the product so that it

can be sold or not at the POS.
Values:
Y = enable
N = disable (it cannot be sold like
a single product) For example,
this option can be used for
ingredients)
Consignment indicator
No
EFT or ATOS code

Applies only to EssoCard module,
otherwise, do not send Tag.
id_categ1
A 15
Any
Yes
id_categ2
A 15
Any
No
id_categ3
A 15
Any
No
id_categ4
A 15
Any
No
unit_measure
A 15
See Table
Measurement Unit
Yes
Version 1.41
First level category.

This level is used to represent general
groups of products.
Every product must be associated to
one category at least.
Second level category. Subcategory of
id_categ1.
Third level category. Subcategory of
id_categ2.
Fourth level category. Subcategory of
id_categ3.
This level is used to represent specific
groups of products.
Unit measure valid.
Page 38 of 91
PLatino POS
icon
A 30
Any
No
id_department
A 20
See table Department
Yes
doc_category
A 15
Yes
quantifiable
L1
See table Document

Category
Y, N
manual_price
L1
Y, N
Yes
activity
I 10
0 - 999999999
No
Yes
Icon file name.

This icon will be showed in the POS for
this product. If this attribute does not
appear or is empty, a default icon will be
used.
It is the place where the product can be
sold.
Document category
Indicates if the product can be
considered in the stock
Indicates if the price can be entered
manually by the cashier
Activity Id Number
Only when the article requires individually
Activity ID Number.
5.B.1.1
barcode
It is a barcode assigned to a product, which is used to recognize the product with a scanner.
Attribute Name
number
desc
Type /
Size
A 20
A 50
Possible Values
Required?
Description
099999999999999999999
Yes
Barcode number to identify the product
Any
No
Specific description for the product with

this barcode.
5.B.1.2
tax
Special taxes assigned directly to the product that are not included in the TAX GROUP. This subelement is
optional.
Attribute Name
id_tax
Type /
Size
A5
value
R 16,8
Possible Values
099999999999999999
999
Any
Required?
Description
Yes
A valid TAX_TYPE available in Platinos

RTL_TIPO_IMPUESTO table
No
Value to be applied
5.B.2 combo
Version 1.41
Page 39 of 91
PLatino POS
Attribute Name
id
desc
Type /
Size
A 16
A 50
Possible Values
Required?
Description
0 999999999999999
Any
Yes
Yes
Product identifier
POS
ticket
Values:
Y = enable
ingredients)
ticket_desc
A 15
Any
Yes
sale_enable
L1
Y, N
Yes
consig_indic
I 18
No
eft_code
id_categ1
I 15
A 15
0
999999999999999999
0 999999999999999
id_categ2
Any
No
Yes
A 15
Any
No
id_categ3
A 15
Any
No
id_categ4
A 15
Any
No
unit_measure
icon
A 15
A 30
Any
Any
Yes
No
id_department
A 20
Yes
doc_category
A 15
Yes
Yes
quantifiable
L1
See table Document

Category
Y, N
manual_price
L1
Y, N
Yes
EFT or ATOS code

groups of products.
id_categ1.
id_categ2.
id_categ3.
groups of products.
Unit measure valid
Icon file name.
used.
sold.
Document category
Indicates if the product can be
considered in the stock
Indicates if the price can be entered
manually by the cashier
5.B.2.1
barcode
It is a barcode assigned to a product, which is used to recognize the product with a scanner.
Version 1.41
Page 40 of 91
PLatino POS
Attribute Name
number
desc
Type /
Size
A 20
A 50
Possible Values
Required?
Description
099999999999999999999
Yes
Barcode number to identify the product
Any
No
Specific description for the product with

this barcode.
5.B.2.2 item
This is a product that is part of the combo product.
Attribute Name
id
Type /
Size
A 16
qty
R 14,5
099999999999999,99999
Yes
price
R 14,4
0 - 99999999999999,9999
Yes
total_price
R 14,4
0 - 99999999999999,9999
No
F, A, O
Yes
type
A 15
Possible Values
Require
d?
Yes
0 - 999999999999999
Description
Product identifier that is part of the
combo product
Units quantity of this product component
inside the combo
Price per unit. Replaces the price that
comes with the product. If specified,
"total_price" shall not.
qty per price. If not present, Platino will
use the qty and price attributes to
manually calculate the total price of the
item in the combo.
Price type.
Values:
F = Fix
A = Additional
O = Optional
5.B.3 grouped
Attribute Name
id
desc
Type /
Size
A 16
A 50
Possible Values
Required?
Description
0 999999999999999
Any
Yes
Yes
Product identifier
POS
ticket
Values:
Y = enable
ticket_desc
A 15
Any
Yes
sale_enable
L1
Y, N
Yes
Version 1.41
Page 41 of 91
PLatino POS
consig_indic
I 18
eft_code
id_categ1
I 15
A 15
id_categ2
0
999999999999999999
0 999999999999999
No
Any
No
Yes
A 15
Any
No
id_categ3
A 15
Any
No
id_categ4
A 15
Any
No
unit_measure
icon
A 15
A 30
Any
Any
Yes
No
id_department
A 20
Yes
ingredients)
EFT or ATOS code
groups of products.
id_categ1.
id_categ2.
id_categ3.
groups of products.
Unit measure valid.
Icon file name.
used.
sold.
5.B.3.1 item
This is a product that is part of the grouped product.
Attribute Name
id
Type /
Size
A 16
Possible Values
Required?
0 - 999999999999999
Yes
Description
Product identifier that is part of the
grouped product
5.B.4 fuel
Attribute Name
id
desc
ticket_desc
grade
Version 1.41
Type /
Size
A 16
A 50
A 15
R 18,0
Possible Values
Required?
Description
0 999999999999999
Any
Yes
Yes
Any
Yes
0999999999999999999
Yes
Product identifier
POS
ticket
CEM product ID, if present the fuel is
Automatic, if not the fuel is manual.
Page 42 of 91
PLatino POS
id_tax
I5
sale_enable
L1
consig_indic
I 18
0
999999999999999999
No
Tax identifier that represent a group of

taxes.
Values:
Y = enable
ingredients)
Note: this attribute must only appear
when the type attribute has value M.
eft_code
I 15
No
EFT or ATOS code
id_categ1
A 15
0
999999999999999
Any
Yes
id_categ2
A 15
Any
No
id_categ3
A 15
Any
No
id_categ4
A 15
Any
No
unit_measure
icon
A 15
A 30
Any
Any
Yes
No
id_department
A 20
Yes
R 14,4
0,0
99999999999999,9999
No

groups of products.
id_categ1.
id_categ2.
id_categ3.
groups of products.
Unit measure valid.
Icon file name.
used.
sold.
Product Cost
A 15
See table Document

Category
Yes
Document category
cost
doc_category
See table Tax

configuration
Y, N
No
Yes
5.B.4.1
tax
optional.
Attribute Name
id_tax
Type /
Size
A5
value
R 16,8
Version 1.41
Possible Values
099999999999999999
999
Any
Required?
Description
Yes

No
Value to be applied
Page 43 of 91
PLatino POS
5.B.4.2 Manual Fuels

The BO does not specify Manual Fuel products but they must exist in Platino for use when CEM is not
operational for a fuel pump.
When the BO sends the Price Change file for the automatic fuel, Platino will create and update a Manual
Fuel product for each price level and the manual fuel shall be mapped to the grade and level of the price. The
Platino interface can be configured to create automatically the Manual Fuel ID which will be the result of adding
the grade level number to the automatic fuel ID which means that the BO must reserve the 9 sucesive product
IDs of a fuel ID. If this function is not present it shall then be a responsibility of the Platino Administrator to
create and map the manual fuel products.
The manual fuel's other attributes (description, Category, Department, Tax, etc) will be copied and
continuously updated from the automatic fuel.
5.B.5 Telephone_pin
Attribute Name
Id
Type /
Size
A 16
desc
Possible Values
Required?
Description
Yes
Product identifier
A 50
0999999999999999
Any
Yes
ticket_desc
A 15
Any
Yes
id_tax
A 15
No
price
R 14,4
sale_enable
L1
See table Tax

configuration
0,0 99999999999999,999
9
Y, N

POS
ticket
taxes.
id_categ1
A 15
Any
Yes
id_categ2
A 15
Any
No
id_categ3
A 15
Any
No
id_categ4
A 15
Any
No
unit_measure
A 15
Yes
icon
A 30
See Table
Measurement Unit
Any
Version 1.41
Yes
Yes
No

can be sold or not at the POS. Values:
Y = enable N = disable (it cannot be
sold like a single product) For example,
this option can be used for ingredients)
First level category. This level is used to
represent general groups of products.
id_categ1.
id_categ2.
id_categ3. This level is used to
represent specific groups of products.
Unit measure valid.
Icon file name. This icon will be showed
in the POS for this product. If this
attribute does not appear or is empty, a
Page 44 of 91
PLatino POS
id_department
A 20
Yes
doc_category
A 15
See table Document

Category
Yes
default icon will be used.

sold.
Document category
5.B.5.1
tax
optional.
Attribute Name
id_tax
Type /
Size
A5
value
R 16,8
Possible Values
099999999999999999
999
Any
Required?
Description
Yes

No
Value to be applied
5.B.6 Motorway/Freeway Unique Daily Pass

Attribute Name
id
Type /
Size
A 16
desc
Possible Values
Required?
Description
Yes
Product identifier
A 50
0999999999999999
Any
Yes
ticket_desc
A 15
Any
Yes
id_tax
A 15
No
sale_enable
L1
See table Tax

configuration
Y, N
id_categ1
A 15
Any
Yes
id_categ2
A 15
Any
No
id_categ3
A 15
Any
No
id_categ4
A 15
Any
No

POS
ticket
taxes.
can be sold or not at the POS. Values:
Y = enable N = disable (it cannot be
sold like a single product) For example,
this option can be used for ingredients)
First level category. This level is used to
represent general groups of products.
id_categ1.
id_categ2.
id_categ3. This level is used to
Version 1.41
Yes
Page 45 of 91
PLatino POS
unit_measure
A 15
Yes
A 30
See Table
Measurement Unit
Any
icon
id_department
A 20
Yes
doc_category
A 15
See table Document

Category
Yes
No
represent specific groups of products.

Unit measure valid.
Icon file name. This icon will be showed
in the POS for this product. If this
attribute does not appear or is empty, a
default icon will be used.
sold.
Document category
Version 1.41
Page 46 of 91
PLatino POS
5.B.6.1
tax
optional.
Attribute Name
id_tax
Type /
Size
A5
value
R 16,8
Possible Values
099999999999999999
999
Any
Required?
Description
Yes

No
Value to be applied
5.B.7 enable
This product will be unmarked as disabled, therefore it can be sold at the POS.
Attribute Name
id
Type /
Size
I 15
Possible Values
0 - 999999999999999
Required?
Yes
Description
Product identifier to be enabled
5.B.8 disable
This product will be marked as disabled, thereby it can not be sold at the POS. It will not be removed from the
database.
Attribute Name
id
Type /
Size
A 16
Possible Values
0 - 999999999999999
Required?
Yes
Description
Product identifier to be disabled
5.B.9 delete
This product will be deleted from the database.
Attribute Name
id
Type /
Size
A 16
Possible Values
0 - 999999999999999
Required?
Yes
Description
Product identifier to be disabled

Examples:
Version 1.41
Page 47 of 91
PLatino POS
<products>
<single id="12349" desc="SevenUp" ticket_desc="SevenUp" id_tax="DEFAULT" price="2" sale_enable="N"
consig_indic="" eft_code=3837373 id_categ1="1" id_categ2="" id_categ3="" id_categ4="" unit_measure="Unidad"
icon= id_department="0" doc_category="DEFAULT" quantifiable="Y" cost=0.25 manual_price="Y">
<barcode number="112233" />
<tax id_tax="GASEO" value=0.0564 />
<tax id_tax="IVATG" value=21 />
</single>
<grouped id="12348" desc="Bebidas" ticket_desc="Bebidas" sale_enable="Y" consig_indic="" eft_code=""
id_categ1="1" id_categ2="" id_categ3="" id_categ4="" unit_measure="Unidad" icon="" id_department="0">
<item id="12349" />
<item id="12350" />
<item id="12351" />
</grouped>
<fuel id=3 desc="Super" ticket_desc="Super" grade="3" id_tax="DEFAULT" sale_enable="Y" consig_indic=""
eft_code="1029393" id_categ1="1" id_categ2="" id_categ3="" id_categ4="" unit_measure="Unidad" icon=""
id_department="0" cost="" doc_category="DEFAULT">
<tax id_tax="ITHSUPER" value=0.05 />
</fuel>
<telephone_pin id="12360" desc="Telecom" ticket_desc="Telecom" id_tax="DEFAULT" price="2" sale_enable="N"
id_categ1="1" id_categ2="" id_categ3="" id_categ4="" unit_measure="Unidad" icon="" id_department="0"
doc_category="DEFAULT" >
<tax id_tax="TEL27" value="27" />
</telephone_pin>
<enable id="36" />
<enable id="036" />
<disable id="43" />
<delete id="212" />
</products>
<products>
<single id="0401620" desc="SKITTLES BERRY 61.53GR." ticket_desc="SKITTLES BERRY" id_tax="IVACH"
price="590" sale_enable="Y" consig_indic="" eft_code="" id_categ1="080700" id_categ2="" id_categ3=""
id_categ4="" unit_measure="Unidad" icon="" id_department="1" doc_category="DEFAULT" quantifiable="Y"
cost="320" manual_price="N">
<barcode number="0401620" desc="SKITTLES BERRY 61.53GR." />
</single>
<single id="78095069" desc="Belmont Ultra Light Box" ticket_desc="Belmont ULight" id_tax="EXEMP"
price="1000" sale_enable="Y" consig_indic="" eft_code="" id_categ1="020200" id_categ2="" id_categ3=""
id_categ4="" unit_measure="Unidad" icon="" id_department="1" doc_category="EXENTO" quantifiable="Y"
cost="500" manual_price="N">
<barcode number="78095069" desc="Belmont Ultra Light Box" />
</single>
</products>
</products>
<single id="436" desc="WINSTON BOX" ticket_desc="WINSTON BOX" id_tax="1" price="2,9" cost="0,6582"
sale_enable="Y" eft_code="74" id_categ1="6" id_categ2="30" unit_measure="Unidad" id_department="1"
doc_category="DEFAULT" quantifiable="Y" manual_price="N">
<barcode number="7730579" desc="WINSTON BOX" />
<tax id_tax="IVAT21GD" value="0" />
<tax id_tax="FIX" value="1,6053" />
</single>
</products>
5.C Concepts
This file contains the paid ins and paid outs to be created, deleted or modified at the store.
Version 1.41
Page 48 of 91
PLatino POS
File: concepts
Root element: concepts
5.C.1 paid_in_out
Attribute Name
Id
type
Type /
Size
A 16
A1
Possible Values
Required?
0 999999999999999
I, O,B
Yes
Yes
desc
A 50
Any
Yes
ticket_desc
A 15
Any
Yes
sale_enable
L1
Y, N
Yes
id_categ1
A 15
Any
Yes
id_categ2
A 15
Any
No
id_categ3
A 15
Any
No
id_categ4
A 15
Any
No
icon
A 30
Any
No
id_department
A 20
Yes
doc_category
A 15
See table Document

Category
Yes
Description
Product identifier
Indicates to which concept it refer.
Values:
I = paid in concept
O = paid out concept.
B = both
POS
ticket
Values:
Y = enable
ingredients)
groups of products.
id_categ1.
id_categ2.
id_categ3.
groups of products.
Icon file name.
used.
sold.
Document category
Version 1.41
Page 49 of 91
PLatino POS
5.C.2 credit_debit
Attribute Name
Id
type
Type /
Size
A 16
A1
Possible Values
Required?
0 999999999999999
C, D, B
Yes
Yes
desc
A 50
Any
Yes
ticket_desc
A 15
Any
Yes
sale_enable
L1
Y, N
Yes
No
Yes
id_tax
A 15
id_categ1
A 15
See table Tax

configuration
Any
id_categ2
A 15
Any
No
id_categ3
A 15
Any
No
id_categ4
A 15
Any
No
icon
A 30
Any
No
id_department
A 20
Yes
doc_category
A 15
See table Document

Category
Yes
Description
Product identifier
Indicates to which concept it refer.
Values:
C = credit concept
D = debit concept.
B = both
POS
ticket
Values:
Y = enable
ingredients)
taxes.
groups of products.
id_categ1.
id_categ2.
id_categ3.
groups of products.
Icon file name.
used.
sold.
Document category

5.C.2.1
tax
Version 1.41
Page 50 of 91
PLatino POS
optional.
Attribute Name
id_tax
Type /
Size
A5
value
R 16,8
Possible Values
099999999999999999
999
Any
Required?
Description
Yes

No
Value to be applied
5.C.3 enable
This concept will be unmarked as deleted, thereby it could be sold at the POS.
Attribute Name
Id
Type /
Size
A 16
Possible Values
0 - 999999999999999
Required?
Yes
Description
Product identifier to be deleted
5.C.4 disable
This concept will be marked as deleted, thereby it could be sold at the POS. It will not be removed from the
database.
Attribute Name
Id
Type /
Size
A 16
Possible Values
0 - 999999999999999
Required?
Yes
Description
Product identifier to be deleted

Example:
<concepts>
<paid_in_out id="401" type="O" desc="Paid Out 401 Monto 10" ticket_desc="P/O 401 10" sale_enable="Y"
id_categ1="001" id_categ2="" id_categ3="" id_categ4="" icon="" id_department="DEFAULT"
doc_category="DEFAULT" />
<paid_in_out id="400" type="I" desc="Paid In 400 Monto 10" ticket_desc="P/I 400 10" sale_enable="Y"
id_categ1="001" id_categ2="" id_categ3="" id_categ4="" icon="" id_department="DEFAULT"
<tax id_tax="IVATG" value=21 />
</paid_in_out>
<credit_debit id="300" type="C" desc="Credit/Debit 300 Monto 10" ticket_desc="C/D 300 10" sale_enable="Y"
id_tax="DEFAULT" id_categ1="001" id_categ2="" id_categ3="" id_categ4="" icon="" id_department="DEFAULT"
< enable id = 401 />
< disable id = 400 />
</concepts>
Version 1.41
Page 51 of 91
PLatino POS
5.D Categories
This file contains the categories (merchandises) for organizing the hierarchy of products to be sold. A
category is used to group a variety of related products, and it could contain a subcategory that belongs to a
lower level.
There are 4 category levels numerated from 1 to 4, that represent a generalized to specialized group
respectively.
File: category
Root element: categories
5.D.1 update
This element defines a category to be updated.
If the category does not exist in the POS system, it will be created. Oherwise, it will be modified. It is
important to mention that the desc and split_category attributes are the only that can be modified in case of the
category does already exist. When it is required to change either a level or a parent category, the category
must be deleted and then created again.
Attribute Name
Id
desc
Type /
Size
A 15
A 30
level
id_parent_categ
Possible Values
Required?
Description
Any
Any
Yes
No
I1
14
Yes
A 15
Any
No (1)
Category identifier
Category description
Default: id attribute value.
Category level to represent groups of
products. There exist four levels
categories.
Number one is the general level, and is
more specific toward number 4.
Immediate parent level category.
(1)
If level is 1, the attribute is not
required.
(2)
If level is between 2 and 4, the
value is required to identify the
parent.
BOS/HOS category to split sales
transactions. Only if split process is
activated
(1)
SAP.
(2)
Other BOS
Yes (2)
split_category
I1
Any
No (2)
Yes (1)
5.D.2 delete
This category and all its subcategories will be deleted. There must not exist any product that depends on this
category or its subcategories.
Attribute Name
Id
level
Version 1.41
Type /
Size
A 15
I1
Possible Values
Any
1-4
Required?
Yes
Yes
Description
Category identifier to be deleted
Category level
Page 52 of 91
PLatino POS
Example:
<categories>
<update id="010100" desc="UNLEADED-REGULAR" level="1" split_category="" />
<update id="010000" desc="SNACKS" level="1" split_category="" />
<update id="010200" desc="KEROSENE" level="1" split_category="" />
<update id="010000" desc="GATORADE LIMA LIMON" level="1" split_category="" />
<delete id="010300" level="1" />
</categories>
<categories>
<update id =100 desc=Beverages level=1 id_parent_categ=0 split_category="" />
<update id =100noalc desc=Bev. with no alcohol level=2 id_parent_categ=100 split_category="" />
<update id =100alc desc=Bev. with alcohol level=2 id_parent_categ=100 split_category="" />
<update id =2000 desc=Beers level=3 id_parent_categ=100alc split_category="" />
<update id =2001 desc=Wines level=3 id_parent_categ=100alc split_category="" />
<update id =2101 desc=White level=4 id_parent_categ=2001 split_category="" />
<update id =2102 desc=Red level=4 id_parent_categ=2001 split_category="" />
<delete id =333 level=3 />
</categories>
This figure shows the category hierarchy produced by the above example.
Version 1.41
Page 53 of 91
PLatino POS
Beverages
id: 100
level: 1
id_parent_categ: 0
Bev. with
no alcohol
id: 100noalc
level: 2
id_parent_categ: 100
Bev. with alcohol

id: 100alc
level: 2
Beers
id: 2000
level: 3
id_parent_categ: 100alc
Wines
id: 2001
level: 3
id_parent_categ: 100alc
White
id: 2101
level: 4
Red
id: 2102
level: 4
Version 1.41
Page 54 of 91
PLatino POS
5.E Price Changes

This file contains the new prices to be changed in the specified products beginning at a certain date and time.
The price change is like an update action. There is no delete or modify action.
File: pricechg
Root element: price_changes
5.E.1 product
Attribute Name
Id
Type /
Size
A 16
value
R 14,4
Possible Values
Required?
Description
0 - 999999999999999
Yes
099999999999999,9999
Yes
Product identifier.
This product can only be one of the
following types: Single, Fuel or
Combo.
Grouped product is not allowed.
A value to be applied to the product
price depending on type attribute.
For fuel product, this attribute is not
considered.
Date on which the price begins to be
valid for this product
Time on which the price begins to be
valid for this product
date_from
D 10
Any valid date
Yes
time_from
T6
Any valid time
Yes

Note: the date/time contained in the filename indicates when Platino is going to import all price changes
included in the file. On the other hand, the date/time at record level defines the application for each price
change individually.
5.E.1.1
combo_item
This element should only appear when the product type is a combo. If the product type of the id attribute is
not a combo, this element will not be considered even though it is present.
All the components of the combo must appear like a sub-element. Although it would be required to change
the price of some components, they must all be in the interface.
Attribute Name
Id
price
Type /
Size
A 16
R 14,4
total_price
R 14,4
Possible Values
Required?
Description
0 999999999999999
0 - 99999999999999,9999
Yes
No
0 - 99999999999999,9999
No
Product identifier
Product price per unit. If specified,
"total_price" shall not.
Quantity per price. If specified, "price"
shall not.
Version 1.41
Page 55 of 91
PLatino POS
5.E.1.2
price_level
This element should only appear when the product is Automatic Fuel. Otherwise, it will be ignored.
Attribute Name
level
price
Type /
Size
I1
R 14,4
Possible Values
15
0 - 99999999999999,9999
Required?
Yes
Yes
Description
Price level for fuel products.
Example:
<price_changes>
<product id=5 value=0.10 date_from=25/11/2001 time_from=220000 />
</price_changes>
The following example shows how an error is generated by Platino when applying a price_changes:
<price_changes>
<product id="7777" value="1300" date_from="23/05/2005" time_from="000000" error="Precio Desactualizado" />
</price_changes>
Version 1.41
Page 56 of 91
PLatino POS
5.F Special Price List

This file contains the list of special prices to be applied in certain period of time to products at the store so that
different prices can be managed for the same product.
File: pricelis
Root element: special_price_list
5.F.1 update
This element defines the list to be updated.
If the price list does not exist in the POS system, it will be created. Otherwise, it will be modified.
Attribute Name
country
id_list
Type /
Size
A 15
I5
desc
A 30
Possible Values
Required?
See table Country
Yes
0 99999
Yes
Any
Yes
Description
Country on which the customer belongs
to
Values:
customer.
1 - 99999 = Its a special list. The
price in this list is only
valid for those customers
who have the same
number identifier in the
special_price_list attribute
(see Customers file).
Price list description

5.F.1.1
special_price
Attribute Name
Id
description
type
value
Type /
Size
I5
A 50
A1
Possible Values
Required?
0 99999
Yes
Any
G, D, I, E, F
Yes
Yes
R 14,4 0,0 -
Yes
99999999999999,9999
date_from
Version 1.41
D 10
Any valid date
Yes
Description
Special Price identifier, this is not the
price list identifier.
Description
Special price type
Values:
G = Rate growth (%)
D = Rate discount (%)
I = Flat growth amount
E = Flat discount amount
F = Overwrite price
It is the special price.
Initial date from which the discount can
be applied
Page 57 of 91
PLatino POS
date_to
D 10
Any valid time
Yes
time_from
T6
Any
Yes
time_to
T6
Any
Yes
quantity_applied
I8
1 99999999
Yes
period_type
A1
F, R
Yes
mon
tue
wed
thu
fri
sat
sun
id_prod_cond
L1
L1
L1
L1
L1
L1
L1
A 16
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
type_cond
A1
Y, N
Y, N
Y, N
Y, N
Y, N
Y, N
Y, N
1
99999999999999
A, Q
quantity_min_cond
R 14,4 0,0 -
No
No
99999999999999,9999
quantity_max_cond
R 14,4 0,0 99999999999999,9999
Version 1.41
No
Final date until the discount will not be

available
Initial time from which the discount can
be applied
Final time until the discount will not be
available
Quantity of products to be applied the
special price
Indicates how to interpret the valid
period of time for the special price.
Values:
F = Fix.
The special price is valid all the time
from date_from at time_from until
date_to at time_to, for each day
with value Y.
R = Range.
The special price is valid from
date_from until date_to, between
time_from and time_to for each day
with value Y.
See figure below.
Discount is valid or not on Monday
Discount is valid or not on Tuesday
Discount is valid or not on Wednesday
Discount is valid or not on Thursday
Discount is valid or not on Friday
Discount is valid or not on Saturday
Discount is valid or not on Sunday
Product condition identifier
Condition type. It informs if the condition
to be considered is about quantity
condition or amount condition.
Values:
A = Amount condition
Q = Quantity condition
This value depends of the type_cond
attribute value:
- when type_cond is A, this value
represent the minimum amount of
products required to apply the product
condition
- when type_cond is U, this value
represent the minimum quantity of
condition
attribute value:
represent the maximum amount of
condition
represent the maximum quantity of
Page 58 of 91
PLatino POS
multiple
I3
0 999
No
multiple_type
A1
A, Q
No
which_multiple
A1
C, P
No
condition
It is the quantity of products that must
exist in the sale so that the special price
can be applied
Multiple type. It informs if the multiple to
be considered is quantity or amount.
Values:
A = Amount
Q = Quantity
Indicates on which product is used the
multiple.
Values:
C = Product Condition. It is the product
that must be in the sale so that the
special price can be applied to the
product conditioned.
P = Product Conditioned. It is the
product that will have the special
price.

Validation:
The product id_prod_cond attribute must exist in the system
Notes:
If both Quantity_from_cond and Quantity_to_cond attributes are zero, this condition range will not be
checked.
5.F.1.1.1 product
Attribute Name
id
product
Type /
Size
I5
A 16
Possible Values
Required?
Description
0 99999
199999999999999
Yes
Yes
Unique Price-Product Id
Product identifier.
following types: Single, Fuel or Combo.
Minimum value of quantity or amount
(depending on the range_type attribute)
of the product required to use the
special price
Maximum value of quantity or amount
special price
Range type.
It informs if the range of values to be
considered is about quantity condition
or amount condition.
Values:
quantity_min
I8
0 99999999
Yes
quantity_max
I8
0 99999999
Yes
range_type
A1
A, Q
Yes
Version 1.41
Page 59 of 91
PLatino POS

Validation:
The product id attribute must exist in the system
Notes:
If both Quantity_min and Quantity_max attributes are zero, this condition range will not be checked.
5.F.1.1.2 category
Attribute Name
id
id_categ1
id_categ2
Type /
Size
I5
A 15
A 15
Possible Values
Required?
Description
0 99999
Any
Any
Yes
No
No
Unique Price-Category Id
id_categ1.
id_categ2.
id_categ3.
groups of products.
id_categ3
A 15
Any
No
id_categ4
A 15
Any
No
5.F.2 delete
This element will delete the price list specified.
Attribute Name
country
id_list
5.F.2.1
Type /
Size
A 15
I5
Possible Values
Required?
Description
See table Country
Yes
0 99999
Yes

to
Price list identifier
Required?
Description
special_price
If present will delete a special_price and not the whole list.

Attribute Name
id
Type /
Size
I5
Possible Values
0 99999
Yes
Special Price identifier, this is not the

price list identifier.

5.F.2.1.1 product
If present will delete the product-special_price relationship buy not the whole Special_Price.
Attribute Name
id
Version 1.41
Type /
Size
I5
Possible Values
0 99999
Required?
Yes
Description
Unique Price-Product Id
Page 60 of 91
PLatino POS
5.F.2.1.2 category
If present will delete the category-special_price relationship buy not the whole Special_Price.
Attribute Name
id
Type /
Size
I5
Possible Values
Required?
0 99999
Yes
Description
Unique Price-Category Id
Example:
<special_price_list>
<update country=ARG id_list=0 desc=Lista General >
<special_price id=1 description=Lorry drivers sale type=F value=1.50 date_from=26/01/2001
date_to=28/01/2001 time_from=100000 time_to=140000 quantity_applied=5 period_type=F mon=Y
tue=Y wed=Y thu=Y fri=Y sat=Y sun=Y>
<product id=1 product=71 quantity_min=0 quantity_max=0 range_type=Q />
<special_price/>
</update>
<update country=ARG id_list=1 desc=Lista Especial 1 >
<special_price id=2 description=Oferta para Verduleros type=D value=50 date_from=26/01/2001
date_to=28/01/2001 time_from=100000 time_to=140000 quantity_applied=1 period_type=F mon=Y
tue=Y wed=Y thu=Y fri=Y sat=Y sun=Y id_prod_cond=71 type_cond=Q quantity_min_cond=0
quantity_max_cond=0 multiple=2 multiple_type=Q which_multiple=C >
<category id=1 categ1=BRE categ2=DRK />
<special_price/>
</update>
For every two products get one 50% off. This is applied
to coffee or "Breakfast"/"Drinks" category.
<delete country=ARG id_list=1 />

<delete country=ARG id_list=2 >
<special_price id=1>
<product id=2/>
<category id=4/>
<category id=6/>
</special_price>
</delete>
</special_price_list>
Observations for price treatment:

Price treatment has 3 cases to be considered:
1) Products file
The price to be applied is obtained from the Products file.
Version 1.41
Page 61 of 91
PLatino POS
Conditions:
a. There is no General or Special price list for the product.
2) General price list
The price to be applied is obtained from the General price list.
The product price of the Products file is not considered.
Conditions:
a. There exists a general list (id=0).
b. The product is in the list.
c. All the conditions are fulfilled.
d. There not exists a special list for the product.
3) Special price list
The price to be applied is obtained from the Special price list.
The product price of the Products file is not considered.
Conditions:
a. There exists a special list (id<>0).
b. The product is in the list.
c. All the conditions are fulfilled.
Version 1.41
Page 62 of 91
PLatino POS
This figure depicts two cases of special prices to show the differences about the period of time.
It depends on the values of period_type attribute (R for Range or F for Fix).
Fix Period Type

This figure shows the period of time on which special price is valid for product id 71 in the above example (<create
id_list="0" >).
Friday
26/01/2001
00:00:00
Saturday
27/01/2001
10:00:00
14:00:00
00:00:00
Sunday
28/01/2001
10:00:00
14:00:00
00:00:00
Monday
29/01/2001
10:00:00
14:00:00
00:00:00
Time
Range Period Type

This figure shows the period of time on which special price is valid for product id 72 in the above example (<create
id_list="0" >).
Friday
26/01/2001
00:00:00
Saturday
27/01/2001
10:00:00
14:00:00
00:00:00
Sunday
28/01/2001
10:00:00
14:00:00
00:00:00
Monday
29/01/2001
10:00:00
14:00:00
00:00:00
Time
Reference
Period on wich the special price of the product

is valid and active.
Version 1.41
Page 63 of 91
PLatino POS
5.G Bonus Buy Promotions

This file has the purpose of maintaining Bonus Buy type promotions. So, Platino has the capability of accepting
promotions in Platino proprietary and Bonus Buy format. This interface complies with the NAXML Standard.
These kind of promotions are loaded into the special price list configured in Platino as the General List that
applies to any customer.
In this interface, promotions are based on groups of articles that are needed to activate the promotion and
groups where the discount is applied. There are two kind of promotions: mix & match (promotions with only one
group) and combos (promotions with more than one group).
File: bonusbuy
Root element: NAXML-MaintenanceRequest
5.G.1 TransmissionHeader
Attribute Name
StoreLocationID
VendorName
VendorModelVersion
Type /
Size
N4
A 40
A 40
Possible Values
Any
Any
Any
Required?
Yes
No
No
Description
Site ID
POS or BOS vendor name
A description of the POS o BOS vendor
name.
Amount of elements: One per file
5.G.2 ComboMaintenance
The Combo Maintenance table (CBT) provides information to the Point-of-Sale system regarding a combo
pricing scheme. Combo is defined as selling a specific set of items at promotional price", e.g. 1 drink, 1
sandwich, 1 bag of chips. Such items are generally not of the same product or family of products and generally
do not have the same retail price.
Attribute Name
TableAction
Type /
Size
A6
RecordAction
CBTDetail
Possible Values
Required?
update
Yes
A9
addchange,
delete
Yes
Segment
See 4.G.2.1
Yes
Description
Create or update the CBT segments
included.
Create/update or delete the CBT
segments included.
The element applies to any elements in
the current sub-tree that are not
otherwise marked. RecordAction
appearing within a sub-tree overrides
any parent definition within that subtree.
Single combo item data

5.G.2.1 CBTDetail
Segment group to link all data related to a single combo item within the maintenance request.
Attribute Name
Type /
Possible Values Required?
Description
Version 1.41
Page 64 of 91
PLatino POS
RecordAction
Size
A9
Promotion
ComboDescription
ComboPrice
Segment
A 50
R 12,4
ComboList
StartDate
No
Create/update or delete this CBT.
Yes
Yes
Yes
Combo identification data.

A free form description of the combo.
The regular sell price of the combo.
Segment
D 10
addchange,
delete
See 4.G.2.1.1
Any
0,0 999999999999,999
9
See 4.G.2.1.2
Any valid date
Yes
Yes
StartTime
T5
00:01
Yes
StopDate
D 10
Any valid date
Yes
StopTime
T5
23:59
Yes
All combo list items of the combo.

Start date of the combo offer. Format:
YYYY-MM-DD.
Start time of the combo offer. Format:
HH:MM.
End date of the combo offer. Format:
YYYY-MM-DD.
End time of the combo offer. Format:
HH:MM.
TransactionLimit
Not Used

5.G.2.1.1 Promotion
Segment group to link all data related to a single combo item within the maintenance request.
Attribute Name
PromotionID
PromotionReason
Type /
Size
A 12
A 16
Possible Values
CombinationOffer
Required?
Yes
Yes
Description
Unique identifier for the promotion.
Reason code for the promotion.
Amount of elements: One per CBTDetail segment

5.G.2.1.2 ComboList
Segment group to link all combo list items contained within a sales combo.
Attribute Name
ComboItemList
Type /
Size
Segment
Possible Values
See 4.G.2.1.2.1
Required?
Yes
Description
Element which groups together
attributes of a single item list within a
combo.
Amount of elements: One per CBTDetail
5.G.2.1.2.1
ComboItemList
Segment group to link all attributes of a single item within a combo.

Attribute Name
ItemListID
Type /
Size
A 15
ComboItemQuantity
R 12,3
Version 1.41
Possible Values
<promotionID> +
_ + <seq.nr.>
Required?
Yes
Yes
Description
Unique identifier for the item list inside a
combo. It is composed with
PromotionID plus a sequence number.
The quantity of the individual item list in
the combo, i.e., one sandwich, or one
bag of chips, or one large soft drink.
Page 65 of 91
PLatino POS
ComboItemUnitPrice
ComboItemDiscountA
llocation
I3
Value attribute will

be always 0 or 100.
Type attribute will
be always percent
Not Used
No
How POS will distribute the promotions

discount among Item Lists.
If not present, POS will determine an
even distribution among items. If cero,
no discount applies to the Item List. If
100, the Item List participates in the
discount distribution.
If one group has empty, all other must
be empty too. If one group is 0 or 100,
all other must be 0 or 100 too. Empty
means this tag is not included, NOT
means that is included with null value.
5.G.3 ItemListMaintenance
The Item List Maintenance table (ILT) provides a linking mechanism to be used by the Mix-Match and Combo
Tables to designate items (or group of articles) for inclusion in the either the mix-match scheme or the combo.
Attribute Name
TableAction
Type /
Size
A6
RecordAction
ILTDetail
Possible Values
Required?
update
Yes
A9
addchange,
delete
Yes
Segment
See 4.G.3.1
Yes
Description
Create or update the ILT segments
included.
Create/update or delete the ILT
segments included.
Groups together all sub-elements
related to a single set of grouped items.
Can be multiple ILTDetail segment
groups per file.

5.G.3.1 ILTDetail
Segment group to link all items (or group of articles) in a mix match or combo offer to the mix match/combo
item product code.
Attribute Name
RecordAction
Type /
Size
A9
ItemListID
A 15
ItemListDescription
ItemListEntry
Segment
Version 1.41
Possible Values
addchange,
delete
<promotionID> +
_ + <seq.nr.>
See 4.G.3.1.1
Required?
Description
No
Create/update or delete this ILT.
Yes
The identification of the list of items in

the combo or mix-match. As per is
constructed, always make a reference
to the belonging promotion.
Not Used
Yes
Segment that groups details relating to

Page 66 of 91
PLatino POS
a single item belonging to a mix-match

or combo item. Each item in the deal
will be listed in a separate ItemListEntry
group.
5.G.3.1.1 ItemListEntry
Segment containing elements relevant to a single item (or single article) within a combo or mix match offer.
Attribute Name
ItemCode
Type /
Size
Segment
Possible Values
See 4.G.3.1.1.1
MerchandiseCode
Required?
Yes
Description
Segment used to group data elements
that uniquely identify an item in the
database.
Not Used
5.G.3.1.1.1
ItemCode
Segment containing elements that uniquely identify an item (or article) within the database.
Attribute Name
POSCodeFormat
POSCode
Type /
Size
A 14
Possible Values
Any
POSCodeModifier
InventoryItemID
Required?
Not Used
Yes
Description
The scan code or PLU number used to

access an item's information.
Not Used
Not Used
Amount of elements: One per ItemListEntry
5.G.4 MixMatchMaintenance
The Mix and Match Maintenance table (MMT) provides information to the Point-of-Sale system regarding a
special combo pricing scheme. This combo is one with only one group of articles.
Attribute Name
TableAction
Type /
Size
A6
RecordAction
MMTDetail
Possible Values
Required?
update
Yes
A9
addchange,
delete
Yes
Segment
See 4.G.4.1
Yes
Description
Create or update the MMT segments
included.
Create/update or delete the MMT
segments included.
Single mix & match combination data.

Version 1.41
Page 67 of 91
PLatino POS
5.G.4.1 MMTDetail
Segment group to link all mix match offer update relating to a single offer combination.
Attribute Name
RecordAction
Type /
Size
A9
Promotion
MixMatchDescription
Segment
A 50
Possible Values
addchange,
delete
See 4.G.4.1.1
Any
Required?
Description
No
Create/update or delete this MMT.
Yes
Yes
Mix & Match identification data.

A free form description of the mix &
match.
MixMatchStrictHighFl
ag
MixMatchStrictLowFla
g
ItemListID
Not Used
A 15
<promotionID> +
_ + <seq.nr.>
Yes
StartDate
D 10
Any valid date
Yes
StartTime
T5
00:01
Yes
StopDate
D 10
Any valid date
Yes
StopTime
T5
23:59
Yes
MixMatchEntry
Segment
See 4.G.4.1.2
Yes
Not Used
Reference to the unique ItemList for this
kind of promotion. Link to
ItemListMaintenance.
Start date of the m&m offer. Format:
YYYY-MM-DD.
Start time of the m&m offer. Format:
HH:MM.
End date of the m&m offer. Format:
YYYY-MM-DD.
End time of the m&m offer. Format:
HH:MM.
Segment that stores the quantity and
price information relevant to a single
mix match offer.

5.G.4.1.1 Promotion
Segment group to link all data related to a single mix & match item within the maintenance request.
Attribute Name
PromotionID
PromotionReason
Type /
Size
A 12
A 16
Possible Values
MixAndMatchOffer
Required?
Yes
Yes
Description
Unique identifier for the promotion.
Reason code for the promotion.
Amount of elements: One per MMTDetail segment

5.G.4.1.2 MixMatchEntry
Segment group containing the price and quantity data relating to a single mix match offer combination.
Attribute Name
MixMatchUnits
Type /
Size
R 12,3
Any
Yes
MixMatchPrice
R 12,3
Any
Yes (*)
MixMatchDiscountPer
R 12,3
Any
Yes (*)
Version 1.41
Possible Values
Required?
Description
The number of units that need to be
purchased to qualify for this price.
Promotional price.
(*) MixMatchPrice and
MixMatchDiscountPercent are mutually
exclusive.
The percentage discount to be applied
Page 68 of 91
PLatino POS
cent
to an item in the mix match deal when

the mix match criteria are satisfied.
(*) MixMatchPrice and
MixMatchDiscountPercent are mutually
exclusive.
Amount of elements: One per MMTDetail
Examples: see Apendix C
5.HSpecial Price List (backward compatibility)

This version is provided for backward compatibility with the specification version 1.16.5 but this is not the same
since it has already evolved since that version.
File: listprice
Root element: special_price_list
5.H.1 update
This element defines the list to be updated.
If the price list does not exist in the POS system, it will be created. Otherwise, it will be modified.
Attribute Name
country
Id_list
Type /
Size
A 15
I5
desc
A 30
Possible Values
Required?
See table Country
Yes
0 99999
Yes
Any
Yes
Description
to
Values:
customer.
1 - 99999 = Its a special list. The
price in this list is only
valid for those customers
who have the same
number identifier in the
special_price_list attribute
(see Customers file).
Price list description
5.H.1.1
product
Attribute Name
Id
product
Version 1.41
Type /
Size
I 15
I 15
Possible Values
Required?
Description
199999999999999
199999999999999
Yes
Unique ID
Yes
Product identifier.
following types: Single, Fuel or Combo.
Page 69 of 91
PLatino POS

type
value
A1
G, D, I, E, F
R 14,4 0,0 -
Yes
Yes
99999999999999,9999
date_from
D 10
Any valid date
Yes
date_to
D 10
Any valid time
Yes
time_from
T6
Any
Yes
time_to
T6
Any
Yes
quantity
I8
1 99999999
Yes
value_from
I8
0 99999999
Yes
value_to
I8
0 99999999
Yes
range_type
A1
A, Q
Yes
period_type
A1
F, R
Yes
mon
tue
wed
thu
fri
sat
sun
id_prod_cond
L1
L1
L1
L1
L1
L1
L1
I 15
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
type_cond
A1
Y, N
Y, N
Y, N
Y, N
Y, N
Y, N
Y, N
1
99999999999999
A, Q
Version 1.41
No

It is the special price.
Initial date from which the discount can
be applied
Final date until the discount will not be
available
Initial time from which the discount can
be applied
Final time until the discount will not be
available
Quantity of products to be applied the
special price
Minimum value of quantity or amount
special price
Maximum value of quantity or amount
special price
Range type.
It informs if the range of values to be
considered is about quantity condition
or amount condition.
Values:
Indicates how to interpret the valid
period of time for the special price.
Values:
F = Fix.
The special price is valid all the time
from date_from at time_from until
date_to at time_to, for each day
with value Y.
R = Range.
The special price is valid from
date_from until date_to, between
time_from and time_to for each day
with value Y.
See figure below.
Discount is valid or not on Monday
Discount is valid or not on Tuesday
Discount is valid or not on Wednesday
Discount is valid or not on Thursday
Discount is valid or not on Friday
Discount is valid or not on Saturday
Discount is valid or not on Sunday
Product condition identifier
Condition type. It informs if the condition
to be considered is about quantity
Page 70 of 91
PLatino POS
value_from_cond
R 14,4 0,0 -
No
99999999999999,9999
value_to_cond
R 14,4 0,0 -
No
99999999999999,9999
multiple
I3
0 999
No
multiple_type
A1
A, Q
No
which_multiple
A1
C, P
No
condition or amount condition.

Values:
attribute value:
represent the minimum amount of
condition
represent the minimum quantity of
condition
attribute value:
represent the maximum amount of
condition
represent the maximum quantity of
condition
It is the quantity of products that must
exist in the sale so that the special price
can be applied
Multiple type. It informs if the multiple to
be considered is quantity or amount.
Values:
A = Amount
Q = Quantity
Indicates on which product is used the
multiple.
Values:
C = Product Condition. It is the product
that must be in the sale so that the
special price can be applied to the
product conditioned.
P = Product Conditioned. It is the
product that will have the special
price.
5.H.2 delete
This element will delete the price list specified.
Attribute Name
country
id_list
Type /
Size
A 15
I5
Possible Values
Required?
Description
See table Country
Yes
0 99999
Yes

to
Price list identifier
Version 1.41
Page 71 of 91
PLatino POS
5.I
Tax by Province
This file contains the configuration of taxes to be applied by countries and provinces.
File: taxprovi
Root element: tax_province
5.I.1 update
Attribute Name
tax_type
Type /
Size
A5
Possible Values
See table Tax types
Required?
Yes
Description
Tax type identifier
5.I.1.1
data
Attribute Name
province
value_type
value
taxable_amount
Type /
Size
A 15
A 10
R 16,8
A 15
Possible Values
Required?
Description
See table Province
Yes
FIX,
PERCENTAGE
Yes
Province identifier.
The value ALL means that this tax
apply to the country
Value of the Tax
Any
No
SALE
PURCHASE
Yes
FIX = fix value

Percentage = value% of the taxable
amount
Value to be applied according to
value_type. It can be negative or
positive. It will not be requiered if the
subelement VARIANT is present.
Net amount calculation method:
SALE = Over the Net amount
PURCHASE = Over the Cost
R 16,4
0
99999999999999,9999
No
minimum_whole_sale_t R 16,4
ax_amount
0
99999999999999,9999
No
minimum_tax_rate
Minimum tax rate.

When this attribute is not present, it
should be interpreted as if it exists
with a value of zero.
If present, the total tax of the sale
must be more than this value to be
fully applied.
5.I.1.1.1 Variant
The variants are optional and can be a subelement of the global province (ALL) or of any particular province.
Version 1.41
Page 72 of 91
PLatino POS
Attribute Name
variant_id
Type /
Size
I8
description
value
Possible Values
Required?
Description
Any
Yes
A 50
Any
No
R 16,8
Any
Yes
Unique ID for the tax-province it is

related to.
If not present, the variant_id will be
automatically set as the Description
Value to be applied to the price. It can
be negative or positive
Example:
<tax_province>
<update tax_type= IVAT21GD >
<data province=ALL value_type=PERCENTAGE value=21 taxable_amount=SALE
minimum_tax_rate=0 >
</data>
</update>
<update tax_type= CIGAR >
<data province=ALL value_type=FIX taxable_amount=SALE
minimum_tax_rate=0 >
<variant variant_id=1 description=A value=1.23 />
<variant variant_id=2 description=B value=1.28 />
<variant variant_id=3 description=C value=1.13 />
<variant variant_id=4 description=Extra value=0.98 />
</data>
</update>
<update tax_type="EXEMP">
<data province="ALL" value_type="PERCENTAGE" value="0.00" taxable_amount="SALE"
minimum_tax_rate="" minimum_whole_sale_tax_amount="" />
</update>
</tax_province>
Version 1.41
Page 73 of 91
PLatino POS
5.J Account
This file contains the customers who have global account.
File: accounts
Root element: accounts
5.J.1 update
Attribute Name
cust_number
Type /
Size
E 18
limit
R 12,4
limit_control
limit_day
type
Possible Values
Required?
Description
1
999999999999999999
-999999999999,9999
999999999999,9999
Yes
Y, N
Yes
R 12,4
-999999999999,9999
999999999999,9999
Yes
A 10
Yes
Customer number who has the

account.
Limit amount allowed to buy products
for this account.
Indicates if the attribute limit must be
checked when a transaction is made.
Limit day amount allowed to buy
products for this account.
Indicates which type of account it is.
No
Limit purchase.
No
No
No
Days until the invoice is not

considered a debt
Invoice Period:
State account
L1
due_days
N3
Credit
Saving
-999999999999,9999
999999999999,9999
999
invoice_period
account_enable
N1
L1
1,2,3
Y, N
limit_purchase
R 12.4
Yes
5.J.1.1
subaccount
Attribute Name
number
card_id
currency
description
limit_purchase
Type /
Size
R 4,0
A 10
A 15
A 30
R 12.4
limit_credit
R 12.4
limit_control
L1
subaccount_enable
license_plate
L1
A 20
Possible Values
Required?
Description
Any
Any
See Table Currency
Any
-999999999999,9999
999999999999,9999
-999999999999,9999
999999999999,9999
Y,N
Yes
No
Yes
No
No
Sub account identifier.

Card id subaccounts
Currency allowed to buy products.
Subaccount description
Limit purchase
No
Y,N
Any
No
No
Limit amount allowed to buy products

for this account.
Indicates if the attribute limit_credit
must be checked when a transaction
is made
State subaccount
License plate
Yes
Example:
Version 1.41
Page 74 of 91
PLatino POS
<accounts>
<update cust_number="102" limit="1000" limit_control="Y" limit_day="500" type="CREDIT" limit_purchase="100"
due_days="7" invoice_period="30" account_enable="Y" >
<subaccount number="1" card_id=1111444455 currency="PESOS_ARG" description= subcuenta en
pesos limit_purchase=50 limit_credit=800 limit_control=Y subaccount_enable="Y" license_plate=""/>
</update>
</accounts>
5.J.2 new_balance
When the subaccount 0 represents the Clients united account balance including the sum of all the
independent subaccounts plus the balance not held in a subaccount this must be informed for appropiate
configuration of the Platino interface driver for the specific vendor.
As a consecuence, all of the subaccount balances must also acompany the main account balance
since the omitted subaccount balances will be forced to zero because Platino will calculate the main account
balance as the substraction between the main account balance and the sum of all the subaccount balances.
Attribute Name
cust_number
Type /
Size
E 18
Possible Values
Required?
1
999999999999999999
Yes
Description
account.
5.J.2.1
subaccount
Attribute Name
number
amount
Type /
Size
R 4,0
R 12,4
Possible Values
Any
-999999999999,9999
999999999999,9999
Required?
Yes
Yes
Description
New balance that must be updated for
this customer.
Example:
<accounts>
<new_balance cust_number=105 >
<subaccount number="1" amount=50 />
</new_balance>
</accounts>
5.J.3 new_balance (backward compatibility with Version 1-16-5)

Attribute Name
cust_number
Type /
Size
E 18
subaccount
amount
R 4,0
R 12,4
Version 1.41
Possible Values
Required?
1
999999999999999999
Any
-999999999999,9999
999999999999,9999
Yes
Yes
Yes
Description
account.
New balance that must be updated for
this customer.
Page 75 of 91
PLatino POS

Example:
<accounts>
<new_balance cust_number=105 subaccount=ABC123 amount=50 />
</accounts>
5.J.4 disable
If no subaccounts are present in this element then the full account will be marked as disabled, therefor it cannot
be used for a sale or delivery operation.
Attribute Name
cust_number
Type /
Size
E 18
Possible Values
Required?
1
999999999999999999
Yes
Description
account.

5.J.4.1
subaccount
The subaccounts will be marked as disabled, therefor they cannot used for a sale or delivery operation.
Attribute Name
subaccount
Type /
Size
R 4,0
Possible Values
Any
Required?
Yes
Description

Example of full account disabled:
<accounts>
<disable cust_number="1">
</disable>
</accounts>
Example of subaccounts disabled:

<accounts>
<disable cust_number="1">
<subaccount number="1"/>
<subaccount number="0"/>
</disable>
</accounts>
Version 1.41
Page 76 of 91
PLatino POS
5.K Transactions
Each transaction always includes all the hierarchy of products that depends on the main products
delivered (which are showed in the Delivery Note), i.e. every product with its components, and the components
of the component, and so on.
It is not requiered that the products exist on the Platino destiny server.
File: importTx
Root element: transactions
5.K.1 update
Customer Considerations
If the Customer exists en the Platino local master table it shall be referenced to complete the customer
attributes on the transaction record (address, customer category).
In the case of a non-existing customer Platino shall asume a NULL address and default values for the
rest of the attributes based on the Anonymous Customer.
These attributes have general transaction information.
Attribute Name
node
id_trans
Type /
Size
A 15
I 18
Possible Values
Description
Any
1
999999999999999999
Node identifier. It is unique by HO

pos
country
node_description
trans_type
I5
A 15
A 50
A 10
1 99999
See Table Country
Any
delivnote
POS identifier
The local country of the Transactions Node
The Transactions Node Description
Indicates what type of transaction it is.
gen_date
gen_time
id_issuer
D 10
T6
A 10
Any valid date

Any valid time
Any
fiscal_doc_type
A 10
See table
Fiscal document
Date at the moment of end transaction

Time at the moment of end transaction
country.
fiscal_doc_num
I 18
1
999999999999999999

fiscal_doc_type.
cust_num
I 18
1
999999999999999999
Any
Unique customer identifier in the whole system
cust_comm_name
tic
tax_payer
net_amount
A 50
A 20
A4
R 14,4
total_amount
R 14,4
total_tax
R 14,4
manual
L1
Version 1.41
Any
See table Tax Payer
0,0
99999999999999,9999
0,0
99999999999999,9999
0,0
99999999999999,9999
Y,N
Customer name or commercial name

Tributary identifier code of the customer
Tax payer
Net amount of the transaction. It does not
include any tax
Total amount of the transaction
Total tax for the transaction
Notifies whether the transaction was manual or
Automatic
Page 77 of 91
PLatino POS
5.K.1.1
item
This is the information of the product sold. If the product type is combo, there will not be any tax element.
Product Considerations
The imported product will not affect nor reference the Master Table of Products for viewing or any subsequent
operation applied to the imported transaction. This will allow Platino to import products the are not present in its
local product master table or even product codes that are in use and have different types, taxes, etc.
Attribute Name
id
seq_number
Type /
Size
A 16
I5
Possible Values
0 999999999999999
0 99999
parent_seq_number
I5
0 99999
type
A1
S, C, G, F, M, P, O
description
quantity
quantity_in_combo
unit_measure
A 50
R 18,6
R 18,6
A1
price
R 14,4
price_orig
R 14,4
Any
Any
Any
See Table
Measurement Unit
0,0
99999999999999,9999
0,0
99999999999999,9999
Description
Product (or item) identifier
Sequential number assigned to each product
included in the transaction
0 the product belongs to the first level, which
are printed in the ticket
<> 0 the product is a component of the
product associated with the parent_seq_number
Product type
Values:
S = Single
C = Combo
G = Grouped
F = Fuel Automatic
M = Fuel Manual
Product description
Quantity of sold products
Only for Combo component products. Quantity
of the component within its combo.
Unit measure
Price per unit of the product with tax included.
Price original per unit of the product with tax
included.
5.K.1.1.1 tax
Taxes are only applied to single or fuel products.
Attribute Name
id
amount
taxable_amount
Type /
Size
A5
R 18,8
R 18,8
Possible Values
See table Tax types
Any
Any
Description
Tax identifier
Tax amount per unit for the item
Taxable amount
Amount of elements: One element per tax identifier.

Version 1.41
Page 78 of 91
PLatino POS
Note:
If an item is exempt(it has no taxes), the tax element will not be present for the item.
In case that the transaction had only exempt items, both net_amount and total_amount attributes would
be equal.
5.K.1.2
tender
Attribute Name
type
amount
amount_not_returned
currency
rate
Type /
Size
A 10
R 14,4
R1
A 15
R 14,4
Possible Values
Description
See table Tender type

Any
Tender type identifier

type
Amount not returned to type of payment that not
accept cash back.
Currency.
local currency.
Any
See Table Currency
Any
5.K.1.2.1 account
This element will only appear if the tender type is an account.
Attribute Name
number
subaccount
Type /
Size
R 15,0
R 12,0
Possible Values
Any
Any
Description
Account Number
Subaccount Number

Example:
< transactions>
<update node=00001 id_trans=1 pos=1 country="ARG" node_description="SS xxx" trans_type=delivnote
gen_date=01/01/2001 gen_time=220005 id_issuer=1234 fiscal_doc_type=RT fiscal_doc_num=102
cust_num=1250 cust_comm_name=Gilbarco tic=20234567807 tax_payer=CF net_amount=300.5085
total_amount=1970 total_tax= manual=N >
<item id=70 seq_number=1 parent_seq_number=0 type=C description="Combo1" quantity=1
quantity_in_combo="" unit_measure="Unidad" price=1900" price_orig="1900">
<tax id=IVATG amount=289,83 taxable_amount="1610,17" />
</item>
<item id=710 seq_number=2 parent_seq_number=1 type=S description="Coke" quantity=1
quantity_in_combo="1" unit_measure="Unidad" price=600 price_orig="600">
</item>
<item id=720 seq_number=3 parent_seq_number=1 type= S description="French Fries"
quantity=1 quantity_in_combo="1" unit_measure="Unidad" price=300 price_orig="300">
</item>
<item id=500 seq_number=4 parent_seq_number=0 type=S description="Lemmon Cookie"
quantity=1 quantity_in_combo="" unit_measure="Unidad" price=70 price_orig="70">
</item>
Version 1.41
Page 79 of 91
PLatino POS
<tender type=CC amount=1970 currency="PESOS_CHI" rate=1 >
<account number=21231056454 subaccount=0 />
</tender>
</update>
</transactions >
5.L Account-Product Restriction

This file describes the product restriction for accounts and subaccounts. The allowed products will be the
union of the account and subaccount product restrictions.
If the account has no product restriction Platino will allow any product to be sold.
The non-presence of the subaccount determines that the restriction is for the account level.
File: accoprod
Root element: account_product
5.L.1 update
Attribute Name
id_account
Type /
Size
E 18
Possible Values
Required?
1 999999999999999999
Yes
subaccount
R 12,0
Any
No
Description
account.

5.L.1.1
product
Attribute Name
id
Type /
Size
A 18
Possible Values
1 999999999999999999
Required?
Yes
Description
Product identifier.
5.L.2 delete
Attribute Name
id_account
Type /
Size
E 18
Possible Values
Required?
1 999999999999999999
Yes
id_subaccount
R 12,0
Any
No
Description
account.

5.L.2.1
product
Attribute Name
id
Version 1.41
Type /
Size
A 18
Possible Values
1 999999999999999999
Required?
Yes
Description
Product identifier.
Page 80 of 91
PLatino POS
Example:
Update products into an account:
<account_product>
<update id_account="111" >
<product id="5"/>
<product id="6"/>
</update>
</account_product>
Update products into a subaccount:

<account_product>
<update id_account="1" id_subaccount="2">
<product id="5"/>
<product id="6"/>
<product id="156"/>
</update>
</account_product>
Delete products from an account:

<account_product>
<delete id_account="111" >
<product id="6"/>
<product id="1"/>
<product id="155"/>
</delete>
</account_product>
Delete products from a subaccount:

<account_product>
<delete id_account="1" id_subaccount="2">
<product id="5"/>
<product id="6"/>
<product id="146"/>
</delete>
</account_product>
Version 1.41
Page 81 of 91
PLatino POS
5.M
Currency Rate
File: currrate
Root element: currency_rate
5.M.1 update
Attribute Name
currency
country
rate
Type /
Size
A 15
See Table Currency
A 15
See Table Country
R 18,4
Possible Values
0,0
99999999999999,9999
Required?
Description
Yes

account.
The local country of the Transactions
Node Country
Rate for conversion to the local
currency.
Yes
Yes

Example:
<currency_rate>
<update currency="USD" country="Per" rate="2.12"/>
<update currency="PRU" country="Per" rate="2.34"/>
</currency_rate>
5.N Banks
File: bankcode
Root element: banks
5.N.1 update
Attribute Name
code
country
description
Type /
Size
A3
A 15
A 60
Possible Values
Required?
Description
See Table Banks
Yes
See table Country

Any
Yes
Yes
Bank Code accoding dispositions of

local goberment
Country of origin
The corresponding desription for the
code

Example:
<banks>
<update code="092" country="ARG" description="BANCO RIO DE LA PLATA S.A." />
<update code="00" country="ARG" description="AMR AMRO BANK S.A." />
</banks>
Version 1.41
Page 82 of 91
PLatino POS
5.O
Payments eFleet
This file contains the details of each attribute that makes up the payment transaction. The payment need not be
related to any Fleet Delivery Invoice.
File: Payments eFleet
Root element: fltpagos
5.O.1 insert
Attribute Name
contrato
id_pago_externo
fecha_pago_externo
monto_externo
observacion
mdp_cheque
mdp_efectivo
mdp_transferencia
mdp_otro
Type /
Size
I 005
A 050
D 010
N 12,4
A 200
L 001
L 001
L 001
L 001
Possible Values
Required
?
0 99999
Yes
Any
Yes
dd/mm/yyyyy
Yes
0,0 999999999999,9999
Yes
Any
No
Y, N
No
Y, N
No
Y, N
No
Y, N
No
Description
Identification number of contract
Identification number of payement
Date of payment
Value of payement
Comments
Check payements
Cash payements
Payments by bank transfer
Other payments type

Example
<?xml version="1.0" encoding="iso-8859-1" ?>
<fltpagos>
<update contrato="10" id_pago_externo="1" fecha_pago_externo="18/06/2010"
monto_externo=100.50 observacion=Pago 1 mdp_cheque=N
mdp_efectivo=Y mdp_transferencia=N mdp_otro=N />
</fltpagos>
If there is more than one payment file contents should be:
<?xml version="1.0" encoding="iso-8859-1" ?>
<fltpagos>
monto_externo=372 observacion=Pago 2 mdp_cheque=N
monto_externo=230.32 observacion=Pago 3 mdp_cheque=N
</fltpagos>
Version 1.41
Page 83 of 91
PLatino POS
Apendix A: Table of Constant Values

The tables showed below are the possible values that can be used for specific attributes contained in the files.
A.1 Modules
Module
SHOP
PLATINO
CASHIER
EPAY
CEM
GNC
Version 1.41
Description
Shop Endings (shift => group ending)
PLatino POS
Cashier
ePay
CEM
GNC
Page 84 of 91
PLatino POS
Apendix B: Combo Examples

B.1 Saletrans
Below is an example of Saletrans.XML with a combo sale.
Version 1.41
Page 85 of 91
PLatino POS
<trans node = GLA0005 id_trans=1 pos=1 trans_type=sale business_date=17/05/2005
gen_date=17/05/2005 gen_time=220005 id_cashier=2 cashier_name=Juan id_issuer=1234
fiscal_doc_type=FB fiscal_doc_num=102 net_amount=1669,49153 total_amount=1970 total_tax=300.51
exempt_amount=0.0 cashier_relative_shift_id=1 cashier_absolute_shift_id=15 main_group_abs="255"
main_group_rel="1" id_initial_day_abs="105" id_initial_day="10" voided="N" cancel_conc_id="" cust_num=1250
cust_comm_name=Jhon Doe tic=20234567807 tic_type=CU tax_payer=MT origin=pos manual=N
cash_drawer=1 rev_trans= rev_pos= split_category=1 fiscal_auth=12345678901234
fiscal_auth_expire=16/06/2005 cust_address_street="Belgrano 1022" cust_address_city="Buenos Aires" >
<item id=70 seq_number=1 parent_seq_number=0 type=C quantity=1 price=1900
price_orig=1900 line_amount=1900 tax_amount=289,8305085 total_tax_amount=289,83
exempt_amount=0.0 net_amount=1610,169492 barcode= desc=Combo1 special_price_list_id=
promotion_id= discount_reason_code= discount_amount= manual_fuel_selected=NO >
<tax id=IVATG amount=289,8305085 taxable_amount=1610,169492
total_amount="289,83"/>
</item>
<item id=710 seq_number=3 parent_seq_number=1 type=S quantity=1 price=600
price_orig=600 line_amount=600 tax_amount=91,5254237 total_tax_amount=91.53
exempt_amount=0.0 net_amount=508,474576 barcode= desc=Coke special_price_list_id=
<tax id=IVATG amount=91,5254237 taxable_amount=508,474576 total_amount="91,53" />
</item>
<item id=720 seq_number=4 parent_seq_number=1 type= S quantity=1 price=300
price_orig=300 line_amount=300 tax_amount=45,7627119 total_tax_amount=45,76
exempt_amount=00 net_amount=254,237288 barcode= desc=French Fries special_price_list_id=
promotion_id= discount_reason_code= discount_amount= manual_fuel_selected=NO>
</item>
<item id=800 seq_number=5 parent_seq_number=1 type= C quantity=1 price=1000
price_orig=1000 line_amount=1000 tax_amount=152.542373 total_tax_amount=152,54
exempt_amount= net_amount=847,457627 barcode= desc=Hamburguer special_price_list_id=
<tax id=IVATG amount=152,542373 taxable_amount=847,457627 total_amount="152,54"
/>
</item>
<item id=810 seq_number=6 parent_seq_number=5 type=S quantity=1 price=850
price_orig=850 line_amount=850 tax_amount=129.661017 total_tax_amount=129.66
exempt_amount= net_amount=720,338983 barcode= desc=Meat special_price_list_id=
<tax id=IVATG amount=129,661017 taxable_amount=720,338983 total_amount="129,66"
/>
</item>
price_orig=100 line_amount=100 tax_amount=15,2542373 total_tax_amount=15.25
exempt_amount= net_amount=84,7457627 barcode= desc=Cheese special_price_list_id=
</item>
price_orig=50 line_amount=50 tax_amount=7,62711864 total_tax_amount=7,63 exempt_amount=
net_amount=42,3728814 barcode= desc=Tomato special_price_list_id= promotion_id=
discount_reason_code= discount_amount= manual_fuel_selected=NO >
</item>
<item id=500 seq_number=2 parent_seq_number=0 type=S quantity=1 price=70 price_orig=70
line_amount=70 tax_amount=10,6779661 total_tax_amount=10,68 exempt_amount=
net_amount=59,3220339 barcode=9123456789012 desc=Lemon Cookie special_price_list_id=
</item>
<tender type=CC currency="PESOS_CHI" amount=1970 rate=1 >
<check number="7894444444444444" bank="1" issue_date="10/12/2005" payable_date=""/>
</tender>
Version 1.41
Page 86 of 91
PLatino POS
<total_tax id="IVATG" total_amount="300,51" />
<additional_data odometer=15222 license_plate=ADB970 driver= observations= />
<customer_tax_config fiscal_group="IVA" tax_payer="MT" id_fiscal_number="20234567807"
tic_type="CU" />
</trans>
B.2 Products
Below is an example of Products.XML with a combo article.
<products>
<combo id="12347" desc="Bebidas" ticket_desc="Bebidas" sale_enable="N" consig_indic="" eft_code=
id_categ1="1" id_categ2="" id_categ3="" id_categ4="" unit_measure="Unidad" icon="" id_department="0"
doc_category="DEFAULT" quantifiable="Y" manual_price="Y">
<item id="2" qty="3" price="1. 50" total_price="4.50" type="F" />
<item id="14" qty="2" total_price="6" total_price="12" type="F" />
</combo>
</products>
B.3 Price Changes

Below is an example of PriceChg.XML over a combo article.
<price_changes>
<product id=6 value=1.59 date_from=25/11/2001 time_from=220000 >
<combo_item id=100 total_price="1.00" />
<combo_item id=101 price=1.34 />
</product>
</price_changes>
Version 1.41
Page 87 of 91
PLatino POS
Apendix C: NAXML Promotions Examples

C.1 Combo Promotion
Below is an example of a Combo promotion in NAXML format.
- <NAXML-MaintenanceRequest>
- <TransmissionHeader>
<StoreLocationID>8469</StoreLocationID>
<VendorName>SAP GROC</VendorName>
<VendorModelVersion>REL.4.6C</VendorModelVersion>
</TransmissionHeader>
- <ComboMaintenance>
<TableAction type="update" />
<RecordAction type="addchange" />
- <CBTDetail>
- <Promotion>
<PromotionID>US02XX000002</PromotionID>
<PromotionReason>combinationOffer</PromotionReason>
</Promotion>
<ComboDescription>Antone Fountain Drink and Frito Big</ComboDescription>
<ComboPrice>4.00</ComboPrice>
- <ComboList>
- <ComboItemList>
<ItemListID>US02XX000002_01</ItemListID>
<ComboItemQuantity>1.000</ComboItemQuantity>
<ComboItemUnitPrice>1</ComboItemUnitPrice>
</ComboItemList>
- <ComboItemList>
</ComboItemList>
- <ComboItemList>
</ComboItemList>
</ComboList>
<StartDate>2005-09-13</StartDate>
<StartTime>00:00:01</StartTime>
<StopDate>2005-09-30</StopDate>
<StopTime>23:59:59</StopTime>
</CBTDetail>
</ComboMaintenance>
- <ItemListMaintenance>
- <ILTDetail>
<ItemListDescription>US02XX000002_01</ItemListDescription>
- <ItemListEntry>
- <ItemCode>
<POSCodeFormat format="plu" />
<POSCode>2101</POSCode>
<POSCodeModifier>1</POSCodeModifier>
</ItemCode>
<MerchandiseCode>020100</MerchandiseCode>
</ItemListEntry>
- <ItemListEntry>
- <ItemCode>
Version 1.41
Page 88 of 91
PLatino POS
</ItemCode>
</ItemListEntry>
- <ItemListEntry>
- <ItemCode>
</ItemCode>
</ItemListEntry>
</ILTDetail>
- <ILTDetail>
- <ItemListEntry>
- <ItemCode>
</ItemCode>
</ItemListEntry>
- <ItemListEntry>
- <ItemCode>
</ItemCode>
</ItemListEntry>
- <ItemListEntry>
- <ItemCode>
</ItemCode>
</ItemListEntry>
</ILTDetail>
- <ILTDetail>
- <ItemListEntry>
- <ItemCode>
</ItemCode>
</ItemListEntry>
- <ItemListEntry>
- <ItemCode>
</ItemCode>
</ItemListEntry>
- <ItemListEntry>
- <ItemCode>
Version 1.41
Page 89 of 91
PLatino POS
</ItemCode>
</ItemListEntry>
</ILTDetail>
</ItemListMaintenance>
</NAXML-MaintenanceRequest>
C.2 NAXML Mix & Match Promotion

Below is an example of a Mix & Match promotion in NAXML format.
- <NAXML-MaintenanceRequest>
- <TransmissionHeader>
<StoreLocationID>8469</StoreLocationID>
<VendorName>SAP GROC</VendorName>
<VendorModelVersion>REL.4.6C</VendorModelVersion>
</TransmissionHeader>
- <ItemListMaintenance>
- <ILTDetail>
- <ItemListEntry>
- <ItemCode>
</ItemCode>
</ItemListEntry>
- <ItemListEntry>
- <ItemCode>
</ItemCode>
</ItemListEntry>
- <ItemListEntry>
- <ItemCode>
</ItemCode>
</ItemListEntry>
- <ItemListEntry>
- <ItemCode>
</ItemCode>
</ItemListEntry>
</ILTDetail>
</ItemListMaintenance>
- <MixMatchMaintenance>
Version 1.41
Page 90 of 91
PLatino POS
- <MMTDetail>
- <Promotion>
<PromotionID>US01XX000004</PromotionID>
<PromotionReason>mixAndMatchOffer</PromotionReason>
</Promotion>
<MixMatchDescription>Mix and Match with Plu 02</MixMatchDescription>
<MixMatchStrictHighFlag value="yes" />
<MixMatchStrictLowFlag value="yes" />
<StartDate>2005-09-14</StartDate>
<StartTime>00:00:01</StartTime>
<StopDate>2005-09-30</StopDate>
<StopTime>23:59:59</StopTime>
- <MixMatchEntry>
<MixMatchUnits>2.000</MixMatchUnits>
<MixMatchPrice>3.00</MixMatchPrice>
</MixMatchEntry>
</MMTDetail>
</MixMatchMaintenance>
</NAXML-MaintenanceRequest>
Version 1.41
Page 91 of 91

InterfazPlatino-Version 1 41

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

InterfazPlatino-Version 1 41

Hochgeladen von

Copyright:

Verfügbare Formate

Point Of Sale

Last modification: Junio 2015

Copyright Gilbarco Latin America

A Brief introduction ............................................................................................................................... 6

XML file specification ..................................................................................................... 12

Data Types ........................................................................................................................................... 14

Output files: POS to BO.................................................................................................. 15

Sales transactions ............................................................................................................................... 15

Cash Drop ............................................................................................................................................ 24

Input files: BO to POS ..................................................................................................... 35

5.A.1.1 tax_config ..................................................................................................................... 36

Bonus Buy Promotions ....................................................................................................................... 64

5.G.2.1.2.1 ComboItemList ................................................................................................ 65

5.G.3.1.1.1 ItemCode .......................................................................................................... 67

Special Price List (backward compatibility) ....................................................................................... 69

Account-Product Restriction .............................................................................................................. 80

Apendix A: Table of Constant Values ................................................................................... 84

Apendix B: Combo Examples ................................................................................................ 85

Apendix C: NAXML Promotions Examples .......................................................................... 88

Combo Promotion ............................................................................................................................... 88

Actual Platino Version

Version from Platino

2.A.2 XML Background and references

New standard for interfaces

2.A.3 XML vs. TXT size

The size of the uncompressed TXT file is 21300 bytes

The size of the uncompressed TXT file is 37898 bytes

2.B XML Operations

2.B.2 Data import

2.B.3 Error manipulation for input files

A required attribute does not appear in the XML file.

The error file is compound by:

A root element with the name errores.

2.B.4 File names

2.B.5 Share folders

When a xml is processed, any of these possibilities can take

1) The xml file has no error

Each process is executed after other in a specific

The ZIP process should be a new one which depends

3 XML file specification

1.C A Subject to understand the data information in the file

Root element: root_name

(This word is the tag of an element of the first level)

\----------------------------------------------------------------- END ------------------------------------------------------------------------/

The following is the meaning of each column showed above.

Description: A short description of the attribute meaning.

An element without sub-elements can appear in two ways:

3.A Data Types

An integer number with sign.

A type I n mean an integer number with

A real number with sign. It has both an

A chain of alphanumeric characters.

A date with format DD/MM/YYYY

A time with format 24 hour HHMMSS

4 Output files: POS to BO

Amount of elements: one

Date for the business

See Table TIC Type

See table Tax Payer

Store operator identifier (system user id) who

Pos identifier reverse

BOS/HOS category to split sales transactions.

Any valid date

Depending on the fiscal document type and tax