Does the ESIGN Act apply to commercial customers?

This comes up a lot with clients selling B2B, software subscriptions, consulting services, wholesale supply agreements, who've read that the ESIGN Act requires specific consumer consent steps and assume that means extra hoops for every signature, including business customers. It doesn't work quite that way, and the difference matters for how much friction you actually need to build into your signing process. If you want the basics first, read ESIGN Act and UETA explained.

Consumer rules vs business rules

The ESIGN Act's general validity rule, that electronic signatures and records can't be denied legal effect solely for being electronic, applies broadly to any transaction in interstate or foreign commerce, with no carve-out for B2B deals. A contract between two businesses, signed electronically, is just as enforceable under ESIGN as a contract with a consumer.

Where the Act gets specific and strict is a separate section covering consumer disclosures. When some other law requires a business to give a consumer a written disclosure, loan terms, a cancellation notice, certain insurance documents, ESIGN lays out exact steps before you can deliver that disclosure electronically instead of on paper: the consumer has to affirmatively consent, you have to give clear notice of their right to a paper copy and how to withdraw consent, and you have to confirm they can actually access the electronic format you're using. None of that language is written with a business-to-business relationship in mind, and it generally doesn't apply when your customer is itself a business rather than an individual consumer. That gap between a formal legal obligation with specific required language and a looser general practice you're free to shape yourself is exactly what trips people up when they read about ESIGN's consumer rules and assume the same rigidity applies everywhere, including to their ordinary vendor and client contracts. The full consumer process is explained in e-sign consent and disclosure.

When extra consent steps are still worth adding, even for B2B

Just because the strict consumer rules don't apply doesn't mean consent is irrelevant in B2B contracts. A few situations where I'd still build in an explicit consent step:

• Selling to a sole proprietor or very small operator where the line between "business" and "individual consumer" is genuinely blurry. If there's any ambiguity about whether the person signing is acting as a business or as an individual, treating it with the more careful consumer-style consent process is the safer default.
• Contracts likely to end up in a dispute, large deals, anything with a counterparty you don't have history with. Explicit, documented consent to sign electronically removes one more thing a lawyer could argue about later. What makes an e-signature valid in court covers the evidence side.
• Cross-border B2B deals, where the other country's law, the EU's eIDAS framework for example, may have its own consent or format expectations independent of the US consumer-specific rules.
• Industries with their own layered regulations, certain financial or healthcare-adjacent B2B relationships, where a sector-specific rule might require something closer to the consumer disclosure process regardless of who the customer is.

A practical checklist for B2B contracts

• State plainly in the contract itself that both parties agree to conduct the transaction electronically. This is simple, costs nothing, and removes ambiguity about consent.
• Use an e-signature tool that generates a real audit trail, signer identity, timestamp, document integrity, regardless of whether the strict consumer rules technically apply. It's good practice either way.
• Confirm your counterparty can actually open and retain the signed document in whatever format you're sending it, especially for larger organizations with their own document retention systems.
• Keep your own copy of the fully executed, audit-trailed document somewhere retrievable, which matters for your own protection regardless of what the law strictly requires. Whether a paper copy still wins is covered in electronic vs wet signatures.
• If there's any chance the "business" you're contracting with is actually an individual acting personally, lean toward the more careful consumer-style process rather than assuming the looser B2B treatment applies.

A worked example

Say you run a small B2B software company selling to other businesses on annual contracts. One customer is technically a two-person LLC, run by a married couple who use the software personally as much as for their small side business. Is that a "commercial customer" for ESIGN purposes, or close enough to a consumer that the stricter rules should apply? This is exactly the gray zone I mentioned above, and it's genuinely more common than people expect once a business gets below a certain size. My practical answer: when the line is blurry, treat it like a consumer transaction. The extra consent language costs you a sentence or two and a checkbox. Getting caught on the wrong side of that distinction, if a dispute ever actually escalates to a regulator or a court, costs considerably more.

Compare that to a clear-cut case: selling the same software to a 200-person logistics company with a dedicated procurement department signing the contract on the company's behalf. There's no ambiguity there, it's a commercial transaction through and through, and the looser B2B consent standard applies comfortably.

What this means for your contract language

A simple, durable approach that works across almost every B2B relationship: add one sentence near the signature block stating that both parties agree the transaction, and any related notices, may be conducted electronically, and that either party may request a paper copy. This single sentence does double duty. It satisfies the spirit of ESIGN's consent principle even where it's not strictly required, and it gives you a clean, written answer if a counterparty ever claims they didn't realize they were agreeing to something electronically. It's the kind of boilerplate that costs nothing to add and genuinely closes off an argument before it starts.

International B2B complications worth knowing

This gets another layer when your business customer is based outside the US. ESIGN itself is domestic law, governing the US side of the transaction, but the counterparty's own country has its own rules governing their side, the UK's Electronic Communications Act 2000, the EU's eIDAS framework, or similar laws elsewhere, each covered in more depth elsewhere on this site. For most ordinary cross-border B2B contracts, this doesn't create a real conflict, both sides' laws generally recognize electronic signatures for routine commercial dealings. Where it's worth a second look is a cross-border deal with a specific regulatory angle, exporting into a regulated industry, a contract that will be relied on in a foreign court or government filing, where confirming the counterparty's own country's specific requirements, rather than assuming your US process automatically satisfies them, is worth the extra five minutes.

A quick self-check before you send a disclosure electronically

Ask yourself three questions before relying on the looser B2B standard: is the person signing clearly acting in a business capacity, with a title or role that makes this obvious? Is there any specific law (lending, insurance, a sector-specific rule) that already requires a written disclosure for this document? And is this a one-off deal with an unfamiliar counterparty, or an established relationship? If the answers lean toward "individual, not clearly business," "yes, a specific disclosure law applies," or "unfamiliar, high-value, first deal," that's your signal to add the more careful consent language rather than assume the lighter B2B treatment is automatically fine.

How I'd approach this

For a genuinely business-to-business relationship, a vendor contract, a service agreement, a wholesale supply deal, I don't build in the full consumer disclosure machinery, because the law doesn't require it and it just adds friction to a deal that doesn't need it. I do always add a simple consent line in the contract and make sure the signing tool generates a real audit trail, because that costs nothing and is the actual thing that protects you if the relationship sours later, not the specific disclosure steps written for consumer protection. And whenever the "business" on the other side is small enough that the line to "individual consumer" gets blurry, I default to the more careful process rather than assuming the looser B2B standard clearly applies.

Frequently asked questions