Omnivore Integration

To exchange data with certain POS systems, Bbot uses "middleware" software called Omnivore. Omnivore installs a small program on the POS system, which allows it to connect to modern, cloud-based systems such as Bbot.

Prerequisites

This section may be skipped if you do not have or know this information, however, skipping this section will likely prolong the process.

  • The Back of House POS server must meet the following requirements:
    • 700 MB available/free memory on the system for Windows 7 or higher
    • 1.8 GHz dual-core processor
  • Add firewall exceptions to allow outbound TCP connections to the following addresses and ports:
  • If security software runs on the BoH POS server, it may interfere with Omnivore’s software package. Add the following executables to your security software’s exception list:
    • C:\Program Files (x86)\POS Agent\pos_agent.exe
    • C:\Program Files (x86)\POS Agent\agent_updater.exe
    • C:\Program Files (x86)\POS Agent\init.exe
  • Create the following in your POS system:
    • An ordering employee named Bbot
    • A 3rd party tender named Bbot
    • A zero-dollar item named Bbot
  • Please have the following Test Plan filled out and ready:
    • Which Revenue Center should Bbot orders be categorized in?
    • Will Bbot orders be dine-in or takeout?
    • What is an example food item (include its ID in the POS).
    • If you have multiple fulfillment stations that get different items, please list 1 item for each. (Including each item’s ID in the POS)
    • What is an example drink item (include its ID in the POS)

Get Omnivore 3

This section is NOT optional. All steps must be completed to move forward with setting up Omnivore.

  • Create an Omnivore account at panel.omnivore.io/register - make sure you save/write down these credentials
  • Invite Bbot to your Omnivore account
    1. Click 'Account > Settings' in the upper right corner
    2. Expand 'Users' and click 'Add'
    3. In the 'Email Address' field enter 'omnivore+[venue name]@bbot.menu' where '[venue name]' is the name of your venue
    4. Select 'Yes' for 'Admin'
    5. Click 'Add User'
  • On your POS computer follow this link to download the Omnivore installer: https://connect.omnivore.io/invite/BBOTINVITE
  • Download and run the installer
  • Log in with the Omnivore account credentials you created above. Click through the software to schedule an appointment
  • Omnivore will send a confirmation email. “Reply all” to Omnivore and Bbot with the test plan form

Omnivore Installation

Omnivore will be in touch to schedule an installation session. They will help you make sure that your POS employee, payment tender, revenue center, and order type are correctly defined. They will also put through some test orders.

Tips for Building a Smart Ordering Menu

Your Bbot menu is a vital part of the smart ordering guest experience. A properly curated menu is very important for increasing sales. We recommend these guidelines:

  • Use names that guests can easily understand for all menu sections, items, modifier groups, and modifiers. For example:
GOOD NAME BAD NAME
Draft Beers DRFT
Choose a Bread Sandwich Mods
Bottle of Cabernet Sauvignon BTL Cab
6 Piece Chicken Tenders CHX TND
  • Write appetizing descriptions that answer the guest’s questions about size or ingredients. For example, “Three large, crispy, freshly-fried chicken tenders with our house barbecue dipping sauce.”
  • Food modifiers should include all the common customizations, such as “no onions”, “no cheese”, “dressing on the side” etc. The modifier group name will be displayed in Bbot, and the modifiers will be displayed under it.
  • If there are combo items like “shot and a beer”, make sure there are modifiers to select the shot & select the beer.
  • The modifiers should only include relevant items. Don’t offer “Gluten-Free Bun” as an option on ice cream. If customers see a long list of irrelevant options, they will distrust the system.
  • It’s a good idea also to include one or two “upsell” options. These are some upsell options that other Bbot restaurants have used:
    • On french fries - “Cheese dipping sauce - $1.50”
    • On a salad - “Add grilled chicken - $3.00”
    • On a vodka cocktail - “Upgrade liquor to Grey Goose - $3.00”

Adding Your Menu to Bbot

  • CSV Menus: Create a CSV menu to upload to the Bbot owner panel. When doing so, you will need to create a new column for 'POS ID' in which you will need to add the POS ID for each individual item.
    • Log in to the Bbot owner panel and navigate to the Menus page.
    • Under the "Menus" tab, create a new menu by selecting the blue + sign, then add the new menu name in the popup that appears. Upload your CSV menu to the new menu you've created.
    • Upload your CSV menu to the new menu you've created.
  • Non-CSV Menu Additions & Edits
    • Creating New Menus: If you create a new menu or menu heading manually rather than by CSV upload, you can do so just as you would for a non-integrated customer.
    • Adding / Editing Single Menu Items: This process is similar to adding/editing a single menu item for a non-integrated customer; however, there is an additional 'External POS' field at the top of the menu item editor. This field links the specific item to its counterpart in the POS. Modifiers will also have a POS ID, and if they are invalid, the validations of the modifiers will be shown and highlighted, indicating the POS ID is invalid.

  • Syncing Menus
    • Regardless of how you add new menus or menu items, you will need to sync with Omnivore to make the changes go live.
    • Click the 'Check Omnivore 3 Menu Sync Status' button.

