wc-product-crud-cache

WooCommerce product CRUD and request cache

Use this skill for products and variations whenever an extension reads, changes, imports, or caches catalog data. WooCommerce 11.0 enables product instance caching for newly installed stores; existing stores preserve their previous opt-in state. Correct code must work in both modes.

Public contract

Load and persist through WooCommerce CRUD:

$product = wc_get_product( $product_id );

if ( ! $product instanceof WC_Product ) {
    return;
}

$product->set_regular_price( wc_format_decimal( $price ) );
$product->set_name( sanitize_text_field( $name ) );
$product->save();

Use view getters for customer-facing output and edit getters for canonical stored values:

$display_name = $product->get_name( 'view' );
$stored_name  = $product->get_name( 'edit' );

Filters can alter view results. Do not use display-filtered values as storage input or as a concurrency token.

WooCommerce 11.0 product instance cache

The public feature check is:

use Automattic\WooCommerce\Utilities\FeaturesUtil;

$enabled = FeaturesUtil::feature_is_enabled( 'product_instance_caching' );

When enabled, WC_Product_Factory caches loaded WC_Product objects in the product_objects WordPress object-cache group. WooCommerce marks that group non-persistent, so the optimization is request-local even when Redis or Memcached is installed. The cache saves repeated hydration work; it is not a durable catalog cache.

WordPress object cache returns object clones. Do not depend on object identity across repeated wc_get_product( $id ) calls, and do not assume mutating one loaded object changes another. A setter changes only that object until save() persists it.

Do not import Automattic\WooCommerce\Internal\Caches\ProductCache or its controller. They are internal implementation APIs. Use CRUD and WooCommerce's public feature check.

Invalidation boundaries

WooCommerce 11.0 invalidates request-cached product instances on: