Embedding legal texts in Shopware, Shopify and WooCommerce

Legal texts in Shopware, Shopify and WooCommerce — overview

This guide is an overview page. It explains the fundamental integration patterns shop systems use to pull approved legal texts from a central source — and points to the dedicated detail page per shop system for the implementation. The operational specifics of Shopware, Shopify and WooCommerce are covered in the linked guides.

Otherwise shop systems maintain legal texts separately: Shopware in shopping experiences and sales channels, Shopify via policy pages and notification templates, WooCommerce via WordPress pages and theme templates. As soon as the same shop runs in several languages or countries, the maintenance effort multiplies. TermShelf does not change the shop system but the source: instead of maintaining full texts in the shop, the shop consumes the centrally approved version via the Public Delivery API.

Which integration patterns exist in principle

Regardless of the shop system, a few recurring patterns appear. They can be combined freely:

• HTML fragment — the approved version appears in a shop page or a mail block.
• JSON/API — custom themes, headless storefronts or middleware render themselves and further process text and version info.
• PDF artifact — a self-contained, archivable version as an attachment to the order confirmation or order email.
• Version pinning — a fixed version is referenced via ?version=N.
• Order/contract moment — via ?effective_at=<ISO-8601> the state valid at the transaction moment is fetched.

The formats in detail are compared in delivering legal content via API; the full delivery contract is described on the feature page Public Delivery API. The transactional case is covered on the feature page transactional delivery.

Shopware

In Shopware, legal texts spread across sales channels, shopping experiences and Twig-based mail templates. Per language, market and B2B/B2C the number of places that must stay consistent grows. How to embed terms, withdrawal and privacy in a versioned way in storefront and order confirmation is described in embedding legal texts in Shopware order confirmations.

Shopify

Shopify renders transactional emails via Liquid notification templates that do not fetch external content at send time. The artifact retrieval therefore usually sits in a custom app or middleware logic. How terms and withdrawal reach the order confirmation as PDF, HTML or JSON from an external delivery source is described in terms and withdrawal as PDF in Shopify order confirmations.

WooCommerce

WooCommerce order emails are PHP templates that can be overridden in the theme — and displaced on updates. How to fetch the approved version server-side when generating the order email as a PDF attachment, HTML fragment or JSON is described in attaching terms as a PDF to WooCommerce order emails.

Deeper guides on the transactional case

• Attaching terms as a PDF to order confirmations
• Embedding the withdrawal notice in order confirmations
• Which terms version applied at contract conclusion?
• Public Delivery API in the API reference

Multiple languages and markets in one shop

International shops often run one storefront per language or market. If each storefront maintains its own copy of the legal texts, they drift apart. Through central variants with targeted overrides, each storefront automatically receives the version approved for its language and market. The variant model is described in how TermShelf models variants.

What this guide does not promise

TermShelf does not produce legally binding content and is not a substitute for legal advice. This article describes an integration-open approach via the Public Delivery API — it does not claim ready-made, certified plugins for Shopware, Shopify or WooCommerce. How deep the integration goes depends on the respective shop and the chosen artifact form.