The concept of API (Application Programming Interface) means a software interface that exposes software, thus enabling other products to use its internal services and procedures. Priority’s API module connects the commerce site to the Head Office system that exists in the ERP, enabling uniform management of all the organization’s sales channels, inventory, purchasing, and logistics.
In fact, use of the EDEA API enables easy operation of the commerce site, managing it as another branch of the retail chain

 

 

 

 

eCommerce API sites for Priority

 

The concept of API (Application Programming Interface) means a software interface that exposes software, thus enabling other products to use its internal services and procedures. Priority’s API module connects the commerce site to the Head Office system that exists in the ERP, enabling uniform management of all the organization’s sales channels, inventory, purchasing, and logistics.
In fact, use of the EDEA API enables easy operation of the commerce site, managing it as another branch of the retail chain

eCommerce API sites for Priority

What is API service for eCommerce sites, and what is its function?

Since the actions performed on commerce sites are essentially purchases, usually of the same merchandise offered for sale in the chain’s stores, all transactions performed by the customer on the site take place in the chain’s stores as well, using the cash register software. The API service is, in essence, exposure of all functions, capabilities and routines of a cash register through the use of a software interface instead of a human interface.

In addition, every transaction is registered by the API component in the retail database, enabling reporting capabilities, customer service and treatment of transactions and returns. It should be noted that the API component can provide the same services for any software asking to use the services that exist in the product, and not only for eCommerce sites.

Every API interface has two sides:

Server Side – the side that exposes the functions, enabling other software programs to request and receive services from it.
Client Side – the side that sends input to the server and receives replies and errors corresponding to the input sent.

The information transmitted between server and client is usually contained in text files or XML files, in which the information passing between the two sides is stored. The conversation between the parties may be conducted in two different ways: the first is a one-way conversation in which the client side transmits a request, without waiting for a reply, whereas the other way is that after transmitting the request, the client side waits to receive a reply from the server.

Synchronic Interface – the client side does not disconnect communication with the server until receiving a reply or a time-out.

Time-Out – a predetermined period of time in which to wait for reply. If no reply is given by the server within this time, the client disconnects communication with the server for the particular enquiry.

A synchronic Interface – the client side transmits a request, is given confirmation that the request was received, but does not wait for reply. In this type of interface, the client side opens a new request in which he awaits reply by the server.

The absolute majority of interfaces in the API system in this document, are of the synchronic type.

 

  • No need for human intervention in order to transmit the information in both directions; hence, maximum savings in manpower is achieved.
  • The work is absolutely online i.e. data is transmitted in real time.
  • In the event of error in data transmitted to API a clear, focused error is received by client software in real time.
  • No partial registration of data in the event of an interface malfunction occurring in the middle of document registration.
  • Maintains serviceability and integrity of data registered on the ERP server in accordance with all the rules by which a transaction is registered.
  • Maintains all reporting and control capabilities that exist in the transactions arriving from physical stores
  • Ability to recall transactions, in order to perform returns or enquiries in any physical store, as if the data were registered by another physical store
  • Capable of working at nearly full capacity even when the ERP server is not available
  • Transmission of unique cash register system capabilities, such as optimization between campaigns competing for the same transaction line, and real time calculation of gross profit for the eCommerce site as well
  • Realization of all club capabilities, from customer registration and recruitment stage until the realization of benefits stage (points, coupons, and eligibilities)
  • Ability to capture the customer’s credit card information, and charge him at delivery time only, as opposed to charging the customer immediately upon ordering, and the need to reimburse in the event of a gap in supply

 

 

 

The API component is also capable of working directly with the Priority system database i.e. the meta-data are drawn from the Priority database and not from that of the API component. Furthermore, the orders created by the API are registered directly to the transaction table in the chain center database, without undergoing a synchronization process from within the local database of the API. This capability is suitable only when there is no significance to working online i.e. when a state in which the API component cannot return or receive data for a certain period of time is acceptable.

 

 

 

  • Item search – according to code, description, barcode, main item, product family, color, and size
  • Pricelists and prices
  • Drawing items according to LUD (Last Update Date)
  • Receipt of item parameters to website according to LUD
  • Locating and creating a customer according to name, ID No., Club Member No., Tel. No., and mobile
  • Enquiry of customer balances and entitlements
  • Receipt of price for item
  • Receipt of up-to-date prices for all items according to LUD
  • Calculation of transaction
  • Currency table
  • Receipt of list of campaigns for item according to LUD
  • Coupons
  • Color table
  • List of chain branches
  • Compositions of cloth according to LUD
  • Drawing of item inventory in real time
  • Drawing of inventory updates for items according to inventory movements for date
  • Drawing of customer invoice heading in range of dates
  • Drawing of customer invoice including details according to Invoice No
  • Creating order transaction
  • Order status according to Order No
  • Transfer of customer charge details by means of credit card, PayPal or any other payment method supported by the site
  • Calculation of purchase basket according to club campaigns and benefits
  • Registering a new order
  • Reporting employee attendance
  • List of brands and credit card clearing services
  • Table of codes for campaign types
  • List of invoice types

 

 

 

Soon – full purchase basket for hosting at websites with full API integration

In addition to the above, the purchase basket will enable the following capabilities:

  • Realization of points
  • Realization of gift cards
  • Realization of entitlements
  • Purchases of employee club

 

 

API Service Installation Process:

 

Infrastructure:

  • API component installed on a Windows 2008 server or higher
  • 100 GB hard disc
  • RAM 4 Giga-byte
  • API server installed with connectivity in a secured communication line to the IIS server at the chain center and to the internet server
  • On the API server is installed a IIS service for communication with the internet server
  • A server side of POS should be installed, according to the version number of the API service installed on the API server

 

Instructions:

  • Establish a branch for the website
  • Create a point for the branch; mark the field on the branch’s POS screen, that this is an internet cash register
  • Connect the cash register to the bookkeeping cash register for creating orders
  • Connect the branch to the customer for charging
  • Create or verify creation of a Cat No. connected to use code 09 – creating an order
  • Mark the items participating in the website in the field – participating in website
  • Mark the pricelists participating in the website in the field – participating in website