Build, price and book tour packages in Odoo — itineraries, sub-bookings, per-pax pricing and auto agent commissions. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $499.00 USD; request a quote for a scoped proposal.
Manifeste de l'app
Conçu autour de votre flux de travail
Build, price and book tour packages in Odoo — itineraries, sub-bookings, per-pax pricing and auto agent commissions.
Aucune configuration à faire vous-même — une app fonctionnelle conçue, installée et prise en charge par ECOSIRE.
Commencez par un prix de développement unique. Nous cadrons le projet avec vous au lancement.
ECOSIRE la développe, la configure et l'installe sur votre Odoo.
Vous êtes en ligne en 2–4 semaines environ, avec une période d’assistance après le lancement.
Tour & Tour-Package Management is a build-to-order Odoo application that ECOSIRE designs, develops, installs and supports for tour operators and destination management companies (DMCs) who sell packaged tours rather than one-off, quote-per-trip travel arrangements. This is not an instant apps.odoo.com download — it is a net-new module engineered for your Odoo 17, 18 or 19 database (Community or Enterprise), shaped around how your operation actually assembles, prices and fulfils tours, then delivered in roughly 2–4 weeks.
At its core sits a new tour.package model that lets your product team compose a sellable package from reusable building blocks: a day-by-day itinerary, inclusions and exclusions, and linked sub-bookings for hotels, flights, ground transport and visas. Each package carries a per-pax pricing engine implemented as @api.depends compute fields, so adult/child/infant rates, seasonal price lists, optional extras and travel insurance roll up into a live, transparent total instead of a spreadsheet nobody trusts. Because everything is a real Odoo model, your package catalogue is filterable, reportable and translatable, and it plugs straight into Sales, Invoicing and Accounting.
The booking lifecycle is modelled end to end. A tour.booking record captures the lead passenger, pax composition and chosen departure, generates a confirmable itinerary, then flows into a native Odoo sale order and invoice with payment tracking, deposit and balance stages. Agents and sub-agents are first-class contacts with their own commission rules, so commission accrues automatically on confirmation via automated actions — no month-end reconciliation guesswork. QWeb reports produce branded booking vouchers, itineraries and passenger manifests, and a documented XML-RPC / JSON-RPC surface lets your website, OTA feeds or channel manager create and read bookings programmatically.
Security is designed in, not bolted on: ir.model.access.csv grants role-appropriate access (reservations agent, operations, finance, manager) and record rules scope agents to their own bookings and companies to their own data in multi-company setups. Everything ships as clean, upgrade-safe module code with a proper __manifest__.py, migration-friendly structure and no core hacks — so your database stays maintainable across future Odoo upgrades. ECOSIRE handles requirements, build, data migration where needed, UAT, go-live and a post-launch support window.
Assembles and prices packaged tours and needs a single catalogue where itineraries, inclusions and per-pax margins are transparent and reusable across seasons — not rebuilt in a spreadsheet for every departure.
Takes enquiries and books passengers fast, needs the per-pax total, extras and insurance to compute automatically, and wants the booking to flow straight into a quote, invoice and voucher without re-keying.
Tracks deposits, balances and payments against each booking and needs agent commissions to accrue automatically on confirmation so month-end reconciliation is a review, not a rebuild.
Manages the hotel, transport and visa sub-bookings behind each package and needs manifests, rooming lists and departure capacity visible in one place.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Fits how packaged tours are actually built and priced | Built around your itineraries, sub-bookings and per-pax rules | Possible but you specify and maintain everything yourself | Generic assumptions; often forces your process to fit the app | |
| Per-pax pricing with extras, insurance and seasonal price lists | Compute fields (`@api.depends`) + Odoo price lists, live totals | Depends entirely on your build effort | Prise en charge partielle | |
| Automatic agent commission accrual on confirmation | Automated actions post commission per configured rule | Must be designed and coded from scratch | Prise en charge partielle | |
| Hotel / flight / transport / visa sub-bookings linked to a package | Modelled as related records with status and cost | Buildable with significant modelling work | Prise en charge partielle | |
| Branded vouchers, itineraries and manifests | QWeb PDF templates styled to your brand | Build your own QWeb templates | Prise en charge partielle | |
| Role-based security and multi-company isolation | `ir.model.access.csv` + record rules per role | Your responsibility to define correctly | Prise en charge partielle | |
| Booking-to-invoice with deposit and payment tracking | Native sale order + invoice flow wired into the booking | Integration work required | Prise en charge partielle | |
| Upgrade-safe, no core hacks, supported across versions | Clean module + documented upgrade path + support window | Depends on your team's discipline | Varies by vendor; may lag Odoo releases | |
| API for website / OTA / channel-manager integration | Documented XML-RPC / JSON-RPC endpoints | You expose and document it yourself | Prise en charge partielle |
This is a build-to-order module, not an instant apps.odoo.com download. After a short requirements call, ECOSIRE builds, installs and tests the module on your database. Typical lead time is 2–4 weeks depending on scope, integrations and data migration. You receive staging access for UAT before we go live on production.
Every build includes a post-launch support window covering bug fixes and configuration guidance. We deliver clean, upgrade-safe module code (no core hacks) with a documented upgrade path, so the module carries forward across future Odoo versions. Ongoing support and enhancement retainers are available if you want us to keep evolving it.
Odoo 17, 18 and 19, on both Community and Enterprise. The module is built against your target version so it uses the correct ORM, view and reporting APIs for that release. Tell us your version and edition and we build to match.
Pricing is implemented with Odoo compute fields (`@api.depends`) that combine adult/child/infant rates, optional extras and travel insurance into a live package total. Seasonal and departure-based rates are driven by Odoo price lists, so peak and off-season pricing applies automatically without manual overrides.
Agents and sub-agents are Odoo contacts with configurable commission rules (per agent, package or tier). When a booking is confirmed, an automated action accrues the commission and records it against the agent, giving finance a clear ledger to review and pay out — no manual month-end calculation.
Yes. The module exposes a documented XML-RPC / JSON-RPC surface so external systems — your website, an OTA feed or a channel manager — can create and read bookings programmatically. We scope the exact integration points during requirements and document them for your developers.
A travel-agency flow quotes each trip on request. This module is for operators who sell repeatable packaged tours: reusable itineraries, fixed departures, per-pax pricing and capacity. If you need per-request quotations instead, ask us about our travel-agency management module — or we can combine both.
Build, price and book tour packages in Odoo — itineraries, sub-bookings, per-pax pricing and auto agent commissions.