🗃️ Available filters
6 items
🗃️ Checkout payment methods
3 items
🗃️ Hooks
2 items
📄️ Additional checkout fields
A common use-case for developers and merchants is to add a new field to the Checkout form to collect additional data about a customer or their order.
📄️ Available slots
This document presents the list of available Slots that you can use for adding your custom content (Fill).
📄️ DOM Events
Some blocks need to react to certain events in order to display the most up to date data or behave in a certain way. That's the case of the Cart block, for example, that must listen to 'add to cart' events in order to update the cart contents; or the Mini-Cart block, that gets opened every time a product is added to the cart.
📄️ Cart and Checkout extensibility
This document is a high-level overview of the moving parts required to extend the Cart and Checkout blocks.
📄️ Frequently asked questions
This document aims to answer some of the frequently asked questions we see from developers extending WooCommerce Blocks.
📄️ Processing an order
This document will shed some light on the inner workings of the Checkout flow. More specifically, what happens after a user hits the "Place Order" button.
📄️ Script, styles, and data handling
The problem
📄️ Data flow overview
In the WooCommerce Cart and Checkout blocks, the server is the source of truth for critical transactional and persistent data. This includes:
📄️ Removing checkout fields
If you're trying to extend the new Checkout block, you might notice the previous checkout_fields isn't working. This is intentional as we want to offer more curated extensibility paths. With that said, one of the most common requests we get is how to disable Checkout fields for certain order types. This is not something we encourage, but we are sharing the details due to how commonly requested it is.
📄️ Slot and fill
The problem