> ## Documentation Index
> Fetch the complete documentation index at: https://voyant.travel/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> The canonical travel vocabulary shared across every Voyant module. Use these terms precisely and consistently.

Voyant models the travel business with a precise, shared vocabulary. Every module, API, and SDK uses these terms the same way. Getting the language right keeps the domain clear and prevents subtle modeling mistakes, so this page is worth reading before you design anything on top of the platform.

The terms below are the ones you will meet most often. They are grouped by subdomain. Where a word is commonly misused, the precise definition makes the distinction explicit.

## People and organizations

<ResponseField name="Person" type="CRM identity">
  An individual contact known to the operator. This is the canonical CRM record. Avoid "customer", "client", or "contact" as entity names.
</ResponseField>

<ResponseField name="Organization" type="legal entity">
  A company or legal entity: a buyer, supplier, agency, or other counterparty.
</ResponseField>

<ResponseField name="Traveler" type="person on a booking">
  A person who actually travels on a booking. Carries a category (adult, child, infant, senior) and personally identifiable information. Use this rather than "guest", "pax", or "passenger".
</ResponseField>

<ResponseField name="Participant" type="role on a record">
  A role-bearer on a quote, booking, program, or booking item: traveler, booker, decision-maker, or finance contact.
</ResponseField>

<ResponseField name="Operator" type="commercial principal">
  The organization accountable for commercial control and, when applicable, operational fulfillment. An operator can be both an operating party for some inventory and a reseller for other inventory at the same time.
</ResponseField>

<ResponseField name="Supplier" type="vendor">
  An operational vendor contracted directly to deliver owned or assembled products.
</ResponseField>

<ResponseField name="Channel" type="distribution counterparty">
  A distribution counterparty that sells the operator's inventory: direct, OTA, affiliate, reseller, marketplace, or API partner.
</ResponseField>

## Catalog: what you sell

<ResponseField name="Product" type="sellable offering">
  A sellable travel offering with a booking mode (date, date-time, open, stay, transfer, itinerary), a capacity mode, and visibility. Canonical, module-owned truth. Avoid collapsing "tour", "experience", or "package" into ambiguous terms.
</ResponseField>

<ResponseField name="Product Option" type="variant">
  A configurable variant of a product, such as "English Guided" or "Private Group". Composed of option units.
</ResponseField>

<ResponseField name="Option Unit" type="pricing dimension">
  A pricing or age dimension within an option, such as "Adult", "Child 3 to 11", or "Group 1 to 4".
</ResponseField>

<ResponseField name="Catalog Item" type="discovery projection">
  A normalized, sellable discovery and booking record used by admin search, the storefront, the composer, and CMS sync, regardless of where the inventory comes from. A catalog item may resolve to a local product or to sourced inventory.
</ResponseField>

<ResponseField name="Operated Inventory" type="owned">
  Inventory the operator owns or manages operationally.
</ResponseField>

<ResponseField name="Sourced Inventory" type="resold">
  Inventory the operator sells but does not operate, reached through an inventory source such as Connect or a GDS.
</ResponseField>

## Sales pipeline

<ResponseField name="Proposal" type="sales pursuit">
  A tracked travel sales pursuit with a person or organization. Moves through stages, owns value, participants, and activities, and produces one or more Proposal Versions. Use "Proposal", not "opportunity" or "deal".
</ResponseField>

<ResponseField name="Proposal Version" type="immutable revision">
  An immutable proposal revision or alternative sent to the client. Freezes a trip envelope snapshot, pricing, validity, and decision state. Editing a sent version creates a new version.
</ResponseField>

<ResponseField name="Pipeline" type="stage set">
  An ordered set of stages a Proposal moves through, such as Qualified, Proposal, Negotiation.
</ResponseField>

<ResponseField name="Quote" type="priced result">
  An immutable, expiring, server-produced price and terms result for an exact Booking Session revision. A Quote is a **pricing artifact**, not a sales pursuit, and is distinct from a Proposal Version.
</ResponseField>

## Commitment chain

There are two ladders.

