Preface

Oracle Simphony Mobile Order and Pay (MOP) allows customers to browse menus, place orders, and pay using their mobile device.

Customers access the ordering experience through a web-based ordering widget without installing a mobile application. Ordering is typically initiated by scanning a QR code or selecting an ordering link from the venue’s website.

MOP is designed to reuse existing Simphony menu, pricing, and operational configuration wherever possible. This approach minimizes duplicate administration and ensures online ordering remains aligned with the POS.

MOP integrates with:

• Oracle Simphony
• Simphony Transaction Services (STS) Generation 2
• Oracle Payments
• Simphony Frontline Manager (FLM)
• Simphony Content and Configuration (C&C) API

Depending on the deployment, MOP may also integrate with additional Oracle Restaurant products and supported payment providers.

Purpose

This guide includes implemented administrator flows and the customer journeys used to validate them.

Audience

This publication is intended for:

• Oracle implementation consultants
• Customer system administrators
• Venue operators

Customer Support

To contact Oracle Customer Support, access the Customer Support Portal at:

https://iccp.custhelp.com

When contacting Customer Support, please provide the following:

• Product version and program/module name
• Functional and technical description of the problem (include business impact)
• Detailed step-by-step instructions to re-create
• Exact error message received and any associated log files
• Screen shots of each step you take

Documentation

Product documentation is available on the Oracle Help Center at https://docs.oracle.com/en/industries/food-beverage/pos.html.

The following documentation may also be useful:

• Oracle Simphony Configuration Guide
• Oracle Simphony Frontline Manager User Guide
• Oracle Simphony Transaction Services Generation 2 API Guide
• Oracle Restaurants Payments Service Feature Reference
• Oracle Simphony Reporting and Analytics User Guide

Revision History

Date	Description of Change
November 2026	Initial publication.