This is a build-to-order module, not an instant apps.odoo.com download. After a short scoping call we build it against your Odoo 17, 18 or 19 database, targeting a typical delivery of one working week from kickoff depending on the number of document types, approval routes and integrations you need. You receive a firm timeline before work starts, and we install and validate it in your environment before go-live.

Every engagement includes a post-go-live support and bug-fix window with a defined SLA covering the delivered scope. Within that window we resolve defects, answer configuration questions and assist your admins. We also provide the full source code and documentation so your team can maintain it, and we offer ongoing support or version-upgrade retainers (for example migrating the module to a newer Odoo release) as a separate, optional package.

The module captures the elements that make an electronic signature enforceable in most jurisdictions: signer intent and explicit consent, an authentication step (including optional SMS/OTP), and a tamper-evident audit trail with a cryptographic hash, timestamp and IP for each action, all preserved on a QWeb completion certificate. We configure the consent text and authentication level to your requirements. We are not a law firm, so we recommend confirming specifics with your legal counsel for your industry and region.

It runs on both. We build the module to target Odoo 17, 18 or 19 on either Community or Enterprise. The core signing, multi-party routing, security and audit trail are all delivered in the module itself, so you are not forced into an Enterprise upgrade — though if you run Enterprise we can align it with related Enterprise apps where useful.

Yes. The module hooks into standard Odoo records — Sale Orders, HR contracts, Purchase Orders, Projects — so a user can send a document for signature in one click from those records. It also exposes XML-RPC / JSON-RPC endpoints so external systems, or your own custom models, can create requests, poll signing status and retrieve the signed certificate programmatically. Scope of integrations is agreed during the build.

Everything stays inside your own Odoo database and filestore — documents, signatures, hashes and certificates. There is no third-party signing SaaS in the loop and no per-envelope fee, which is a key reason teams choose an in-Odoo module over an external service. Access is governed by ir.model.access.csv and record rules so each department only reaches its own documents.