WooCommerce & integrations
WooCommerce provides REST and webhook interfaces for external systems, but a production integration still needs a source-of-truth model, duplicate handling and failure recovery.
Direct answer
WooCommerce’s current WordPress-integrated REST API uses v3 as the primary endpoint version. HPOS has been enabled by default on new installations since WooCommerce 8.2, so custom integrations should rely on supported WooCommerce APIs rather than direct post-table assumptions.
Current facts
Answer scope
REST is useful for reading and changing resources, while webhooks can notify another system when an event occurs. Many integrations use webhooks for triggers and REST for reconciliation or enrichment.
The design should account for webhook retries and events that arrive more than once.
Products, prices, stock, customers and orders may have different owners.
A field-by-field ownership matrix prevents two systems from overwriting each other in a loop.
HPOS stores orders in dedicated WooCommerce tables and is the default for new installations from 8.2. Supported CRUD and REST APIs insulate integrations from storage differences.
Direct SQL against legacy post tables creates unnecessary compatibility risk.
Stable external IDs, order IDs or event IDs can help ensure retries do not create duplicate orders or apply stock twice.
Record the synchronization state so operations can distinguish waiting, completed and failed records.
Periodic reconciliation can compare WooCommerce orders or inventory with the external system and flag mismatches that real-time events missed.
This is especially valuable when the integration crosses vendor APIs outside your direct control.
Questions
WooCommerce currently documents v3 as the primary WordPress-integrated REST API version.
REST performs requests to read or modify data. Webhooks notify a destination when configured events occur.
Supported REST/CRUD integrations should be insulated from the storage change. Code that directly assumes orders are WordPress posts may need changes.
Evidence
First-party platform documentation and clearly labelled public market benchmarks used for factual claims on this page. A source link does not imply endorsement.
Orders, customers, products and external-system integration.
Event-driven order and customer workflows.
Current order-storage architecture, compatibility considerations and the fact that HPOS is enabled by default on new stores from WooCommerce 8.2 onward.
Start a conversation
Send the current setup and the result you need. I will review the problem and suggest the most practical next step.