WooCommerce 8.3.0 Released

We are pleased to announce the release of WooCommerce 8.3.0. This release should be backwards compatible with the previous version.

This release contains:

As always, we recommend creating a backup of your site and making sure that your theme and any other plugins are compatible before updating. You can check out this update guide for more information.

WordPress Version Support

The versions of WordPress supported are now WP6.4 and WP6.3 (due to the release of WordPress 6.4 last week given the L-1 support policy).

Whats new in 8.3.0?

Default Cart, Checkout, and Order Confirmation Blocks on new installations

We’re thrilled to announce a significant enhancement to the WooCommerce experience, designed to simplify and elevate your online store setup. Starting with WooCommerce version 8.3, we’ve integrated Cart, Checkout, and Order Confirmation blocks as the default checkout experience for new installations. This means that from the beginning, your store will feature a modern, intuitive, and visually appealing checkout journey.

Compatibility and Scope

For new installations with block-based themes (such as TT3, TT4, etc.), the default checkout experience includes the Cart Block, the Checkout Block, and the new Blockified Order Confirmation template. We’ve ensured that this change won’t impact existing stores, providing a worry-free transition for our users. Users updating to 8.3 will keep the existing checkout experience.

Effortless Migration using Page Creation tool

For existing stores, you can now use the WooCommerce > Status > Tools > Create Pages tool to generate new pages effortlessly, incorporating blocks seamlessly into the checkout flow after deleting the old Cart and Checkout pages. This feature is designed to give users a hassle-free way to update the Cart and Checkout experience in one go.

Note: While we’re bringing you an enhanced checkout experience, please note that, for now, the blockified Order Confirmation template will be exclusively available for block-based themes. Stay tuned for future updates as we refine and expand our offerings.

Themes in the WooCommerce Marketplace

With WooCommerce 8.2, we soft-launched a revamped Extensions page. With this release we see the next evolution with the introduction of themes. Visit WooCommerce > Extensions to quickly find the theme that’s perfect for your business.

Marketplace search improvements

The search experience in the new Marketplace has been improved by showing themes first if there are no extensions, empty search will open the discovery page, and large screens will show 8 results if available.

Mobile app onboarding experience has been improved

In this first iteration, we aim to improve the app installation rate by showing a QR code with text instructions on where to install the app. As Woo mobile no longer requires Jetpack (the merchant can log in with site credentials and the app generates an application password), we also want to remove the Jetpack setup steps for non-Jetpack sites since we’re seeing a low conversion rate. For WPCOM/Jetpack sites, the CTA to send a magic link email stays the same.

In iteration 2, we plan to provide a QR code with a link to pre-fill the site credentials except for the password for non-Jetpack sites at least. We’re also exploring generating an application password and including it in the QR code.

Other changes

  • The experimental email opt-in field from the Core Profiler has been improved to perform better email validation. #41152
  • Jetpack data is now preloaded even without the Jetpack plugin installed. #41092
  • Images have been optimized to reduce the WooCommerce package size
  • The compatibility issue with PHP 8.3 related to performing an array_sum() is resolved. #41205
  • New blockified Order Confirmation template is now available by default on new installations. #41276
  • Using WordPress 6.4 release sites that rely on using the Classic Template block for the Single Product template are no longer broken. #41291

For a complete list of the changes included in this release, please see the changelog in the readme for this release.

Much 💜 to all the contributors

Finally a big thanks to everyone in the community who has contributed via issue reports, fixes, translation, testing, supporting other users, or simply spreading the word.

WooCommerce Core

nathanss
psealock
senadir
rrennick
sebcode
moon0326
Dan-Q
danieldudzic
raicem
tommyshellberg
ibndawood
n2erjo00
mattsherman
vladolaru
jimjasson
puntope
lsinger
chihsuan
crunnells
nefeline
rodelgc
dmallory42
lanej0
webdados
nigeljamesstevenson
louwie17
mdperez86
octaedro
tarhi-saad
tjcafferkey
waclawjacek
tarunvijwani
invalid-email-address
wavvves
Lenny4
veljkho
andfinally
ismaeldcom
ilyasfoo
coreymckrill
sanesh-acowebs
gigitux
jaclync
YordanSoares
brentmackinnon
vedanshujain
opr
mpskovvang
ObliviousHarmony
rjchow
bgrgicak
PanosSynetos
roykho
mi5t4n
kdevnel
jorgeatorres
nielslange
barryhughes
joelclimbsthings
daniyalahmadk
Konamiman
alopezari
jonathansadowski
adamsilverstein
johanmolen

