- STATUS: ACTIVE

- COMPATIBLE VERSION: 3.2


1. WHAT IS COVERMANAGER?
2. HOW DOES THE INTEGRATION BETWEEN COVERMANAGER <-> REVO WORK?
3. INFORMATION TO SEND TO COVERMANAGER
4. CONFIGURATION IN REVO


1. WHAT IS COVERMANAGER?

CoverManager is a technology company serving restaurants.

Its goal is to help restaurants eliminate "no shows," improve demand, and retain customers, without depending on a sales channel.

CoverManager is the way to make reservations at restaurants in the 21st century, easily accessible for every restaurant and customer from anywhere in the world. You can manage reservations from a computer or tablet, without the need to download any application or install software.

More information about CoverManager can be found at this link.






2. HOW DOES THE INTEGRATION BETWEEN COVERMANAGER <-> REVO WORK?

Integration with REVO allows us to synchronize reservations in the CoverManager system. An agile and quick way to connect the system with the REVO POS.

  • By clicking on Sit in CoverManager, the table will be occupied in Revo XEF.
  • Allows us to move reservations on the table layout from REVO.
  • It allows us to separate tables from the layout once the order is paid.
  • It allows us to import the room and table layout from CoverManager to REVO.
  • It allows us to share information about the state of the tables: occupied or released.

In summary, the two platforms will be connected, sending information from one to the other, achieving a very simple and comfortable workflow.


3. INFORMATION TO SEND TO COVERMANAGER

To be able to correctly integrate with the CoverManager reservation manager in REVO, it is necessary to send them certain information from our Revo XEF account so that they can provide us with the necessary keys. To do this, we will send an email to hospitality@covermanager.com with the following:

  • Tenant: Username of the REVO account.

  • Authorization XEF: This is the "token" (sequence of alphanumeric characters) that must be generated in the back-office. To do this, access Account / TOKENS and click on +New:




4. CONFIGURATION IN REVO

1. Access the back-office of REVO.

2. Click on Integrations.

3. From the Add button, search for CoverManager, and click Add.



4. Fill in the following information:



  • Active:

  • Name: Identifying name of the integration.

  • Test: Deactivated.

  • API Key: Provided by CoverManager.

  • Restaurant: Provided by CoverManager.

  • Separate tables on close: Choose whether to separate tables when closing the order.


5. We can import tables from CoverManager to respect the configuration and distribution already set up. To do this, go to Design / ROOMS, and in the upper right corner, the Import button will appear.
Once imported, it is advisable to close the app completely and reopen it. This ensures that the rooms are synchronized correctly, and their layout is preserved.

IMPORTANT: We must have the shifts closed, and we must ensure that the data is correctly filled out on the integration screen; error messages will specify the reason, for example:



Note: Once we activate the CoverManager integration, we can no longer create new rooms from the XEF back-office.


IMPORTANT: All accounts that already had the integration created will continue to work as before, but we recommend contacting and requesting the API Key and Restaurant from CoverManager to update the integration, as the old keys will become obsolete.


The integration is now completely configured!


Once we have the reservation created in CoverManager, when customers arrive at the venue, we will click on Sit in CoverManager. This way, the table will appear in Revo XEF. Once we finish the order, REVO will send the information to CoverManager, and the table will be released.



Similarly, when we open a new table from REVO, a Walk-In will be created in CoverManager, to make a reservation from Revo XEF and for the update to be done correctly in CoverManager, it is necessary to first perform the action of occupying the table (on the table of interest, swipe down with the finger and press Occupy table).



If we wanted to deactivate the integration with CoverManager, we should not only deactivate it from the INTEGRATIONS section, but also deactivate the TOKEN previously created.