Integrations

What the tab holds#

In the dashboard under Settings, tab Integrations, is everything outside Flavoso that works with your restaurant. Right at the top, one line shows at a glance what is connected right now.

Below it, each connection has its own card:

• Online payment: the payment accounts through which guests pay online. From Pro.
• Receipt printer: a printer in the kitchen that prints every new order as a slip. From Pro.
• Orders by e-mail: every new order also goes to an e-mail address. In every plan.
• Connected apps: software that works with your restaurant, for example a point of sale. In every plan.
• Your own webhooks for systems of your own. In every plan, owners only.

Online payment#

In the “Online payment” card you connect your payment account and switch it on for guests. The money goes straight to your restaurant's account; Flavoso is never the payee. Online payment belongs to the Pro plan and above.

How connecting works step by step is in the chapter “Payment”.

Receipt printer#

In the “Receipt printer” card you set up a printer in the kitchen that prints every new order as a slip. You need a network printer that speaks Star CloudPRNT or Epson Server Direct Print. From Pro.

The setup in detail is in the chapter “Kitchen screen”, under “A receipt printer instead of a screen”.

Orders by e-mail#

Every new order also goes to an e-mail address, for example the kitchen's. This is in every plan.

You enter the address in the “Orders by e-mail” card, or straight away in the setup wizard. Orders paid online only go out once the payment is confirmed.

Connecting apps#

Any software can connect to your restaurant through the open Flavoso API if you agree: a point of sale, a delivery program or an accounting program. Whether a particular system supports this is something its vendor can tell you.

The path starts in the other software, and only an owner of the restaurant can connect. There is no key to copy across: you sign in and agree.

An app can only be connected to your restaurant once Flavoso has reviewed and approved it. It then carries “Reviewed by Flavoso”. Until then only its developer connects it, to their test restaurant and to restaurants where they are an owner themselves.

Reviewed apps are listed in the app directory: in the dashboard under Settings, tab Integrations, and publicly at flavoso.com/en/integrations. You still connect inside the app itself; the directory takes you there.

After connecting, every owner of the restaurant gets an e-mail: which app, which vendor, which permissions, who connected it and when. It carries the button “Manage connected apps”.

An app sees only the restaurant you connected it to, and only what it has permissions for; the list is below the steps. Orders contain no e-mail address of the guest, the phone number only for pickup and delivery, and the address only for deliveries. By connecting, you instruct Flavoso to pass this data on to the app. The app's vendor is responsible for its own processing.

1. 1

   Choose “Connect with Flavoso”

   In the other software. Where exactly it is, its vendor can tell you.

   In the other software

2. 2

   Sign in

   With your Flavoso account. If you have set up a second factor, it is asked for.

   At Flavoso

3. 3

   Pick the restaurant

   The restaurant the app should work with. You can only connect restaurants where you are an owner.

4. 4

   Read the permissions

   The screen shows the app's logo, name and website, and in plain words what it may do. Approved apps carry “Reviewed by Flavoso”.

5. 5

   Connect

   Click “Connect”, and you are taken back to the other software. Done. “Cancel” connects nothing.

• Orders: see them, or accept, reject, advance them and take them over into the app's own system.
• Menu: see it, or edit it: dishes, categories, options, prices and sold out.
• Restaurant: see opening hours, status and tables, or pause online ordering and change opening hours and lead times.
• Reservations: see them, or create, confirm and change them. This only takes effect from Pro, like reservations themselves, and the consent screen points that out.
• Sales: see sales and revenue figures.

Disconnecting#

An owner can disconnect at any time: Settings, tab Integrations, card “Connected apps”, button “Disconnect”, then confirm. The app loses all access at once.

The owners get a short e-mail about it. Connecting and disconnecting are recorded in the log.

The app itself can also end the connection. In the phone app you see and disconnect connected apps under More, Settings, Integrations.

Own webhooks#

For systems of your own or automation services there are own webhooks: when something happens, for example a new order, Flavoso sends a message to your address. They sit under Settings, tab Integrations, “Your own webhooks”, for owners only and in every plan.

How the messages are built and how your system checks the signature is in the developer documentation at docs.flavoso.com/en/api, pages “Webhooks” and “Verifying signatures”.

• Up to five addresses. Each one uses https and must be publicly reachable, and for each address you choose the events.
• Every delivery is signed (header Flavoso-Signature, HMAC-SHA256). That is how your system knows it really comes from Flavoso.
• If a delivery fails, Flavoso tries again: up to eight attempts over almost two days.
• If nothing gets through for 24 hours and at least ten attempts in a row fail, the address is switched off and the owners get an e-mail.
• Each address shows the log of its latest deliveries and the button “Send test event”.

Building your own app#

You create your own app in the developer console: at app.flavoso.com/en/developers, or from the dashboard via the account menu at the top right, under “Developer console”. A Flavoso account is all you need; you don't need a restaurant of your own or a subscription.

On your first visit, a setup assistant takes you from the app through a free test restaurant to your first request. The test restaurant is there purely for trying out the API and comes with a sample menu and tables. In the console under “Test restaurant” you create orders and reservations and move them along, just as the kitchen would. Your app receives every change as an event, by webhook too.

Other restaurants can connect your app once you have submitted it for review and Flavoso has reviewed and approved it. Everything else for developers is in the developer documentation at docs.flavoso.com/en/api.