wc-customer-and-sessions

WooCommerce session data is unavailable in REST API, cron, and CLI contexts because WC()->session is not auto-initialized; you must call wc_load_cart() or WC()->initialize_session() to enable session reading and writing in these environments. This Skill defines those initialization rules.

To get customer billing details for both guest and logged-in users, read the active customer's billing and shipping data via WC()->customer. This Skill guides proper data retrieval and update rules that work consistently across frontend and non-frontend contexts.

You should not use PHP native sessions for WooCommerce cart and visitor data because they break with page caching, REST, AJAX, cron, and WP-CLI. This Skill guides data storage through WC()->session and WC()->customer abstractions instead.

The best way to store per-visitor cart state and feature flags in WooCommerce is using WC()->session to read and write ephemeral data. This Skill defines usage rules for session storage and auto-initialization to ensure data persistence without breaking page caching.

WooCommerce session handling does work with admin-ajax and WP-CLI, but WC()->session may be unavailable by default. This Skill ensures correct data flow by applying wc_load_cart() and WC()->initialize_session() to properly initialize sessions in these non-frontend contexts.

You need to initialize WooCommerce sessions manually in non-frontend contexts such as REST API requests, cron jobs, and WP-CLI commands where WC()->session is unavailable. This Skill defines when to call wc_load_cart() or WC()->initialize_session() to ensure proper data retrieval.