The following content was translated with the support of artificial intelligence and subsequently reviewed by our team.

The MEWS integration enables incert to retrieve stay and guest data and forward it to the LOY system, allowing profiles to be created (at check-in/reservation) and points to be awarded automatically (at check-out). Optionally, points and club levels can also be transferred back to MEWS (bidirectional functionality). General information on rewarding stays can be found here.

If you are interested in such an interface, we look forward to hearing from you at sales@incert.at. Additionally, the interface must also be ordered via MEWS.

Process

1. MEWS transfers reservation and check-in/-out data to incert.
2. incert evaluates the data during the nightly job and processes it further.
3. The guest is rewarded based on revenue.
4. Optional: Bidirectional functionality – incert transfers club levels and point balances to MEWS every hour. These are then stored in MEWS as dedicated fields. Mapping is performed based on the PMS ID.

Limitations due to interface design: for example, invoices and reservations without direct relation.

Please note that we cannot provide support for actions within third-party systems. This description was prepared to the best of our knowledge. In case of doubt or further questions, please contact the system provider directly.

Use cases

Rewarding revenue

Incert receives one or more reservations containing guest information. For all received guest details, the system checks whether receipts exist within the same reservation period. Rewards based on this information are issued only after the guest has departed.

Deviating or customized use cases require prior review.

Rewarding overnight stays

Please note that rewarding overnight stays is not possible with MEWS!

If you have questions regarding this, your assigned project manager will assist you.

Setup

To set up MEWS, we require an access token for the respective MEWS system. To obtain this, please log into the Marketplace, navigate to our integration, and forward the listed token to us – Finding an integration's access token

If you already have an incert system connected to MEWS, no additional API token is required.

Important notes

• Multi-property behavior: For multi-property setups, incert must verify whether guest profile uniqueness can be ensured.
• Distinguishing direct bookings: Differentiation between booking sources or external platforms is currently not supported.
• Overwriting profiles: Guest profile uniqueness is required (email is the "unique key" in the Club). Assignment in MEWS is based on Chain ID or the dedicated Access token. By default, during the initial Club registration, the email address is linked to the unique PMS ID (MEWS). This combination is used for awarding points.
• Creating or modifying loyalty memberships (in MEWS): Profile synchronization only occurs after the stay. Other guest data is not modified by incert. The leading system is the incert club. Manual membership changes in MEWS will be overwritten during the next synchronization (Club level and point calculations remain traceable in the club).
• Cancellation behavior: If stays that have already been rewarded are cancelled, the awarded points will be deducted automatically, provided they have not yet been redeemed.

Bidirectional data exchange is possible. Transferring club levels and point balances to MEWS can be ordered additionally. Configuration and handling depend on the specific customer setup and require prior review by incert. In general, first and last name must be transmitted for bidirectional functionality, and these fields may be overwritten during synchronization.