Our Simphony integration synchronises reservations, tables, and POS activity between both systems to support smooth front of house operations. It automatically creates and manages checks when tables are seated, applies deposits taken in ResDiary to the POS, updates meal progress in real time, and sends spend data back to ResDiary to enrich guest profiles and reporting. This ensures online availability and in venue activity always remain accurate and aligned.
⚠️ Important: You can read this article to familiarise yourself with Simphony POS functionality with ResDiary. If you plan to use the integration, ensure your setup process is completed.
Seat your reservation
When a reservation in ResDiary is marked as fully seated, a check opens automatically in Simphony, with booking details and any deposit information passed through. Read the steps below to see this functionality in action:
From our interface, ensure the reservation has arrived.
Click your reservation, then click the Fully Seated
icon.This opens a check automatically in Simphony with the following details:
Customer name.
Booking reference.
Promotion, if applicable.
Deposit amount paid.
Below you can find an example image showing how the check appears in Simphony:
📌 Note: As orders are placed, meal statuses update in ResDiary, once a payment is taken and the reservation is closed, spend details are stored back in ResDiary.
Seat your walk-in
When a guest arrives without a reservation, adding a walk‑in booking in our system opens a new check in Simphony. If no walk‑in is created in ResDiary, a walk‑in booking is created automatically when a check is opened in Simphony.
Handle deposits
If you reservation has a deposit attached then it appears on the open check within Simphony, you staff need to apply the deposit manually depending on your configuration:
As a service charge.
As a menu item.
Update your meal statuses
⚠️ Important : Meal status updates only occur when menu items in Simphony use recognised category tags. A menu item is treated as a match if any supported tag is found in a tag group, family group, or SLU, screen lookup category.
As the guest journey progresses, our integration will real time update the following events on your booking history if they are tagged as follows on Simphony:
Drinks: Drink or Drinks.
Starters: Starter, Starters, Appetisers or Appetizers.
Mains: Main, Mains or Main Courses.
Desserts: Dessert or Desserts.
Paid.
Closed.
Move your tables
Simphony API doesn’t transfer checks, therefore moving a booking on ResDiary after it is seated, will not automatically move the check on Simphony POS. You can follow the steps below to move your tables on both systems:
Move the booking to the new table in ResDiary.
Open a new check on the new table in Simphony.
Transfer the items from the original check to the new check.
📌 Note: Moving a check on the POS does not automatically move the booking in ResDiary.
Close your check
When your guest pays and the check is closed within Simphony the following happens automatically:
Booking status within ResDiary changes to closed.
Total send is recorded.
Itemised receipt is stored in the booking details.
Below you can find an example image showing how the itemised receipt appears:
📌 Note: Itemised check details are not recorded for walk-ins.
Update your API password
Simphony API user password expires every 60 days. When it expires, the integration stops running and the password need to be reset, then updated in your ResDiary settings. Follow these steps to reset the expired password:
Ensure you are on Simphony web page.
Click Can't Sign In on the Reporting and Analytics sign-in.
Enter the below details and click Send Email:
UserName : API username.
EnterpriseName : Enterprise short name.
A password reset email will be sent to the email address associated with your API user.
Once you have the new password login to your ResDiary account.
Click Settings, then Simphony Settings.
Enter the new API password in the relevant fields, then click Update.
⚠️ Warning: If you have multiple diaries connected to Simphony, you'll need to update this configuration for each of them. The integration should resume running after approximately 15 minutes.