Peppol E-Invoicing Access Point Connector for WooCommerce

核心功能

Generates Peppol BIS Billing 3.0 invoices in UBL 2.1 XML from each WooCommerce order, mapped from line items, tax rates and customer data

EN 16931 + BIS 3.0 validation runs in wp-admin before transmission, so rejected/malformed invoices are surfaced locally instead of failing at the receiver

Certified Peppol Access Point routing via API (B2Brouter, peppol.sh, Storecove or your existing provider) — no self-certification required

Participant lookup against the Peppol Directory / SML to confirm the buyer's Peppol ID is registered and reachable before sending

Hooks into the WooCommerce order lifecycle (woocommerce_order_status_completed, woocommerce_payment_complete) so e-invoicing fires automatically on the right status

HPOS-aware: reads and writes against WooCommerce High-Performance Order Storage (custom order tables), not just legacy post meta

Transmission status, Peppol message ID and validation errors stored against the order and shown in the order admin screen

WP-Cron retry queue for transient Access Point failures, with manual re-send action from the order list

Maps VAT categories, exemption reason codes, and seller/buyer Peppol endpoint IDs (e.g. VAT, GLN, EAS schemes) per EN 16931 rules

Belgium / EU B2B mandate alignment and ViDA-readiness in the document profile, configurable as national specifications evolve

Settings screen under WooCommerce admin for Access Point credentials, sender Peppol ID, document profile and environment (test/production)

Optional WPML and multisite-aware configuration so multi-store / multi-language setups send under the correct legal entity

Outbound XML and API payloads logged for audit and dispute resolution; archived copy retained against the order

Built against the WooCommerce REST API and WordPress action/filter hooks so your own automations can extend or override invoice mapping

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 WooCommerce 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

National Peppol mandates are arriving fast — Belgium's structured B2B e-invoicing requirement, Poland's KSeF, and the EU-wide ViDA timeline all push EU sellers toward machine-readable invoices. WooCommerce core has no concept of Peppol: it generates PDFs and emails, not UBL documents on a four-corner network. This connector closes that gap.

This is a build-to-order plugin. ECOSIRE builds it for your specific WooCommerce store, installs it on your WordPress site, configures your Peppol Access Point credentials, and supports it after go-live. It is not an instant WordPress.org or WooCommerce.com download — it is engineered against your tax setup, product catalogue, and the Access Point you choose.

On each qualifying order, the plugin hooks into WooCommerce's order lifecycle (woocommerce_order_status_completed, woocommerce_payment_complete) and builds a Peppol BIS Billing 3.0 invoice in UBL 2.1 XML. It maps your line items, tax rates, customer VAT/registration data, and currency into the EN 16931 semantic model, then runs EN 16931 + BIS 3.0 validation before anything is transmitted — so malformed invoices are caught in wp-admin, not rejected downstream.

Validated documents are routed through a certified Peppol Access Point (B2Brouter, peppol.sh, Storecove or your existing provider) over the API. The plugin performs participant lookup against the Peppol Directory / SML to confirm the buyer is reachable before sending, stores the transmission status and message ID against the order, and surfaces failures for retry via WP-Cron. Built HPOS-aware (custom order tables) and compatible with WPML and WooCommerce Subscriptions where relevant.

You own the code on your own server. ECOSIRE delivers a documented, supported plugin — not a black box.

你得到什么

A custom-built WooCommerce/WordPress plugin engineered for your store, installed on your site by ECOSIRE

Configuration of your chosen certified Peppol Access Point credentials and sender Peppol participant ID (test + production environments)

Field mapping from your WooCommerce tax classes, product catalogue and checkout fields into the EN 16931 semantic model

End-to-end validation test: sample orders sent through the Access Point's test corner and confirmed against EN 16931 / BIS 3.0

Admin documentation covering settings, the retry queue, validation errors and how to read transmission status

Post-launch support window and compatibility maintenance for WooCommerce / WordPress / PHP updates (per agreed plan)

这是给谁的

EU B2B WooCommerce seller facing a national mandate

A Belgian, Polish or other EU merchant whose B2B sales will soon require structured e-invoices over Peppol. They need every WooCommerce order turned into a compliant BIS 3.0 document and sent through a certified Access Point without rebuilding their store.

Finance / compliance lead at a growing online wholesaler

Responsible for getting invoices accepted and audit-ready. They care that documents pass EN 16931 validation before transmission, that message IDs and statuses are stored against each order, and that failures are visible and retryable rather than silently lost.

WooCommerce agency or in-house developer

Maintains a custom WooCommerce build (HPOS enabled, WPML, custom checkout fields) and wants Peppol handled by a documented, hook-friendly plugin they can extend via the WooCommerce REST API and WordPress filters, rather than a rigid off-the-shelf addon.

Peppol E-Invoicing Access Point Connector for WooCommerce 如何比较

标准	伊科西尔	定制建造	竞争对手
Peppol BIS Billing 3.0 / UBL invoice generation from WooCommerce orders	包含	部分支持	部分支持
EN 16931 validation before transmission	包含	部分支持	部分支持
Routing through a certified Peppol Access Point	包含	部分支持	部分支持
Participant lookup via Peppol Directory / SML before sending	包含	不包括在内	部分支持
HPOS (custom order tables) aware	包含	部分支持	部分支持
Built and field-mapped specifically for your store, tax setup and Access Point	包含	包含	不包括在内
Installed and supported on your site by the builder	包含	部分支持	不包括在内
Instant self-service marketplace download	不包括在内	不包括在内	包含
Ongoing compatibility maintenance as mandates / ViDA evolve	包含	不包括在内	部分支持

关于Peppol E-Invoicing Access Point Connector for WooCommerce的常见问题

How long does delivery take, since this is build-to-order?

This is a custom build, not an instant download. After a short scoping call to confirm your tax setup, Access Point choice and country profile, a standard build typically takes about 2 to 4 weeks to deliver, install on your site and validate against the Access Point's test environment before go-live. More complex setups (multisite, multiple legal entities, custom checkout fields) may take longer — we give you a firm timeline before you commit.

What ongoing support and updates are included?

Each engagement includes a post-launch support window plus compatibility maintenance, so the plugin keeps working as WooCommerce, WordPress and PHP are updated and as national Peppol specifications (and the ViDA timeline) evolve. ECOSIRE supports the plugin we built directly — bug fixes, configuration help and document-profile updates are handled under your agreed support plan rather than left to a generic marketplace forum.

Do I still need a Peppol Access Point provider?

Yes. Peppol is a four-corner network and only certified Access Points can transmit on it. This plugin is the bridge between WooCommerce and a certified Access Point (such as B2Brouter, peppol.sh or Storecove); it builds, validates and submits the invoice, but the certified provider performs the actual network transmission. We configure the connector against the provider you choose, or help you select one.

Will it work with my existing WooCommerce setup, HPOS and WPML?

It is built HPOS-aware, reading and writing against WooCommerce's High-Performance Order Storage (custom order tables) as well as legacy data where needed. WPML and multisite configurations are supported so multi-language or multi-store setups send under the correct legal entity and sender Peppol ID. Because we build to order, we engineer the field mapping around your actual checkout fields, tax classes and catalogue rather than assuming a generic store.

What happens if an invoice fails validation or the Access Point is unreachable?

Invoices are validated against EN 16931 and BIS Billing 3.0 in wp-admin before anything is sent, so malformed documents are caught locally and shown with the failing rule against the order. Transient Access Point failures are queued and retried via WP-Cron, and you can manually re-send from the order screen. Outbound XML and the Peppol message ID are stored against the order for audit and dispute resolution.