Breakfast Consistency Across Hotel OTA Listings

Breakfast is represented by several separate attributes, not a single yes/no. Google's lodging reference defines fields such as breakfast_available, breakfast_for_free, and buffet_breakfast. A listing can therefore be internally consistent yet still disagree with another channel about whether breakfast is offered, included in the rate, or charged as an extra.

On Booking.com, whether a meal is included depends on how it is configured: meals can be attached to specific rate plans or offered as a paid add-on with a price. That means the same property can present a room as breakfast-included on one channel and breakfast-extra on another, depending on which rate plans are published where.

This is why breakfast is one of the fields MisMatchMaker compares: availability, inclusion, and price can each drift independently.

Common causes of a breakfast mismatch:

• A breakfast-included rate plan exists on one channel but not another.
• The breakfast price is updated in one extranet and left stale elsewhere.
• Breakfast hours or type (continental, buffet, à la carte) are described differently.
• A promotion bundles breakfast temporarily and the listings are not realigned afterwards.

Use the property's current food-and-beverage offer as the authority.

• Record whether breakfast is available, whether it is included, and the price when charged.
• Compare at least two accessible listings before declaring the field consistent.
• Separate a real contradiction from a rate-plan scope difference.
• Log a missing breakfast value as incomplete evidence rather than 'not available'.