Pricer Integration

SYSTEM GUIDES
Pricer
Integration
and communication
Information in this document is subject to change without notice. No part of this document may be reproduced or re-
transmitted in any form or by any means, electronic or mechanical, for any purpose, without permission in writing from
Pricer AB.
Version R5.5.0 (2018-02-02)

Copyright © 2018 Pricer AB. All rights reserved.
Contents
1 Introduction ...................................................................... 4
1.1 How it works? ............................................................ 4
1.2 IR Communication ..................................................... 5
1.3 Electronic Shelf Label ............................................... 5
1.3.1 TRX-group ........................................................... 6
1.3.2 Roaming .............................................................. 6
1.3.3 ESL barcode........................................................ 7
1.3.4 Low battery indication ........................................ 7
1.3.5 Temperature indication ...................................... 8
1.4 Basestation ............................................................... 8
1.5 Transceiver ................................................................ 8
1.6 Front-End LAN ........................................................... 8
1.7 Department ............................................................... 8
2 General Configuration ...................................................... 9
2.1.1 System Specific Fields ..................................... 10
2.1.2 Customer Specific Fields .................................. 11
2.1.3 How to add an Item Property ............................ 12
2.1.4 How to delete an Item Property ........................ 13
3 Pricer File Interface (PFI) ................................................ 14
3.1 Communication Interface ........................................ 14
3.2 Text Files ................................................................. 14
3.3 Environment Independent ....................................... 15
3.4 PFI Specification ..................................................... 15
3.4.1 PFI Procedures and Communication Method ... 15
3.5 PFI File Names ......................................................... 21
3.6 PFI Message Specification ...................................... 21
3.6.1 UPDATE ............................................................. 21
3.6.2 TARGETLINK ..................................................... 23
3.6.3 PRINT ................................................................ 25
3.6.4 REFRESH .......................................................... 25
3.6.5 SETGLOBAL....................................................... 26
3.6.6 DELETE ............................................................. 26
3.6.7 ESLUPDATE ...................................................... 27
3.6.8 LINKUPDATE ..................................................... 28
3.6.9 LED ................................................................... 29
3.6.10 PICKLIST ........................................................... 30
3.7 PFI Configuration ..................................................... 31
3.8 PFI Backward Compatibility Summary .................... 32
4 Text Adapter ................................................................... 33
4.1 Text Adapter fields .................................................. 33
4.2 File type examples ................................................... 35
4.3 File processing steps ............................................... 36
5 Drop Folder ..................................................................... 37
5.1 System Parameters ................................................. 37
5.2 Item Properties ........................................................ 37
5.3 ESL Configuration .................................................... 38
5.4 Image information ................................................... 38
2
6 Public API ....................................................................... 40
6.1 Ports ........................................................................ 40
6.2 Usage ....................................................................... 40
Appendix A Complete List of R7 Return Codes................. 41
Appendix B Secondary Item Codes (SIC) .......................... 44
Appendix C Ports Overview .............................................. 47
1 Introduction
In order for the Pricer Server to display item information on an Electronic Shelf Label (ESL) an
integration is needed between the Pricer Server and the customer Price Controlling Application
(PCA) system. In this document there are information of different ways to integrate with Pricer
and how the IR communication works.
1.1 How it works?

The PCA1 system send the new item information 2 (that is the integration) to the Pricer Server3
which then with the transceivers transmit4 the information to the ESL5.
The ESL acknowledge back to the Pricer Server that the new update has been received
successfully.
4
1.2 IR Communication
The IR link is a wireless communication media used to transmit data between
the ESLs and the transceivers in the store. It uses infrared light (IR) for the
transmission using the proprietary Pricer protocol PP4 or PP16.
Infrared (IR) transmission is a technique for wireless communication. In the Pricer System,
infrared (IR) is used for communication with the ESLs. Infrared is the part of the
electromagnetic spectrum that has wavelengths extending from 800 nm to 1 mm
(corresponding to frequencies from 4x10 14 Hz down to about 3x1011 Hz).
The wavelength used for the Pricer System infrared (IR) link is around 900 nm which is near the
visible part of the spectrum. This implies that the behavior of infrared (IR), in terms of
reflections and shadowing, is similar to visible light. Infrared (IR) light is emitted diffusely (at a
wide angle) from arrays of LEDs (Light Emitting Diodes) in the transceiver. There is also a LED
in the ESL for acknowledgement.
The IR can reach the receivers via reflections from the floor and shelves in the store, so the
signal does not need line of sight.
The communication link from the transceiver to the ESL is called the downlink, and the
communication link from the ESL to the transceiver is called the uplink.
The information in the downlink to the ESLs is arranged into frames. A frame contains
information such as ESL address, the length of a frame, the command to the ESL data (i.e. new
price), and finally the checksum. By using the checksum, any error in the link during
transmission can be detected. All communication is initiated by frames sent from the Pricer
Server via the base stations and the transceivers to set the ESLs in a listening mode. The
actual command is then sent to the ESL, and the ESL acknowledges this command by sending
an acknowledge signal back.
1.3 Electronic Shelf Label

The Electronic Shelf Label (ESL) has a unique address (see detailed information
below) that is printed on the back of every ESL. Each ESL is then logically
connected to a sales item in the store. This is done by using the unique address of
the ESL and link that to the unique identifier of the sales item (normally the EAN code).
The ESL contains a transmitter and a receiver. The receiver is used to receive information from
the transceivers via the infrared light (IR). The transmitter in the ESL is used to send an
acknowledgment back to the transceiver to indicate if the data received is correct.
Transmitter LED
(SmartFlash)
Receiver
The acknowledgement is received by the transceiver and passed back to the Pricer Server. The
active acknowledgement is used by the Pricer Server to confirm that the ESL has the correct
information. Batteries provide the power for the ESLs and in an event of a power outage in the
store the ESLs will still show the information.
1.3.1 TRX-group
For a normal ESL update the Pricer Server automatically calculates the
optimal number of transceivers that is needed for the update, this is referred
as a TRX-group. Normally only one transceiver is needed in the TRX-group,
but in some cases more transceivers are required. The TRX-group should not
be confused with Department (see below).
1.3.2 Roaming
If the acknowledgement from the ESL is not received by the transceiver the ESL
will enter roaming state. The Pricer Server will automatically try to re-establish
contact with the ESL again in a certain time interval. For roaming transmissions
the Pricer Server automatically creates up to 3 optimized TRX-groups for each
basestation with maximum 12 transceivers in each TRX-group.
Roaming logic
The roaming logic can change depending on several special cases.

The typical roaming logic look like this:
6
*) The retransmission can be done up to 4 times for an HD label (2 x PP16 and 2 x PP4) if no
acknowledge is seen. Segment labels always use the PP4 communication protocol, and only
one retransmission.
Fast-, normal- and slow roaming always use the PP4 communication protocol regardless of HD
or segment label, and only one transmission/interval.
1.3.3 ESL barcode

The ESL barcode is in the CODE128 format and is unique for each produced ESL.
L Revision level. One upper case letter (A-Z)

