ResNexus

Named subscription tiers offered for this PMS; do not treat optional modules as tiers.

Documented listing or property limits for named tiers; audience ranges do not establish hard limits.

How subscription charges are calculated and billed; distinguish listings, accounts and booking revenue.

Percentage or fixed booking-related vendor fees and the transactions to which they apply.

Features or services requiring a separate payment beyond the selected subscription.

Documented trial duration and conditions; a demo is not a free trial.

Documented one-time implementation or onboarding charges; absent pricing is not zero.

Documented connection method and account/listing restrictions for Airbnb.

Documented connection method and account/listing restrictions for Vrbo.

Documented connection method and account/listing restrictions for Booking.com.

Importing external calendar feeds; document data imported and update constraints.

Exporting calendar feeds for other tools; distinguish feed export from full reservation export.

Sending rates to connected booking channels; identify supported channels and restrictions.

Sending available and blocked dates to booking channels; state method and limits.

Importing or synchronizing channel reservations and changes; identify supported channels.

Receiving and sending guest messages through channel connections; specify channel scope.

Documented update delays, unsupported fields or connection restrictions; no reliability inference.

A calendar view showing multiple listings and bookings together.

Creating reservations manually, rather than only importing channel bookings.

Editing documented reservation fields and whether edits affect connected channels.

Cancelling reservations and documented channel/refund constraints.

Blocking dates without creating a paid guest reservation.

Migrating or importing existing bookings; specify source or import format.

Storing and viewing guest/contact history; do not infer a full CRM.

Exporting reservation records and documented output formats.

Defining rates for date ranges or seasons within the PMS.

Setting minimum-night rules and any date/channel constraints.

Adjusting rules specifically for orphan or gap nights between reservations.

Applying discounts based on stay duration.

Applying discounts based on time remaining before arrival.

Built-in dynamic rate calculation versus external pricing integration; distinguish both.

Named dynamic-pricing integrations and their documented requirements.

Guest message threads combined across supported channels in a shared view.

Messages scheduled relative to documented reservation times or dates.

Messages triggered by reservation events, with named supported events.

Rules that send or skip a message based on documented booking conditions.

Reusable templates and supported guest/reservation placeholders.

AI generates draft replies for a human to review or send.

AI can send guest replies without individual human approval; specify limits.

Documented human-review controls before an AI-generated reply is sent.

Documented message translation functions; multilingual templates are not automatic translation.

Guest communication by SMS; specify country, number and fee conditions.

Guest communication by email and documented sender or channel restrictions.

Vendor-provided tools to create and host a direct-booking website.

Embedding a booking engine in an independently hosted website.

Using a host-owned domain for a vendor-provided direct-booking website.

Named payment services and documented geographical or plan requirements.

Scheduling booking payments or installments; identify relevant booking types.

Taking or holding refundable deposits; distinguish damage insurance/protection.

Issuing refunds through documented payment flows; no fee-refund assumption.

Creating, delivering or signing guest agreements; specify electronic signature support.

Documented guest identity or booking verification; no legal-compliance guarantee.

Vendor fees specific to direct bookings; distinguish processor fees and paid protection.

Creating operational tasks automatically from bookings or reservation events.

Giving cleaners task or calendar access without exposing unnecessary management functions.

Reusable task lists that can be marked complete.

Requesting or requiring photos as task-completion evidence.

Sending documented task assignment, change or completion notifications.

Recording or assigning maintenance work; distinguish generic reminders.

Named external cleaning/turnover connections and documented dependencies.

Delivering guest check-in information at documented reservation stages.

A guest-facing reservation page or portal; specify actions available.

Named smart-lock platforms supported via native or third-party connections.

Creating reservation-specific lock codes automatically, with hardware/service conditions.

Setting code validity to documented check-in/check-out times.

Sending reservation access codes to guests through documented channels.

Additional software or integration charges for smart access; hardware cost separate.

Reports about reservation activity; specify documented measures.

Occupancy reporting and documented date/property filters.

Revenue reporting and supported measures; do not equate to financial accounting.

Statements for property owners, including documented income/expense scope.

Recording property or reservation expenses inside the product.

Named external accounting connections and documented scope.

Exporting reporting outputs in documented formats.

Additional staff accounts and any documented seats or plan limits.

Configurable permissions or predefined access roles.

Restricting a user's access to selected properties.

Owner-facing access to documented property, booking or financial information.

Documented native mobile app availability; responsive website separate.

A documented API for external developers; channel API connections alone do not establish this.

Who may use the developer API and subscription, approval or access restrictions.

Documented outbound event notifications for external integrations.

Officially documented Zapier integration, with triggers/actions or plan conditions.

Documented portability of product data beyond calendar feeds; identify datasets and formats.

Documented onboarding assistance and whether optional or separately paid.

Documented assistance or tools for importing data from another system.

Public documentation or help resources; availability is not support-quality proof.

Documented support by email and any tier restrictions; no response-time inference.

Documented live or in-app support chat; distinguish AI bot/self-service.

Documented support by telephone and any tier or geography restrictions.

Versions represented by the captured public machine-readable schemas; not a runtime compatibility guarantee.

Security schemes declared in the captured schemas; API authorization and plan eligibility remain separate.

An explicit API operation retrieves property records.

An explicit API operation retrieves reservation or booking records.

An explicit API operation creates a reservation or booking; not proof of an equivalent user-interface flow.

An explicit API operation modifies reservation fields; specify field and channel limits.

An explicit guest read operation or documented guest data included in a reservation response; distinguish these forms.

An explicit operation updates guest records, rather than merely booking contact fields.

An explicit API operation reads guest messages or message-thread details.

An explicit API operation adds or sends guest messages; access restrictions remain separate.

An explicit rate read operation or nightly price fields in a calendar response.

An explicit API operation writes nightly rates; distinguish from rate calculation.

An explicit API operation retrieves date availability or calendar nights.

An explicit operation retrieves actual payment records; payment settings and payment-link generation do not establish this.

An explicit API operation retrieves refund records; no ability to issue refunds inferred.

An explicit API operation retrieves property-owner records.

Explicit API field-definition/value operations or documented reservation enrichment resources; specify differences.

Explicit API operations list, create or remove webhook subscriptions; outbound webhook documentation alone does not establish management endpoints.

A declared HTTP 429 response or explicit throttle condition in captured machine-readable contracts; numeric limits require separate evidence.

Documented parameters that page reservation collections, including declared defaults or maximums.