The short answer
Start with the operating record guests rely on: the correct property category, the breakfast offer attached to the dates and rate, the last arrival time someone can actually support, and the exact parking arrangement. Compare those facts against the public pages, then record what still needs a manual check.
Choose the category that describes the real operating model
A guesthouse, pension and bed and breakfast can sound interchangeable in everyday conversation, but an OTA may offer them as separate property categories. Booking.com’s current property-class reference lists Bed and Breakfast and Guest House separately. Expedia Group’s Rapid content reference likewise lists Bed & Breakfast and Guesthouse as distinct categories. Those lists show that a cross-channel audit needs a platform-by-platform mapping; they do not establish that one label is universally correct for every business using the word guesthouse.
Write down what the property actually operates before opening an extranet: accommodation type, whether guests book rooms or an entire unit, the services included as standard, and the name customers recognize. Then compare each OTA’s selected category with that approved description. Keep the reason for a choice beside the value so a future editor does not change it just to make two unlike platform labels match.
The goal is an accurate representation on each channel, not identical category wording. For a deeper explanation of how the platforms model categories, use the linked property-type guide; this page applies that distinction to a small property’s audit record.
| Record | Example evidence to keep | Audit question |
|---|---|---|
| Approved business identity | Trading name, address, accommodation model | Does each listing represent the same property? |
| Platform category | Displayed category and the date checked | Does this platform's choice fit the real offer? |
| Reason for a difference | Short note from the owner or listing administrator | Is the difference intentional, or just inherited? |
Audit breakfast as a promise attached to a stay
For a B&B, ‘breakfast’ is often a core part of the guest’s reason for choosing the property. The operational question is more specific than whether a breakfast icon appears: what does this guest receive, on which days, during what service window, and is it included in the booked rate or offered for an additional charge? Keep the approved answer in a single property record before comparing platform displays.
Small properties can change the breakfast service with the season, weekday staffing, an early departure, or a temporary kitchen closure. Record the normal service and any date-limited exception separately. A rate that includes breakfast on one listing and a breakfast add-on on another is a materially different booking promise; a channel that does not show a detail is incomplete evidence, not proof that breakfast is unavailable.
This page does not repeat the channel-specific breakfast field map. Use the breakfast guide for the field mechanics, then use this segment checklist to test that the public wording still matches the service your team can deliver on the booked date.
- State whether breakfast is included, optional at a stated charge, or not offered.
- Record serving days and the service window, including any recurring closed day.
- Check the guest-facing rate terms as well as the property-level breakfast description.
- Assign one person to update temporary closures and confirm when the public pages reflect them.
Make the arrival promise match the person on duty
At a small property, ‘check-in available until 22:00’ can quietly depend on one host, a phone that is not always answered, or a keypad guests cannot use until they receive a code. The audit should capture the actual guest journey: the published arrival window, the latest time a person is available, the after-hours method, and what happens if a guest is delayed.
Do not let a scheduled reception period stand in for a self check-in process. If access after hours relies on prior notice, a message, a working phone number, or a code issued for that reservation, make sure the public arrival instructions explain the required action without exposing private access credentials. Keep the same operating rule on every listing even when each platform offers different fields.
MisMatchMaker can compare supported check-in and check-out details when it extracts comparable values. It does not verify your staffing roster, whether an arrival message was sent, or whether a lockbox or access code works. Those remain operational checks for the property.
- Compare published check-in times with the latest staffed arrival time.
- Record the action a late guest must take and who responds if it fails.
- Check that instructions are visible before booking where the platform permits it.
- Keep private codes and guest-specific access details out of public listing copy.
Describe parking at the capacity you can actually offer
A B&B with two spaces and six rooms does not offer the same parking experience as a hotel car park. Record whether spaces are on the property or nearby, whether they are free or charged, whether a reservation is needed, and what the guest should do when the spaces are full. Those details are especially important when parking is limited or shared with another business.
Audit the public promise against the physical arrangement, not against the word ‘parking’ in a checklist. A nearby public garage, street parking and a space reserved by the property are different offers. If a booking requires advance confirmation, keep that condition clear and use the same source record when updating each channel.
The parking guide covers channel differences in more depth. For this segment, the key control is capacity: name the number or reservation condition only when the property can keep that information current, and do not imply a guaranteed space when allocation is first come, first served.
| Question | Approved property answer | Public check |
|---|---|---|
| Where is it? | On site, reserved nearby, or public street/garage | Does the listing say the same location? |
| Can every booking use it? | Capacity, allocation and reservation condition | Could a guest read this as a guarantee? |
| What does it cost? | Free, paid, or no property-controlled option | Does the charge or limitation appear clearly? |
Separate the scanner’s comparison from the owner’s review
The scanner can compare supported breakfast, parking and arrival fields when at least two readable listings provide comparable evidence. A missing value, one readable value, or a page the scanner cannot access is not a consistency result. The methodology page carries the current channel list and evidence rules.
Reception opening hours, staffing, breakfast service quality and whether a limited parking space has been reserved require a manual review. The scanner also does not read the property’s extranet or internal operating record, so it cannot tell you which of two public values is correct. Confirm every finding against the B&B’s approved record before changing a listing.
For the current field list and limitations, see the methodology. For the field-by-field publishing instructions, use the breakfast, reception-hours, check-in and parking guides linked below.
- Run a scan for the supported public listing fields it covers.
- Manually check reception coverage, self check-in steps and limited parking capacity.
- Use one dated owner-approved record to decide which value should be published.
- Revisit each public listing after an edit; the scanner does not confirm that a change was submitted or published.
Questions operators ask
Should a B&B use the same property category on every OTA?
Use the category that accurately represents the property within each platform’s available taxonomy. Platform category lists differ, so record why the selected labels fit rather than forcing identical wording across unlike systems.
Does the scanner check whether breakfast is actually served?
No. It compares public listing evidence for supported fields. The property must confirm the service, dates, hours and rate inclusion against its own approved operating record.
Can it verify that our self check-in instructions work?
No. The scanner can compare supported published arrival-time fields, but it cannot test staffing, send or validate guest-specific instructions, or operate a lock or keypad.
What should I do when parking is limited?
Record capacity, location, price and whether a reservation is required. Make the public wording clear about whether a space is guaranteed, allocated by the property, or subject to availability.
Primary sources and limits
- Property Class Type Codes (OTA 2014B) — Booking.com Connectivity documentation, accessed . Lists Bed and Breakfast and Guest House as separate property classes in its current reference.
- Content reference lists — Expedia Group Developer Hub, accessed . Lists Bed & Breakfast and Guesthouse separately; this API reference does not define the correct category for a particular property.
- MisMatchMaker scanner methodology — current supported channels, comparison fields and limitations. Platform API references cited above describe their documented content models and are not hotelier interface instructions.
Continue the audit
Breakfast consistency across hotel OTA listings
Check whether breakfast availability, inclusion, and price agree across channels.
Hotel reception hours and self check-in across OTAs
Publish the arrival facts that have no structured field: reception hours, out-of-hours access, and key collection.
Hotel parking information across OTAs
Audit parking availability, fees, access, type, EV charging, and accessibility without collapsing distinct facts into one label.
Check the listing details your guests rely on
Compare supported breakfast, parking and arrival fields across public pages. Then confirm service dates, late-arrival coverage and limited-space availability with the property owner.
Run a free match check