Nino Aratari is a Senior Magento Developer with over 25 years of experience in software development, working with Magento since its 1.4 release and now building on Mage-OS. He is the author of an open-source digital signature extension for Magento/Mage-OS integrating DocuSign, Adobe Sign, and other e-signature providers into the order flow, built with a strong focus on automated testing, cross-version compatibility, and security.
Meet Magento Poland 2026
Digital Signature in Mage-OS
Every merchant selling B2B, high-value goods, rentals, or regulated products eventually hits the same wall: a contract, waiver, or delivery confirmation needs to be signed, and that step almost always happens outside the e-commerce platform — via email, a separate portal, or manual back-office work. This breaks the customer journey, creates operational overhead, and makes it hard to track which orders are actually legally finalized. This talk tells the story of building a digital signature extension for Magento and Mage-OS designed to close that gap, and the business decisions that shaped it far more than the code did.
The first decision was who to build for: not a single signature provider, but merchants with different budgets, compliance needs, and existing vendor relationships. That meant supporting DocuSign and Adobe Sign for enterprise merchants who already have contracts with them, alongside a lightweight in-house alternative for smaller merchants who don’t want a per-envelope cost. This multi-provider approach directly shaped the commercial model of the extension itself, including a usage/cost-tracking layer so merchants can monitor how much they’re spending per provider and make informed decisions about which one to use for which document type.
A second theme is where in the customer journey signature happens, and why that matters commercially. Requiring a signature at checkout can protect the merchant legally, but it also introduces friction that can hurt conversion; deferring it to a post-purchasentroduces collection risk. We’ll walk through how the extension supports bothmodels — trigger-based rules tied to cart contents, order status, or product type — and how that flexibility became a key selling point for merchants operating across different product
lines with different risk profiles.The talk also covers the operational reality of running this in production: wrequest goes unanswered, how expiring documents and reminders are handled, and how webhook-driven status updates keep the order lifecycle (and store staff) in sync without manual follow-up. I’ll share what actually broke in real deployments — including a case
where required-signature rules silently failed to trigger for an entire batchght us about the gap between “the feature works” and “the feature istrustworthy enough for finance and legal teams to rely on.”Finally, we’ll touch on the compliance and trust dimension: audit trails, document retention, and why “digitally signed” only has business value if it can be defended later. Attendees – whether merchants, agency owners, or platform architects — will leave with en digital signature workflows are worth the investment, and what to demand from any solution (this one included) before trusting it with legally binding documents.