Most teams that run Odoo end up with documents scattered across the Attachments sidebar, ir.attachment records with no lifecycle, shared drives, and email threads. Odoo's native Documents app (Enterprise) and raw attachments cover storage and basic folders, but they run out of road the moment you need real version control (not just "replace file"), reviewer markup directly on a PDF, controlled check-in/check-out to prevent two people overwriting each other, or an approval trail that ties a document revision to the business record it belongs to. Community editions have even less. Teams then resort to naming files contract_final_v3_REALLY_final.pdf, and audits become guesswork.

Advanced DMS is a made-to-order Odoo module that ECOSIRE builds for your database. Technically it introduces a document.file model with a linked document.file.version model so every upload is an immutable revision (superseded versions are retained, never destroyed), plus a document.folder hierarchy with inherited access. Each revision stores its own ir.attachment, a version_number computed via @api.depends, author, timestamp, and a change note. The PDF annotation layer is an OWL component embedded in the form view that renders the document in-browser and lets reviewers add highlights, sticky notes, stamps, and freehand markup; annotations are persisted as structured JSON on their own model and rendered back over the page coordinates, so the source PDF is never mutated and markup is queryable and reportable. Check-out locks a file to one user (a state field guarded by a record rule), and check-in creates the next version and releases the lock. QWeb reports can render a version-history sheet or an annotation summary for sign-off.

Access is enforced the Odoo-native way: ir.model.access.csv for model-level CRUD per group, plus ir.rule record rules so folder membership, ownership, and (optionally) company_id decide visibility rather than a bolted-on permission scheme. Automated actions and server actions handle retention reminders, stale-checkout escalation, and status transitions. Everything is reachable over the standard XML-RPC/JSON-RPC API, so an external portal, scanner intake, or DMS-adjacent system can create files, post versions, and read annotations programmatically. We build against your target — Odoo 17.0, 18.0, or 19.0 — and adapt to Community or Enterprise (on Enterprise we can integrate with the Documents app and its workspaces rather than duplicate them; on Community we ship the full standalone stack).

Delivery is build-to-order. We start with a scoping call to pin down folder taxonomy, groups and record-rule matrix, which annotation tools you actually need, retention rules, and any integration endpoints. We then build on a branch, deliver the installable module and technical docs, run UAT on a staging copy of your database with a rollback plan, and only then deploy to production, followed by a user-training session and a post-go-live support window. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company record-rule isolation, deep localization, large historical-document migration volume, and additional integrations increase the quoted scope — you get a fixed quote after the scoping call.