| 开发者 | nestero |
|---|---|
| 更新时间 | 2026年10月18日 23:56 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL v2 or later |
| 版权网址: | 版权信息 |
oid_unique) so one order never produces two documents,Fakturownia handles the submission to KSeF on its side, if your Fakturownia account is set up for it. The plugin checks the invoice data against KSeF limits before sending it, and shows the KSeF status Fakturownia returns when a document is issued or refreshed. Neither this plugin nor the Pro extension follows the KSeF status afterwards on its own — refresh the document on the order screen to see the current one.
Every skipped order is logged with a reason: manual mode, a zero-value order, a business/private rule, or the customer not asking for an invoice. Check Fakturownia → Logs, or open the order — the reason is shown in the metabox as well.
No. Two integrations issue two documents for the same order, and with KSeF both are sent to the tax authority. The plugin keeps one invoice per order: when Fakturownia already has a document with the order number, it does not issue another one and asks you to decide. A document the other integration issues at the very same moment cannot be seen in advance — the plugin then marks the order "Check" and does not e-mail its invoice. It also warns when another Fakturownia plugin, or the WooCommerce module in your Fakturownia account (Settings → Integrations and add-ons → E-commerce → WooCommerce), is connected to the store — switch one of them off. The automatic invoice e-mail waits two minutes after issuing, so the plugin can see the other document first.
The plugin reads the tax number from its own field first, then from Flexible Checkout Fields (_billing_tax_no) and common VAT number fields (_billing_vat_number, _vat_number, _billing_vat_id). For any other plugin, enter its order field name in Settings → Customers and tax numbers → "Tax number from another plugin", and switch off the plugin's own field so customers do not see two. The company name works the same way: the WooCommerce "Company name" field first, then _billing_company_name, or the field set in "Company name from another plugin". A company name is printed on the invoice instead of the customer's name; the tax number decides whether it is a company invoice.
Encrypted in the database with libsodium (XSalsa20-Poly1305), using a key derived from your site's authentication salts or from the NESTERO_FAKT_ENCRYPTION_KEY constant if you define one. The token is never printed in full in the admin and is masked in the logs.
No. The plugin remembers the address of the store that was connected to Fakturownia. A copy under another address, or a site whose environment type is not "production", sends nothing to Fakturownia. A moved store shows a notice with a "This is the production store" button; a test site can be allowed in Settings → Advanced, but only connect it to a test Fakturownia account.
The plugin found something it will not decide for you: a document in Fakturownia with the same order number but a different buyer or total, or an issued document whose totals differ from the order. Nothing is e-mailed to the customer. Open the order, check the document in Fakturownia and choose what to do. Fakturownia → Synchronisation lists all such orders.
No, unless you ask for it. The link between an order and its invoice number is often the only place your store remembers what a document was issued for, so it survives uninstalling. You can opt in to removing it in Settings → Advanced.
_billing_company_name, used with Flexible Checkout Fields), and any other field can be set in Settings → Customers and tax numbers._billing_tax_no) and common VAT number fields are read automatically, and any other field can be set in Settings → Customers and tax numbers. Before, such orders were invoiced as a consumer, without the tax number.