How a module is packaged
A single domain ships as a small family of packages:@voyant-travel/<domain>is the headless core: Drizzle schema, services, and HTTP routes.@voyant-travel/<domain>-contractsdescribes the wire types shared between server and client.@voyant-travel/<domain>-reactprovides hooks, clients, query keys, view-model helpers, and reusable components for that domain.
@voyant-travel/bookings, @voyant-travel/bookings-contracts, and @voyant-travel/bookings-react.
Selling and sourcing
| Module | What it owns |
|---|---|
| catalog | The normalized sellable catalog and the projection that interleaves operated and sourced inventory. |
| inventory | Availability rules, slots, closeouts, allotments, and capacity. |
| commerce | Pricing, the cost, rate, and price distinction, markets, FX, promotions, and sellability. |
| distribution | Channels, commission rules, channel push, reconciliation, and settlement. |
Sales and relationships
| Module | What it owns |
|---|---|
| relationships | The CRM core: people, organizations, contact points, and addresses. |
| quotes | The sales pipeline: quotes, quote versions, stages, and activities. |
Commitment and operations
| Module | What it owns |
|---|---|
| bookings | The durable first-party commitment: bookings, items, allocations, fulfillments, and provenance. |
| trips | Trip envelopes that group component bookings into one customer-facing itinerary. |
| operations | Ground operations, dispatches, resources, and resource holds. |
Money and compliance
| Module | What it owns |
|---|---|
| finance | Invoices, credit notes, payments, payment schedules, guarantees, and collection plans. |
| legal | Contracts, contract templates, signatures, policies, and policy acceptances. |
| notifications | Templated notifications and multi-channel delivery. |
Travel verticals
| Module | What it owns |
|---|---|
| cruises | Cruise catalog, sailings, cabin categories, and itinerary modeling. |
| flights | Flight search, pricing, booking, and order management. |
| accommodations | Accommodation as catalog inventory for resale, packaging, and trip composition. |
| charters | Charter operations and inventory. |
Platform packages
These are not domain modules, but the runtime and surfaces everything builds on:@voyant-travel/core, @voyant-travel/db, @voyant-travel/hono, @voyant-travel/auth, @voyant-travel/storage, @voyant-travel/i18n, the storefront, and the admin shell. There are also supporting modules such as catalog-authoring, identity, and octo (OCTO-standard connectivity for tours and activities).
Each headless module has matching
-contracts and -react packages where a UI surface exists. The tables list the core module name; install the family that fits your app.Next steps
How modules work
The anatomy of a module, isolation, and custom modules.
Links
How modules relate without coupling.
Data models
How module schemas are authored.
Glossary
The vocabulary these modules share.