How do the `do_action` dynamic data hooks work in Checkout V2?

Hello bricks team,

There are numerous dynamic do_action elements on the WooCommerce checkout and certain other pages, which make the builder appear very cluttered and disorganized. Do they serve a specific purpose, and would removing them cause any issues?

Best regards

You should not remove these, if you want to WooCommerce to work properly. They are needed for Plugins that extend WooCommerce or to e.g. show VAT. By removing them you might run into some big issues.

If they annoy you inside the Builder you have the option to hide them with the visibility switch, so you only see them inside the structure panel.

Best regards
suat

Yes,

As @UserfreundSuat explained, those {do_action:…} items are WooCommerce hook placeholders. They run the matching WordPress/WooCommerce action on the frontend, so output added by WooCommerce itself, extensions, or custom code can still appear in the right checkout/cart/account location when the layout is built with Bricks. (This is not a feature in Bricks, it was introduced since 1.7)

You can remove one if you are sure your site does not need anything attached to that hook. The risk is that notices, payment/shipping/plugin output, compliance text, or other hooked content may disappear. The safer approach is to leave them in place unless you remove one deliberately and then test the full relevant WooCommerce flow.

Reference: WooCommerce Template Hooks | Bricks Academy