If your team runs ERPNext, the signature step is usually where a clean workflow falls apart. A Quotation is finished in ERPNext, then it gets exported to PDF, emailed to the customer, printed, signed, scanned, and mailed back — and someone manually re-keys the "signed" status days later, if they remember. ERPNext core has no concept of a legally binding electronic signature: there is no signer envelope, no tamper-evident audit trail, no automatic status change when the counterparty signs, and no way to prove after the fact who signed what, from which IP, and when. For quotes, Sales Orders, contracts, and NDAs, that gap turns into revenue leakage and compliance risk.

ECOSIRE builds the ERPNext E-Signature Suite to close that gap directly inside your ERPNext instance. It is delivered as a proper Frappe app (its own module, DocTypes, and hooks.py) rather than a bolt-on. We add a Signature Request DocType that references any source document (Quotation, Sales Order, Contract, or a configurable list via a Link/Dynamic Link field), a Signature Template DocType that maps signer roles to placeholder tags on the generated Print Format PDF, and a child table of signers with order, email, and status. From any supported document you get a "Send for Signature" action (a client script button plus a whitelisted server method) that renders the Print Format to PDF and dispatches it.

Technically, the suite supports two signing backends behind one interface. The DocuSign path uses the DocuSign eSignature REST API with OAuth (JWT grant), creating an envelope from the rendered PDF and anchor tabs derived from the template; a webhook (DocuSign Connect) hits a whitelisted endpoint that verifies the signature and updates ERPNext. The native path uses a secure, tokenized public signing page served by Frappe, capturing a drawn/typed signature, timestamp, IP, and user agent, then embedding the mark into the PDF and sealing it. Both paths write to an immutable Signature Audit Log DocType (append-only, with document hash at each event) so you can produce a defensible certificate of completion. doc_events hooks and a on_signature_completed handler flip the source document's status — Quotation to Ordered/accepted, or a custom workflow state — and a scheduler event (scheduler_events) sweeps for pending envelopes to send reminders and expire stale requests. Role Profiles and permission rules control who can send, who can void, and who can view the audit trail; every action is also exposed over the Frappe REST API and whitelisted methods for integration.

Because this is build-to-order, you are not downloading a pre-baked app off a marketplace. We start with a short scoping call, confirm which DocTypes you want signable, which signer roles and templates you need, whether you go DocuSign, native, or both, and your v15 or v16 target. We then build against that scope, install and configure on your staging site, run UAT with you, and hand over the git repository plus documentation. Typical delivery is one working week from confirmed scope, and every version is tested for compatibility with your ERPNext release before go-live.