Mews x Delphi is an indirect integration with Omniboost as a middleware to help you manage events. You can learn more about Delphi here. You can enable the integration anytime within the Mews Marketplace in Mews Operations. The integration supports Delphi based only on the Salesforce version. This is the newest Delphi edition and the only version you can connect to Mews via API.

 

The integration supports the following:

• Delphi creates, updates, and cancels blocks in Mews.
• Mews updates blocks in Delphi.
• Mews sends pickup information to Delphi.

 

In this article, you can find answers to the following frequently asked questions:

• What does the Mews x Delphi integration support?
  • What can the integration sync from Delphi to Mews?
  • What can the integration update from Mews to Delphi?
  • What is the availability updates logic from Mews to Delphi?
  • How does the integration sync pick-ups?
  • What is an Activity?
• What does the Mews x Delphi integration not support?
• Can I overbook availability blocks from Delphi to Mews?
• Can I modify an availability block after the release date from Delphi to Mews?
• Can I modify the availability block arrival/ departure dates?
• Can I downgrade an availability block status from Delphi to Mews?
• Can I cancel an availability block with a pick-up?
• Can I reinstate an availability block?
• Can I modify an availability block in the "In house" state?
• What is the difference between packages in Delphi and Mews, and how do I configure them?
• How do Delphi packages apply to different types of blocks in Mews?
• How do I manage data during onboarding with the Mews x Delphi integration?
  • Scenario 1: New to Mews and already using Delphi
  • Scenario 2: Already using Mews and Delphi
  • Scenario 3: Already using Mews and new to Delphi

 

What does the Mews x Delphi integration support?

The integration syncs availability blocks from Delphi to Mews, for example, creation, update, and cancelation.

 

What can the integration sync from Delphi to Mews?

• Booker details, for example, Booker, Company, Travel agency
• Block status
• Start and end date
• Release date
• Allocated space categories
• Number of allocated spaces
  • The integration syncs only blocked spaces processed by Mews.
  • The current version of the integration bypasses Agreed and forecasted spaces.
• Night prices.
  • The integration supports both net and gross.
  • The integration adds Price as per the Mews pricing environment.
• Booking types

 

What can the integration update from Mews to Delphi?

• Allocated space categories
• Night prices
• Block name under Room Block in Delphi
• Release date
  • The release date must be no later than the arrival date due to Delphi's business logic.
• Every other update must come from Delphi. Note: The integration cannot,
  • create Blocks from Mews to Delphi.
  • cancel Blocks from Mews to Delphi
  • update Block status from Mews to Delphi.

 

What is the availability updates logic from Mews to Delphi?

• Mews is the source of truth for availability.
• Mews sends Transient Sold and Out of Order rooms to Delphi, and Delphi calculates availability. Note:
  • • Transient sold is any reservation the system creates outside of synced blocks.
    • If the system creates a block in Mews directly, the integration considers it Transient Sold in Delphi.

 

How does the integration sync pick-ups?

• Mews syncs a number of picked-up reservations to Delphi as Mews creates them.
  • Pick-up information includes,
    • the number of picked-up rooms per space category.
    • the average night price per space category.
• 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. You can then use this information to build reports within Delphi.

 

What is an Activity?

The integration creates an Activity for your Delphi users to notify them about a failed block synchronization. Once the user fixes the error, the integration automatically re-tries the block synchronization. A failed block synchronization happens because of the following:

• You used an unknown room type code.
• The integration does not support Run of House.
• You made a modification after the cutoff date.
  • Mews does not accept block modifications that affect availability or night prices after the release date.
• You updated the dates for a pick-up booking.
  • Mews does not accept date updates for availability blocks that have picked up rooms.
• You canceled a pick-up booking.
  • Mews does not accept availability block cancellation if the block has picked up rooms.

 

What does the Mews x Delphi integration not support?

• Run of House
  • The integration fails to sync blocks created for Run of House into Mews.
  • The Delphi user receives a task to remove Run of House and assign a room category.
