For apartment-style stays

    An OTA content audit for aparthotels and serviced apartments

    Apartment-style accommodation is sold through several layers at once: the property identity, the particular unit or room type, and the terms attached to a rate. This audit helps an operator check those layers together so a building-wide claim does not accidentally promise a feature or service in every unit.

    The short answer

    Build the audit around a unit-and-rate matrix. Confirm the property category, list each sellable unit’s actual facilities, and attach cleaning, linen, utility and minimum-stay terms to the booking condition where they apply. Then compare public listings and manually review the details outside scanner scope.

    Keep property category separate from the unit being booked

    An aparthotel or serviced-apartment operator may use a familiar market description that does not map one-to-one onto every OTA’s category list. Expedia Group’s content reference says a property has one property category and lists Apartment and Aparthotel as separate values. Booking.com’s current property-class documentation lists Apartment and ApartHotel as different classes. This is a reason to verify the selected category on each platform, not to copy one platform’s label blindly into another.

    Separate the building-level category from the inventory that guests actually book. A property can have one identity while offering studios, one-bedroom units and larger apartments with different layouts. Record each public room or unit name, its occupancy and its defining facilities in an internal crosswalk. A building-level label cannot tell a guest which unit they selected.

    The general property-type and room-mapping guides explain the wider taxonomies. The segment-specific task here is checking that category, sellable unit and booking terms do not collapse into one ambiguous description.

    Three distinct levels to keep in an aparthotel audit
    LevelWhat belongs hereExample check
    PropertyThe building's category and shared servicesDoes the category describe the property as operated?
    Unit or room typeLayout, occupancy and facilities in that inventoryDoes the booked unit itself have the stated kitchen?
    Rate or stay termsInclusions, charges and length-of-stay conditionsDoes this rate explain the fee and minimum stay?

    Verify kitchen claims against each sellable unit

    A kitchen in the building is not evidence that every unit has a kitchen. List facilities at the granularity the guest books: full kitchen, kitchenette, cooking facilities, refrigerator, or no cooking provision. Use only descriptions that match the actual inventory, and note any unit where a facility differs from the rest of the property.

    There is a platform-specific operational reason to make this check carefully. Booking.com’s property-class reference says Apartment and ApartHotel room types require a kitchen or kitchenette to become open and bookable. Treat that as a Booking.com connectivity rule in the cited documentation; it is not a universal definition of an apartment or a statement about another OTA’s setup.

    Expedia Group’s Rapid content model places amenities at property, room and rate-plan level. Its developer documentation is not a Partner Central click-path guide, but it illustrates why a kitchen or other amenity should be checked at the level where it applies. A facility that is limited to one unit should not be described as available to every guest unless it truly is.

    • Maintain a unit list with the exact inventory name and maximum occupancy.
    • Record the kitchen or kitchenette facilities for each unit, including exceptions.
    • Distinguish a shared building facility from an in-unit facility.
    • Verify both the public room description and any structured amenity attached to that room.

    Attach cleaning and service charges to the right booking terms

    Serviced apartments often combine accommodation with periodic cleaning, linen replacement, utilities or other services. The audit question is not whether these arrangements are common; it is which service this property provides, when it is provided, and whether the booked rate or length of stay changes the terms.

    Keep a charge register with the charge name, amount or calculation basis, whether it is one-off or recurring, the stay condition that triggers it, and where it appears before the guest books. Include cleaning fees and any other mandatory property charge that the guest needs to understand. Keep optional services separate from mandatory charges, and do not label a rate ‘all inclusive’ if a required property charge remains due.

    A minimum-stay rule belongs in the dates and rate conditions that control bookability, while a cleaning service description belongs with the property or unit information it describes. These can be maintained in different systems, so compare the public booking path rather than assuming a channel manager sent every detail. For tax and fee display rules, use the dedicated fee guide; this page concentrates on matching the charge to the unit and stay condition.

    A charge register that catches scope mismatches
    FieldRecord before editingCommon scope question
    CleaningAmount, frequency, and the stay conditionIs it per booking, per night, or a service included in the rate?
    Linen or utilitiesIncluded service or separately payable chargeDoes the term apply to all units and all rates?
    Minimum stayDates, season or unit/rate where it appliesCan the guest see the restriction before choosing the stay?

    Use a unit-and-rate crosswalk instead of one property checklist

    A generic property checklist can hide the errors that matter most in an apartment operation. A studio may have a kitchenette and a two-night minimum, while a larger unit has a full kitchen and a longer cleaning interval. If the team stores only one answer for ‘kitchen’ or ‘cleaning’, a listing editor can apply the wrong fact to a particular unit or rate.

    Use one row per bookable unit type and record the channels where it appears. Add columns for guest capacity, facilities, cleaning cadence, fee terms, minimum stay and last verification. Where a rule changes by rate or date, keep that as a linked rule rather than overwriting the unit’s underlying fact. The record should make it possible for someone else to see why the public page differs between products.

    When a unit is renamed or retired, preserve the old name and the effective date in the audit log. That makes it easier to tell a stale listing from a legitimate inventory change and prevents a broad edit from reintroducing a retired unit under an old label.

    • Compare the same unit to itself across channels before comparing unlike unit names.
    • Separate permanent unit facilities from rate-dependent or date-dependent terms.
    • Check the full guest booking path for minimum-stay restrictions and mandatory charges.
    • Assign a named owner to approve changes to the property’s unit crosswalk.

    Use automated comparison for the fields it can actually read

    A public-listing scan cannot audit an apartment’s unit-and-rate matrix. Room identity, full amenity inventory and stay terms require manual review; consult the methodology for the scanner’s current scope. It cannot confirm that the apartment a guest selected has the kitchen shown in your unit list or validate a minimum-stay rule.

    Use the scan to find supported listing facts that differ across readable pages, then work through the unit-and-rate crosswalk manually for room identity, kitchen facilities, cleaning charges and minimum stays. A field with one source or no reliable value stays insufficient or unavailable; neither outcome proves the values agree.

    The methodology page publishes the current scanner field list. The room-mapping, amenity and fee guides explain the wider cross-channel checks without repeating that material here.

    Questions operators ask

    Does every unit in an aparthotel need the same kitchen facilities?

    No. Record facilities for each sellable unit and distinguish in-unit equipment from shared building facilities. If a feature is limited to one unit type, make sure the public listing does not imply it applies to all units.

    Why does Booking.com’s apartment category need a kitchen check?

    Booking.com’s current connectivity reference says Apartment and ApartHotel room types require a kitchen or kitchenette to become open and bookable. Check the cited documentation and your own connection setup; the rule should not be assumed to apply to other channels.

    Does MisMatchMaker check cleaning fees or minimum stays?

    No. Rates, availability, taxes, room types and full amenity inventories are outside the scanner’s comparison scope. Review those terms through the public booking flow and your unit-and-rate record.

    Should cleaning be described as included if a fee is charged?

    Describe the service and its charge separately and make the booking terms clear. Whether a fee is mandatory and how it must be displayed can depend on the market and platform, so use the dedicated fee-disclosure guide and applicable rules for that question.

    Primary sources and limits

    • Property Class Type Codes (OTA 2014B) — Booking.com Connectivity documentation, accessed . Lists Apartment and ApartHotel separately and documents the kitchen/kitchenette requirement for the referenced Booking.com room types.
    • Content reference lists — Expedia Group Developer Hub, accessed . Documents one property category and property-, room- and rate-plan-level amenities in Expedia Group's Rapid content model.
    • 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.

    Compare supported details around your unit matrix

    Use the scanner for supported public fields, then use the unit-and-rate matrix for kitchens, cleaning terms and minimum stays that the scan does not evaluate.

    Run a free match check