CBD / Hemp

WooCommerce 11.2 Lets Age-Restricted Stores Collect Birthdays in the Checkout Block

WooCommerce 11.2 adds a date field type to the Additional Checkout Fields API, letting Checkout block stores collect a birth date and reject underage birthdays with relative limits such as -P21Y. The field is self-reported, so vape sellers still need PACT Act database verification.

E-commerce 4 Internet Marketers Editorial

Illustration of a vendor checking a customer's ID at a New England harvest fair booth on an overcast October morning.

WooCommerce 11.2, released October 7, 2026, adds a date field type to the Additional Checkout Fields API, giving stores that use the Checkout block a supported way to ask shoppers for a birth date. For nicotine, CBD, and other age-restricted sellers, the useful part is the range limit. A developer can set the field so the browser’s date picker, and the server check that follows, refuse any birthday that would make the buyer younger than 18 or 21.

The WooCommerce team listed the change among the release’s three highlights in its 11.2.0 release notes, saying extensions and developers can now collect “information such as birthdays and preferred delivery dates through the Checkout block.” There is no settings screen for it. The company’s merchant summary of 11.2 says adding the field “takes a short code snippet.”

How the new date field works

According to the Additional Checkout Fields documentation, a field registered with 'type' => 'date' stores its value as a YYYY-MM-DD string. Shoppers pick the date with their own browser or phone date picker in their local format, while order screens and emails show it in the date format set under Settings, General.

Two new options, min and max, cap the range. Each accepts either a fixed date or a duration relative to today written in ISO 8601-2 form, such as P1D for tomorrow or -P18Y for 18 years ago. WooCommerce’s own documentation table uses -P18Y as its example max value, which is exactly the shape an age gate needs. A store with a 21-plus rule would set max to -P21Y, so no birthday later than 21 years before the current date can be picked or submitted.

The documentation tells developers to pass the duration itself rather than calculating a date in PHP. WooCommerce’s checkout fields tutorial explains that the duration is resolved against the current date each time the field is rendered or validated, so it stays correct behind a page cache and across midnight. A date computed once at registration can go stale, which on an age gate could mean turning away a buyer on their 21st birthday or letting through one who is a day short.

The 11.2 pre-release notes add that the limits apply in both the Checkout block and My Account forms, and that date fields can also use JSON Schema validation, a rule format that can compare one field against another or against cart conditions.

Where a birthday field should live

Each additional field renders in one of three places, and the choice changes what gets saved. A field in the contact section is saved to the shopper’s account and shows up as editable under Account details. A field in the address section appears in both shipping and billing forms and stores two separate values. A field in the order section is saved only to that order and is never pre-filled on the next purchase.

For a date of birth, the contact location avoids collecting two birthdays per order, though it also lets a logged-in customer change the date later from My Account. The documentation notes that the order keeps the value as it stood when the purchase was placed, while the customer record holds the most recent value. Stores that need a record of what was attested at checkout would read the order copy.

JSON Schema rules can also make the field conditional. The documentation’s checkout “document object” includes the product IDs in the cart, the shipping address, and the selected payment method, so a mixed catalog could require a birthday only when a restricted product is in the cart rather than on every order.

A typed birthday is not a verified age

The new field collects what a shopper types. It does not check that date against any record. For vape and other tobacco sellers, federal law asks for more. Under the Prevent All Cigarette Trafficking (PACT) Act, which Congress extended to electronic nicotine delivery systems in December 2020, 15 U.S.C. 376a(b)(4) bars a delivery seller from accepting an order without obtaining the buyer’s full name, birth date, and residential address and verifying them through a commercially available database built mainly from government sources. The same section requires shipping that collects an adult signature with photo ID at delivery, and it says the verification database cannot be controlled by the seller.

What 11.2 changes is the plumbing. A birth date captured through the core API lands in a predictable meta key, such as _wc_other/namespace/field for contact and order fields, and can be read with WooCommerce’s get_field_from_object helper. An age verification extension can pick it up from there instead of injecting its own checkout field, which tends to be the piece that breaks when a store moves from the classic shortcode checkout to blocks. The EC4IM guide to age verification architecture for nicotine, CBD, and adult-restricted carts covers how those verification layers usually fit together.

The API only works with the Checkout block. Stores still on the shortcode checkout will not see these fields, although WooCommerce documents hooks such as woocommerce_set_additional_field_value that let older plugins mirror values into their existing meta keys during a migration.

Why hemp and vape processors care

Analysis. Age rules for hemp products are tightening at the state level. Missouri House Bill 2641, which takes effect November 12, sets a floor that remaining hemp-derived cannabinoid products may not be sold to anyone under 21, as covered in EC4IM’s report on Missouri and Illinois hemp cart blocks. Underwriters reviewing CBD stores often ask how checkout keeps minors out, and a shop applying through Organic Payment Gateways for CBD-friendly processing can now show a birthday rule enforced by WooCommerce core, with the stored date on every order, rather than a theme script that may not survive the next update.

Update notes for 11.2

WooCommerce describes 11.2 as backwards compatible but says it includes a database update and security fixes, and it asks merchants to update every store after taking a backup. One plugin conflict is flagged in the release notes. PublishPress Future versions 3.0.0 through 4.10.3 can cause a fatal error with WooCommerce 11.2 because they load an outdated copy of Action Scheduler, so sites using it should move to 4.10.4 or later first. The release’s shop manager permission change is covered separately in EC4IM’s WooCommerce 11.2 shop manager fix report.

What the change adds up to

WooCommerce 11.2 gives age-restricted stores on the Checkout block a native date field with relative limits like -P21Y, server-side validation, and a standard storage location for the result. It stops underage birthdays from being entered, but it does not verify identity, so vape sellers still need the database checks and adult-signature delivery the PACT Act requires, and CBD sellers still need to match each state’s age floor. For developers, the practical gain is one supported place to collect the date that every verification tool and processor review can read.

Sources