In this article, you can learn how the Mews x Delphi integration syncs information between Delphi and Mews in the following ways:

• The user creates a Booking in Delphi
  • Understanding the values related to Booking
• The user creates a Room Block in Delphi
  • Understanding the values related to Room Block
• Availability information
• Pick up information

 

You can learn more about the Mews x Delphi integration in our frequently asked questions guide here.

 

 

The user creates a Booking in Delphi

When a user creates a booking in Delphi, the integration syncs the information as an Availability block shell in Mews with business details.

 

The following are values related to the Booking step:

 

Understanding the values related to Booking

 

Information

Mews does not process information added under Information in the Booking step in Delphi. This is because you add the same information in the Room Block step in Delphi, where Mews syncs the details.

 

Customer information

• Contact in Delphi = Booker in Mews.
  • If a Booker profile does not exist in Mews, the integration automatically creates it along with the block.
• Account in Delphi = Company in Mews.
  • If a company profile does not exist in Mews, the integration automatically creates it along with the block.
  • The integration may create company duplicates in Mews. This happens during the first time the integration syncs the company into Mews only. The following times, the integration assigns the duplicate profile to blocks. If this happens, merge the company profiles and keep the one the integration created. Note: You can locate this in the Company notes.

 

 

• Agency in Delphi = Travel Agency in Mews
  • If a Travel agency profile does not exist in Mews, the integration automatically creates it along with the block.
• All other profiles remain in Delphi only. Mews does not process them.

 

Segmentation

• Mews processes Booking type only from this section.
  • This translates to Booking purpose in Mews.
  • Mews has three hardcoded values: Business, Leisure, and Student. You can map Delphi values to the three Mews values in Omniboost. Note: These values are visible in Availability blocks in Mews.

 

 

• To add the Market segment:
  • In Mews, segments are assigned based on the rate plan and added when the system creates a pickup reservation.
  • For the integration to correctly populate the market segment, you need to add a rate plan code when creating a group block in Delphi.

 

Booking sources

• The integration does not sync this section into Mews.

 

 

The user creates a Room block in Delphi

A Room block in Delphi equals a step of space category allocation in Mews.

 

The following are values related to the Room block step:

 

Understanding the values related to Room block

 

Room block details

• The integration syncs Arrival and Departure dates both ways into Mews and Delphi.
• The integration syncs Cutoff date both ways into Mews and Delphi.
• The integration syncs Block name both ways into Mews and Delphi.
• You must enter the Rate code before saving the block to have a specific rate plan assigned to Mews. For example, you can attach a Rate plan to segmentation, product rules, and billing automations. Note: You cannot update the rate plan once the system creates the block in Mews.

 

PMS ID/Group code

• The integration populates the External identifier in Mews.
• The External identifier,
  • serves as a unique identifier for blocks between Delphi and Mews and distribution channels.
  • helps to synchronize blocks to iHotelier and SynXis. Note: You need to use a unique identifier.
• If you do not enter Group code in Delphi, the integration automatically generates it. Note:
  • You can update the Group code in Delphi but not in Mews.
  • If you update the Group code in Delphi, the system stores the original value in Mews.
  • This does not affect synchronization, as Omniboost creates a unique code not visible in the interface during initial synchronization and uses it to recognize blocks.

 

Room block status

• You can add block status in two places in Delphi; they don't have to match. Mews accepts the status from the Room block message.
• The following table defines how Delphi statuses translate into Mews block states:

Delphi block status	Mews block state
Prospect (non-deductible)	Inquired (non-deductible)
Tentative (deductible)	Optional (deductible)
Definite (deductible)	Confirmed (deductible)
Booking cancelled (released)	Cancelled (released)
Block cancelled (released)	Cancelled (released)
Lost (released)	Cancelled  (released)
TurnedDown (released)	Cancelled (released)

 

 

Room allocation

• The integration does not sync,
  • Agreed and Forecasted values into Mews.
• The integration syncs,
  • Blocked values into Mews. It is visible under Blocked spaces in Availability block and syncs them both ways.
  • Exclusive and Inclusive rates into Mews depending on the legal environment and syncs them both ways.

 

Update rooms and rates for a specific room category

• In Delphi, you can block rooms per occupancy. This is reffered to as single-quad. The integration does not support this functionality. Instead, Mews adds up blocked values per occupancy. For example, if you block a King room for three single and five double occupancy, in Mews, you will see eight blocked rooms.
• In Delphi rates can be set per occupancy. The integration does not support this functionality. Instead, Mews picks the single occupancy rate and adds it to the availability block.
  • You can set the availability adjustment for the block rate to offer different night prices based on the number of guests. Note: When adjusting rates, consider your distribution strategy, for example, where reservations get picked up.
    • In the Mews Reservation screen and Mews Booking Engine, you can adjust the rate for up to two guests.
    • In Mews Distribution/Channels, you can adjust the rate for up to any guest count depending on room capacity.

 

 

Availability information

Mews is the source of truth for availability. Mews sends transient sold and out-of-order spaces, and then Delphi calculates availability.

• Transient sold includes:
  • The number of reservations not related to availability blocks in Mews.
  • Availability blocks created in Mews only, for example, the number of blocked spaces.
• Out of Order
• Out of Service. The integration does not synchronize this space to Delphi, as it does not affect availability in Mews.

 

 

Pick-up information

• Mews syncs a number of picked-up reservations to Delphi as you create them in Mews.
  • Pick-up information includes,
    • the number of picked-up rooms per space category.
    • the average night price per space category.
  • Average night cost includes night prices only, no package cost or other additional charges.
  • The integration sends inclusive or exclusive of tax depending on the legal environment.
• When all picked-up reservations check out, Mews sends a complete update to Delphi. Note: This process automatically checks the checkbox under RoomBlock in Delphi. The integration checks for it every hour. You can then use this information to build reports within Delphi.

 

You can learn more about the Mews x Delphi integration in our frequently asked questions guide here.