• Event only bookings
  • Delphi does not support meeting room types. The integration cannot map meeting room types to meeting rooms in Mews.
  • The integration syncs event-only bookings to Mews as a block shell only, for example, if the event has no space category assigned.
  • The integration cannot sync packages/ revenue into Mews.
    • You need to manually post items consumed by guests without a room reservation in Mews.
• Billing
  • The integration does not communicate billing-related information between Mews and Delphi.
  • Mews does not update Delphi when you settle a group invoice in Mews. You need to check this manually.
• Per pax pricing
  • Mews always accepts price per 1 pax. The integration does not process prices per other pax counts.
  • If needed, you can create availability adjustments directly in Mews.
• Multiple blocks
  • If you create several room blocks within one booking in Delphi, the integration creates them as separate availability blocks in Mews. The system assigns the same external IDs and names to the blocks.

 

Can I overbook availability blocks from Delphi to Mews?

Delphi can send a room allocation update that adjusts the allocated room number, even if the amount is higher than the available rooms for this space category.

 

Can I modify an availability block after the release date from Delphi to Mews?

Mews accepts any modification other than night price and room category updates. If you need to update the night price or room allocation, you need first to set the release date to the future date. Note: Delphi allows arrival date as the latest release date.

If you need to make changes to the block after the arrival date, you need to do this in Mews directly. Note: The integration does not then sync the information into Delphi.

 

Can I modify the availability block arrival/ departure dates?

Yes, as long as it does not conflict with picked-up reservation dates.

 

Can I downgrade an availability block status from Delphi to Mews?

• Definite > Tentative: The integration still deducts the availability of the block from the total availability.
• Tentative > Prospect: The integration no longer deducts the availability from the total availability.
• Definite > Canceled: Release availability.
• Canceled > Definite: This is not possible in Delphi, but it is possible in Mews.

 

Can I cancel an availability block with a pick-up?

You cannot cancel it from Delphi directly. First, you need to cancel reservations in Mews. If a Delphi user tries to cancel a group with a pick-up, the update fails and creates an Activity for that user.

 

Can I reinstate an availability block?

Delphi does not support group reinstatement. You need to create canceled groups again and have a unique PMS ID. Note: This cannot be the canceled group PMS ID.

Mews allows reinstating canceled groups, but the integration won't sync this information to Delphi, creating availability discrepancies.

 

Can I modify an availability block in the "In house" state?

Yes, as long as the release date is in the future.

 

What is the difference between packages in Delphi and Mews, and how do I configure them?

Packages in Delphi and Mews work differently, and Delphi packages do not sync to Mews.

• In Delphi, packages include all booked services, for example, meals and coffee breaks. The system assigns these packages to a group block, but the integration cannot sent them to Mews because Delphi does not support this through its API.
• In Mews, you manage packages through product rules that you link to rate plans. The system assigns them to picked-up reservations, not to availability blocks.

To configure packages in Mews when using the Delphi integration:

1. Create a list of rate codes that match product rules in Mews.

• • For example, use the BFST rate code for blocks that include breakfast packages.

2. Enter the correct rate code in Delphi before creating the block. Note: Once a block syncs to Mews, you cannot update or add a rate code. Even if Delphi allows changes, Mews does not process them.
3. When the system picks up a reservation, it automatically assigns products linked to the rate plan.

You can learn more about product rules here.

 

How do Delphi packages apply to different types of blocks in Mews?

Delphi packages apply differently in Mews depending on how users book rooms and services. Delphi does not send package information to Mews. You need to configure product rules in Mews to automate package assignments where possible.

Here are three common use cases:

• All guests have a room reservation:
  • If all guests in the block stay at the hotel, you can automatically assign Delphi packages through product rules in Mews.
  • For example, a wedding with 30 guests staying overnight. When guests make their reservations, their packages are added automatically and appear on their bill.