ActionScheduler

lsinger
prettyboymp
coreymckrill
barryhughes
alopezari

WooCommerce Blocks

iamahens
senadir
thealexandrelara
wavvves
tarunvijwani
masteradhoc
ralucaStan
invalid-email-address
opr
albarin
gigitux
tjcafferkey
nefeline
danieldudzic
roykho
alexflorisca
dinhtungdu
danielwrobert
mikejolley
kmanijak
message-dimke
nielslange
larsenlarsson
hritikchaudhary
hsingyuc
tarhi-saad
samueljseay
imanish003

Keep yourself in the loop!

This field is hidden when viewing the form
This field is hidden when viewing the form
This field is hidden when viewing the form


10 responses to “WooCommerce 8.3.0 Released”

  1. simbahosting Avatar
    simbahosting

    Do I understand rightly that the blockified order confirmation was only introduced 6 weeks ago (https://developer.woocommerce.com/2023/10/03/woocommerce-blocks-11-2-0-release-notes/) and is now the default? Does this potentially mean that developers who declared their extensions “block compatible” may now actually have incompatible extensions if their extensions were operating on the “order confirmation” page, and potentially very few of them are aware of this? Or did I (I’m hoping!) misunderstand something?

    1. Hi, the Order Confirmation block-based experience was built with backward compatibility in mind, to support existing hooks and filters. Therefore, all extensions should work out of the box, and there’s no need to declare compatibility. Additionally, we allow users to easily revert to the legacy Order Confirmation page. See this section in our documentation for more details.
      Feel free to open a request in our GitHub repository, in case you identify any bugs or have suggestions. Thank you.

  2. In the updated version 8.3, my Custom Payment Gateway Plugin is not working, but the same plugin works fine in version 8.1.1. How can I fix this issue?

    1. Hello Anbu,
      if you installed a new store using WooCommerce 8.3, it’s checkout flow will be powered by the Checkout blocks.

      Extensions will need to do a separate registration of their payment methods specifically targeting the blocks.

      To help payment method developers integrate with the blocks, we’ve created some documentation https://github.com/woocommerce/woocommerce-blocks/blob/trunk/docs/third-party-developers/extensibility/checkout-payment-methods/payment-method-integration.md that gives details on both the client side (JS) and server side (PHP) components of the integration. There is also a tutorial on the blog Exposing Payment Options in the Checkout Block https://developer.woocommerce.com/2022/07/07/exposing-payment-options-in-the-checkout-block/ that we recommend.

      1. Hi Raluca,
        Thanks for the response, Actually I have some other issues. I have created a custom payment plugin using stripe api’s need to integrate with woocommerce plugin. In my plugin i have used the WC_Payment_Gateway classes and process payment default functions. while hitting on “place order” button it triggers the process payment functions automatically. But i need call customer creation api and payment api before it triggers the process payment function. I have tried to convert those as function in same file but confirmcardsetup method can be achieve only through the js which was provided by stripe. So, i have enqueued the js file and handles the onclick submit function. Then using through ajax call called the customer creation api but the process payment triggered automatically once hit place order button so while calling api’s each time it went process payment function and returns back to the api. So i couldn’t handle the positive scenarios and negative as well as. Is there any method to handle process payment function manually in js to resolve my issues or any other methods to achieve custom payment plugin. Please do the needful help to implement the plugin.

  3. Después de esta upgrade mi pagina no sirve, solo si desactivo woocommerce.

  4. […] a versão 8.3.0 do WooCommerce, em todas as novas instalações, são activados por omissão o carrinho e finalização de compras […]

  5. […] a versão 8.3.0 do WooCommerce, em todas as novas instalações, são activados por omissão o carrinho e finalização de compras […]

  6. […] version 8.3 (released in November 2023) WooCommerce Cart and Checkout Blocks has become default experience. […]

  7. NextCloud is an open-source, self-facilitated document the board application that allows you to make, alter, host, and offer records without limits. This article makes sense of how you can introduce NextCloud on a Ubuntu 22.04 server with Snap and secure the application for creation use.

Leave a Reply

Your email address will not be published. Required fields are marked *