The **Category** and **Sub-Category** will be different for every location - you will need to manually investigate this to ensure the data comes in clean for SKU mapping, otherwise we'll have to re-pull the data
5\. The last step in the Toast dashboard is to determine if a customer utilizes modifiers for their Draft Beer products. Once you're done identifying the **Category** and **Sub-Category** usage, click on one the Draft Beer items and it will pull up the *Order Details* - if you scroll down you'll see a list of items on the order and there will be a column labeled `Modifiers`. [](https://wiki.bartrack.beer/uploads/images/gallery/2022-04/image-1651062498384-28-15-am.png) - If there are things related to the glassware size, we will want to ensure that modifiers are marked as TRUE - otherwise, if modifiers do not appear to be a determining factor in identifying what a SKU represents mark this as FALSEThe Onboarding Team should have already identified if the customer utilizes modifiers so you can ask them for that information, otherwise, you can verify this yourself by looking at the data in Toast.
- - - - - - ## Database Configuration 1\. The next step in the configuration process 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 - Timezone - Location Name from Toast Dashboard - Modifier Usage - Category / Sub-Category 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 UPDATEMake sure you are careful when editing the configuration file - incorrect formatting will result in the inability to pull POS data for any locations on the server. In order to minimize error, it is recommended to copy the existing structure and paste it into the necessary position - modifying the establishment
4\. Now that the establishment has been correctly configured you will be able to pull the POS data for the location, you will need to pull the data from the **Activation Date** onwards - it is recommended to pull at least one day of data to ensure that things are operational and there were no configuration-related issues. # Omnivore ## Gather POS Information 1\. In order to configure customers who utilize **Omnivore** for their POS Integration the Customer Success team needs to have the customer install the Omnivore agent on their back-office machine. Visit the [Omnivore Control Panel Login](https://panel.omnivore.io/login) in a web browser and proceed to **Login** - input the BarTrack `technology@bartrack.beer` credentials 2\. Navigate to 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. You may utilize the search box on the top right side of the screen to quickly filter locations. See the attached image below for reference - [](https://wiki.bartrack.beer/uploads/images/gallery/2022-04/image-1651065136740.png) 3\. Once you have found the location you're looking to configure, 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` [](https://wiki.bartrack.beer/uploads/images/gallery/2022-04/image-1651065215673.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 significant yellow or red periods you are good to proceed.
If you do not see a location in the Omnivore Control Panel or their **Status** is offline - please contact the Customer Success team to coordinate a meeting with the customer
- - - - - - ## Database Configuration 1\. The next step in the configuration process 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 - Timezone - Modifier Usage - Location IdentifierThe Onboarding Team should have already identified if the customer utilizes modifiers so you will need to ask them for that information - if they are unsure, set this to FALSE and then reference the POS data that is captured
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 UPDATEMake sure you are careful when editing the configuration file - incorrect formatting will result in the inability to pull POS data for any locations on the server. In order to minimize error, it is recommended to copy the existing structure and paste it into the necessary position - modifying the establishment
4\. Now that the establishment has been correctly configured you will be able to pull the POS data for the location, you will need to pull the data from the **Activation Date** onwards - it is recommended to pull at least one day of data to ensure that things are operational and there were no configuration-related issues. # Square ## Gather POS Information 1\. In order to configure customers who utilize **Square** as their POS provider, the Customer Success team needs to gather an `Access Token` from the customer. - The Customer Success team typically shares this in the [\#customer-pos-integrations](https://bartrack.slack.com/archives/C01V90HPYAJ) Slack channel or [Customer Onboarding Tracker](https://docs.google.com/spreadsheets/d/1IBeZlgJ_QjTNu7DRPAYuL-pgQR3NyUhv88KPFtXC2es/edit#gid=0) spreadsheet 2\. Once you have obtained an `Access Token` for a customers location, you will need to execute the following command on your Terminal - ```shell curl https://connect.squareup.com/v2/locations \Make sure to replace the bearer token in the provided example with the Access Token that the customer provided
3\. After executing the command the server will return a large JSON object of location(s). You should utilize a [JSON Formatter](https://jsonformatter.org/json-pretty-print) to make this more legible, the output should look similar to the example below - ```JSON {If there are no locations in the JSON object that match the location in the database, reach out to the Onboarding team and have them verify the address and which location that we are supposed to use for our integration
- - - - - - ## Database Configuration 1\. The next step in the configuration process 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 - Timezone - Location ID (Square) - Modifier UsageThe Onboarding Team should have already identified if the customer utilizes modifiers so you will need to ask them for that information - if they are unsure, set this to FALSE and then reference the POS data that is captured
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 UPDATEMake sure you are careful when editing the configuration file - incorrect formatting will result in the inability to pull POS data for any locations on the server. In order to minimize error, it is recommended to copy the existing structure and paste it into the necessary position - modifying the establishment
4\. Now that the establishment has been correctly configured you will be able to pull the POS data for the location, you will need to pull the data from the **Activation Date** onwards - it is recommended to pull at least one day of data to ensure that things are operational and there were no configuration-related issues. # UpServe ## Gather POS Information 1\. In order to configure customers who utilize **UpServe** as their POS provider the Customer Success team needs to have the customer create a guest account for us using the integration email address. Visit the [UpServe Dashboard](https://reports.breadcrumb.com/login) in a web browser and proceed to login - input the BarTrack `technology@bartrack.beer` credentials 2\. Upon authentication, utilize the search box to identify the location you're attempting to configure. Once you've found the location, make a note of the establishment name. [](https://wiki.bartrack.beer/uploads/images/gallery/2022-04/image-1651073590206-33-07-am.png) - - - - - - ## Database Configuration 1\. The next step in the configuration process 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 - Timezone - Location Name (UpServe) - Modifier UsageThe Onboarding Team should have already identified if the customer utilizes modifiers so you will need to ask them for that information - if they are unsure, set this to FALSE and then reference the POS data that is captured
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 UPDATEMake sure you are careful when editing the configuration file - incorrect formatting will result in the inability to pull POS data for any locations on the server. In order to minimize error, it is recommended to copy the existing structure and paste it into the necessary position - modifying the establishment
4\. Now that the establishment has been correctly configured you will be able to pull the POS data for the location, you will need to pull the data from the **Activation Date** onwards - it is recommended to pull at least one day of data to ensure that things are operational and there were no configuration-related issues. # Revel ## Gather POS Information 1\. In order to configure customers who utilize **Revel** as their POS provider, the Customer Success team needs to gather the custom Revel `Login URL` from the customer and inform us which email address that the customer used to create a guest access account for us - The Customer Success team typically shares this in the [\#customer-pos-integrations](https://bartrack.slack.com/archives/C01V90HPYAJ) Slack channel or [Customer Onboarding Tracker](https://docs.google.com/spreadsheets/d/1IBeZlgJ_QjTNu7DRPAYuL-pgQR3NyUhv88KPFtXC2es/edit#gid=0) spreadsheet - - - - - - ## Database Configuration 1\. The next step in the configuration process 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 - Timezone - Login URL (Revel) - Modifier UsageThe Onboarding Team should have already identified if the customer utilizes modifiers so you will need to ask them for that information - if they are unsure, set this to FALSE and then reference the POS data that is captured
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 UPDATEMake sure you are careful when editing the configuration file - incorrect formatting will result in the inability to pull POS data for any locations on the server. In order to minimize error, it is recommended to copy the existing structure and paste it into the necessary position - modifying the establishment
4\. Now that the establishment has been correctly configured you will be able to pull the POS data for the location, you will need to pull the data from the **Activation Date** onwards - it is recommended to pull at least one day of data to ensure that things are operational and there were no configuration-related issues.