• Only some guests have a room reservation:
  • If some guests in the block stay overnight and others attend only for specific services, the system only adds packages for those with a room reservation.
  • For example, a wedding with 30 guests, where only 10 guests stay at the hotel. The system automatically adds the packages for the 10 guests, but not for the remaining 20 guests. You need to manually post additional services to the booker profile in Mews to ensure the full event bill is recorded.
• The guest books a non-room type space:
  • If the block includes a meeting room or event space without hotel rooms, Delphi creates an availability block shell in Mews. This includes the date details and contact information, but no rooms or prices.
  • You need to manually post additional services and space costs to the booker profile in Mews to ensure all charges appear on the final event bill.

 

How do I manage data during onboarding with the Mews x Delphi integration?

Onboarding to Delphi depends on the data already in Mews and whether your property is connected to iHotelier or SynXis. Follow the steps below based on your specific situation.

Scenario 1: New to Mews and already using Delphi

If your Mews environment is clean, the connection to Delphi is faster. Delphi creates blocks in Mews without needing to link existing ones. However, if you are connected to iHotelier or SynXis, follow the steps below to ensure that picked-up reservations sync correctly.

Delphi x Mews x SynXis/iHotelier

If your property has blocks created in Delphi and synced to iHotelier or SynXis through a previous property management system, there are picked-up reservations in iHotelier or SynXis that you need to import into Mews only after you sync the blocks. Otherwise, the system creates reservations independently from blocks. Once you create a reservation in Mews, you cannot assign it to a block.

 

Steps to onboard:

1. Check block codes.

• • Ensure that block codes, also called External ID in Mews, match between Delphi and iHotelier or SynXis.
  • If they do not match, update block codes in Delphi to match those in iHotelier or SynXis.

2. Connect Delphi.
3. Import blocks from Delphi into Mews.
4. Connect iHotelier or SynXis.

• • Since blocks already exist in iHotelier or SynXis, Mews links them instead of creating new ones.
  • Contact support using the Mews Digital Assistant or your onboarding manager for assistance.

5. Import reservations from iHotelier or SynXis. Note: Do not push all reservations at once. Push several first to ensure correct integration.
6. Import additional reservations that cannot be imported from iHotelier or SynXis.
7. Enable iHotelier or SynXis integrations.

Note: It is best to connect Delphi on the go-live date to maintain correct inventory and simplify the onboarding process.

 

Delphi x Mews

If your property creates blocks in Delphi but they are not synced to iHotelier or SynXis, picked-up reservations remain in the previous property management system. You must import these reservations into Mews only after you sync the blocks. Otherwise, they are created independently from blocks. Once created in Mews, reservations cannot be assigned to a block.

 

Steps to onboard:

1. Connect Delphi.
2. Import blocks from Delphi into Mews.
3. Import reservations.

 

Scenario 2: Already using Mews and Delphi

If you are already using both systems and now connecting them, ensure that blocks between Delphi and Mews match to enable future updates.

Delphi x Mews x SynXis/iHotelier

If your property is connected to iHotelier or SynXis, block codes between Mews and iHotelier or SynXis always match.

 

Steps to onboard:

1. Check block codes.

• • Ensure that block codes, also called External ID in Mews, match between Delphi and Mews.
  • If they do not match, update block codes in Delphi to match those in Mews.
  • You can find the correct code in Mews under Availability Blocks > External ID.

2. Connect Delphi.

 

Delphi x Mews

If your property is not connected to iHotelier or SynXis, block codes only need to match between Mews and Delphi.

 

Steps to onboard:

1. Connect Delphi.

Scenario 3: Already using Mews and new to Delphi

If your property is new to Delphi but already using Mews, follow these steps to ensure a smooth transition.

 

Steps to onboard:

1. Manually create Mews blocks in Delphi.
2. Connect Delphi.

 

 

 

 

You can learn more about how the Mews x Delphi integration syncs information between Delphi and Mews here.