Extending WooCommerce: Hooks & Custom Functionality

Chapter 3 warned that copying a template file forks it, permanently losing that file's future WooCommerce updates — and pointed forward to hooks as the lower-risk alternative. This chapter is that payoff: WordPress Intermediate/Advanced 5's own actions-and-filters material, applied to WooCommerce's own large, separate set of hooks.

Actions vs. Filters, Recapped for WooCommerce

This is exactly the mechanism WordPress Intermediate/Advanced 5 already taught — nothing new conceptually. What's new is the specific set of hooks: WooCommerce fires hundreds of its own action and filter hooks throughout the cart, checkout, product display, and order lifecycle, entirely separate from WordPress core's own hooks.

Finding the Right Hook

WooCommerce publishes an official hook reference documenting its own actions and filters by name and by the data each one provides. In practice, confirming a hook actually fires when and how expected is often done directly and quickly — temporarily adding a logging line inside a candidate callback while testing is a normal, standard part of the workflow, not a sign of doing it wrong.

A Real Example: A Bulk-Discount Pricing Filter

A common, genuinely useful customization: automatically discounting a cart item once its quantity reaches a threshold. The standard, reliable pattern for adjusting cart-item prices hooks into woocommerce_before_calculate_totals — an action, despite modifying a price, because it acts on the whole cart object rather than returning a single filtered value.

$cart_item['data'] is the product object for that line item — the same product object WordPress Intermediate/Advanced 4 already covered as a custom post type instance, reached here through the cart rather than a direct query. Calling set_price() on it changes the price used for totals, tax, and the order eventually created at checkout, without ever touching the product's own stored price in wp_postmeta.

A Real Example: An Action for a Side Effect

Not every customization changes a value — some just need to do something at a specific point. Notifying an internal fulfillment system once an order is marked complete is a genuine action, not a filter:

wc_get_order() returns a full order object — the same underlying order data Chapter 4 described being created at checkout, now available inside a hook triggered by that same order's own status change.

Where to Put This Code

WordPress Intermediate/Advanced 5 already made the case for a small custom plugin over a theme's own functions.php — a plugin survives a future theme change, functions.php doesn't. That reasoning applies here without modification.

Hands-On Exercises