'4' Barcode format identifier (2=Transceiver, 3=Basestation/BLE stick, 4=ESL)
ff Production line. Two digits (00 - 64)
ddd Production date. Three digits (000 - 953). Year followed by week (713 = 2017 week
13)
nnnny Serial number. Five digits (00000 - 65535). Is unique within the production line aaaa
ESL type. Four digits (0000 - 9999)
c Check sum. One digit (0 - 9). The modulo-10 value of the sum of ASCII values for all
16 preceding characters.
Fff Production line. Derived from ff in the barcode. Printed as F followed by two
decimal digits in the range 00 -64
#ppppp Product number. Printed as # followed by five decimal digits in the range 00000 -
99999. This field is not derived from the barcode
-pp Variation / customization within same product.
yyww Manufacturing date. This field is derived from ddd in the barcode and printed as
four digits in the range yyww, indicating year and week
<A> Option field. Any printable characters. May be used for customer-specific
identifier.
1.3.4 Low battery indication

The ESL regularly monitors the voltage level of the battery and can on demand
acknowledge whether the battery voltage is sufficient or not. After the battery voltage is
considered low the ESL will be functional for some months more. It is recommended that the
battery cassette should be changed as soon as possible after the battery voltage is considered
low. The graphical HD ESL will show a low voltage symbol if the voltage from the battery is low.
For more detailed information see the production specification for the specific ESL.
1.3.5 Temperature indication
To protect the ESL if it is placed outside its operating temperature an out-of-range
symbol will be displayed on the graphical HD ESL. The ESL should then be moved to a
temperature within the operating temperature range. If the temperature is more than 4
degrees outside the operating range no display update at all will be done and the ESL will not
send an acknowledge.
For more detailed information about the operating temperature range see the production
specification for the specific ESL.
1.4 Basestation
The basestation is a hardware component connected to the Pricer Server
computer via the network and to the transceivers via the Front-End LAN cable.
The main function of the basestation is to manage and supervise the transceivers and control
the transmission of ESL data to the transceivers. The transceivers are also powered from the
basestation.
There is a set of light emitting diodes (LEDs) on the basestation, displaying status information.
1.5 Transceiver
The transceiver is a hardware unit between the infrared (IR) link and the
basestation. The transceivers transmit data to the ESLs using infrared light. They
also receive acknowledgements from the ESLs confirming that the data was received. This
confirmation is sent to the Pricer Server so the operator can see that the transmission was
successful.
1.6 Front-End LAN

The Front-End LAN is a cable-based LAN star network that connects the
transceivers with the basestation and transfers both ESL data and electrical
power to the transceivers.
1.7 Department
The department concept is only used for link and unlink operations to get a
faster response time on the ESL. The department consist of a group of
transceivers (max 12 transceivers/department) connected to the same
basestation that will cover one specific area in the store. The different
departments should be a logic area in the store such as fruit and vegetable,
freezers, bread, dairy etc. for easier recognition by the user that is performing the link or
unlink operation. If department is not specified during the link or unlink operation the ESL will
immediately go into roaming.
8
2 General Configuration
To store the item data Pricer use its own MySQL database. The database needs to be updated
with new item properties to be able to store the item data that is send from the customers own
PCA system. The item properties to use is configured in the Pricer Client under Platform |
System Configuration | Item Configuration.
The table below specifies various fields. Type N is numerical and type AN is alphanumerical.
The fields are of two types:
System specific fields These fields are system specific and shall not be changed.
Customer specific fields These fields are specified for a customer as part of the
Customer Configuration. Any unassigned number may be used
freely.
2.1.1 System Specific Fields
No Field Size Type Note

1 ESL action 1 AN Used in the TARGETLINK message.
This field is used to indicate the type of
operation that is carried out for an ESL in the
Pricer Server database.
N = Create a link between an ESL and an
item.
D = Remove a link between an ESL and an
item.
2 Item ID N/a N/a Reserved for the Pricer System.
3 PL Barcode N/a N/a Reserved for the Pricer System.
77 Number of labels 3 N The number of overlay copies to be printed,
must be in the 1 – 255 range.
93 ESL id 27 AN Used in the TARGETLINK message.
121 Item presentation form x AN Used in the UPDATE message to choose item
presentation form (IPF).
124 Model 50 AN Used in TARGETLINK to specify a model.
250 PFI_UPDATE_TIME AN Time (YYYY-MM-DD hh:mm:ss) when the item
where updated in the database.
7001 Global Parameter Name 50 AN Used to identify a global system parameter.
The format is “name of parameter”.
7002 Global Parameter Value 50 AN The value to set for the global system
parameter.
9100 Department 50 AN Used in TARGETLINK to specify a department.
The syntax is : department/<department
name>
9103 Geo Location This is an ESL property that provides the
ESLs geo location in the store.
9104 ESL Location 20 AN This is an ESL property that provides the
ESLs location in the store. Used in
ESLUPDATE message. Optionally, this
location can be specified in TARGETLINK.
9105 Facings 20 AN This is an ESL property that provides the
ESLs facings in the store. Used in
ESLUPDATE message. Optionally, this
10
location can be specified in TARGETLINK.
9500 Valid from N/a N/a Date and time for when a timed update shall
be activated (VALID_FROM). Accepted
formats are either
yyyy-MM-dd HH:mm:ss
or the locale based long format
-101 Link order N Specifies where to link an item on an ESL
configured to show multiple items. ‘0’ would
be the first position, ‘1’ the second etc.
9611 Printer name Name of printer to use for stickers.
2.1.2 Customer Specific Fields

These fields are specified for a customer as part of the Customer Configuration. The preferred
fields are described to make troubleshooting and maintaining the configuration easier.

