Ordering API
Release Notes (Version 1.1)
Version 1.1 of the Ordering API adds support for a payment status so partner Apps can indicate whether an order has to be paid or not.
For more information, refer to the Ordering Changelog.
Release Notes (Version 1.0)
Our research has shown that hospitality Merchants want to have a choice of which Ordering Apps they accept. Through interviews, we have learned how much extra work it puts on the Merchants as the effort to re-enter each order into the POS (particularly during busy periods) can be quite onerous. For Apps to meet the integration needs of their merchants, they will need to maintain separate integrations with a range of hospitality POSs. Given the level of fragmentation of hospitality POSs in Australia, this seems like an unnecessary overhead.
The goal of Tyro Connect’s Ordering API is to alleviate both of these problems by developing an API that has been specifically designed to support all types of Ordering Apps. The key value proposition for App Partners is that one integration with our Ordering API provides access to a number of Australia’s top hospitality POSs. For Merchants, having orders flow straight into their POS and workflow saves time and eliminates errors.
Version 1.0 of the Ordering API supports the following App types:
- Take away (including both delivery and pick up)
- In restaurant (table service and counter service with notifications)
Hospitality POSs that are signed up to Tyro Connect include:
Typical Ordering Workflow:
