A build-to-order Odoo module that unifies student bus routing, hostel bed allocation, and their recurring billing inside your education ERP. ECOSIRE scopes, builds, installs, and supports it on Odoo 17, 18, or 19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo module that unifies student bus routing, hostel bed allocation, and their recurring billing inside your education ERP. ECOSIRE scopes, builds, installs, and supports it on Odoo 17, 18, or 19.
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
Schools and colleges that run their own transport fleet and boarding facilities usually end up managing two of their most operationally intense services in spreadsheets: which student is on which bus route and stop, who has paid this term's transport fee, which bed in which hostel block is free, and whose mess charges are outstanding. Odoo out of the box has no concept of a bus route, a stop, a hostel room, or a per-student recurring service fee. You can approximate pieces of it with generic sale.order lines and account.move invoices, but there is no model that ties a student to a route, a vehicle, a driver's compliance status, or a physical bed — so the day-to-day work (re-routing a stop, reassigning a bed at check-in, chasing an unpaid mess bill) falls back to manual tracking outside the system.
New `school.transport.route`, `school.transport.stop`, and `school.transport.registration` models with Many2one links from student partner to route, stop, and assigned vehicle
Per-student transport registration that generates recurring `account.move` invoices on your chosen fee cycle (monthly/term/annual) through the native accounting pipeline
`@api.depends` compute fields for live route capacity, registered-seat count, and per-stop passenger lists — no manual seat tallies
Vehicle and driver compliance records on the `fleet.vehicle` model: license expiry, fitness/registration certificate dates, and insurance renewal with `ir.cron` expiry alerts
Hostel hierarchy models — `school.hostel.block`, `.room`, and `.bed` — with One2many rollups and computed vacancy/occupancy flags
Bed-level allocation and check-in/check-out workflow (`school.hostel.allocation`) that prevents double-booking a bed via a SQL/constraint guard
ECOSIRE builds a dedicated module that adds these missing domain models to your Odoo. We define new models via models.Model — school.transport.route, school.transport.stop, fleet.vehicle extensions, school.transport.registration, school.hostel.block, school.hostel.room, school.hostel.bed, and school.hostel.allocation — each with proper relational fields (Many2one to the student partner and to the route/bed, One2many for a route's stops or a block's rooms). Fee amounts, occupancy counts, and vacancy flags are compute fields with @api.depends so a route's registered-seat count or a block's free-bed count is always live, never a stale manual tally. The registration and allocation records generate invoices through the standard account.move pipeline, so transport and mess/accommodation charges land in your existing accounting, reconcile against payments, and appear on the same customer statement as any other Odoo invoice.
Technically the build ships as a clean custom addon: a proper __manifest__.py declaring dependencies (typically base, contacts, account, and fleet), backend list/form/kanban and calendar views in XML (with OWL components where an interactive allocation board helps), access control in ir.model.access.csv, and multi-campus ir.rule record rules so a warden or transport coordinator only sees their own block or depot. QWeb reports produce the printable route manifests, bed-occupancy sheets, and fee-due statements your staff actually hand out. Automated actions (server actions on ir.cron or on record triggers) handle recurring work such as raising the next term's transport invoices or flagging a driver whose license or vehicle-fitness certificate is about to expire. Everything is reachable over Odoo's XML-RPC/JSON-RPC API, so a parent portal, a gate-security app, or an SMS gateway can read allocations and post attendance without touching the database directly.
Because this is build-to-order, you are not downloading a pre-packaged app from apps.odoo.com and hoping it fits. We start from a short scoping call, confirm exactly how your routes, fee cycles, hostel blocks, and compliance rules work, and build the module against your Odoo version (17.0, 18.0, or 19.0) and edition (Community or Enterprise — the module works on both; Enterprise-only features like the fleet dashboard or Studio integration are used only where you already have them). Typical delivery is 2–4 weeks from confirmed scope. We install it, run UAT on a staging copy of your database, and hand over the full git repository so you own the source outright.
Runs the daily route sheet, assigns students to buses and stops, and tracks driver license and vehicle fitness expiries. Needs live seat counts and a printable manifest per bus instead of a shared spreadsheet.
Allocates rooms and beds at intake, handles check-in/check-out, and monitors occupancy across blocks. Needs a bed-level board that blocks double-booking and shows real-time vacancies.
Bills transport, mess, and accommodation charges each cycle and chases outstanding balances. Needs these fees to flow into standard Odoo `account.move` invoices and the same customer statement as tuition.
Owns the Odoo instance and integrations. Needs a clean addon with proper access rules, record-rule multi-campus isolation, and an XML-RPC/JSON-RPC surface for the parent portal and gate app.
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden School Transport & Hostel Management modülünün ZIP dosyasını indirin.
ZIP'i sunucudaki Odoo özel eklentiler klasörünüze çıkarın (veya Uygulamalar > Odoo.sh / runbot'taki dosyadan yükle yoluyla yükleyin).
Geliştirici Modunu etkinleştirin, Uygulamalar'ı açın, Uygulama Listesini Güncelle'ye tıklayın, School Transport & Hostel Management'i arayın ve Yükle'ye basın.
Yeni menüyü açın, ECOSIRE lisans anahtarınızı yapıştırın, tüm harici kimlik bilgilerini (Shopify, Amazon, Stripe vb.) bağlayın ve kaydedin.
Yerleşik bağlantı testini çalıştırın, ilk 10 kaydınızı senkronize edin ve yinelenen cronu planlayın. Herhangi bir sorun olursa desteğe başvurun.
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Domain fit (routes, beds, fees) | Purpose-built models scoped to your exact routes, blocks, and fee cycles | Depends entirely on your in-house team's Odoo depth | Generic feature set; rarely matches your fee or campus structure | |
| Billing integration | Native `account.move` invoices on your chosen cycle, same statement as tuition | Buildable but often bolted on inconsistently | Varies; some keep fees in a separate ledger | |
| Compliance tracking | Driver license, fitness, and insurance expiry with `ir.cron` alerts | Only if explicitly specified and built | Often absent or basic date fields | |
| Multi-campus access control | `ir.rule` record rules isolate wardens/coordinators per block/depot | Requires careful in-house rule design | Usually global access, no per-campus scoping | |
| Source ownership | Full git repository handover — you own and can extend it | You own it, but you also carry all the build cost | Licensed/obfuscated; limited or no source access | |
| Delivery model | Scoped build in 2–4 weeks, installed and supported by us | Weeks to months depending on hiring and ramp-up | Instant download but no fit guarantee or support depth | |
| Version support | Built and tested for Odoo 17.0/18.0/19.0, Community or Enterprise | Whatever your team targets | Often lags new Odoo releases | |
| Post-go-live support | Defined support window plus optional upgrade/feature contracts | Internal team must maintain it | Ticket-based, often slow for niche needs |
No. This is a build-to-order module. ECOSIRE scopes it to how your routes, fee cycles, and hostel blocks actually work, then builds, installs, and supports it. You get the full source and git repository at handover — it is not a locked apps.odoo.com download.
Typical delivery is 2–4 weeks from confirmed scope. After the scoping call we agree the exact models, fee rules, and reports; the timeline depends on how many campuses, integrations (parent portal, SMS, gate scanner), and custom reports you need. We confirm a firm date before starting.
It works on both Community and Enterprise, and we build against Odoo 17.0, 18.0, or 19.0 to match your instance. Enterprise-only features (like the fleet dashboard or Studio) are used only where you already have them; the core transport and hostel logic runs fine on Community.
No, it is fully integrated. Registrations and allocations generate standard Odoo `account.move` invoices, so transport, mess, and accommodation charges reconcile against payments and appear on the same customer statement as tuition and other Odoo invoices. An `ir.cron` server action can raise the next cycle's invoices in one batch.
Every build includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full git repository, you can maintain it yourself or contract ECOSIRE for version upgrades (e.g. migrating from 17.0 to 18.0/19.0) and new features on request.
Yes. All models are exposed over Odoo's XML-RPC/JSON-RPC API, so a parent portal, an SMS gateway, or a gate-security scanner can read a student's route/bed assignment and write attendance or check-in events without direct database access. We can build those integrations as part of scope.
We develop and run UAT on a staging copy of your database with a documented test script, and we prepare a rollback plan before any production install. Access is controlled via `ir.model.access.csv` and multi-campus `ir.rule` record rules so staff only see their own block or depot.
A build-to-order Odoo module that unifies student bus routing, hostel bed allocation, and their recurring billing inside your education ERP. ECOSIRE scopes, builds, installs, and supports it on Odoo 17, 18, or 19.