MICROS POS: RES 3700 FAQs

Audience

Operators, Technical Teams, Account Managers, Engineers, & Product Teams

Description 

This article is iterative and lists the most common FAQs we get from brands that are using Olo with integration to MICROS (AKA Oracle Hospitality) RES 3700 POS.

FAQs 

1. Do my guests get charged tax from Olo or from MICROS?

• Your micros system is the final authority on charging tax thru a function called Tax Validation. The tax that shows in Olo during the process of building their cart is called Estimated Tax. Once on to the checkout page, MICROS responds with the correct tax according to your tax configuration.

2. Where does pricing in Olo come from?

• Olo pulls prices from the POS that is initially shown to the guest while building their cart before they proceed to checkout. Typically brands are enabled for automatic price updates which pulls the pricing 2 times daily. The price updater can be run manually from the Dashboard (under Brand Settings) or by a store (under Store Settings/POS Settings).
  
  
• When the item is mapped, Olo assumes it's on menu level 1 unless you specify a different level. Olo cannot identify the active main or sub level in your POS so all items will ring through at the level that is assigned in the corporate menu in Olo
  
  
• If for some reason, the price reflected while building the basket is not the correct price, the POS will send the correct price back to the guest on Checkout similar to the tax validation mentioned in Question #1.

3. What do I need to configure in MICROS to support Discounts from Olo?

• Olo supports the use of Open Dollar discounts. They are to be mapped using the discount object number.
  • These are used for either $ off Discounts in Olo or % off Discounts in Olo (where Olo calculates the percentage and then sends that value down to POS to the open dollar Discount).  There is an article containing more details on the Olo Help Center.

4. How do I control printing or KDS routing in MICROS?

• Olo will send the order to the API employee and the API workstation. All printer and KDS routing is controlled by micros using the same configuration that is used for in-store orders.
  
  
• If your brand is using any of the micros order device maskings, please confirm the Olo Order Type and Olo Tenders have the appropriate print class settings.

5. What is an API workstation?

• The API workstation is added as a user workstation in the Micros POS Configurator and it is used to accept and place the orders coming through from OLO.  This workstation is also used to configure the receipt printer and order device access for orders from Olo.

6. What is an API employee?

• An API employee is an employee that acts just like a regular FOH employee in micros It is an employee record that Olo uses to log in and performs an action on the API workstation for order entry. 

7. What does 'POS Order Ready' with a red dot mean on the Dashboard for my MICROS location?

• A red dot on "POS Order Ready" means that one or more of the Olo configurations for this store do not match your POS.  Please refer to the Olo log for more details.  Some reasons might be that the employee class linked to the POS API employee is not properly configured or the micros POS API workstation might not be configured properly.  The Olo logs are data stamped and they typically explain the cause in plain English. The most common error messages are "Employee Class not set to a POS API Employee Class", "Could not find Employee in the database", and "Creating an instance of the COM component with CLSID".  There are solutions for each of these on the Help Center.

8. What does 'Connected' mean in the Dashboard?

• Connected means that the OloMicrosService was able to properly reach our server in the cloud and authenticate the POS User Account for that specific location. 

9. Why did my store get disabled automatically? 

• Stores will get disabled automatically if a validation error is received back from POS 5 times consecutively without any successful requests.

10. Why do I need to set up multiple Order Types in MICROS?

• Olo in its simplest form only needs one Order Type to get orders committed to POS for Online Ordering. However, if your business requires reporting broken out between different order types like delivery, curbside, or take out then you will need an order type configured for each. 

11. Can credit cards be separated into individual tenders?

• Olo, in its simplest form, only needs one Tender to submit prepaid orders to Micros (via a "general" tender type). However, if your business requires that prepaid order tenders are split up by Visa, MasterCard, Discover or American Express, then an additional tender will be required for each.
  
  
• The difference with these above store payments is that they are processed above store and are, therefore, not part of your credit card batch through Micros, but they will be on your sales and tender reports in Micros.

12. Where will I see tips from guests on my checks once they are in POS?

• Tips will be posted to a service charge number from micros that is declared in the Olo Configuration Variables. MICROS determines how these tips are processed in POS.  They will be linked to the POS API Employee.

13. Can I accept payment in-store with Olo or do all orders have to be pre-paid?

• Yes, you can accept unpaid orders that will be paid in-store. When your guest arrives, you will find the check in your open orders for the Revenue center you have defined for use by Olo.  You will need to create a send tender for Olo to use when posting a paid-in-store order.