Tropratik e-Facture

1. 01Make sure WooCommerce is installed and active, and that the server runs PHP 8.1 or later .
2. 02Install the plugin from the WordPress “Plugins” screen or upload its folder to /wp-content/plugins/ .
3. 03Activate the plugin from the “Plugins” menu.
4. 04Open WooCommerce → Tropratik e-Facture to configure the issuer, numbering, and invoice appearance.
5. 05Configure the Chorus Pro or Super PDP tab as needed, then use the test buttons before the first transmission.

Does the plugin send my invoices automatically?

Only if you enable automatic transmission for the relevant platform. Chorus Pro handles public-sector invoices; Super PDP handles B2B and B2C invoices. Manual transmission remains available from the orders list.

What invoice format is generated?

Invoices are generated in Factur-X PDF/A-3 format with XML compliant with the EN 16931 profile. The issuer remains responsible for tax rules and the information entered in WooCommerce.

My hosting provider is blocked by PISTE with a 403 error. What can I do?

The Chorus Pro tab provides a “Via VPS proxy” connection. Install the proxy on a server you control, enter its settings, and then use the test button. This test does not depend on the PISTE credentials or the technical account.

Can I customize the invoice layout?

Yes. The “Invoice appearance” tab lets you set the logo, colors, and font. You can also place a custom invoice.php template in wp-content/themes/your-theme/tropratik-e-facture/ to preserve the customization during updates.

Is the plugin compatible with HPOS?

Yes. The plugin is compatible with High-Performance Order Storage (HPOS) and classic order storage.

Can I retrieve invoices through the WooCommerce REST API?

Yes. The plugin adds a read-only tropratik_ef_invoice field to order responses. It includes the number, dates, customer type, Factur-X profile, PDF hash, and Chorus Pro and Super PDP statuses. It never exposes the file path on the server.

How are sensitive credentials and passwords stored?

PISTE, Chorus Pro, Super PDP, and proxy secrets are encrypted in the database with libsodium, or with AES-256-GCM through OpenSSL as a fallback. They are decrypted only during API calls.

The key is derived from the security salts in wp-config.php . If these salts are regenerated, the secrets must be entered again. To use an independent key during a migration or restoration, define the following in wp-config.php :

define( 'TROPRATIK_EF_ENCRYPTION_KEY', 'a-long-random-and-secret-string' );

Credentials stored in plain text by an earlier version are encrypted the next time the form is saved.