5 Department 4 N Used for a department ID.
6 Item group 6 N Used for an item group ID.
7 Item name 25 AN The name of the item.
9 Supplier 15 AN The supplier of the item.
10 Package size 5 N Number of items in a retailer package.
23 Price 8 N Standard price including VAT
25 Discount price 8 N Discount price including VAT.
45 Unit price 8 N Unit price. Price per liter or per kg.
46 Discount unit price 8 N Unit price of discount price.
9510 Secondary Item Code N The number to use for a secondary item id.
(SIC_#)
2.1.3 How to add an Item Property
To add an Item Property, follow these steps:
1. At the end of the Item Property list there is a field which contains the text
NEW_PROPERTY.
2. Enter the new preffered name (max 64) of the Item Propery, add the size (max 1024) of the
field and enter a PFI ID number which is not in the list.
3. Click Add so the new Item Property will be added to the list.
4. Click Save to update the database with the new Item Property.
2.1.3.1.1 Price Field checkbox

The Price Field checkbox is used for collecting price change statistics and determine which
item porperties that should be price formated.
Price Change Statistics
Each time an item property, where Price Field is activated, is updated it will trigger a price
change for that item. If same item is updated several times during a day it will still only be
highlighted as one price change. The number of item updates per day can then be viewed in the
Price Change Statistics Report which can be found under Pricer | ESL management | Reports.
12
Price formating
The price formating setting is done under Platform | Server Settings | General Settings.
If set to true (checked) the Price Field will be formated (e.g. 500 will be shown as 5,00) when
this item field is display in the Pricer Client (e.g PRICE field).
2.1.3.1.2 History box

In order to collect ESL position data it can be done in 3 different ways:
GEO_LOCATION_BLE - If BLE position of handheld device is used while linking the ESL on the
shelf, the ESL get that position.
GEO_LOCATION_IR - The ESL is automatically position using IR trilateration. This requires that
the job Generate IR Positioning data is used.
GEO_LOCATION_MANUAL - The ESL is manually positioned on the shelf using the Product
Position Calibration function in the SmartAPP. This also requires that the job the Product Position
Calibration is run after the manual positions has been set.
The History box indicates how many rows per ESL are saved in the database for the geo
position data collection.
For example, if the store has 15 000 ESLs the number of rows will be 1 500 000 (15 000 x 100)
for the GEO_LOCATION_BLE and GEO_LOCATION_IR. For GEO_LOCATION_MANUAL it will
be 150 000.
2.1.4 How to delete an Item Property

To remove an Item Property, follow these steps:
1. Click on the remove icon for the Item Property that should be deleted.
2. Click Save to perform the delete operation.
NOTE! It is not possible to remove an Item Property that is configured in the ESL Configuration
Client.
3 Pricer File Interface (PFI)
The PFI text based interface communicates with the Pricer System through the PCA. The term
PCA is used for the customer system that contains the Price Controlling Application. This is a
Pricer term that is used to describe the component that provides the Pricer System with
information. In a particular customer environment, the PCA can be the Back-Office Computer
System, the POS-system, the Host System or any other system that controls the actual price
of an item and provides the Pricer System with updates whenever the price is changed. The
PCA system interacts with the Pricer System to supply information to the ESLs, either through
the Pricer File Interface (PFI) or through the Pricer Server API.
This section contains:
• Communication Interface
• Text Files
• Environment Independent
The interface takes the following actions:
• Links and unlinks ESLs to items.
• Prints overlays for the ESLs.
• Item maintenance, including add and/or update item information in the Pricer
database. The Pricer System will automatically transmit valid information from the
PCA to the ESLs.
3.1 Communication Interface

The PFI is not a user interface. It is designed to be a software-to-software interface. Before the
PFI information (i.e. the result file) is presented to a user, it should be formatted in a user-
friendly way. This service is not within the scope of the PFI.
3.2 Text Files

The transportation mechanisms through the PFI are common text files, in 8 bit ASCII format or
2-byte UNICODE. The Pricer System automatically detects the format of the input files.
The PCA delivers two files to the Pricer Server, one file to specify the operation to be
performed, and the other file containing the actual data. The two input files for the Pricer
Server are:
• The M1file
A message file produced by the PCA. Contains information about which operation to
perform, where to find the corresponding data file (I1), and where to put the result file.
• The I1 file
The data file related to the operation specified in the M1 file. Produced by the PCA.
The reason for having two separate files as input to the Pricer System (the M1 and I1 files), is
that this allows PCAs built with older components to make the I1 files into static record
14
formats. The Pricer Server creates the result file, R7 which contains result messages which
can be used by the PCA.
NOTE: In the PFI configuration file, the creation of the result file can be optionally switched off.
3.3 Environment Independent

The PFI is not limited to a specific target environment or operating system other than what is
required for the Pricer Server itself. There are no limitations regarding host computers for the
PCA and the Pricer Server. They may be running on the same computer or on two or more
different computers. The only prerequisite is that all PFI files are reachable and can be read
and written within any path of a mounted drive or file system known to the computer where the
PFI service is running.
3.4 PFI Specification

This section contains:
• PFI Procedures and Communication Method
• PFI File Names
3.4.1 PFI Procedures and Communication Method

The general PFI procedures and communication method are described in the steps below:
1. The PCA produces the I1 file and puts it into a specific directory. The Pricer Server
should have full access to this directory.
2. The PCA produces the M1 file and copies it to the pre-defined message directory.
3. The Pricer System finds the M1 file and processes the message. The scan interval of
the directory is configurable.
4. The I1 file must be accessible in a location specified in the M1-file at the time when the
Pricer Server reads the M1 file. The Pricer Server first checks that the information
provided through the interface is syntactically and semantically correct. If not, proper
error codes are put into the result file, and the correct records are processed.
5. The Pricer System produces the result file (i.e. of R7 type), and puts it in the position
specified in the M1 file. The generation of the result file occurs when the Pricer server
has received and accepted all information in the PFI message (i.e. the M1 file and the
corresponding I1 file). The Pricer System removes the M1 file. The I1 file can also be
optionally removed.
6. As a result of the PFI messages, a send out is initiated to any ESL(s) and/or printing
overlays.
PCA
1 2
PFI
I1 M1 R7
4 3 5
Pricer Server
6 6
Pricer labels Paper overlays

Figure 1. PFI Overview.
Special Considerations
If more than one M1-file is found in the directory, the Pricer System creates an internal list of
the files that have been found, and starts to process the oldest one (i.e. the system checks the
modified date of the file). When that M1 file has been processed, the next file in the list is read.
When the list is processed, the directory is scanned again.
3.4.1.1.1 Message File Formats

Message files are 8 bit ASCII or 2-byte UNICODE files. The system automatically detects which
file is used. Each message file contains only one record.
M1 File
The M1 record consists of information regarding where to find the data file (I1), and where to
produce a result file. The M1 file must be placed in a special directory, serving as a message
area (like a mailbox). The Pricer Server scans this directory and any files present in this
directory are processed as M1 files. If more than one file is found in the message directory at
the same time, they are handled in the order they were created.
M1 record format
• PFI Message
• Sign
• StartPath
• DataPath
• ResultPath
NOTE: A comma is used as a field separator.
The message format is not in free text form. Spaces are valid characters. No “white space”
characters (i.e. space, tab, return) are allowed directly before or after the comma. The
message format is always one line.
16
Four commas are required. An omitted parameter is represented by an empty string, but the
commas must still be there. If the StartPath is omitted, then the format is:
• PFI Message
• Sign
• DataPath
• ResultPath
Data path and result path include the file name with an absolute path.
M1 Record Components
Table 1 M1 record components

Component Length Type Description
PFI Message 1 - 25 AN Mandatory: PFI Message. The PFI
Message command must be in upper
case letters.
Comp. 1 Mandatory: Comma (hex 2C).
separator
Sign 4 N Mandatory: A signature used through
out the entire transaction and
returned in the result file. It is highly
recommended that this signature is
unique for the transaction to avoid
mixing results from different
transactions. Non-numeric values are
reserved for system purposes.
NOTE: Always exactly four digits!
separator
StartPath 0 - 80 AN Deprecated component. Leave this
empty.
separator
DataPath 0 - 80 AN Mandatory: optional or ignored,
depending on the PFI Message. Full
path to the data file (I1).
separator
ResultPath 0 - 80 AN Optional: The full path to the result
file. If omitted, the result file is
created with a default path.
NOTE: The creation of the result file
can be optionally switched off in the
PFI configuration file.
Example of a correct update message:
UPDATE,0001,,C:\pricer\PFIFiles\DataFiles\FIL.I1,C:\pricer\PFIFiles\ResultFiles\RESULTFILE
.R7
3.4.1.1.2 Data File Formats

file is used.
One I1 file may contain 1 - N records, where N is an unlimited number of records.
I1 File
The I1 file is a text file that contains item information formatted in records.
I1 record format:
Sign ItemID [ FieldID Pic |Data| ]... ,
[ Sign ItemID [ FieldID Pic |Data| ]... , ]...
Legend:
[ ] Brackets enclose an optional component or set of components.
… Iteration symbol (0 - N).
I1 record component separators:

The following field separators are valid in I1 files:
Character Value (hex)
Space 20
PFI field data enclosure:

Any characters, apart from field separators, record separators and EOF, can enclose the data
fields. It is configured in the Pricer Client Platform | Server Settings |System Parameters. The
R3 default data enclosure is the pipe |. You can only use the separator that is specified in the
configuration file. Avoid characters in the interval 00-1f (hex) or any other character that is
likely to appear in item descriptions or other item data.
I1 record separator:
Comma (hex 2C)
I1 Record Components
Table 2 I1 record components

Sign 4 N Mandatory: All non-numerical
use of this field is reserved for
system purposes. This must be
the same sign as in the
corresponding M1 file.
Comp. separator 1- Mandatory.
18
ItemID 1-19 N Mandatory: It contains the item
identity number (e.g. the EAN
code. The ItemID may under
certain circumstances be
replaced by a wild card symbol *.
Comp. separator 1- *) Mandatory.
FieldID 1-4 N *) The PFI field identifier. The
first digit must not be 0.
Pic 1 N This field is not used and should
be set to zero.
Data enclosure 1 *)
Data 0-50 AN *) The value of the PFI field in
text string format (must not
contain field or record
separator).
Data enclosure 1 *)
Comp. separator 0- Optional.
Record separator 1 Mandatory.
*) FieldID, Pic and Data together constitute one PFI field. They are optional as a group, but
mandatory within the group, (i.e. if one is present, they all must be present).
The PFI fields are handled by the Pricer Server. The correct fields are processed and inserted
into the database. Fields that are not contained in the configuration are reported in
...\R3Server\logs\BackOfficeLog.txt.
The input stream uses free text format. Any number of blank characters may be present
between the different elements (see the definition of component separators above). It is
recommended that the input data file is formatted in a readable way since this will simplify
debugging. The performance of the system is not affected by the format of the input data files.
All three examples shown below are correctly assembled.
Example 1 (unformatted):
0001 7311540029202 23 0 |00560| 45 0 |01120|,0001 7311540029203 23 0 |01500| 45 0 |06000|
7 0 |Grape Juice|,
Example 2 (formatted):
0001 7311540029202 23 0 |560| 45 0 |1120|,
0001 7311540029203 23 0 |1500| 45 0 |6000| 7 0 |Grape Juice|,
3.4.1.1.3 Result File Formats

