Teams that run their day in Odoo hit a wall the moment their calendar lives in two places. Sales reps book on their phone, project leads schedule in a self-hosted groupware server, and executives live in a mainstream cloud calendar — yet Odoo's calendar.event records only know about what was created inside Odoo. Native Odoo ships a calendar app and, in some editions, a narrow connector to one large consumer provider, but there is no general-purpose, standards-based bridge to arbitrary CalDAV servers, no field-level control over what syncs, and no dependable handling of recurring events, attendee responses, or reschedules that originate outside Odoo. The result is double-booking, stale meeting rooms, and staff who quietly stop trusting the Odoo calendar altogether.

This is where a productized CalDAV Connector earns its keep. We build a dedicated Odoo module that speaks the CalDAV protocol (RFC 4791) and iCalendar (RFC 5545) directly, so it talks to standards-compliant calendar servers — self-hosted collaboration suites, open-source groupware, and the major cloud calendars that expose a CalDAV endpoint. Under the hood it introduces its own configuration models (built on models.Model) to store per-user account credentials, the mapped remote calendar collections, and a sync-state ledger of ETags and remote UIDs. The account secret is held in an encrypted field rather than plaintext, and access is scoped through ir.model.access.csv plus record rules so a user only ever sees and syncs their own linked calendars.

Technically, the two-way engine is driven by a scheduled ir.cron job with an optional on-save base.automation trigger for near-real-time pushes. Outbound, Odoo calendar.event changes are serialized to VEVENT and sent via CalDAV PUT/DELETE, keyed by a stable UID we persist on each event through a compute/@api.depends field so updates never create duplicates. Inbound, the connector performs an ETag-based REPORT sync-collection query, pulls only changed objects, and maps them back onto Odoo events — reconciling recurrence rules (RRULE), exceptions, attendee PARTSTAT, reminders, and timezone (VTIMEZONE) data. A conflict policy you choose during scoping (last-write-wins, Odoo-authoritative, or remote-authoritative per calendar) governs collisions, and every sync writes an audit line so failures are visible rather than silent. We expose a clean admin view (XML/OWL) for mapping calendars, a manual "sync now" action, and a log the JSON-RPC/XML-RPC API can also read for external monitoring. The module targets Odoo 17.0, 18.0, and 19.0, works on Community and Enterprise, and its __manifest__.py declares only the dependencies your edition actually needs.

Because this is build-to-order, nothing is downloaded off a shelf. After a short scoping call we confirm your target CalDAV servers, sync direction, conflict policy, field mapping, and Odoo version, then build the module against your exact environment, test it on a staging database with your real calendars, and install it in production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $299 (indicative, single-company base scope); additional CalDAV endpoints, multi-company routing, per-team calendar mapping, and deeper recurrence/attendee edge-case handling increase the quoted scope.