Storefront

The storefront is Voyant’s customer-facing surface. It is the discovery and booking experience a traveler interacts with: browsing the catalog, viewing a product or departure, previewing prices, and moving through a booking session to checkout. It is a first-class part of the framework rather than a loose collection of public routes. The shared storefront contract is owned by the framework, while the final storefront application is owned by your starter, so you control branding, layout, and UX while building on a stable public contract.

​

What the storefront covers

• Catalog browsing across owned and sourced inventory.
• Departure and product detail pages.
• Pricing preview and sellability resolution.
• Booking-session flows that lead to checkout.
• Customer-facing itinerary reads and self-service.

​

The public API boundary

The HTTP transport draws a clear line between staff and customer surfaces:

• /v1/admin/* serves staff and operator surfaces.
• /v1/public/* serves external, customer-facing surfaces.

The storefront runs against /v1/public/*. Public contracts are kept separate from admin CRUD semantics: the public surface exposes only what a customer should see and do, with its own request and response shapes, rather than reusing internal admin endpoints.

​

Packages

The customer experience is assembled from @voyant-travel/storefront and @voyant-travel/storefront-react, with @voyant-travel/storefront-sdk available for building a custom storefront against the public contract. The catalog projection that powers discovery is produced by the catalog module and can be enriched with Connect sourced inventory.

​

Checkout

Checkout UI is provided through the finance React family under @voyant-travel/finance-react/checkout-ui, so payment collection composes with the storefront booking session and the finance module’s payment schedules and sessions.

​

Next steps