ResPak
      Back to home
      1. INTERNAL - Bepoz Help Guides
      2. Interfaces | Reservation & Bookings
      3. ResPak

      2 | ResPAK Interface Setup - Deep Dive

      Prerequisites​​​​​​​ Bepoz backoffice device: Device Type: Transaction Queue External DLL: Stdlibrary.dll Class Name: Respak IP address: Respak Server IP’s (usually bepozserver. Make sure the respak-Generic POS program is auto run, will have an blue icon next to time) TCP Port: 5602 (by default, can be change in respak program) Installation - A Special Till Function Table Course Served can be added to the Till Override Maps. This function has an Item option of the course number (1-3).

      Prerequisites​​​​​​​

       

      • Bepoz backoffice device:
      • Device Type: Transaction Queue
      • External DLL: Stdlibrary.dll
      • Class Name: Respak
      • IP address: Respak Server IP’s (usually bepozserver. Make sure the respak-Generic POS program is auto run, will have an blue icon next to time)
      • TCP Port: 5602 (by default, can be change in respak program)

       

      Installation 

       

       -  A Special Till Function Table Course Served can be added to the Till Override Maps. This function has an Item option of the course number (1-3). Therefore Entrée Served, Mains Served and Dessert Served functions can all be added. These have no internal effect on the tables – they simply send to ResPak.

      - Setup SortGroups as Food, Beverage, Other (no more). These are used to send totals to ResPak.

       

      In respak program:
      RVC = revenue centre, usually “1”. Venue number or table group number start from 1 not 0.
      For eg: Table group 0 in bepoz is 1 in RVC

       

       

       

      To enable the log file of what bepoz send to respak, do the following:

       C:\Program Files\ResPAK-Services\RPOSInterface.exe" --database=192.168.0.99:ResPAK --debug

       

       It will generate the log file in C:\Program Files\ResPAK-Services\Audit

       

       

      Table Reservation Link (ResPak)

       

      BePOZ can interface to the ResPak Table Management and Reservation System for the purposes of sending current table status and table sales.

      BePOZ will supply Table events and charges to ResPak for Realtime tracking of Table Status and later analysis of table sales.

      There is one actual TCPIP connection between SmartController and the ResPAK Software. This one connection can control multiple areas (restaurants).

      The Interface is done within Smartcontroller. When a ResPak Device is setup, all transactions received by SmartController are processed through its internal ResPak module. Any transactions that are relevant will cause the proper message to be sent to the ResPak System. Messages include opening tables, paying and closing tables, and optionally special functions such as Entrée Served, Mains Served, Desserts served etc. Different TableGroups can be setup to run different restaurants within the ResPak system.

       

       

      BePOZ fields sent to ResPAK. ResPAK Field

      BePOZ Field

      Notes

      Area

      TableGroup

      1 - 8

      Meal Period

      Shift Number

      1 - 10

      Table ID

      Table Number

      First 6 digits

      Food,Beverage,Other

      Sort Groups 1,2,3

      These should be setup as such

      Check No.

      Transaction Number

      First 6 Digits

      Item Number

      Product ID

      Item type

      Sort type (1-30)

      These add into the Sort groups above

      POSID

      Till ID

       

       

      Respak Connection Overview:

      The interface simply sends messages to ResPAK upon certain table “events” .

      When a table is first opened, a “Check Opened” message for that table.

      If Entrée Served, Main Served or Dessert Served functions are used against a table, a message will be sent.

      If a Table if transferred to another table or tablegroup, this message will be sent.

      When a table is closed, the table totals and product line details will be sent to ResPAK.

      Respak then will automatically “vacate” and “reset” the table on a timer.

      No Membership requests are sent – membership is to be handled by BePOZ.

      The Interface will wait for a response from ResPAK before sending another packet.

       

      Interface Notes:

      1. We do not support the Membership interface to ResPak. BePOZ has its own internal fully functional Members package and that should be used.

      2. Currently we should not send the Meal Period. As they can select the correct period based on transaction time – this saves changing the ResPak Meal Period definitions.

      3. Messages supported are: C – Check opened, 1 - Entrees served, 2 - Mains served, 3 - Desserts served, # - Check printed, $ - Check Totals, D - Check Details. Vacate Table and Reset Table are triggered within ResPak automatically based on a timer after the $ Check Totals is received.

      4. Area is BePOZ (TableGroupID +1).

      5. We send the TillID as the <POSID> field.