Issue invoices under Veri*factu without changing your shop

What it does, in one sentence

It turns every WooCommerce order into an invoicing record that follows RD 1007/2023 and Order HAC/1177/2024: it signs it with its hash, chains it to the previous one and, if you run it in VERI*FACTU mode, submits it to the AEAT.

• One record per invoice, with the SHA-256 hash calculated over the fields the regulation requires and chained to the previous record of the same series.
• The hash comes out the same as in the official examples: it reproduces the three cases in the technical specification document for the hash (v0.1.2), and the QR reproduces the four official URL variants.
• Records are never touched: they are inserted and never updated or deleted. The submission status lives in a separate table, so the tax content of a record never changes.
• Independent chains per taxpayer and consecutive numbering per series and per tax ID, as article 2 of the Order requires.
• Tax QR with the four parameters (tax ID, number, date and amount) printed on the invoice. If you have «PDF Invoices & Packing Slips» active, the PDF invoice comes out with the record number and date, the customer tax ID and the matching QR.
• Two modes: VERI*FACTU, which submits every record to the AEAT, or non-VERI*FACTU, which keeps them chained without submitting and logs the event records.
• The certificate, stored as it should be: the .p12 stays outside the public directory and encrypted, and its password is not kept in the database: it is read from the VF_CERT_PASS constant in wp-config.php.
• HPOS compatible, WooCommerce's high-performance order storage.
• AEAT test environment included: you invoice against the test environment until you decide to move to the live one.

What it is not, and it is worth saying before you buy: this covers Veri*factu, which means the invoicing records. B2B e-invoicing is a different set of rules (Law 18/2022 and RD 238/2026) and is not included. And there is no AEAT «approval»: what exists is the manufacturer's responsible declaration (article 15 of the RRSIF), reproduced in the plugin's Help tab.

What it asks of you: three pieces of data

Everything else —the system identifier, the version, the producer and the responsible declaration— travels in the code. You fill in your own details and that is it.

After that, place a test order at the status that issues the invoice and the record appears under Records, with its hash and its submission status. If something fails, the panel says so in the header and in the Summary: for example, that there is no certificate or that the submission was rejected.

What an invoice looks like

WooCommerce invoices come out with the tax details of the order, the record number and the tax QR with its four parameters. This is a sample one, with made-up data.

FaroWP Demo, S.L.

B12345678
Carrer Cedrers, 6 · 08184 Palau-solità i Plegamans (Barcelona)

Invoice 2026-0007 19/10/2026
VERI*FACTU

CustomerExample Workshops, S.L.
B87654321
Calle Mayor, 14 · 28013 Madrid

Order detailsOrder 1042 from the shop
Card payment · 19/10/2026
Simplified invoice

Item	Amount
Zancada theme · annual licence	65,00 €
Faro Factu plugin · annual licence	35,00 €

Net amount100,00 €

VAT 21 %21,00 €

Total121,00 €

Tax QR:

Invoice verifiable at the AEAT e-office.

Tax ID B12345678 · Series 2026-0007 · 19-10-2026 · 121,00 €

Registration record: 19-10-2026 10:42 · Hash chained to the previous record

This is a fake invoice: the tax ID does not exist. The QR is real and carries the four parameters the regulation requires —tax ID, number, date and amount—, so if you scan it the AEAT will tell you it cannot find that invoice. With a real one, it finds it.

Faro Factu SIF Pro

The directory version is free and complete for one shop and one tax ID. Pro is for those who invoice from several shops or for their own clients. It has no price yet: we will publish it here once it is settled.

Requirements and the small print

• WordPress 6.0 or later, WooCommerce 8.0 or later and PHP 7.4 or later.
• An electronic signature certificate in .p12 or .pfx format in the issuer's name. You upload it and set the password from the panel; both are stored encrypted and nobody has to edit files by hand. Without a certificate the plugin still issues and chains, but it cannot submit, and it warns you.
• On uninstall the settings are deleted, not the invoicing records: they have to be kept by law.
• The plugin ships with the manufacturer's responsible declaration and the system details already filled in; there is nothing to declare by hand.
• The licence covers a number of sites. If you change domain, it is moved from the client area.

Quick questions

If your shop already sells, it already has to invoice this way

The regulation requires computerised invoicing systems to keep chained records and to submit them. Faro Factu does it inside WooCommerce, without moving to another platform.

Coming soon See the free tax details plugin

In the meantime, the free plugin already works: it collects and validates the tax details of the order, and leaves the records ready for when you activate Faro Factu.