Then select the 'Sync Now' option to begin the sync. Depending on the size of the menu(s), this may take

Once menus are synced over, you will need to ensure all items are enabled. Go to 'Menu Items' in the owner panel and select all items, and check the 'Enabled' boxes next to the items. If an item is disabled, the menu will be re-enabled after the menu sync occurs. Any item that is disabled will keep the POS ID on the menu item that links it to the item in Omnivore.

Order-Ahead Ticket Printing

When future orders are placed, a ticket will be printed when the order is first received. A second ticket will be printed when an order is taken out of the 'Future Orders' section, of the KDS. This can be done with the 'Unsnooze' button or by letting the timer determine when the order is to be 'Unsnoozed'. 

Omnivore Integration Settings

1. Navigate to your Bbot Owner Panel and select ‘Bbot App Store’ under 'Integrations'.

2. Use the drop-down menu to select 'POS Integrations', then click on the ‘Connect Omnivore’ button.

3. You must enter your Omnivore Location Id and click 'Next' to establish your Omnivore integration.

4. To edit, click the 'edit' button under the 'Omnivore Direct Orders + Menu Items' box. 

5. A popup menu will appear, and can then add/edit the following settings:

Omnivore Location ID: This ID allows us to link to the customer's POS. This ID is provided to the customer by Omnivore once they complete an install.

  • Employee: Often, a customer will create a Bbot employee to associate with Bbot orders; however, we can connect to an existing employee in their system if they so choose.
  • Revenue Center: Select the Omnivore Revenue Center that you would like bbot orders to be injected into. If no Revenue Center is selected, orders will default to the Customer Level Configuration.
  • Order Type: We can select a specific fulfillment that is in their system, or we can select the 'Auto' option, which will inject the order according to its fulfillment method in Bbot.
  • Use Custom Tender Type Mappings: If selected, you can assign Visa, Amex, Discover, and Mastercard to be injected as different tenders by selecting the alternative tender in the dropdown menu.
  • Tender Type: Often, a customer will create a Bbot tender type to associate with Bbot orders; however, we can connect to an existing tender type in their system if they choose.
  • Sync 'In Stock' from POS (if compatible): Checking this box will sync when an item is marked in or out of stock in the POS to Bbot.
  • Sync Price Levels from POS: This will sync the current menu price on items from the POS to Bbot.
  • Inject Orders into POS: Checking this box will cause orders to inject from Bbot into the POS. The majority of the time, this option should be selecte
  • Inject last four numbers of credit card: If checked, this will include the last 4 digits of the credit card used into the sales information for the Bbot order.
  • Action on Omnivore POS outage or injection failure?: In the event of an outage or failed injection, the customer can choose to have the system behave in one of two ways
    • Accept checkout / fulfill solely with Bbot
    • Abort checkout and refund the guests
  • Action on successful injection in Omnivore?: This depends on whether the customer will be using the Bbot KDS and if they would like guests to receive feedback on their orders
    • Keep the ticket open in Bbot / staff will update status in Bbot to notify guests - use if running off of Bbot KDS and would like guests to receive feedback on orders
    • Close the ticket in Bbot / Guests won't receive feedback about their orders - use if not running off of Bbot KDS and would not like guests to receive feedback on orders
  • Ticket Name Field Format: This allows you to enter the variables below to include additional information at the top of the printed ticket and on the KDS.
    • $ORDER NUMBER
    • §LOCATION
    • $PATRON NAME
    • $ROOM
  • Inject User Info into POS: This will include the Required Checkout Information entered by the guest on the printed ticket and on the KDS.
  • Default Service Fee Name: This changes the name of the Bbot service fee to whatever is entered when it injects into the POS.
  •  Auto-refund items that were refunded in POS: Checking this box will automatically trigger refunds in Bbot for orders that were refunded in the POS
  • Re-enable disabled menu items: If items are disabled during the Omnivore menu sync because they cannot be found through Omnivore, this will re-enable them if they are found again during a later menu sync.
  • Log Successful Order Injections: This option will allow for successful order injections to be logged in the Integration Activity Feed

You can also include guest information when injecting orders directly into the POS, including the guest's name, location code, and address for delivery orders.

5. Click 'Save' To save your integration settings.

Promo Codes and Discounts

In order to use promo codes and discounts with the Omnivore integration, you will need to make sure the discounts follow the rules below. 

  • The name of the discount in Aloha must start with Bbot.
  • It must apply to the entire ticket and not a discount to a specific item.
  • It must be an open discount and cannot have a minimum or maximum discount amount.

For any questions about the Omnivore integration or help in connecting the Omnivore integration, please contact our support team at support@bbot.menu.