Oracle
Send documents from Oracle business processes for signature and return the signed result.
Typical workflows
Quotes and sales orders.
Purchase orders.
HR contracts.
Related
API
A REST API to create documents, add signers, send for signature and download signed copies.
Discuss an Odoo integration.
Integrations are scoped per agreement. Tell us about your environment.
How the integration works
A document is sent from Odoo to WQ3, signers sign from a secure link, and the signed copy and each signer's status flow back to Odoo automatically.
Send
Create a signing request from inside Odoo through the WQ3 API.
Sign
Each party signs at the level set for them: electronic, remote or token.
Return
Real-time status updates, with the sealed file and completion certificate saved to the same record.
What we need from you
Your Odoo version, the documents to connect, your current approval flow and a technical contact. Each integration is scoped by agreement with your team.
Define when a document is ready to leave Odoo
Before connecting an Odoo action to a signing request, decide when the document is ready to leave your organisation. A useful review checkpoint covers internal approvals, party details and final content, because WQ3 locks documents once they are sent.
Keep internal approval separate from signing authority: an employee who approves a document is not necessarily authorised to sign for the organisation. Also agree how your team will handle changes requested after dispatch, so a revised draft in Odoo is not confused with the version already presented to signers.
Set a policy for signature levels
Choose the signing level according to the document’s purpose and each party’s requirements, rather than simply because it originates in Odoo. Electronic signature suits everyday agreements, while remote signing or token signing is recommended for formal, high-value contracts and organisations requiring a digital certificate.
Different signers can use different levels within one document, so document these requirements during integration design rather than leaving each sender to decide. Where the process requires proof of the account holder’s identity, add eKYC account verification to any level. It is an account-verification add-on, not a fourth signing level.
Review evidence, not just completion
When reviewing an agreement associated with an Odoo record, look beyond whether signing is complete. WQ3’s audit trail records document actions and accompanies the completion certificate, helping reviewers establish who acted and when.
For authenticity checks, a public verification page is accessible through the QR code and reference without an account. File verification compares a SHA-256 fingerprint to reveal changes, while the verification record shows signer names, signature levels and timestamps. Give reviewers a clear distinction between opening a stored attachment and checking that the copy they hold has not changed.
Agree acceptance checks before going live
Turn business requirements into an agreed acceptance checklist for the Odoo integration. Suggested checks include the selected document version, signer details, required signing levels and association with the intended business record; these are implementation checks, not promises of additional features.
Test the distinction between one party finishing and the entire document being complete, and identify who will investigate discrepancies. Review any document-specific legal requirements before approving the workflow. WQ3 is aligned with Egyptian E-Signature Law No. 15 of 2004, but legal validity depends on meeting applicable conditions, not on using Odoo alone.
Start your first signing journey today.
Create your WQ3 account, or talk to us about your organization’s requirements.
Frequently asked questions
Does signing replace our internal approvals?+
Not necessarily. Define required approvals before dispatch, and distinguish permission to approve a document from authority to sign for the organisation.
What if a change is requested after sending?+
WQ3 locks documents once sent. Agree a correction and resubmission procedure during integration design rather than assuming the sent version can be edited.
Is eKYC mandatory for every Odoo document?+
It is an optional account-verification add-on, not a stated universal requirement. Require it where your process needs proof of the account holder’s identity.
Can an external reviewer verify a document without a WQ3 account?+
Yes. The public check page supports authenticity checks without an account, using the QR code and reference provided with the completion materials.
Does the integration guarantee legal validity?+
No integration alone guarantees it. Egyptian law recognises electronic signatures and documents when applicable conditions are met; review your document’s requirements and intended use.