WooCommerce placement guide for the EU legal-guarantee notice

Map the purchase journey before choosing hooks

Begin with the storefront that shoppers actually use. List the product template, catalogue path, mini-cart or cart and checkout, then record order confirmation and transactional email as unsupported Notice27 boundaries. Note which supported surfaces are classic PHP templates and which use WooCommerce Blocks. A plugin can register many hooks, but enabling all of them without a plan can create duplication and visual noise.

Use the Commission’s prominence guidance as an input and obtain professional interpretation for the final placement decision. The technical goal is narrower: ensure the selected, official colour artwork is reliably present, legible and testable on the chosen surfaces.

Classic templates and Blocks are different systems

Traditional WooCommerce templates expose PHP actions around product, cart and checkout markup. Cart and Checkout Blocks use a JavaScript-driven extension model, with declared compatibility and supported extensibility interfaces. WooCommerce’s developer documentation warns that not every classic hook works in block checkout.

Treat block support as a first-class test case. Confirm that extension scripts register through documented interfaces, that the notice survives hydration and cart updates, and that it does not depend on brittle DOM selectors. A classic-checkout screenshot is not evidence for a store using Checkout Blocks.

• Identify the active cart and checkout implementation.
• Declare compatibility only after testing.
• Verify guest and logged-in paths.
• Check notices after quantity, shipping and payment-method changes.

Product and cart review

On product pages, check simple and variable products, out-of-stock states, product bundles created by other extensions and narrow screens. Keep the notice separate from the product gallery if theme cropping could alter it. Verify that lazy loading does not postpone it beyond the point a shopper can reasonably encounter it.

On cart pages, test empty and populated carts, coupons, notices, shipping calculators and cart fragments. If the same graphic already appears site-wide, decide whether a second cart copy adds clarity or merely repeats content. Record the decision rather than assuming more placements are always better.

Checkout and unsupported post-purchase surfaces

Checkout deserves focused regression testing because payment and address extensions frequently alter its layout. The legal-notice component should not capture data, interfere with validation, move payment controls or introduce a remote dependency. Verify both error and successful form states without placing a real order in production.

Neither stable Notice27 1.2 nor the current private candidate provides production order-received or transactional-email placement. The guided confirmation and account-email views are fictional product designs only; do not treat them as enabled surfaces or implementation evidence.

Create evidence that survives a theme update

For each selected placement, record the page type, template mode, language, viewport, test date and screenshot. Repeat the matrix after WooCommerce, theme, checkout-block or multilingual-plugin changes. That small discipline is more useful than a settings toggle with no storefront verification.

Notice27 exposes placement controls and supplied language files while keeping the artwork local. It does not read cart contents, orders or customer records. The merchant remains responsible for deciding the appropriate placement and confirming the result.

Include a negative test as well: disable the selected placement or move the store to an unsupported template and confirm the diagnostic is understandable. Evidence is stronger when it shows both the expected display and the failure mode the team knows how to recognise.