file is used.
The result file contains one record per line. The format of this file can be configured. Creation
of the result file can be optionally switched off.
R7 File
The R7 file format prescribes that a result file is produced for each PFI message file executed
by the Pricer Server. This file contains a status report indicating the success or failure of the
corresponding PFI message file operation. The result file does not include the result of the
actual send-out.
The result file is placed in the specified location by the ResultPath in the M1 record, or, if
ResultPath is omitted, at a default location. This is configurable in Pricer Client Platform |
Server Settings |System Parameters. Default location and file name is
\Pricer\PFIFiles\ResultFiles\ResultFile.r7.
One record in the R7 file may refer to either:
• The complete PFI message.
• One record in the I1 file.
R7 File Record Components

Sign 4 N Always present. Sign (the same as
in the M1 and I1 files).
ItemID 19 (or AN Always present. Item identity (as in
longer if the corresponding I1 file). Item
actual ID identity is set to 19 spaces (ASCII
is longer) 20 hex) if the item id is not relevant
for the R7 record.
Support
for 255
char.
ResultCode 3 AN Always present. Result code (i.e.
E00 if OK).
CRLF 2 Always present. <CR><LF> (hex 0D
0A). Marks end of record.
Example of R7 records:
0001 7310070009401E00
0001 57165134E51
1001ABC-123-731-554-992E00
1001ABC-123-731-554-992-523-4533-1213E00
0001 7324568003215E09
0001 E37
NOTE: The difference between the records: The first two records refer to an I1 record, and the
fourth to a complete PFI message.
20
3.5 PFI File Names
There are no restrictions on how to name the PFI files. The only rule is that the M1 file must be
moved or copied to a directory that is configured for the Pricer Server.
The PFI message server will consider each file found in that directory as an M1 file. The full
paths (drive, directory path and file name) to the I1 and result files are specified within the
contents of the M1 file.
3.6 PFI Message Specification

This section covers the PFI messages supported by the Pricer System. The function and syntax
for each message is described in detail. For a complete list of return codes, refer Appendix A.
This chapter describes the following commands:
• UPDATE
• TARGETLINK
• PRINT
• REFRESH
• SETGLOBAL
• DELETE
• ESLUPDATE
• LINKUPDATE
• LED
• PICKLIST
3.6.1 UPDATE
The UPDATE PFI message is used for item maintenance. This message is mainly used for
updating the information (e.g. the price) on different items. A send out is always performed on
all ESLs that do not have up-to-date information. The result file is normally created when
updating the Pricer database and is finished before the send out is complete.
The behavior of the message can be configured according to the following parameters:
“Unknown item in UPDATE”
Install Adds the item to the Pricer item database.

Report Reports an error in the result file and
ignores the item.
Ignore Ignores the item.
“Reject UPDATE on Unlinked”
True Does not allow an unlinked item to be

updated.
False Allows an unlinked item to be updated.
M1 File
PFI Messages: UPDATE
Mandatory M1 parameters: PFI Message, Sign, DataPath
Optional M1 parameters: StartPath, ResultPath
Ignored M1 parameters: None
M1 record examples:
UPDATE,0001,,C:\UPDATE.I1,C:\UPDATE.R7
I1 File (for both messages)
All PFI fields can be used, except for those normally used in TARGETLINK (1 and 124).
Field 121 is used to specify the Item Presentation Form for the item, and decides which layout
to use for the send out.
Format of field 121:
121 0 |IPF|
I1 record examples
0001 1111122222333 23 0 |1230| 45 0 |12300| 43 0 |54321| 121 0 |normalprice|,
R7 File
The R7 file contains the result codes.
3.6.1.1.1 PFI Timed Updates

Normally the item table is updated immediately after a PFI Update file is found in the message
folder. To delay the update and schedule a future change it is possible to use the system PFI
field 9500 for specifying the date and time for the change to take effect.
Format of field 9500:
9500 0 |Date|
Date format is either yyyy-MM-dd HH:mm:ss or the locale based long format. If an incorrect
date format is detected the error code E64 is returned in the R7 result file, and the I1 record is
rejected.
If a past date/time is detected the update will take immediate effect.
I1 record example:
0001 1111122222333 23 0 |1230| 45 0 |12300| 43 0 |54321| 9500 0 |2015-06-06 13:23:00|,
The Timed Update function requires a license key. If the system does not have a valid license
key the I1 record is rejected and error code E65 is returned in the R7 result file.
22
3.6.2 TARGETLINK
The TARGETLINK message is used for linking and unlinking ESLs to and from items in the
Pricer System database. As the result of a successful linking operation, the ESL is
automatically updated with the current item information. "OFF” is sent to the ESL which is
unlinked from its item as a result of a TARGETLINK message. The TARGETLINK message can
specify which department OFF is sent. If the department is not specified, OFF is sent in the
Back Office department or in the last known department location. The result file is generated
prior to any send out completion.
NOTE: Items are never deleted from the Pricer database as a consequence of this message.
The behavior of the TARGETLINK message can be configured according to the following
parameters:
• “Item must exist”: true/false
If “false”, a link between the ESL and the item is prepared in advance, and fulfilled
when the item is updated in the Pricer server by an UPDATE PFI message.
If “true”, a link between the ESL and a non existing item is rejected.
• “Allow moving PL”: true/false
If “true”, a given ESL that is already linked to another item then the one specified in
the I1 record, will have the old link removed, and a new one created.
If “false”, an already linked ESL cannot be linked to a new item.
M1 File
PFI Message: TARGETLINK

