| 开发者 | faktura1 |
|---|---|
| 更新时间 | 2026年10月27日 00:48 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
Yes. An account and a valid company API token are required. This is a connector to the external service, not a standalone invoice generator.
WordPress administrators with manage_options can configure credentials and mappings. Users with manage_woocommerce can use the order document actions.
Yes. Clear both automatic creation status fields and disable automatic credit notes and payment updates. Document buttons remain available when the integration is enabled and authorized.
Yes. Map existing fields for company name and registration number; both are required for company invoices. VAT number and responsible person are optional. The plugin does not create new checkout inputs.
The integration uses WC_Order CRUD and declares compatibility with WooCommerce High-Performance Order Storage. It also supports legacy order storage.
After confirmation the plugin requests deletion in Faktura1. The local order reference is removed only after a successful response. Faktura1 business rules may refuse deletion, for example for an accounted document.
Uninstall removes plugin settings, the stored API token and nomenclature caches for the current site. Order document references and financial documents in Faktura1 are retained. Optional technical logs follow WooCommerce's log retention. Multisite installations must remove per-site settings individually; network-wide activation is not supported.
No. Optional WooCommerce diagnostics contain technical identifiers and error codes, not API tokens, complete billing payloads or complete API responses. Orders retain document references and sanitized integration errors.
Deactivate the copy in faktura1-woocommerce before activating the WordPress.org copy in faktura1-for-woocommerce. Do not activate both. Existing settings and order references use the same keys. Review and authorize the external service after upgrade.