Keep WooCommerce as your sales system
The plugin reads orders and refunds through WooCommerce CRUD APIs and sends only a neutral payload to Kairoseth Fiscal.
VERIFACTU FOR WOOCOMMERCEConnector v0.3.0 released
VeriFactu for WooCommerce without replacing your store or duplicating fiscal logic.
We connect WooCommerce orders, invoices, and refunds to Kairoseth Fiscal. You keep WordPress and WooCommerce while the fiscal layer, preflight, and reconciliation stay centralized outside the store.
WHY THIS INTEGRATION
Your store keeps selling. Kairoseth Fiscal adds the VeriFactu layer.
The connector does not turn WordPress into a second fiscal engine. It extracts commercial facts and delegates classification, AEAT rules, submission, and reconciliation to the fiscal core.
HPOS compatible
The connector declares HPOS compatibility and avoids direct access to legacy order tables or metadata APIs.
Preflight before fiscalization
Validate an order before creating a fiscal record. If data or mapping is incomplete, the workflow blocks before issuing.
Retry without duplicate invoices
Idempotency and reconciliation prevent a network retry from becoming another fiscal operation.
Refunds handled as corrective operations
Each refund has its own identity and uses server-side fiscal configuration; WooCommerce never decides R1–R5 or correction type.
VeriFactu presentation ready for your renderer
WooCommerce does not ship one universal PDF engine. The plugin stores a neutral presentation contract so your invoice renderer can consume QR, URL, and required text.
FISCAL CONNECT IMPLEMENTATION
What we review before go-live.
We do not sell only a ZIP. Integration depends on fiscal numbering, PDF rendering, refunds, and the quality of data already present in your WooCommerce store.
Review your current invoicing flow
We check where the fiscal invoice number comes from, which PDF renderer you use, how refunds work, and which data is available on the order.
Install connector v0.3.0
The integration starts from Kairoseth Fiscal's published and reproducible WooCommerce artifact, not duplicated fiscal code inside the store.
Configuration and preflight
We define server-side mapping and validate test orders before allowing fiscal side effects.
Test order and refund flows
We verify an invoice and, when relevant, a corrective refund including idempotency and status updates.
Integrate your PDF renderer
We review how your existing renderer consumes VeriFactu presentation data so you are not forced to replace tools that already work.
Handoff and support
Go-live leaves the configuration, validation checks, and support channel documented for your Fiscal Connect setup.
HOW IT WORKS
A WooCommerce → VeriFactu flow designed to fail closed.
Validate first, fiscalize second. When an operation already exists, reconcile it instead of issuing again.
WooCommerce provides commercial facts
Order data, configured invoice number, date, customer, totals, currency, and tax lines.
Kairoseth Fiscal runs preflight
The server-side MappingProfile validates and supplies sensitive fiscal classification that WooCommerce must not decide.
The operation is created or reconciled
Idempotency keeps a stable identity. If recordId already exists, the connector refreshes state instead of issuing again.
WooCommerce displays operational state
The order stores normalized state and a traffic-light summary for invoice and refunds without storing the AEAT certificate.
TESTED COMPATIBILITY
Current WooCommerce, HPOS, and three real CI combinations.
Compatibility is validated using the reproducible ZIP and public WooCommerce APIs, not only through a supported-version claim.
- WordPress 6.5+
- WooCommerce 8.2+
- PHP 7.4+
- HPOS declared compatible
- Real matrix validated with WooCommerce 8.2, 11.0, and 11.1
- Action Scheduler with WP-Cron fallback
WordPress 6.5 · WooCommerce 8.2.0 · PHP 7.4
Connector installation and smoke test completed successfully.
WordPress 7.0.4 · WooCommerce 11.0.1 · PHP 8.2
Connector installation and smoke test completed successfully.
WordPress 7.1 · WooCommerce 11.1.0 · PHP 8.3
Connector installation and smoke test completed successfully.
QR AND INVOICE
You are not forced to replace your PDF plugin to consume the VeriFactu presentation contract.
WooCommerce has no universal PDF renderer. The connector therefore stores the presentation authored by Kairoseth Fiscal and exposes helpers, filters, and events that an invoice renderer can consume. This avoids rebuilding taxpayer ID, URL, or regulatory text inside each PDF plugin.
FAQ
WooCommerce and VeriFactu questions.
Key points before connecting a store.
Is there a WooCommerce VeriFactu plugin in Kairoseth Fiscal?
Yes. Technical release v0.1.0 publishes WooCommerce connector v0.3.0. The plugin stays intentionally thin: it extracts order data, runs preflight, creates or reconciles the record, and keeps AEAT rules inside the fiscal engine.
Does it work with WooCommerce HPOS?
Yes. The connector declares HPOS compatibility and uses WooCommerce CRUD APIs for both orders and refunds.
Does WooCommerce automatically provide the fiscal invoice number?
WooCommerce core creates orders but does not define one universal fiscal numbering source. Kairoseth Fiscal requires an explicit source: an invoice plugin meta key, the order number only when the business confirms it is also the fiscal number, or a fail-closed state when no valid source exists.
What happens with refunds?
Refunds are processed as independent corrective operations. They require their own fiscal number and a server-side corrective MappingProfile; the plugin does not infer sensitive fiscal classification.
Does the plugin inject the QR into every WooCommerce PDF plugin?
WooCommerce has no single universal PDF engine. The connector stores and exposes a neutral VeriFactu presentation contract so the invoice renderer in use can integrate it without rebuilding AEAT rules.
Is the AEAT certificate stored in WordPress?
No. The certificate and sensitive fiscal credentials remain inside the secure Kairoseth Fiscal runtime.
Does publishing the plugin mean my store can enable AEAT production immediately?
No. Connector v0.3.0 is published and tested, but fiscal production activation is a separate gate. Controlled access refers to assisted fiscal go-live and onboarding, not to a pending connector release.
How much does the WooCommerce integration cost?
We are not publishing amounts until W4 closes unit economics and support. The planned model separates setup where needed from a recurring Fiscal Connect fee.
TRUST & CONTROL
Authority stays explicit as the platform grows.
Kairoseth separates identity, organization scope, product roles and product capabilities. A login route, browser state or AI response never becomes an authorization boundary by itself.
KAIROSETH PLATFORMCONTROL PLANE
- Identity
- Shared account
- Verified
- Organization
- Tenant scope
- Required
- Product
- RBAC assignment
- Explicit
- Sensitive actions
- Policy gate
- Controlled
Organization scope
Customer resources and access are resolved inside an active organization context rather than treated as global account state.
Product-scoped roles
Owner, Admin and Member authority is assigned per product. Organization membership alone does not automatically grant every product.
Server authority
Sensitive access, policy and capability decisions remain authoritative on the server instead of trusting client UI state or model output.
Controlled execution
Capabilities that can act are introduced behind explicit grants, staged gates and audit rather than implied autonomy.
Public trust evidence
Review the customer-facing policies that define privacy, security reporting, acceptable use and the current legal operating framework.
KAIROSETH FISCAL + WOOCOMMERCE
Request WooCommerce assessmentShow us how you invoice in WooCommerce today.
We review your invoice-number source, current PDF renderer, refunds, and available data to define the integration without unnecessarily changing your store.