M1 record example:
TARGETLINK,0001,,C:\TARGLINK.I1,C:\TARGLINK.R7
I1 File
The PFI field 1 is used to specify whether it is a "link" or an "unlink" operation. The PFI field 93
holds the ESL ID, a 17 character code that is found both as a barcode and in clear text on the
back of each ESL. The PFI field 124 is used to choose a model. The model can be seen as a soft
ESL type, not only deciding the physical ESL type, but also which type of paper overlay to use,
and what ESL layouts to use for specific item presentation forms.
Generic rules:
Mandatory PFI fields: 1

If PFI field 1 is set to”N” (install a new ESL), then ItemID and field 93 are mandatory. The PFI
field, 124 is optional according to the following list:
93, Link an item to ESL, use the model specified in field
124 124.
93 Link an item to ESL and use a default model for the
ESL type.
Field 9100 (department) can be used to specify that an ESL is placed at a certain location in
the store.
It is also possible to include the system specific fields 9104 (ESL Location) and 9105 (Facings)
in the I1 record.
If the PFI field 1 is set to”D”, (remove a link between an item and an ESL or a group of ESLs) the
ItemID or field 93 may be excluded according to the following lists (the “excluded” ItemID is
set to the wild card character *). Field 124 is never used. Valid combinations if field 1 is set to
”D”:
ItemID Remove the link(s) between ItemID and all its
ESLs. Field 93 is not allowed. All ESLs linked to
the item are deleted.
93 Remove the link between the ESL and the item.
The ItemID is set to ‘*’.
NOTE: The ESL ID and Item ID may not be used together. Either use ESL ID with Item ID set to
‘*’, or the Item ID. Field 9100 (department) may be used when removing the link between an
item and an ESL. It specifies where OFF is sent.
I1 record examples:
0001 1111122222444 1 0 |N| 93 0 |D4575254697412032| 124 0 |3P-FOOD|,
0001 1111122222555 1 0 |N| 93 0 |D4575254697412032|,
0001 1111122222666 1 0 |D|,
0001 * 1 0 |D| 93 0 |D4575254697412032|,
I1 record examples with defined departments:

0001 1111122222444 1 0 |N| 93 0 |D4575254697412032| 124 0 |3P-FOOD| 9100 0 |A02|,
0001 1111122222666 1 0 |D| 9100 0 |A02|,,
0001 * 1 0 |D| 93 0 |D4575254697412032| 9100 0 |A02|,
I1 record examples with defined ESL Location and Facings:

0001 1111122222444 1 0 |N| 93 0 |D4575254697412032| 124 0 |3P-FOOD| 9100 0 |A02| 9104 0
|Row4| 9105 0 |9|,
If an ESL model is configured to show several items on the same ESL, field -101 indicates on
which position an item shall be put on the ESL. ‘0’ would be the first position, ‘1’ the second
etc. Examples:
Link to position 1: 0001 12345 1 0 |N| 93 0 |Z4543063315013154| -101 0 |0| 124 0 |SmartTAG HD
L_Multi|,
Link to position 2: 0001 67890 1 0 |N| 93 0 |Z4543063315013154| -101 0 |1| 124 0 |SmartTAG
HD L_Multi|,
Unlinking items from a multi item ESL can be done by either indicating no position, which will
unlink all items linked to the ESL, or by indicating position. Examples:
Unlink position 1: 0001 * 1 0 |D| 93 0 |Z4543063315013154| -101 0 |0|,
Unlink position 2: 0001 * 1 0 |D| 93 0 |Z4543063315013154| -101 0 |1|,
Unlink the whole ESL: 0001 * 1 0 |D| 93 0 |Z4543063315013154|,
R7 File
The R7 file contains the result codes.
24
3.6.3 PRINT
This PFI Message is used for printing overlays.
M1 File
PFI Message: PRINT

M1 record example:
PRINT,0001,,C:\PRINT.I1,C:\PRINT.R7
I1 File
The following PFI fields may be used in the I1 file:

• 124 - The name of the model.
• 77 - The number of overlay copies.
If any of these fields are missing, the default values will be used. The default for field 124
depends on the ESL. The default for field 77 is 1 and is not configurable.
I1 record examples:
0001 1111122222441 124 0 |B_MODEL_0| 77 0 |2|,
0001 1111122222442 124 0 |B_MODEL_0 |,
0001 1111122222443,
Result File
The result file contains the result codes.
3.6.4 REFRESH
This message is used for creating a send out to all ESLs if the displayed information is not
currently up-to-date because of a change in the item information or the ESL layout. ESLs that
do not respond are sent into roaming.
M1 File
PFI Message REFRESH

Mandatory M1 parameters PFI Message, Sign
Optional M1 parameters StartPath, ResultPath
Ignored M1 parameters DataPath
M1 record example:
REFRESH,0001,,,C:\REFRESH.R7
I1 File
No I1 file is used for this PFI Message.
Result File
The result file contains an E00 if the PFI Message was successfully executed or an E04 if the
transmission failed.
3.6.5 SETGLOBAL
This message is used for setting the value of global system parameters. It is normally used for
currency handling. Note that you need to send a PFI REFRESH command after the SETGLOBAL
command to trigger a price update.
M1 File
PFI Message SETGLOBAL

Mandatory M1 parameters PFI Message, Sign, DataPath
Optional M1 parameters StartPath, AnswerPath
Ignored M1 parameters None
M1 record example:
SETGLOBAL,0001,,C:\SETGLOB.I1,C:\SETGLOB.R7
I1 File
The following PFI fields are used to specify the parameter name and the associated value in
the I1 file:7001, 7002.
The Item ID should be set to the wildcard character (*, hex 2A), indicating that no item is
involved in this operation, PFI field 7001 specifies the name of the system parameter. PFI field
7002 holds the value to be assigned to the parameter.
Mandatory PFI fields: 7001, 7002

I1 record example:
0001 * 7001 0 |CurrencyRate:SEK| 7002 0 |3.5|,
Result File
This file contains the result codes.
3.6.6 DELETE
The DELETE message is used for deleting items from the Pricer database. If the item is linked
to an ESL the link will be removed. (OFF is sent to the ESL) and the item is deleted.
26
M1 File
PFI Message: DELETE

