WooCommerce integration
Configure the store connector and official plugin, including checkout tax IDs and connection diagnostics.
The connector processes orders and refunds in Factuarea. The official WordPress plugin adds the store-side setup, checkout tax-ID capture and invoice access. Download the v0.1.0 release; this guide does not depend on a WordPress directory listing. It requires WordPress 6.5+, WooCommerce 8.9+ and PHP 8.1+.
Set up the connection
Install the release ZIP in WordPress and authorize WooCommerce in Factuarea. Follow the store lifecycle to associate the provider connection with the shop. Configure the plugin with its Factuarea API key, store ID and webhook signing secret. The API key reads the store and invoice PDFs; the signing secret verifies incoming notifications. Keep those credentials separate.
Review checkout NIF collection, whether prices include tax, the simplified-invoice threshold and automatic sending before enabling the integration. The plugin stays inactive until explicitly enabled. A store in test mode discards order events with an explained reason; test credentials also suppress real email and public webhook delivery.
Check both directions
curl -X POST "https://api.factuarea.com/v1/woocommerce/stores/$STORE_ID/connection-test" \
-H "Authorization: Bearer $FACTUAREA_API_KEY" \
-H "Idempotency-Key: woocommerce-check-2026-09-08"The plugin’s connection check reads the Factuarea store. The REST operation above checks Factuarea’s access to WooCommerce and needs woocommerce_store:write. woocommerce_credentials_rejected calls for checking the provider authorization; woocommerce_rest_route_missing calls for checking the WooCommerce REST routes; woocommerce_store_unreachable calls for checking availability and connectivity. Inspect the 200 response fields, not only the HTTP status.
After a paid order or refund, inspect the integration inbox and the resulting order.invoiced or order.refunded event. Reconciliation may recover missed provider notifications. Before manually creating an invoice, check whether the event is parked and whether its document already exists, to avoid invoicing the same order twice.