Transactional Legal Text Delivery
Deliver legal texts where contracts are created.
Whether it's an order confirmation, a contract email, a sign-up flow or checkout — transactional delivery brings the approved version into the exact moment it matters. Three artifact forms, one stable version reference.
What is Transactional Legal Text Delivery?
- Transactional Legal Text Delivery
- Transactional Legal Text Delivery is the delivery of approved legal texts into transactional systems — order and contract confirmations, sign-up emails, checkout steps. TermShelf serves the content as embedded HTML, as JSON for your own templates or as a PDF attachment, each tied to a specific published version.
Typical use cases
Terms as a PDF on the order confirmation
Fetch the terms version approved at order time as a PDF artifact and attach it to the confirmation email.
Withdrawal notice in the confirmation
Embed the withdrawal notice as HTML in the email footer or attach it as a PDF — versioned instead of static in the template.
Contract confirmation with receipt
Send the applicable version on contract conclusion and store the version number used with the transaction.
Sign-up flow
On sign-up, pull the approved terms as JSON into your own template and render them consistently.
Checkout disclaimer
Embed legal-text sections directly into the checkout step instead of maintaining them separately there.
How TermShelf helps
Versioning matters most in transactional mail: a confirmation should later show traceably which version was actually sent with it.
Three paths into transactional systems
HTML for embedding directly into emails and footers, JSON for your own mail or app templates, PDF as an attachment to order, contract or sign-up emails.
Correct version per transaction
Via version pinning (?version=N) or effective_at you can reference exactly the version that applies to a given transaction.
Stable version reference
Every publication is a dated, immutable snapshot. If the version number is stored with the order, the same version can be retrieved again later.
One source for all channels
Website, app and transactional mail pull the same approved version — no stale PDF in the mail template, no footer drift.
What transactional delivery does not do
- It does not produce legal texts and is not a substitute for legal advice.
- It does not decide whether a mandatory attachment is legally sufficient — that stays with the user in coordination with qualified counsel.
- It is not an email sending service; it provides the artifacts a mail or shop system embeds.
- It does not attach anything automatically — embedding happens in the respective transactional system.
Frequently asked questions
- How does the right terms version get into an order confirmation?
- When generating the confirmation, the shop or mail system fetches the approved version via the Public Delivery API — as HTML, JSON or PDF. Via ?version=N or effective_at you can reference the version that applied at order time.
- Does it stay traceable which version was sent?
- Yes, provided the version number used is stored with the transaction. Since every publication is a dated, immutable snapshot, the same version can be retrieved again later.
Shop systems and order confirmations
Order confirmations in Shopware, Shopify and WooCommerce are a typical place for versioned legal-text delivery. Depending on the setup, a PDF attachment, embedded HTML or JSON/API is used — with TermShelf as the delivery and versioning layer, not a shop plugin and not legal advice.
Read on
- Guide: Embedding legal texts in order and contract confirmations
- Guide: Attaching terms as a PDF to order confirmations
- Guide: Embedding the withdrawal notice in order confirmations
- Guide: Which terms version applied at contract conclusion?
- Developers overview: transactional delivery technically
- Glossary: Transactional Legal Text Delivery & version pinning
The right version — at the right moment.
Deliver approved legal texts, versioned, into confirmations, contracts and checkout flows.