How does Rails work?
Rails allows third-party UI’s to submit prepaid orders through the Ordering API. All payments are collected and processed on the marketplace’s end. Dashboard cannot be used to do refunds or adjustments for prepaid Rails orders. Rails is currently integrated with several POS systems including Aloha, Brink, Micros, Xpient and OloCloud. We are consistently working to add additional POS systems.
Which third-party marketplaces are already integrated with Olo?
Rails is integrated with popular food ordering marketplaces like Amazon Restaurants, DoorDash, EatStreet, Caviar, etc. Contact us for an up-to-date list of providers as we are constantly integrating to new partners.
How much does Rails cost?
There is no specific usage fee for current Olo customers to use Rails. If you are on a flat monthly fee structure, there is no charge to use Rails. If you pay a per-order transaction fee, Rails orders count toward orders processed in your agreement. Olo and marketplaces have a contractual agreement that stipulates a fee structure for the marketplace’s usage of Rails.
What does the money flow look like for brands and marketplaces using Rails?
Typically, there is a contractual arrangement between the stores and marketplaces where the stores agree to pay a fee/commission for digital orders placed from the marketplace. This is a fee/commission collected by the marketplaces for driving order volume to the store locations. Olo is not part of that contractual arrangement and does not necessarily even know the fee/commission arrangement between the two parties.
In the current prepaid solution, the marketplace has collected payment from the customer for the full order value. The amount to pay the store location is a money flow that exists directly between the store and the marketplace. Olo is not involved in this money flow.
For each Rails order submitted through Olo, the marketplace will pay an agreed upon fee to Olo for usage of our Rails product.
Is there a way to differentiate Rails orders from orders coming from the store’s white-label site?
Olo includes Rails-specific fields on order receipts such as the name of the marketplace and the marketplace's order ID, allowing stores to determine where the order came from. POS’s can also be configured to use a different tender type from a traditional Olo order. You'll also be able to view marketplace details for Rails orders in Dashboard.
Is there a Rails API?
Rails is built as a series of new features on our Olo Ordering API. There is not a separate API. For Rails v0.5, the key features are:
- The ability for the Rails Partner to be issued one API key from Olo that gives them access to specific store locations that could span across different Restaurant brands.
- The ability to submit prepaid orders through Olo’s Ordering API.
What else can you do with Rails?
There is also an opportunity for kiosk providers to use Rails. This would allow kiosk providers to submit digital orders via the Olo Ordering API and leverage the prepaid feature to allow kiosks to implement an EMV card-reader to collect payment prior to transmitting the order through Rails. The kiosk provider would need to create a separate solution (outside of Dashboard) to handle refunds for those orders. For brands using an agency to build a native mobile ordering experience, Rails can be used to introduce mobile payments (e.g. Apple Pay, Android Pay, etc.) to the customer’s online ordering experience. This assumes the agency is willing to do development work on their side to allow in-app purchases with mobile payment providers. Payment collection using this approach would happen outside of the Olo platform and the order would be submitted as prepaid through the Olo Ordering API. The agency/store locations would need to have a separate solution (outside of Olo Dashboard) to handle refunds for those orders.