WooCommerce 11.2 Matches CSV Imports by GTIN and Adds Checkout Date Fields

WooCommerce 11.2.0 was released on October 7, 2026, with 642 pull requests from 93 contributors and a database update. It improves product CSV imports, adds date fields to the Additional Checkout Fields API, makes order withdrawal emails configurable and includes security fixes that WooCommerce asks every store to install.

Minimum requirements stay at WordPress 7.0 and PHP 7.4. WooCommerce 11.2.1, a non security fix release, followed on October 9, 2026.

CSV imports match products by GTIN, UPC, EAN or ISBN

With "Update existing products" enabled, the product CSV importer now matches rows by GTIN, UPC, EAN or ISBN when no ID or SKU is present, checking ID first, then SKU, then the global unique ID. A non blank identifier that matches nothing skips the row instead of creating a product, and a match with a different product type is refused. Import cleanup now removes only the placeholder products created by that import instead of running site wide orphan deletes.

Supplier feeds keyed on barcodes. Clients who receive supplier spreadsheets keyed on barcodes can now update products without mapping SKUs first. We run the supplier's file through the importer on staging, review skipped rows and refused type changes and only then import in production.

Date fields arrive in the Additional Checkout Fields API

The Additional Checkout Fields API now supports date fields in the Checkout block, using the browser's native date picker. Developers can restrict choices with fixed limits or periods relative to today, such as delivery dates from tomorrow through the next 30 days, and those limits also apply in My Account forms.

Delivery dates without a plugin. Florists, caterers and other stores that ask for a delivery or event date have often relied on a separate checkout plugin. We can now build that field with the core API, test it on phones and desktops and confirm the date appears correctly in order emails and the admin.

Configurable order withdrawal emails and new block styles

Order withdrawal requests now send configurable emails that acknowledge the customer and notify the merchant, managed under WooCommerce, Settings, Emails. Product Image, Product Quantity, Product Filters and Chips blocks gain extra styling options such as borders, shadows, colors, sticky positioning and typography.

Security fixes in WooCommerce 11.2

• Cc and Bcc recipients can no longer be set on the Reset password, New account and Confirm email address emails, and previously saved addresses are ignored
• Downloadable product authorization rejects malformed order and email credentials before permission lookup
• Shop managers can no longer edit users who also hold a role outside woocommerce_shop_manager_editable_roles
• On multisite, importing Blueprints requires network super admin rights
• Usage tracking checks that sensitive information is left out of the data it sends

Downloads and staff accounts. Two of these fixes can change day to day behavior. We test a sample of download links from older orders on staging, reissuing any that stop working, and check that shop managers can still edit the customer accounts they handle without reaching roles they should not.

PublishPress Future and the 11.2 update

PublishPress Future versions 3.0.0 to 4.10.3 can cause a fatal error with WooCommerce 11.2 because they load an outdated copy of Action Scheduler. PublishPress fixed this in version 4.10.4, and WooCommerce advises updating PublishPress Future before updating WooCommerce.

Plugin order on update day. This is a case where update order matters. On stores with PublishPress Future, we update it to 4.10.4 or later first, confirm scheduled content still publishes, and then apply WooCommerce 11.2.

Developer advisories and the PHP 8.1 plan announced before 11.2

• wc_get_orders() and wc_get_products() read date strings in the store's timezone
• Experimental abandoned cart recovery and Agentic Checkout APIs are removed, and the database update drops the wc_email_unsubscribes table
• Sequential coupons of equal priority apply in the order entered, which can shift cart totals
• Cart and Checkout blocks use a fixed 360px order summary column and a 920px two column breakpoint
• On September 29, 2026, WooCommerce announced that version 11.6, planned for February 2027, will require PHP 8.1 or newer and recommended PHP 8.3 or newer

Getting ahead of the PHP 8.1 requirement. Stores still on PHP 7.4 or 8.0 have time, but not unlimited time. We check each client's PHP version, test the store on PHP 8.3 in staging with its full extension set and schedule the hosting change well before WooCommerce stops supporting older PHP.

Classic checkout address fix in 11.2.1

WooCommerce 11.2.1, released on October 9, 2026, restores 11.1 behavior for stores that remove address fields from the classic checkout with filters, where 11.2.0 could block checkout, skip tax or hide shipping options. It also accepts Argentine postcodes without the province letter again, along with formats for El Salvador, Saint Vincent and the Grenadines and the British Virgin Islands.

WooCommerce 11.2 FAQ

Does WooCommerce 11.2 include security fixes?

Yes. WooCommerce says 11.2 includes security fixes and asks all stores to update.

Does 11.2 require PHP 8.1?

No. WooCommerce 11.2 requires PHP 7.4 or newer. WooCommerce has announced that 11.6, planned for February 2027, will require PHP 8.1.

I use PublishPress Future. What should I do first?

Update PublishPress Future to version 4.10.4 or later before updating WooCommerce to 11.2.

From plugin update order to PHP upgrades, WooCommerce 11.2 is a release that rewards planning. Our support and maintenance plans take care of it on staging first, then in production. Contact us to talk about your store.