M1 record example:
DELETE,0001,,C:\pricer\PFIFiles\DataFiles\Delete.i1,C:\pricer\PFIFiles\ResultFiles\Delete.
r7
I1 File
No PFI fields are mandatory in the I1 file. The I1 record can include only the sign and item ID or
also include the item fields for the item properties that are used.
Mandatory PFI fields: none
I1 record example:
0001 11111222222344,
Result File
The result file contains the result of the PFI Message File (an R7 code).
• E00
This error is reported when the command is successfully processed.
• E50
This error is reported if the item does not exist in the Pricer database.
R7 record examples:
0001 11111222222344E00
3.6.7 ESLUPDATE
The ESLUPDATE message is used for updating ESL properties on individual ESL basis. To use
the command the integrating system must have the knowledge of which ESLs that are linked
to which items. For a transmission to occur, support in the layout script is required.
M1 File
PFI Message: ESLUPDATE

M1 record example:
ESLUPDATE,0001,,C:\pricer\PFIFiles\DataFiles\Eslupdate.i1,C:\pricer\PFIFiles\ResultFiles\E
slupdate.r7
I1 File
The PFI fields 9104 (location) and 9105 (facings) can be used.
I1 record example:
0001 * 93 0 |A4645160001912138| 9104 0 |Row4|,
0001 * 93 0 |A4645160001912138| 9104 0 |Row4| 9105 0 |2|,
Result File
• E00
This error is reported when the command is successfully processed.
• E52
When specified label does not exist in your system.
.
R7 record examples:
0001 * E00
0001 * E52
3.6.8 LINKUPDATE
The LINKUPDATE message is used for updating LINK properties on individual LINK basis. To
use the command the integrating system must have the knowledge of which ESLs that are
linked to which items.
M1 File
PFI Message: LINKUPDATE

M1 record example:
ESLUPDATE,0001,,C:\pricer\PFIFiles\DataFiles\Linkupdate.i1,C:\pricer\PFIFiles\ResultFiles\
Linkupdate.r7
I1 File
The PFI field 9105 (facings) can be used.

I1 record example:
0001 1 93 0 |A4645160001912138| 9105 0 |17|,
0001 2 93 0 |A4645160001912138| 9105 0 |2|,
Result File
R7 record examples:
28
0001 * E00
0001 * E78
3.6.9 LED
The LED message is used to enable the SmartFlash on selected ESLs for limited time. Specify
an item id to control the led on all labels linked to the item or a barcode to control a single
label. If both an item id and a barcode are specified the item id is ignored.
M1 File
PFI Message: LED

M1 record example:
LED,0001,,C:\pricer\PFIFiles\DataFiles\Led.i1,C:\pricer\PFIFiles\ResultFiles\Led.r7
I1 File
The following PFI fields are used:

• 93, Barcode
• -107, REALTIME_TRANSMISSION set to realtime or normal (optional).
• -108, PRICER_API_DURATION time in seconds for flash. A value of 0 turns of a flashing
led.
Can only be one of the following values: 0, 4, 8, 30, 60, 300, 900, 1800 in seconds.
• -109, PRICER_API_STRONG_FLASH set to true (strong) or false (weak).
I1 record example:
0001 * 93 0 |N4015131583515145| -108 0 |30| -109 0 |true| -107 0 |true|,
0001 1 -108 0 |30|,
0001 * 93 0 |A4645160001912138| -108 0 |30|,
Result File
R7 record examples:
0001 * E00
0001 1 E00
0001 * E78
3.6.10 PICKLIST
The PICKLIST message is used for importing pick lists for Click & Collect. Pick list import uses
a different format for both the M1 files and the I1 files than the other PFI messages. Pick list
messages also use an output file containing the end result of the picking. The format of the
files are described below.
M1 File
6 comma separated fields:

• Type of message always PICKLIST
• Order number
• Pick up time
• Data file
• Result file
• Output file
M1 record example:
PICKLIST,12345,2014-12-01 14:00:00,C:\Pricer\PFIFiles\DataFiles\pick_list.i1,C:\Pricer\PFI
Files\ResultFiles\pick_list.r7,C:\Pricer\PFIFiles\ResultFiles\pick_list.out
I1 File
4 comma separated fields:

• Item id
• Number of items
• Allow replacement articles
• Comments to the employee
I1 record example
4009900483742,1,false,comment
9312631142105,2,true,
Result File
This file contains the result codes.
Output File
The output file has variable number of fields. The first field contains the order number, the
second contains the requested item and the following fields contain the actually picked items.
Output file example:

12345,4009900483742,4009900483742
12345,9312631142105,9312631142105,5021991000225
30
3.7 PFI Configuration
This section lists the configuration parameters related to PFI.
The PFI is configured in the Pricer Client Platform | Server Settings |System Parameters.
Parameter/Field Default Description/Parameter values

value
•
•
•
value
3.8 PFI Backward Compatibility Summary
R3 and R4 compatibility
Expect full backwards compatibility.

ESLUPDATE commands with link properties will update the link properties on all links to the
label to preserve compatibility with R4.
R2.4 compatibility
Compatibility with R2.4 is removed.
32
4 Text Adapter
The Text Adapter is used to import text files containing item information. It can be configured
to parse either text files with fixed length fields or files using a separator character. The Text
Adapter is included in the Pricer Client.
Select Platform | System Configuration | Text Adapter in the main menu to display the “Text
Adapter” landing page.
4.1 Text Adapter fields
Scan Settings
Parameter/Field Description/Parameter values

Adapter Alias Alias name of adapter.
It is possible to create several adapters that import files from
different locations. Use the + button to create a new adapter.
Scan Method Either Server Directory or Remote FTP Server.
Scan Directory Location where the Pricer Server should check for new files is
scan method Server Directory is used.
FTP Directory Location where the Pricer Server should check for new files if
scan method Remote FTP Server is used.
FTP Username FTP username if scan method Remote FTP Server is used.
FTP Password FTP password if scan method Remote FTP Server is used.
Scan Interval (seconds) Specifies how often to scan the given directory for new files.
Searched File Pattern The file pattern of the file that the Pricer Server will look for. If
the file pattern does not match the file names in the scan
directory folder they will not be processed.
If the data file name pattern is specified as “*dat*.txt”, the
actual files may be named “Update_dat1281.txt”. If “Use Flag
File” is set to Yes, the file name pattern also applies to the flag
file.
Use Flag Files A flag file is an empty file telling the system to read a specific
data file. It is used to make sure the data file is not read before
it is complete. The name of the flag file shall be the same as
the data file but with a different extension. If, for example the
flag file is named “Update.flg”, the data file could be named
“Update.txt” or “Update.csv”.
File Processing Settings

Launch Pre-processing Program Can be used if some formatting is necessary before the Pricer
system can handle the file, for example, changing number
formats or adding and removing data.
Launch Post-processing Can be used to perform some action after the file has been
Program handled. For example, saving data or result file in a special
place.
Start the Parsing at Line Used to start processing on the relevant line if the first few
lines contain other data.
File Type The import files can be of two different formats; Variable
Length or Fixed Length. See below for more information.
Field Separator The separator of the data fields needs to be separated by a
specified character, for example “|” (pipe) or “;” (semicolon).
This is applicable only if file type Variable Length is used.
Delete Processed Files Specify Yes/No if the processed file should be saved in the
processed folder or not. If something went wrong during the
processing of the file, it will instead be moved to the errors
folder. The file will be moved to the errors folder even if delete
file has been set to Yes.
Delay Until Deletion (days) Number of days to wait until file is automatically deleted if it
has been saved in processed folder.
34
Line Parser Settings

