Verifone Commander, Ruby2 and Ruby CI

You can set up QwickServe to work with the following Verifone POS:

Verifone Commander
RubyCI
Ruby2

Setup Considerations

QwickServe devices, including QwickServe Ordering Terminal, QwickServe Order Manager, customer receipt and kitchen ticket printers and label printers must be connected to the same network.
From the Verifone Commander POS standpoint, all QwickServe devices are a part of back-office services. If you use CStoreOffice® as the back-office system, QwickServe devices must be connected in the same way as DC-401. For details, see DC-401.

Site Outline

The table below lists all hardware devices that can be deployed in the QwickServe infrastructure. Refer to the last column to check if the device is mandatory or optional for deployment.

Name	Description	Required
Verifone Commander Forecourt Controller	Verifone Commander Forecourt used at the site to control the Verifone POS and integrate with other devices at the site.	Yes
POS: RubyCI, Ruby2 or Topaz	Verifone POS used to pay for regular customers orders and QwickServe orders. There can be several instances of POS at the site.	Yes
Verifone Commander EPS	Electronic Payment System part of Verifone Commander used to control payment terminals and integrate with the payment gateway.	Yes
Verifone router	Enhanced Zone Router provided by Verifone and used to separate and control POS zone networks.	Yes
ISP router	Internet Service Provider router. Allows access to Internet for all devices, including POS, Petrosoft DC-401 and QwickServe devices.	Yes
Firewall device	Firewall device used to divide the site network into isolated and controller zones, such as fuel zone, back-office zone, payment terminals and gateways zone.	No Yes, if the fuel and payment zone separation are required.
Network switch	Unmanaged network switch with 8 ports (one or few) required to connect several devices to one of firewall ports.	Yes
Edge (DC-401)	Direct Connect Site Controller from Petrosoft designed to allow communication between the site and back-office system.	No Yes, if CStoreOffice® is used as the back-office system.
QwickServe Ordering Terminal	QwickServe Ordering Terminal or QwickServe Ordering Terminal App installed on the Android tablet. Required to create orders onsite.	Yes
QwickServe Order Manager	QwickServe Order Manager installed on the QwickServe Order Manager kiosk or Android tablet. Required to handle orders received from the QwickServe Ordering Terminal or mobile applications.	Yes
QwickServe payment terminal	PIN pad connected to the QwickServe Ordering Terminal and used by customers to pay for orders created at the QwickServe Ordering Terminal.	No
Square contactless and chip reader	Card and contactless reader device from Square (https://squareup.com/shop/hardware/us/en/products/chip-credit-card-reader-with-nfc). Used for card present and contactless payments. Connects to attended QwickServe Ordering Terminal and/or QwickServe Order Manager systems over Bluetooth.	No
Kitchen and customer receipt printer	Thermal printer used to print kitchen tickets and/or customer receipts.	No
Label printer	Thermal printer used to print items labels that can be attached to prepared items.	No
QwickServe Mobile app	QwickServe Mobile app for iOS and Android designed for customers. Allows creating orders to be delivered to the site QwickServe Order Manager. Provides payment options selection, including online payments in the application or later at the POS.	No

General Configuration Diagram: Retail, Fuel and Food Service

Elements that are grayed out may be present at the site but are not a part of the QwickServe infrastructure.
The provided configuration is typical and recommended for majority of sites. In some cases, when a custom network is configured, the configuration may differ. If so, please contact Petrosoft Support Team.

Refer to the sections below to learn about specific configurations for solutions widely used at sites. In case other equipment is used, the configurations below can be used as a reference.