Integration detail

Appetier + Micros integration

Your menu, prices, and checks stay in Simphony, and your own storefront takes direct orders next to it. With a Simphony API account, Appetier reads the menu and prices.

What works

With your access: A Simphony admin creates an API account in the Enterprise Back Office, with the client scope set to Local or Both, and you paste its details into Appetier. Appetier reads your Simphony menu and prices. It changes nothing in Simphony, and direct orders are fulfilled in Appetier.

On our own: Appetier takes direct orders on your storefront and fulfills them on its order and kitchen screens. Or run Appetier POS, free in Growth, on your own hardware.

What it does

With a Simphony API account, Appetier reads your Simphony menu and prices. Your own Appetier storefront takes direct orders, and Appetier fulfills them.

Who it's for

Hotel restaurants and groups on Oracle Simphony that want a direct ordering site next to their existing system.

What Appetier does for you today

Your Appetier storefront goes live in minutes and takes direct orders on your own site. Guests pay at the Appetier checkout, and orders are fulfilled in Appetier. A direct order does not appear in Simphony as a check. Appetier POS is free in Growth.

What you keep doing in Simphony

Your menu, pricing, and checks stay in Simphony. Appetier reads the menu and prices and does not change them or your checks.

What Oracle requires for API access

A Simphony admin creates an API account in the Enterprise Back Office, with the client scope set to Local or Both. Oracle provisions its API for Simphony Cloud Service deployments, and most of Oracle's APIs also need a separate cloud subscription, so ask your Oracle contact whether yours has one.

Access comes per deployment

Oracle gives API access location by location. A rollout across a group is a list of deployments, not one switch. Each deployment's API account is pasted into Appetier on its own.

Setup steps

Where it fits in Appetier

Menus stay matched to your POS, and direct orders print as tickets.

See POS sync
  • Ask your Oracle contact what Simphony API access your deployment can get
  • Have a Simphony admin create an API account
  • Paste its details into Appetier
  • Fulfill direct orders in Appetier

Common questions

How does a Simphony rollout work?
Oracle grants access location by location. A rollout is a list of deployments with one grant each, not a single switch.
Do we need an Oracle cloud subscription?
Most Simphony APIs need one. Ask Oracle before your admin creates an API account.
Will a direct order appear as a check in Simphony?
No. Direct orders are fulfilled in Appetier.
Can head office manage one menu across locations?
In Appetier, yes, for the storefront menu. Appetier reads the Simphony menu and does not change it.

Related integrations

Launch first, then connect it

Your storefront goes live in minutes from your logo and a photo of your menu. Add this connection whenever you're ready.