Field No. The number of the field in the file. Only available when file type
Variable Length has been applied.
Item Property A drop-down list of all the Item Properties that have been
configured for this installation (see the list in Platform |
System Configuration | Item Configuration).
No. of Characters Specify from which number of characters the data can be
found in the file. Only available when file type Fixed Length has
been applied.
Numeric If this check-box is ticked, the data is treated as numeric. For
example, if price is given with leading zeroes, the zeroes are
removed.
Ignore Separators If this check-box is ticked, any separators in the data are
removed. For example, if a price is given with decimals, the
decimal point are removed.
4.2 File type examples
Variable length
Fixed length
4.3 File processing steps
1. The file (i.e. update_001.txt) is put in the scan directory location (i.e.
\Pricer\TextAdapter).
2. When the file has been parsed it will be moved into the processed folder and a result
file will be created in the results folder.
3. If a file contains any errors it will be stored in the errors folder.
36
5 Drop Folder
The Drop Folder functionality offers that a pre-generated image can be send to the Pricer
Server and transmitted to a graphical ESL. The pre-generated image is then “dropped” into a
specified folder within the Pricer installation, for example \Pricer\R3Server\images\drop. It is
important that the size of the image match the actual display size of the ESL.
5.1 System Parameters

To activate and configure the Drop Folder functionality these system parameters are used. Go
to Pricer Client Platform | System Configuration | System Parameters.
Parameter/Field Default value Description/Parameter values

DROP_FOLDER_ACTIVE FALSE Parameter values:
• TRUE: Drop folder functionality is active.
• FALSE: Drop folder functionality is inactive.
DROP_FOLDER_LOCATION images\drop Shows the drop folder default location. The
location is either relative to the R3Server folder or
absolute.
DROP_FOLDER_SCAN_INTERVAL 3 The time in seconds the Pricer Server will scan the
Drop folder for new images.
ITEM_MUST_EXIST TRUE This parameter needs to be set to FALSE in order
for the item to be added automatically to the
database.
5.2 Item Properties

Create an Item Property with the name of the actual size of the display and then followed by
the page number (0 = price page, 1 = info page 1, 2 = info page 2). This example is for
SmartTAG HD M+ for price page (0) and info page (1).
5.3 ESL Configuration
Create a new Image property which should cover the entire display. So for example SmartTAG
HD M+ needs to have the size of 208x112. Then select correct Item Property to use from the
Data source dropdown list. Fine adjust the Metrics for the image box so it covers the entire
display.
5.4 Image information
Image format
The pre-generated image must have the same size as the display it should be transmitted to,
for example a 208x112 image intended for the SmartTAG HD M+.
File name format
The file name must be in a specific format like “5000112579758_0A.bmp”.
Format Description
ITEMID The ITEMID of the product, for example 5000112579758.
Separator _ (underline which is mandatory)
Page number One single character digit representing the page to be updated.
0 = price page
38
Format Description
1 = info page 1
2 = info page 2
ITEMID Format A = strict ASCII if the ITEMID can be represented as a file name, for example
5000112579758.
X = if it cannot be strict ASCII then each character in the filename shall be
represented as its two character HEX. For example, 5000112579758 has
the HEX of 35 30 30 30 31 31 32 35 37 39 37 35 38. In that case the file
should have been named 35303030313132353739373538_0X.bmp.
Extension File extension.
Supported formats:
• BMP
• JPG
• PNG
Result file format
In the specified drop folder a result file like “5000112579758_0A.r” will be created with the
same name as the image that was processed but with the file extension [.r]. The original image
file will automatically be deleted.
Result text Description

SUCCESS Image parsing succeeded.
ERROR_IMAGE_API_ERROR Wrong image format.
ERROR_WRONG_FORMAT_NO_PAGE_OR_NUMERIC Wrong name format of the file.
ERROR_ITEM_DOES_NOT_EXIST ITEMID in database does not exists.
This error message depends on the setting for
the ITEM_MUST_EXIST system parameter.
ERROR_UNABLE_TO_PARSE_HEX_FORMAT Wrong ITEMID HEX format.
6 Public API
Pricer offers a Public API using Web services for the 5.0 API.
RMI is still supported in the old 4.7 API.
6.1 Ports
In the Pricer Client under Platform | System Configuration | System Parameters the ports are
configured.

value
6.2 Usage
To learn more about the public API see Pricer Public API Guide with code examples. The
complete API documentation can be found in the APIDoc_R5_x.zip file.
40
Appendix A COMPLETE LIST OF R7 RETURN CODES
The result codes are used for both PFI and Text Adapter.
Legend to "A List of PFI Result Codes"
Legend Description
1 The return code refers to the complete PFI

Type message.
2 The return code refers to one I1 record.
F REFRESH message.
T TARGETLINK message.
U UPDATE message.
Message
P PRINT message.
D DELETE message
S SETGLOBAL message
E ESLUPDATE message
Normal Normal operation.
Warning Operation fulfilled with minor non-fatal problems.

Severity
Error Operation failed, but the system continues to work
normally.
Fatal Fatal error, the system is degraded or non-

operating.
List of PFI Result Codes
Error Type Message Severity Description

Code
E00 12 TUFPDSE Normal Operation OK.
E01 -2 -U----- Error/Warning The item has no ESL linked to it.
E04 -2 --F---- Warning Transmission failed.

Code
E08 -2 TU-PDSE Error Signature mismatch between M1 file and record in I1

