Most schools run transport on a patchwork of spreadsheets, a shared WhatsApp group and a filing cabinet of vehicle papers. Nobody can answer simple questions in one place: which students are on Route 4, is that bus over capacity, whose driving licence expires next month, and which families still owe transport fees this term. Odoo core gives you fleet for vehicle records and account for invoicing, but nothing connects a student to a stop, a stop to a seat, a seat to a bus, and that bus fare to a customer invoice. The moment you need per-stop pricing, seat-limit validation or a boarding roster, native Odoo runs out of road and you are back to manual reconciliation.

ECOSIRE builds Education Transport Management as a dedicated Odoo module (Odoo 17.0, 18.0 or 19.0, Community or Enterprise) that models the whole transport operation as first-class records. New models such as education.transport.route, education.transport.stop, education.transport.subscription and education.transport.trip sit on models.Model with proper @api.depends computes and constraints — for example a Python @api.constrains and stored compute that compares allocated seats against the vehicle's seating_capacity (read from fleet.vehicle) and blocks over-allocation before it happens. Each route holds ordered stops with pickup and drop timings and a per-stop fare; a student subscription links a contact to a route, a stop and a specific vehicle, and drives billing. Security is enforced with ir.model.access.csv plus record rules so a transport manager, an accountant and a class teacher each see only what their role permits, and everything is multi-company-aware where you need it.

Technically the module reuses Odoo's strengths rather than reinventing them. Vehicle capacity, insurance and registration documents, and service reminders come straight from fleet, surfaced as activity reminders via mail so a document about to expire raises a scheduled activity on the responsible user. Transport-fee billing is generated against account — subscriptions produce invoice lines per student per period at the correct per-stop fare, so transport revenue flows into your normal accounting and aged-receivable reports with no double entry. Trip rosters give drivers a per-trip student list and a simple boarding-attendance record, and a data-agnostic GPS webhook endpoint (a controller exposing a JSON route, alongside the standard XML-RPC/JSON-RPC API) accepts position pings from whatever tracker hardware you already run, logging vehicle location without locking you to one device vendor. Views are delivered as standard XML (with OWL/QWeb where an interactive widget or a printable roster report earns its keep), and a route-utilization and transport-revenue dashboard rolls it all up. Automated actions and mail-based notifications push route-change and delay alerts to parents by email or SMS.

Because this is build-to-order, nothing is downloaded and switched on the same afternoon — we scope it to your institution first. After a short scoping call we confirm the exact route structure, fee model, fleet size, notification channels and which Odoo version and edition you run, then build, test on a staging copy, and install against your database. Typical delivery is one working week from confirmed scope, and you receive the full source, documentation and a training session. Pricing starts from $999 (indicative, single-company base scope); multi-company or multi-branch group structures, deeper fee/localization rules, SMS-gateway and GPS-hardware integrations, and migration of existing student, route and vehicle data increase the quoted scope.