eLink Home | Documentation Home

eLink All Objects API Technical Documentation

eLink protocols define a number of standard packets to transfer information. The contents and structure of these packets is tightly controlled in order to ensure maximum interoperability. These packets are often called APPT packets in reference to the underlying binary protocol name. Each packet has two standardised fields that define the contents of the packet.

APPT packets are defined by an application and each application is granted a unique F3 value. Within this space, that application is responsible for managing the individual packet types, identified by F2 values. For example, RetailMAX has been assigned the unique F3 value of "21", so whenever you see <f3>21</f3> you are able to instantly recognise this as a RetailMAX defined data structure.

RetailMAX Point Of Sale (21)

• 21,1 Salelines. Individual items on a sale or purchase order
• 21,2 Payment lines
• 21,5 Quantity Discount Breaks
• 21,6 Barcode Definition/Parse result
• 21,7 Size/Price detail
• 21,270 Audit log record
• 21,271 Userflow. Internal process information about path used
• 21,380 Reserved for a specific customer
• 21,401 GDS Geographic location

RetailMAX Customer Link (23)

• 23,11 Retailer. Overview information about a retailing entity
• 23,10 Retailer Outlet. Details about a single outlet or store for a retailer.