Volāre has its own vocabulary — part travel industry, part internal names. Keep this page open
during your first weeks. Each entry says what the thing is in one or two sentences and links to
the page that explains it properly.
| Term |
Meaning |
| Web |
byvolare.com, the public online travel agency where customers browse and buy trips. Code in frontend/ (Astro). See Frontend Overview. |
| Arkana |
The back office at arkana.byvolare.com — “the brain”. Staff configure everything here, and it serves the REST API the Web reads. Code in backend/ (Laravel + Filament). Locally it lives at http://localhost/admin. See Arkana Overview. |
| Market |
A country storefront (for example ES = Spain) with its own locales, currency, margins and contact details. Almost everything the customer sees is market-scoped. See Markets. |
| Term |
Meaning |
| Supplier / DMC |
A local company (Destination Management Company) that provides the ground services: hotels, activities, transfers. See Suppliers. |
Tour (SupplierTour) |
The starting point of every trip: a supplier’s package with its day-by-day services. Created under Suppliers › Tours. |
| Product Template |
The master content of a trip (route, itinerary, duration). Owned 1:1 by a Tour. See Products System. |
| Product by Market (PBM) |
The version of a template sold in one market, with translations and flight configuration. SKU looks like ES-138-10-ES1. See Products by Market. |
| Offer |
A bookable package for a specific departure date: flights + land part, with a calculated price and a status. See Offers. |
| Land price / land cost |
What the supplier charges for the ground part of the trip (everything except flights and insurance). |
| Allotment |
The number of units (rooms, seats) a supplier guarantees Volāre per date and rate. Bookings consume it. See Allotment. |
| Stop Sale |
A date window in which a tour cannot be sold. Offers inside it show as not bookable. See Stop Sales. |
| Blackout |
Supplier dates during which a trip cannot run; offers whose whole trip falls into one are rejected. See Suppliers. |
| Last Seats |
Discounted departures with a limited seat quota (“Últimas plazas” on the Web). See Last Seats. |
| Day-by-day itinerary |
The per-day module on the product page (city, highlights, activities). It can be imported from a supplier PDF with AI and switched on per product. See Products in Arkana. |
| POI |
Point of Interest: a shared, searchable location (city, landmark) used in itineraries. See POI System. |
| Term |
Meaning |
| AerTicket |
The flight consolidator Volāre uses to search, book and issue airline tickets. See AerTicket. |
| Leg |
One flight segment of a trip (for example the outbound international flight, or a domestic hop inside the destination). |
| Domestic leg |
A flight inside the destination country. It must fall inside the tour’s departure window. |
| Flight cache |
Pre-fetched flight prices stored so the Web can show prices without calling AerTicket live. See Dynamic Flight Cache. |
| Reference pax |
Cached flight prices are stored for a reference group of 2 passengers; per-person prices divide by that, not by the real party size. |
| L2B (Look-to-Book) |
The ratio of flight searches to bookings that the AerTicket contract caps. See L2B Tracking. |
| Issue / Void |
Issuing turns a flight booking into a real ticket. Voiding cancels it shortly after, usually without cost. |
| Term |
Meaning |
| Lead |
A potential customer who left their details but has not bought yet. Synced to Pipedrive. See Leads API. |
| Booking |
A purchased trip: passengers, flights, land services and payments. See Booking Lifecycle. |
| Pax |
Passengers (travel-industry shorthand). |
| Checkout |
The Web flow from choosing an offer to paying. See Checkout Flow. |
| Trip page |
The customer’s private page for a booked trip. See Trip Access. |
| Trips to Deliver |
The supplier-facing list of bookings they must deliver, without customer pricing. See Trips to Deliver. |
| Margin on sale |
Volāre’s margin is expressed as a percentage of the sale price. Prices are always whole euros. See Financial Model. |
| Term |
Meaning |
| CMS |
The editorial pages served to the Web (home, countries, collections, legal pages), managed in Arkana. See CMS in Arkana. |
| TCAI / Rephrase |
AI rewriting of supplier descriptions into the Volāre brand voice, reviewed by a person before saving. See TCAI Content Management. |
| Arkana MCP |
An MCP server that lets Claude read Arkana data (bookings, products, tours) with your own login. See Arkana MCP. |
| Analytics MCP |
An MCP gateway to Google Analytics, Clarity and read-only database data. See Analytics MCP. |
| Term |
Meaning |
| infra-volare |
The separate repository that defines all AWS infrastructure and runs deployments. See Infrastructure Overview. |
staging-1 / production-1 |
The two application environments, each in its own AWS account in us-east-2. *-shared folders hold their network and database. See Infrastructure Overview. |
| Hermes |
A self-hosted AI agent (NousResearch Hermes Agent) the team talks to; it can read Arkana through the Arkana MCP and is told about every deploy. See Hermes. |
| Twingate |
The zero-trust VPN that gives you private access to the VPC (database, Swagger, Telescope, health pages). See Networking and Access. |
| SSM |
AWS Systems Manager: Parameter Store holds every server’s .env, and Session Manager gives you a shell on a server. |
| api / front / ops-runner / hermes |
The four kinds of servers: api serves Arkana and the API, front serves byvolare.com, ops-runner runs queues, the scheduler and migrations, hermes runs the team’s AI agent. See Servers and Containers. |
| Sail |
Laravel’s Docker wrapper. Every PHP, Composer and Artisan command runs through ./vendor/bin/sail locally. See Installation. |