Compatibility
Which WooCommerce surfaces and third-party plugins were executed against, and the honest boundary of what a compatibility claim covers.
Core WooCommerce surfaces
- High-Performance Order Storage (HPOS)
- Cart and Checkout Blocks
- The classic product editor and the new block product editor
- The WooCommerce REST API and the Store API
- Action Scheduler, with a WP-Cron fallback
- WordPress Multisite, with per-site data isolation
Because converted prices are written into WooCommerce’s own fields rather than filtered at read time, most integration is not integration at all: a surface that reads WooCommerce’s stored price simply reads the correct number.
Third-party products executed for the 1.0.0 verification matrix
- Elementor Free and Elementor Pro
- WooCommerce Subscriptions
- WooCommerce Product Bundles
- WooCommerce Composite Products
- WooCommerce Product Add-Ons
- WooCommerce Dynamic Pricing
Bundles, Composite Products and Add-Ons apply their components or fees after Price Anchor has written the store-currency base price, which is why they compose cleanly.
The boundary of a compatibility claim
Compatibility applies wherever a surface reads WooCommerce’s native product and cart data. Three things fall outside that, and no amount of testing changes it:
- A manually typed builder price is static text. It is not WooCommerce price data and cannot update.
- A separate payment widget that does not read the WooCommerce cart is outside the plugin’s reach.
- A full-page cache or CDN may serve pre-sync HTML until its purge completes. That is caching behaviour, not a pricing bug, but it looks identical to a customer.
Do not run a currency switcher alongside this
A currency switcher and Price Anchor are trying to control the same numbers for opposite reasons. Running both produces prices neither plugin intends. Pick the one that matches your business model: switcher if customers should choose a currency, Price Anchor if you buy in one currency and sell in another.
Page caching
Server-level page-cache compatibility with licensed commercial cache products has not been fully verified end to end and is reported as unverified rather than claimed as passing. The practical guidance is unchanged: purge after a repricing pass.