WooCommerce
HPOS, the blocks cart, Subscriptions and refunds — what is automatic and what needs checking.
updated
Outline — facts still to be confirmed
This article is a structured outline. Its headings and scope are settled; the
specific values, screens and steps are marked TODO(owner: verify)
until they have been checked against the plugin itself. Blueprint §7 is explicit
that no article may state plugin behaviour that has not been verified.
Confirmed today
- HPOS (High-Performance Order Storage) compatibility is declared, and order data is read through WooCommerce’s CRUD methods rather than direct database queries.
- Cart and checkout blocks compatibility is declared.
- The blocks AddToCart dedup path injects the event ID as a request header into the Store API call, which the server hook reads back. One ID, no extra round trip.
- Purchase is server-first, fired from the payment hook with an order-meta guard.
- Consent is stamped onto the order at checkout so webhook-time sends honour it.
Known verification gap
The blocks AddToCart path is covered by unit tests but has not been exercised by a real click-through on a live blocks cart. If your store uses the blocks cart, verify AddToCart specifically before trusting it. See AddToCart.
Outline still to fill
Subscriptions
TODO(owner: verify) — which subscription lifecycle events are sent, and what happens on a renewal versus an initial order.
Refunds
TODO(owner: verify) — trigger conditions, partial versus full refunds, and per-platform mapping.
Deep product data
TODO(owner: verify) — the catalogue fields sent with commerce events and how variations are identified.
Was this page helpful?