Extra tick boxes at checkout: your terms, an age confirmation, a marketing\nopt-in. Up to five, each with its own wording and its own refusal message.<\/p>\n\n
The point of the box is being able to show, months later, that this customer\nticked it. Every \"just add a checkbox\" snippet validates the tick and throws\nit away, which leaves a shop with a checkout that looks compliant and an\norder file that proves nothing. Here the acceptance lands on the order, and\nevery order screen carries a Consent panel showing it.<\/p>\n\n
Rewrite your terms next month and a past order still says what was actually\nagreed to, because the wording as it was shown<\/strong> is written onto the order\nbeside the tick \u2014 not a reference to a setting that has since moved on. The\ntime is recorded too, because \"when\" is half of what a consent record is\nfor.<\/p>\n\n The Immediately above the Place order button, on both checkouts. Agreeing to\nterms three screens earlier is not agreeing to anything a shopper remembers\nreading. The classic checkout prints them through WooCommerce's own hook just\nabove the button; the Checkout block draws them in its Order information step\nthrough WooCommerce's checkout-fields API, which refuses a required box that\nwas not ticked and writes the tick onto the order \u2014 and this plugin then\nrecords the wording and the time beside it, exactly as on the classic\ncheckout.<\/p><\/dd>\n The words do; the link does not. WooCommerce's checkout-fields API shows a\nfield's wording as plain text, so on the block \"I agree to the terms\" is\nshown without its link. Keep the link to your terms in the block's own terms\ntext as well, which is what most block-checkout shops already have.<\/p><\/dd>\n Past orders keep saying what was agreed at the time. The wording is stored\nwith the acceptance rather than looked up when the order is read.<\/p><\/dd>\n No. The acceptances stay on the orders \u2014 they are the record the checkbox\nexisted to create.<\/p><\/dd>\nRequired means required<\/h4>\n\n
required<\/code> attribute is a courtesy to the browser and nothing more \u2014\nanybody can post past it. A required box that was not ticked stops the order\non the server, where the order is actually created.<\/p>\n\nWhat you get<\/h4>\n\n
\n
\n
\n
Where do the boxes appear?<\/h3><\/dt>\n
Does the link in my wording work on the Checkout block?<\/h3><\/dt>\n
What happens if I change my terms later?<\/h3><\/dt>\n
Does uninstalling delete the record?<\/h3><\/dt>\n
Can I edit the checkout fields themselves?<\/h3><\/dt>\n