# Omnivore
Supported POS Software: https://www.olo.com/omnivoreapi
# Omnivore Customer Setup
[Omnivore Installation Process.pdf](https://wiki.bartrack.beer/attachments/1)
# Omnivore BarTrack Setup
1\. Visit the [Omnivore Control Panel Login](https://panel.omnivore.io/login) in a web browser and input the `technology@bartrack.beer` credentials to access the Control Panel
[](https://wiki.bartrack.beer/uploads/images/gallery/2022-03/image-1648692704925.png)
- - - - - -
2\. Locate the `Locations` tab on the top center of the webpage menu - this will provide you a list of all of the customers that are currently integrated with BarTrack through Omnivore
[](https://wiki.bartrack.beer/uploads/images/gallery/2022-03/image-1648692750419.png)
- - - - - -
3\. Utilize the search box on the top right side of the screen to quickly locate customers - in this example we are looking for `The Branch`, which can be seen below -
[](https://wiki.bartrack.beer/uploads/images/gallery/2022-03/image-1648692796344.png)
- - - - - -
4\. Once this has been identified, you will want to click on that customer and cross-reference the address displayed here with what we have captured in the database to ensure that we are referencing the correct location. Once you have confirmed that the location is valid, you will need to copy the `Location ID`. In the example where we are utilizing *The Branch*, the Location ID is `i6EzBB4T`, as seen below -
[](https://wiki.bartrack.beer/uploads/images/gallery/2022-03/image-1648692838405.png)
While here, it is useful to also reference the **Status** and **Ping Latency** in order to determine if there are any issues. As long as the status indicates they are Online and the ping latency does not have any yellow or red periods you are good to proceed.
- - - - - -
5\. The next step is updating the **establishments** table of the database to reflect the necessary information for the integration. The primary things that you’ll need to know are as follows:
- Establishment ID
- Does the customer utilize modifiers?
- Establishment Timezone
- Date Activated
- Location ID from Omnivore Control Panel
Once you have collected all of the necessary information you can proceed with executing the SQL query below, this will prompt you to enter several variables which encompass the information you captured above.
**SQL Query -**
```SQL
UPDATE
establishments
SET
integration_id = 1,
day_week_begins = 2,
default_pour_cost_pct = 20,
pos_hour_integration_done = 5,
pos_modifiers = ${pos_modifier_flag}$,
rpts_daily_deliver = true,
rpts_daily_hour = 9,
rpts_weekly_deliver = true,
rpts_weekly_hour = 9,
rpts_monthly_deliver = true,
rpts_monthly_hour = 9,
rpts_combine_comps_voids = false,
rpts_rotation = '03:00:00',
time_zone = ${timezone}$,
rpts_valid_from = ${date_activated}$,
pos_cloud_based = true,
pos_properties = '{"processed_locations_ids": ["${location_id}$"]}'
WHERE
id = ${establishment_id}$;
```
**Example Data for Variables -**
```
Name Value
------------------------ --------------
pos_modifier_flag true
timezone 'US/Eastern'
date_activated '2021-08-01'
location_id i6EzBB4T
establishment_id 164
```
- - - - - -
6\. After the establishment has been configured in the database, you can proceed to SSH to the POS server to complete the final portion of the configuration. Once you have accessed the server, navigate to the `~/bartrack-pos/integrations/cli` directory
[](https://wiki.bartrack.beer/uploads/images/gallery/2022-03/image-1648692949382.png)
- - - - - -
7\. Once you are in the `~/bartrack-pos/integrations/cli` directory, edit the `settings.json` file and locate the section that contains the **Omnivore** integrations
[](https://wiki.bartrack.beer/uploads/images/gallery/2022-03/image-1648693156488.png)
Once you have found the section, you will need to insert a record in the chronological position based on the establishment ID. Modify the record below to reflect the correct establishment ID and then insert it into the configuration file. Once the changes have been finalized, save your changes.
```JSON
"164": {
"apiKey": "8ca36fdcd28948f892faccd1690f6484"
}
```
Once you have inserted the record into the configuration file, it should look similar to the example below -
[](https://wiki.bartrack.beer/uploads/images/gallery/2022-03/image-1648693185323.png)
- - - - - -
8\. Now that the establishment has been correctly configured you are able to pull the POS data for the customer, you will need to pull the data from the **Activation Date** onwards.
# Omnivore Micros Symphony
##### **Required Info**
- **Simphony version**
- **Is it hosted?**
- **Name of the Property to be integrated**
- **Number of Revenue Centers to be integrated, and their names**
*If your Simphony version is 2.x or if your Enterprise is on-premise, please skip this section and move to the next.* To proceed with our integration into your Simphony system, we request login information for EMC. If you are using a hosted version of Simphony, could you help us get a read-only user set up with permission to view settings from the enterprise level? In order to log in we will need:
- **Server URL**
- **User Name**
- **Company**
- **Password**
We also require Transaction Services. Please use the following information to reach out to Oracle or your re-seller to request they install, configure, and test Transaction Services for your system if you haven't already:
- License: Guest Facing Transaction Services
- Configuration: Add a POSAPI Client
- CAL: Add the Transaction Services role to a host workstation and allow CAL to install the required files
- Testing: Use TSDemoClient to confirm Transaction Services is functioning correctly
- **Results: Reply to Omnivore Support with the Employee ID and RVC number (#) used for testing**
# Omnivore Supported POS
- NCR Aloha
- PAR Brink
- Dinerware
- Micros Simphony
- Micros 3700
- POSitouch
- Squirrel Systems
- XPIENT
- Lavu (Read Only)
- Maitre'D (Read Only)
- NCR Cloud Connect (Read Only)
- Toast (Read Only)