Skip to content
Horecas
TREnglish
Request a Demo
TREnglish
Request a Demoinfo@horecas.com

Ecosystem

Technology ecosystem and integrations

This page sets out the services Horecas runs on, how we approach connections with hotel systems and how we verify partner relationships.

Talk to us about integration

How we publish this page

  • We show a partner relationship only when it can be verified through the programme’s official listing.

  • We describe every integration by the system it connects to, the data involved and the direction of transfer.

  • We never present a connection that only works in a test environment as a live integration.

Connection map

Where information comes from, and who it reaches

Each product connects to a different part of the hotel’s work. Solid lines show the flows the products use today; the dashed line is a connection that does not exist yet and is discussed case by case.

  • Source

    A guest’s WhatsApp message

    Through WhatsApp’s official business platform

    HorecasConcierge
    Destination

    Department screens

    Requests, complaints and conversations

  • Source

    Spa and massage booking requests

    Via Concierge or entered by the spa team

    HorecasWellness
    Destination

    Spa calendar

    Therapists, treatment rooms and sessions

  • Source

    Rates on sales channels

    Prices and conditions publicly visible on each channel

    HorecasParity
    Destination

    Parity findings

    Rate differences and evidence records

  • Source

    Guest and stay list

    Today: Imported into the panel from an Excel file or entered one by one.

    Not available today · discussed case by case: Transfer from the hotel’s own systems (PMS, Oracle Hospitality). There is no live connection today; the scope of a first connection is agreed in conversation.

    HorecasGuest records

    Connecting with hotel systems

    The connected system, data types and direction of transfer are agreed with each hotel.

    Oracle Hospitality
Flow the product uses todayMonitoring publicly available informationNot available today · discussed case by case

How we show partner status

  • Status names are written exactly as they appear in the official record.
  • A programme’s general information page is never used as proof of membership.
  • Using a provider’s technology does not make us that company’s partner.

Connecting with hotel systems

An integration is a defined exchange of data between a system the hotel uses and Horecas. For each hotel, its scope is set by the connected system, the data involved, the direction of transfer and the environment.

Integration page

Oracle Hospitality

For hotels using Oracle Hospitality products, a dedicated page covers where things stand today, how a connection would be set up and what the hotel needs to provide.

  • OPN membership versus integration
  • What is OHIP?
  • Current status and scope
  • Test and live environments
  • Hotel-side requirements
Read the Oracle Hospitality page

Starting without an integration

Get started without waiting for a connection

Guest and stay details can be imported into the panel from an Excel file or entered one by one. Concierge, Wellness and Parity can all be used without a connection to a hotel system.

arrivals.xlsxIllustrative screen · Sample data
GuestRoomArrivalDeparture
A. Demir21421/1024/10
M. Schneider30521/1026/10
L. Rossi11822/1025/10

Using a different PMS or hotel system? Tell us about your system

Services our products rely on

We use the services below as part of our products. Using a service does not mean we have a formal partnership with the company behind it.

  • WhatsApp

    Guest messaging

    Concierge receives and answers guest messages through WhatsApp’s official platform for businesses. Guests do not need to download an app.

  • iyzico

    Subscription payments

    Subscription payments are taken through iyzico, a licensed payment institution; card details are not stored by Horecas.

Process

How an integration conversation works

Every hotel has different systems and priorities. We run the conversation in four steps and record what has been agreed at each one.

  1. Understand your systems

    We learn which system your hotel uses, which version, and who is responsible for managing it.

  2. Agree the scope

    We decide which data moves in which direction and how often, and which Horecas product will use the connection.

  3. Try it in a test environment

    We first try the connection in the hotel’s test environment. A successful test is not the same as a live connection.

  4. Go live with approval

    Moving to the live environment requires the hotel’s authorised approval and a separate verification.

Let’s talk

Let’s review your hotel’s systems together

Tell us which systems you use and what you need; we will work out the possible scope of a connection together.

Talk to us about integration

Want to see the products first? Request a demo