file.
E19 1- TU-PDSE Warning The I1 file was empty.
E21 1- TUFPDSE Error PFI processing interrupted. This error code is present if
the server was shut down in the middle of a PFI job. The
message file will be processed again the next time the
server is started.
E25 1- TU-PDSE Fatal I1 file could not be opened.
E27 1- TUFPDSE Error The result file could not be created at the position
specified in M1. A result file is created at the default
position.
E29 1- TUFPDSE Error Unknown PFI message.
E36 12 TUFPDSE Error Syntax error in M1 file or I1 file.
E37 12 TUFPDSE Error Semantic error in M1 file or I1 file. (Including "unknown

ESL type".)
E39 -2 T------ Error TARGETLINK failed.
E41 -2 -----S- Error System parameter not defined.
E50 -2 TU-PD-- Error Unknown item. I1 record is rejected.
E51 -2 T------ Warning Unknown item. I1 record is handled.
E52 -2 ------E Error Unknown ESL. I1 record is rejected.
E54 -2 T------ Error Unknown model. I1 record is rejected.

This return code was earlier also used when printing
and using an unknown model. Today the default model
is used and E00 is returned. If no default printer model
is set E54 is still returned.
E56 -2 ---P--- Error Overlay could not be found.
E60 -2 T------ Error ESL is already linked to another item. I1 record is

rejected.
E61 -2 -U----- Error Warning ESL is already linked to another item. I1 record
is handled.
E62 -2 TU----E Warning SUBCELL_INPUT_CHANGED_DEFAULT This means that

the department specified in PFI file is changed due to
some reason. The transmission will occur in default
department.
E63 1- T-----E Error SUBCELL_TABLE_NULL

This means that there is no department configured, so
transmission has failed.
E64 -2 -U----- Error Date/time format in PFI field 9500 is incorrect. I1 record
is rejected.
42
Code
E65 -2 -U----- Error No license for Timed Updates. I1 record is rejected.
E66 -2 -U----- Warning Item was updated but one or more item properties were
truncated because it was too long for its database
column.
This return code has been removed. Instead a log
messages is written when truncation has occurred.
E67 -2 -U----- Error You are not permitted to do a secondary item code
update, when the line has a timed update command.
E68 -2 -U----- Error The secondary item code specified already exists
(which is not a problem) but it is linked to a different
item. The relinking of secondary item codes is not
supported with the current configuration. Change the
ALLOW_MOVING_SIC parameter to allow this scenario.
E69 -2 -U----- Error The secondary item code cannot be added as it already
exists as an item id.
E70 -2 -U----- Error The given position on a multi item ESL is not valid.
E71 -2 -U----- Error The item cannot be linked to the multi item ESL
because there is no position available, or no link order
is given.
E72 -2 -U----- Error The given position on a multi item ESL is already linked
to an item.
E74 -2 -U----- Error A multi item position was given for a model which is not
a multi item model.
E75 -2 -U----- Error An attempt was made to unlink using ItemId and multi
item link order. The link order position cannot be given
since unlinking an item removes all links for the item.
E76 -2 -U----- Error Two different ESL models cannot be used on the same
multi item ESL.
E77 T------ Error When a system contains ESLs 10 years or older, and a
new ESL is linked, there is a small risk that the internal
ID of the ESL is duplicated. If a link attempt is done
when a duplicate exists in the system, the link will be
refused.
E78 -2 -------L- Error No matching link for the barcode and item id specified
E79 -2 TU----EL- Error Invalid barcode supplied
E80 -2 Error SmartFlash not supported by label
E81 -2 Error Not supported by license
EEE Error File import failed due to unknown error

Appendix B SECONDARY ITEM CODES (SIC)
This chapter explains Secondary Item Codes (SIC) and how to work with it.
The Pricer system supports handling of coupled EAN codes. This means that there may be
several EAN codes for the same article. The support allows linking an ESL to the same item
using a number of different EAN. Without support for coupled EAN, the PCA system can only
send one EAN (the Item ID) to the Pricer system.
The PCA system on the other hand could have several coupled EAN codes to the same product.
The reason for using coupled EAN codes is to have only one product, for example “Coca Cola
Classic”, instead of having several single products depending on what country the Coca Cola
was produced in.
SIC Explanation
In the following example, the product Coca Cola is used. In the PCA system there are two EAN
codes connected to it, 5000112579758 and 5449000000996.
In order for both codes to be able to be used, the second code must be registered as a
secondary item code. With a configuration to use secondary EAN, linking ESLs to any of the
EAN connected to an item may be done successfully.
Link an ESL using the first EAN:
Link another ESL using the secondary EAN:
44
The link will be successfully performed to the EAN used as Item ID in the system:
It is also possible to use a secondary EAN to search for an item:
How to configure SIC
SIC related parameters can be found in the Pricer Client under Platform | System Configuration
|System Parameters.
Parameter/Field Default value Description/Parameter values

SIC_ALLOW_MOVING_SIC FALSE Parameter values:
• TRUE: The secondary item code is allowed to be
relinked to a different item.
• FALSE: The secondary item code cannot be
relinked to a different item.
SIC_APPEND TRUE Parameter values:
• TRUE: The new secondary item code is added to
the current secondary item code.
• FALSE: The new secondary item code replaces
the current secondary item code.
Pricer File Interface (PFI) configuration
PFI ID number to use for the secondary codes. The default is 9510.
Configure the PFI integration to include secondary item codes on PFI number 9510.
Example: 0001 5000112579758 7 0 |Coca Cola Classic| 23 0 |500| 9510 0 |5449000000996|,
There are no limitation how many SIC that can be provided in the 9510 field. It needs only to be
separated by <space>.
Example: 0001 5000112579758 7 0 |Coca Cola Classic| 23 0 |500| 9510 0 |5449000000996
5449000000439 5449000131843|,
Text Adapter configuration
The Text Adapter has a SIC_# in the dropdown list.
Example:
5000112579758|Coca Cola Classic|500|5449000000996:5449000000439:5449000131843|
SIC related Error Codes
E67 -2 -U----- Error You are not permitted to do a secondary item code
update, when the line has a timed update command.
E68 -2 -U----- Error The secondary item code specified already exists
(which is not a problem) but it is linked to a different
item. The relinking of secondary item codes is not
supported with the current configuration. Change the
ALLOW_MOVING_SIC parameter to allow this scenario.
E69 -2 -U----- Error The secondary item code cannot be added as it already
exists as an item id.
46
Appendix C PORTS OVERVIEW
To be able to communicate with the different Pricer components and functions some TCP/UDP
ports needs to be accessible. For more detailed information see the individual manuals for the
different Pricer components and functions.

Pricer Integration

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Pricer Integration

Transféré par

Droits d'auteur :

Formats disponibles

SYSTEM GUIDES

Version R5.5.0 (2018-02-02)

1.1 How it works?

1.3 Electronic Shelf Label

The roaming logic can change depending on several special cases.

1.3.3 ESL barcode

L Revision level. One upper case letter (A-Z)

1.3.4 Low battery indication

1.6 Front-End LAN

2.1.1 System Specific Fields

No Field Size Type Note

2.1.2 Customer Specific Fields

No Field Size Type Note

2.1.3.1.1 Price Field checkbox

Price Change Statistics

2.1.3.1.2 History box

2.1.4 How to delete an Item Property

3.1 Communication Interface

3.2 Text Files

3.3 Environment Independent

3.4 PFI Specification

3.4.1 PFI Procedures and Communication Method

Pricer labels Paper overlays

3.4.1.1.1 Message File Formats

Table 1 M1 record components

3.4.1.1.2 Data File Formats

I1 record component separators:

PFI field data enclosure:

Table 2 I1 record components

3.4.1.1.3 Result File Formats

R7 File Record Components

Component Length Type Description

3.6 PFI Message Specification

“Unknown item in UPDATE”

Install Adds the item to the Pricer item database.

True Does not allow an unlinked item to be

I1 File (for both messages)

The R7 file contains the result codes.

3.6.1.1.1 PFI Timed Updates

PFI Message: TARGETLINK

Mandatory PFI fields: 1

I1 record examples with defined departments:

I1 record examples with defined ESL Location and Facings:

The R7 file contains the result codes.

PFI Message: PRINT

The following PFI fields may be used in the I1 file:

The result file contains the result codes.

PFI Message REFRESH

No I1 file is used for this PFI Message.

PFI Message SETGLOBAL

Mandatory PFI fields: 7001, 7002

This file contains the result codes.

PFI Message: DELETE

PFI Message: ESLUPDATE

PFI Message: LINKUPDATE

The PFI field 9105 (facings) can be used.

PFI Message: LED

The following PFI fields are used:

6 comma separated fields:

4 comma separated fields:

• Allow replacement articles

• Comments to the employee

This file contains the result codes.

Output file example: