Skip to main content
@voyant-travel/accommodations holds the accommodation resale contracts for Voyant. It is for OTAs, tour operators, and DMCs selling lodging as catalog inventory or as a component of a larger trip. It is not a hotel-operations or property-management surface. The retained scope is sourced lodging content, room options, board basis, rate plans, payment-policy lookup, the booking-draft shape, and the catalog projection. That is everything a reseller, packager, or trip operator needs to sell a stay and nothing a hotel needs to run its own front desk.

​
The resale boundary

This boundary is the single most important thing to understand about the module, and it shapes the package, routes, UI, and documentation. Voyant targets three implementation scenarios: OTAs, tour operators, and DMCs. Accommodation is in scope for all three, as long as the operator is acting as a reseller, packager, or trip operator. What is out of scope is a hotel, resort, or property manager using Voyant as its property-management or hotel-operations system. Put plainly:
  • In scope: selling a stay. Sourced accommodation catalog entries (from bedbanks, GDSs, channel managers, direct supplier APIs, Voyant Connect, or CSV imports), lodging content shown in search and storefront pages, room and unit options needed for resale (occupancy, board basis, rate plan, cancellation policy, supplier reference data), accommodation components inside products and packages and FIT itineraries and DMC programs and cruise extensions, rooming lists and shared-room grouping, and the supplier, channel, finance, and document flows that support reselling lodging.
  • Out of scope: operating a hotel. A staff workspace for managing a property’s own rooms, PMS-style room-unit and rate-grid management, housekeeping, room-maintenance blocks, room-unit status events, folios, room moves, in-stay service posting, and any documentation or navigation that implies a hotel logs into Voyant to run its property.
An Accommodation Location is a Place used to locate lodging content or a stay for resale. It is not a hotel, PMS, or property-operations record.

​
Key concepts

These terms come from the shared glossary.
  • Accommodation as catalog inventory. Lodging shows up as a Catalog Item, the normalized discovery and booking read model. For sourced lodging it resolves to Sourced Inventory reached through an Inventory Source; the operator sells it but does not operate it.
  • Packaging and trip composition. An Accommodation Component is a lodging component sold or arranged inside a Product, package, itinerary, cruise extension, or sourced catalog item. A Composed FIT Trip can assemble a stay alongside a product, flight, transfer, or cruise as independent commitments under one Trip Envelope.
  • Stay Component. A Stay Component is a date-range accommodation line within a Product, Quote Version, Booking, or sourced Catalog Item. It is the unit you add to an itinerary, not a hotel reservation record.
  • Room Option. A Room Option is a bookable accommodation option for resale or trip composition, usually carrying occupancy and board or rate choices. (Avoid “room unit”, which implies physical property operations.)
  • Rate Plan. A Rate Plan is a resale and commercial price and policy choice, usually from a Supplier or Inventory Source. It is the resale tariff, distinct from Cost (what we pay), Rate (the supplier’s per-unit tariff), and Price (what the customer sees).
  • Board Basis. A Board Basis is the included-meals tier for an accommodation component: room-only, breakfast, half-board, full-board, or all-inclusive.

​
What it owns

  • Sourced accommodation content contracts: the lodging shape shown in catalog search, storefront pages, offers, quotes, bookings, and snapshots.
  • Room option, rate plan, and board basis contracts, including occupancy and the cancellation and payment-policy lookup needed to resell a stay.
  • The booking-draft shape for accommodation lines and the catalog projection that interleaves sourced lodging with owned inventory.
  • Supplier and external-reference contracts that let sourced accommodation carry the data a reseller needs to fulfill and reconcile.
What it does not own, by design: room-unit management, housekeeping, maintenance, folios, in-stay operations, or any first-party hotel-staff workflow. Those are explicitly out of the resale boundary.

​
Working with it

Because accommodation is modeled as resale inventory and trip composition rather than a standalone operations product, you work with it through catalog, product composition, the booking journey, storefront, and supplier surfaces. The accommodations package supplies the shared resale contracts those surfaces consume.

​
Compose a stay into a trip

A stay enters an itinerary as a date-range component carrying its room option, board basis, and rate plan. Conceptually: 
import type { StayComponent, RoomOption, RatePlan } from "@voyant-travel/accommodations"

const stay: StayComponent = {
  accommodationLocationId, // a Place reference for where the stay happens
  checkIn: "2026-08-04",
  checkOut: "2026-08-09",
  roomOption: {
    code: "DBL-SEA",
    occupancy: { adults: 2 },
    boardBasis: "half_board",
  } satisfies RoomOption,
  ratePlan: {
    supplierRef, // the inventory source the rate came from
    cancellationPolicyId,
  } satisfies RatePlan,
}

​
Source lodging as catalog inventory

Sourced accommodation arrives through an inventory source (a bedbank, channel manager, direct supplier API, Connect, or a CSV import), surfaces as a catalog item in search and storefront, and resolves to a stay component when added to a quote, package, or booking. The operator resells it; the upstream operates the property. The accommodation contracts describe the wire shape, the room options, and the rate plans the projection and booking draft consume.

​
Frame the work correctly

When you touch a surface that handles lodging, frame it as resale, sourced inventory, or trip-component capability. Use accommodation vocabulary (accommodation, lodging, hotel content, room option, board basis, rate plan, stay component, accommodation booking line, sourced accommodation, accommodation location). Reserve hotel-operations vocabulary (housekeeping, room-unit status, folio, PMS, property operations) for legacy or explicitly out-of-scope material only.
  • catalog. Sourced accommodation is a catalog item; the catalog projection interleaves it with owned inventory for search and storefront.
  • products and trips. An accommodation component lives inside a Product, package, FIT itinerary, DMC program, or pre/post-cruise extension; a Trip Envelope can group an independently committed stay as a sibling component booking.
  • bookings. Accommodation booking lines, rooming lists, shared-room grouping, and room assignment are booking-side data, supported as resale requirements rather than property operations.
  • suppliers and distribution. Sourced lodging carries supplier and external-reference data; channel, distribution, and reconciliation flows support reselling it.
  • finance and legal. Rate plans reference cancellation and payment policies; checkout, invoicing, and documents flow through finance and legal as for any resold line.
  • Connect. Voyant Connect is one of the inventory sources for sourced accommodation. Connect supplies the catalog content the resale contracts describe; see the Connect SDK.

​
React package

Accommodations has no dedicated @voyant-travel/accommodations-react package. Accommodation surfaces are rendered through the catalog, storefront, and booking-journey UI rather than a standalone accommodation operations console, which keeps the resale boundary intact (there is no hotel-staff workspace to ship a UI for). Render lodging content, room options, and stay components through the catalog and storefront React tiers.

​
Next steps

Cruises

Cruise extensions reuse accommodation components.

Connect SDK

Sourcing accommodation content through Connect.

Modules overview

How accommodation composes into trips.

Glossary

Stay component, room option, rate plan, and board basis.