Tourism: get started with journeys and operations
Tourism separates the reusable trip definition from each dated departure and its field work. Start in Tourism Operations: prepare the journey and approved versions, plan a departure, then assign specific work to the people delivering it.
These guides describe the reviewed Odoo 20 Community source. Existing upgrade evidence covers a bounded compatibility qualification; it does not establish full business acceptance, live supplier connectivity or production readiness. No new runtime or complete browser acceptance test was performed for these guides. Odoo 19 behavior is outside this version scope.
Understand the records
| Record | Purpose |
|---|---|
| Journey | Reusable trip identity, linked sale product, trip kind and default time zone. |
| Itinerary Version | A numbered definition of ordered activities, places and times. Approved versions are retained and cannot be edited. |
| Offer Version | A numbered commercial definition with the journey's product, currency, allowed dates, validity note, inclusions and exclusions. Approval does not set a sale price or collect money. |
| Departure | A specific dated instance bound to a journey, itinerary and offer, with its own capacity, cutoff and route-review evidence. |
| Operations Assignment | A scheduled piece of field work for a guide, tour leader, driver or mechanic, with a separate acknowledgement, checklist and completion trail. |
Journey approval, Sales Open and assignment Completed describe different records. None alone proves that a supplier has accepted a reservation, a traveler has paid, or the whole trip is operationally ready.
1. Confirm the installed scope
Have the implementation owner confirm the Odoo 20 Community package and the addons installed for your business. The reviewed suite contains 14 product addons and a separate pilot-data addon; the pilot addon is not a prerequisite for these workflows.
The core Corvus Tourism Operations addon uses native CRM and Sales components. The separate field-operations addon adds Project, Employees and Fleet dependencies. Other addons extend commerce, compliance, supplier exchange, partner access, procurement, equipment, quality, intelligence, growth, distribution, sponsorship and connectivity. Their presence in the source does not mean every feature is installed, configured or qualified in your environment.
Expected result: the implementation owner identifies the installed scope and a place to validate your organization's roles and procedures before live use.
2. Assign access by responsibility
Ask the administrator to grant the appropriate Tourism role and allowed companies. Native Odoo permissions still apply to products, Sales, Employees, projects and other linked records.
| Role shown in access settings | Responsibility in these guides |
|---|---|
| Tourism Access — User | Read the Tourism records allowed by company and record access. |
| Tourism Access — Sales | Work with commercial links when native Sales access also permits. This is not journey-approval authority. |
| Tourism Operations — Operator | Plan departures and create or assign field work. |
| Tourism Operations — Manager | Includes Operator access and controls journey/version approvals and opening departure sales. |
| Tourism Operations — Field User | With the operations addon, work on assignments for the linked assignee; creation and cancellation remain with Operations. |
| Tourism Administration — Administrator | Configuration and permitted retained-record archiving. This role does not imply Manager or Operator. |
| Tourism Confidential Cost — Cost Manager | Separate access to confidential supplier-cost records; not a general operational role. |
Use ordinary assigned accounts for these procedures. A missing button can indicate a missing role or an invalid record state; do not infer permission from a menu being visible.
3. Prepare the minimum business data
For the scheduled-group starter flow, agree the active company, a reusable active sale product, currency, a valid time zone and a low-risk journey definition. Prepare itinerary titles, locations, ordered day/time intervals and a meaningful route-review summary. Destinations, Places and Routes can provide reusable references where your procedure needs them.
Before planning a departure, have approved itinerary and offer versions, intended dates, capacity, booking cutoff and a responsible route reviewer. Before field assignment, prepare the correct employee or contractor identity, its linked user where the person will work in Odoo, and a suitable checklist. Do not add real traveler data or connect providers merely to practice these guides.
Private and custom journeys require a matching qualified enquiry and additional offer bindings and deadlines. They are not covered by the scheduled-group starter procedure.
4. Use the workspaces in order
- Open Tourism Operations → Sales & Bookings → Journeys, Itinerary Versions and Offer Versions. Follow Prepare and approve journey versions.
- Open Operations → Departures. Follow Prepare a departure for sales to record its route review and reach the local Sales Open state.
- With the operations addon installed, open Field Operations → Assignments. Follow Assign and complete field work.
Overview depends on the installed dashboard extension and may not be available in a core-only installation. Other menus also depend on installed addons and access.
Fictional exercise
Use a fictional “Harbor Morning Walk” to discuss the handoffs: a Manager approves its itinerary and offer; an Operator prepares a dated departure and route review; a Manager opens sales; an Operator assigns an employee guide; the linked field user acknowledges and records the work.
The expected learning result is four distinct record states and clear responsibility for each handoff. This is a planning example, not a performed booking, provider commitment or completed-trip acceptance test.
Troubleshooting and limits
| Symptom | Check |
|---|---|
| Tourism menu or a workspace is missing | Installed addon, Tourism role, allowed company and linked model access. |
| An approval is unavailable | Manager role and the exact journey/version state. Administrator alone is not enough. |
| A product or person cannot be selected | Active status, company match and native Odoo permissions. Ask the responsible administrator to review legitimate access. |
| A displayed state appears to conflict with a real-world event | Check the relevant record and evidence. Local workflow state is not proof of live provider acceptance, payment or physical completion. |
Supplier availability/rates/inventory and broader release acceptance retain qualification gaps. Messaging, payments, procurement and provider integrations need their own configuration and acceptance; these guides do not authorize or demonstrate an external transaction. Validate the installed combination and your operating procedure before relying on it for live delivery.
If the troubleshooting checks do not resolve the blocker, prepare a support handoff with the version, installed addon, role, screen, affected record state, and exact redacted message. Describe the issue without traveler or customer records.