ResPak

1 | ResPak Interface Setup

Bepoz can interface to the ResPak Table Management and Reservation System for the purposes of sending current table status and table sales. The setup process of ResPak in Bepoz is details in this article.

Bepoz can interface to the ResPak Table Management and Reservation System for the purposes of sending current table status and table sales. The setup process of ResPak in Bepoz is details in this article.

About
  • 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 Smart Controller and the ResPAK Software
  • This one connection can control multiple areas (restaurants)
  • The Interface is done within Smart controller. When a ResPak Device is setup, all transactions received by Smart Controller 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

Prerequisites

To Setup the ResPak Interface in Bepoz:

  • In Venue Tree, add a new device under the SmartController Workstation
  • The device Settings are:
 

Device Type

Transaction Interface

IP Address

ResPak IP Address

Sub Type

ResPak

TCPPort

As Specifed by ResPak

Shifts are Meal Periods

Send Meal Period data. 1- 10 (Shift Number)    

 

  • TableGroups should be setup to correspond with Respak Areas
  • 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

 

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 Group 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

  • We do not support the Membership interface to ResPak. Bepoz has its own internal fully functional Members package and that should be used
  • 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
  • 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
  • Area is Bepoz (TableGroupID +1)
  • We send the TillID as the <POSID> field