Coworking & Shared Workspace Management for Odoo

We build a dedicated Odoo module that models the coworking business natively. A new coworking.resource model (models.Model) represents every bookable asset — hot desks, dedicated desks, meeting rooms, coliving units, event space — each with a capacity integer, a resource type, a location/floor, and a pricing policy. A coworking.booking model carries start_datetime, end_datetime, member, resource and a @api.depends('start_datetime','end_datetime','resource_id') compute that prevents double-booking via an SQL constraint and an overlap search, and computes billable duration. Membership is a coworking.membership.plan with tiered entitlements (included room-hours, guest passes, day-pass allotment) linked to Odoo's native sale.subscription/sale.order so recurring billing and proration are handled by the standard invoicing engine rather than reinvented. Metered usage above the plan's included allowance is captured as usage lines and pushed onto the next subscription invoice using Odoo's invoicing pipeline, so an audit trail exists on every account.move.

The member-facing side is built with QWeb and the Odoo website/portal controllers, so members log in to /my and see live availability, book a desk or room against a real-time capacity view, view their plan entitlements and remaining credits, and download invoices — all under Odoo's existing portal ACLs. A calendar/Gantt availability view (XML views, with OWL components where an interactive capacity grid is warranted) gives front-desk staff a single screen for the day. Access scheduling is enforced by automated actions and ir.cron jobs that flip member access windows based on plan status and booking times, and can hand a signed payload to a door-controller over the JSON-RPC/XML-RPC API. Security is done properly with ir.model.access.csv plus record rules so members only ever see their own bookings and invoices, while community-manager and finance roles get scoped access. QWeb reports produce occupancy and utilization PDFs, and everything respects multi-company for operators running several locations.

This is build-to-order, not a marketplace download. We start with a short scoping call to map your resource types, membership tiers, metering rules, access-control hardware, and which Odoo edition you run (Community vs Enterprise changes what we lean on — e.g. Enterprise subscriptions and Studio-adjacent flows vs. Community equivalents we implement in code). We then build the module against your exact Odoo version (17.0, 18.0, or 19.0), deliver the full installable source, install and configure it on your staging environment for UAT, and cut over to production with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope, and you receive the git repository and technical documentation so you are never locked in.