Audience
Technical Teams, Account Managers, Product Development
Topic or Issue Description
This article is iterative and lists the most common FAQs we get from brands/app partners that are using Omnivore.
FAQs
1. Q: How do you inject orders through the POS?
A: The Omnivore Agent that is installed in the Windows environment on the server is used to facilitate the steps we take to inject orders into the POS system.
2. Q: Do I need to have an Omnivore account made to get a location ID?
A: Yes, doing so facilitates your signing our agreement associated with using our product.
3. Q: How do I know which POS systems you're compatible with?
A: We have a compatibility matrix that is visible with an active account.
4. Q: How often does the menu data cache?
A: By default, we cache the menu data every 30 mins. This is configurable and can be done X times a day/every X minutes.
5. Q:Does the Omnivore API support PMS Systems like Opera that work with Simphony?
A: No, we are not integrated into any PMS system on the market.
6. Q: What are some of the ways your API is most commonly used?
A: Data gathering from the store, Employee and Shift Management, and Order Injections.
7. Q: How long is ticket data stored on the POS?
A: Omnivore can provide 30 days of ticket history on most POS platforms, and this can be used to retrieve limited sales and inventory history, at least so far as restaurant inventory that was consumed. We recommend collecting and storing data in a separate location over time, since the POS eventually retires its data and it becomes harder and more expensive to access. This way you'll be able to preserve data from the POS, access it easily, and organize it in the way that makes most sense for the particular application.