**Reusable catalog booking:** Product → Booking Session → Quote + optional Hold → Commit → Booking → Fulfillment.

**Bespoke travel sales:** Proposal → accepted Proposal Version → Booking Session → Quote + optional Hold → Commit → Booking / Component Booking → Fulfillment.

Each step hardens the commitment. Accepting a Proposal Version records the customer decision and seeds reservation; it does not by itself confirm suppliers or create a Booking.

<ResponseField name="Booking" type="durable commitment">
  The durable, first-party commitment and customer-safe operational record. Holds travelers, booking items, allocations, fulfillments, redemptions, provenance, and state. Use "Booking", not "reservation" or "order".
</ResponseField>

<ResponseField name="Booking Item" type="line item">
  A single line on a booking: a unit, service, extra, fee, tax, discount, accommodation, or transport line.
</ResponseField>

<ResponseField name="Allocation" type="capacity hold">
  A capacity hold against a slot, pickup point, or resource. Moves through held, then confirmed, then fulfilled.
</ResponseField>

<ResponseField name="Hold" type="temporary claim">
  A temporary, time-limited claim on inventory before a booking is confirmed. It expires.
</ResponseField>

<ResponseField name="Trip Envelope" type="customer-facing itinerary">
  A customer-facing aggregate that groups one or more component bookings into a single itinerary, checkout, support, document, and cancellation experience. Not necessarily one booking.
</ResponseField>

## Inventory and availability

<ResponseField name="Availability Rule" type="recurrence">
  A recurring capacity definition (RFC 5545 recurrence) that generates concrete slots.
</ResponseField>

<ResponseField name="Slot" type="dated unit">
  A concrete dated inventory unit with remaining capacity.
</ResponseField>

<ResponseField name="Allotment" type="channel block">
  A block of inventory reserved for a specific channel.
</ResponseField>

<ResponseField name="Sellability" type="resolved buyability">
  The resolved answer to "is this product buyable now for this date, party size, market, and channel?" It combines availability, pricing, allotments, and policies.
</ResponseField>

## Money

<ResponseField name="Cost, Rate, and Price" type="three distinct amounts">
  These are never interchangeable, even when numerically equal. **Cost** is what you pay a supplier. **Rate** is the supplier's per-unit tariff (per person, per night, per vehicle, flat). **Price** is the customer-facing sell amount.
</ResponseField>

<ResponseField name="Invoice" type="billing document">
  A billing document issued to a payer. Lifecycle: draft, sent, partially paid or paid, overdue, void.
</ResponseField>

<ResponseField name="Payment Schedule" type="installment plan">
  An installment plan attached to a booking (deposit, installment, balance, hold) with due dates.
</ResponseField>

## Fulfillment

<ResponseField name="Fulfillment" type="artifact issuance">
  Issuance of a deliverable artifact such as a voucher, ticket, PDF, QR, or barcode for a booking item.
</ResponseField>

<ResponseField name="Redemption" type="point of service">
  The act of consuming a fulfillment at the point of service, by scan or manual check-in.
</ResponseField>

## Lifecycle verbs

These verbs mean different things in different domains. Keep them distinct.

| Verb          | Meaning                                                            |
| ------------- | ------------------------------------------------------------------ |
| **Hold**      | Place a time-limited claim on inventory.                           |
| **Confirm**   | Promote from draft or held to a binding state.                     |
| **Issue**     | Produce a deliverable artifact (voucher, invoice, contract).       |
| **Fulfill**   | Mark operational delivery complete.                                |
| **Deliver**   | Push an issued artifact to the recipient over a channel.           |
| **Accept**    | Record that the client chose a Proposal Version or accepted terms. |
| **Cancel**    | Operationally reverse a commitment (booking, allocation).          |
| **Void**      | Financially reverse a document (invoice, payment).                 |
| **Close**     | End a Proposal with an outcome (won, lost, archived).              |
| **Reconcile** | Compare expected against actual and emit issues.                   |

<Note>
  This is a curated subset. The platform repository ships the full ubiquitous language reference covering MICE and group travel, distribution, legal and compliance, and ground operations.
</Note>