示意预览Build, price and book tour packages in Odoo
— itineraries, sub-bookings, per-pax pricing and auto agent commissions.
什么是 Tour & Tour-Package Management？
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 $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
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 one working week.
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.
你得到什么
- The complete custom Odoo module source (models, views, security, reports) with a proper `__manifest__.py`, delivered to your repository
- Installation and configuration on your Odoo 17, 18 or 19 database (staging first, then production), including agents, commission rules and price lists
- QWeb report templates for vouchers, itineraries and manifests, styled with your branding
- Configured `ir.model.access.csv` roles and record rules mapped to your reservations, operations, finance and manager teams
- Technical and end-user documentation covering the data model, booking workflow, pricing logic and the XML-RPC / JSON-RPC API
- A live training session (recorded) for agents, operations and finance staff on running the booking-to-invoice cycle
- Data migration of existing packages, agents and open bookings from spreadsheets or your legacy system where applicable
- A post-launch support window with bug fixes and guidance, plus a documented upgrade path for future Odoo versions
这是给谁的
Tour Operator Owner / Product Manager
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.
Reservations & Sales Agent
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.
Finance / Accounts Controller
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.
DMC Operations Coordinator
Manages the hotel, transport and visa sub-bookings behind each package and needs manifests, rooming lists and departure capacity visible in one place.
Tour & Tour-Package Management 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| 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 | 部分支持 | 部分支持 |
| Automatic agent commission accrual on confirmation | Automated actions post commission per configured rule | Must be designed and coded from scratch | 部分支持 | 不包括在内 |
| Hotel / flight / transport / visa sub-bookings linked to a package | Modelled as related records with status and cost | Buildable with significant modelling work | 部分支持 | 不包括在内 |
| Branded vouchers, itineraries and manifests | QWeb PDF templates styled to your brand | Build your own QWeb templates | 部分支持 | 部分支持 |
| Role-based security and multi-company isolation | `ir.model.access.csv` + record rules per role | Your responsibility to define correctly | 部分支持 | 包含 |
| Booking-to-invoice with deposit and payment tracking | Native sale order + invoice flow wired into the booking | Integration work required | 部分支持 | 部分支持 |
| 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 | 部分支持 | 部分支持 |
关于Tour & Tour-Package Management的常见问题
How long does delivery take, and is this an instant download?
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 one working week depending on scope, integrations and data migration. You receive staging access for UAT before we go live on production.
What support and updates are included after launch?
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.
Which Odoo versions and editions does it support?
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.
How is per-pax pricing calculated, and can we handle seasons and extras?
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.
How does agent commission work?
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.
Can it connect to our website, OTA or channel manager?
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.
How is this different from a travel-agency RFQ system?
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.
相关模块
Tour & Tour-Package Management
Build, price and book tour packages in Odoo — itineraries, sub-bookings, per-pax pricing and auto agent commissions.
- Tour package builder on a dedicated `tour.package` model with reusable day-by-day itinerary lines, inclusions and exclusions
- Hotel, flight, ground-transport and visa sub-bookings linked to each package as related records with their own status and cost
- Per-pax pricing engine using `@api.depends` compute fields for adult / child / infant rates that roll up to a live package total
- Seasonal and departure-based pricing driven by Odoo price lists so peak, shoulder and off-season rates apply automatically