E-Invoice Finder
Menu
Countries Compare software Deadlines Guides Checker Check obligation
ENFRDEPLNL
Poland guide · WooCommerce + KSeF

WooCommerce KSeF integration checklist for Poland

Practical WooCommerce KSeF checklist for Polish stores: B2B invoice triggers, FA(3) XML, API connection, VAT data, corrections, status handling and accountant workflow.

Quick verdict:
  • Start with the order trigger: decide exactly when a WooCommerce order becomes a Polish B2B structured invoice.
  • Test FA(3), KSeF status return, rejected NIP, refund and accountant archive before trusting any plugin.
  • Assign an owner for API downtime and failed submissions so the store does not silently miss invoice deadlines.
Check my Poland roadmapOfficial sources
Last checked: 30 June 2026Based on official sourcesClear summaryBusiness guidance, not legal advice
Official sources prioritized
Last-checked dates visible
Free checker, no signup required

What you need to know

Guide

Why WooCommerce stores need a KSeF-specific check

WooCommerce is flexible, but KSeF is a regulated invoice workflow rather than a normal store email. The Polish KSeF portal explains that mandatory issuing entered in phases: from 1 February 2026 for taxpayers with 2024 sales above PLN 200 million including VAT, and from 1 April 2026 for other taxpayers, with specific relief for very small monthly amounts until the end of 2026. Store owners should therefore test the exact invoice path before relying on an existing PDF or accounting extension.

Guide

What to map from WooCommerce before choosing a connector

List the fields that travel from checkout to invoice: buyer legal name, NIP/VAT number, billing address, delivery address, currency, discounts, shipping, VAT rate, payment method, order number, refunds and credit notes. If B2C and B2B orders share the same checkout, add a clear B2B invoice trigger so consumer receipts do not become accidental KSeF cases and business invoices are not missed.

Guide

KSeF terms to use in vendor calls

Use precise vocabulary: KSeF, Krajowy System e-Faktur, FA(3), XML, KSeF-2.0-API, UPO or submission evidence, KSeF number, authentication, token/certificate, NIP, structured invoice, correction invoice, offline or failure mode, archive, accountant access, ERP/accounting export and WooCommerce webhooks. A vendor that cannot discuss these terms may only be selling a document template.

Guide

Demo scenario for WooCommerce + KSeF

Ask the provider to create a realistic Polish B2B order in WooCommerce, convert it into FA(3) XML, validate mandatory fields, send it through the KSeF path, show the KSeF number and status, then store the evidence back against the WooCommerce order and accounting record. Repeat the demo with a discount, shipping line, reverse correction, rejected buyer NIP and terugbetaling.

Guide

Integration choices

Small stores may use an invoicing/accounting plugin connected to KSeF. Higher-volume stores often need a middleware or ERP/accounting connector that consumes WooCommerce order data and owns KSeF submission, retries, status logs and archive. The best choice depends on order volume, multi-channel sales, accountant workflow, Polish VAT scope and how much manual review is acceptable before invoice issue.

Guide

Risks and mistakes to avoid

Do not assume that a PDF invoice attached to an order email is KSeF-bereit. Do not let the store create invoices before buyer data is validated. Do not ignore failed submissions, duplicate invoices, terugbetalingen, partial returns or month-end cut-off. The painful failures usually happen in exceptions, not in the first clean test invoice.

Guide

Decision criteria

Score providers on FA(3) support, official-source update monitoring, KSeF 2.0 API readiness, WooCommerce data mapping, validation before submission, status visibility, herhaling handling, corrections, terugbetalingen, archive search, accountant permissions, security, performance at peak order volume and export if you later change systems.

Guide

Next action this week

Build a test pack with one domestic B2B order, one B2C order that should not be sent as a B2B invoice, one discount and shipping order, one rejected NIP, one correction/terugbetaling, one failed API submission, one accountant export and one archive search. Send the same pack to your WooCommerce developer, accounting software provider and accountant.

Guide

Practical question summary

For WooCommerce + KSeF Poland integration checklist: Most KSeF questions are about who must use the system, whether current accounting software is ready, how authentication works, how corrections are handled, whether ecommerce or ERP needs API integration, and how accountants access invoice data. This guide focuses on those operational decisions.

Guide

Decision framework for businesses

For WooCommerce + KSeF Poland integration checklist: A KSeF-ready workflow should show who creates invoices, who submits them, who monitors status, who handles rejection or correction, how invoices are archived and how the accountant sees the records.

Guide

How to use this guide

Use this guide to decide whether WooCommerce + KSeF Poland integration checklist affects your Poland workflow and which evidence is still missing. Start with KSeF authentication, structured invoice submission, invoice status handling, then test submit a KSeF invoice and simulate an API rejection before comparing software.

Guide

Data and terms to prepare

For WooCommerce + KSeF Poland integration checklist, the important terms are WooCommerce + KSeF Poland integration checklist, Poland, KSeF authentication, structured invoice submission, invoice status handling, corrections and rejections, accounting or ecommerce integration. Clean these fields in customer, supplier, tax and accounting records before rollout; otherwise validation and support issues appear during daily invoicing.

Guide

Software proof to request

For WooCommerce + KSeF Poland integration checklist, ask vendors to show show KSeF authentication, submission status, corrections, permissions and accounting export using your examples. The demo should cover submit a KSeF invoice, simulate an API rejection, create a correction, verify user permissions and explain who handles errors, corrections, archive access and accountant handoff for KSeF authentication, structured invoice submission, invoice status handling.

Guide

Evidence before rollout

Keep official links, screenshots, test invoices and the decision reason for WooCommerce + KSeF Poland integration checklist. For WooCommerce + KSeF Poland integration checklist, the implementation file should prove how KSeF authentication, structured invoice submission, invoice status handling, corrections and rejections were checked, not just that a tool was selected.

Guide

Decision checkpoint

Do not close WooCommerce + KSeF Poland integration checklist until someone can explain WooCommerce + KSeF Poland integration checklist in Poland, name the workflow owner, show one tested invoice scenario and describe how the team avoids choosing software for Poland before proving the real WooCommerce + KSeF Poland integration checklist workflow.

Checklist

Separate B2B invoice orders from B2C consumer orders at checkout

Validate NIP/VAT, legal name, address, VAT rates, discounts and shipping before invoice issue

Confirm FA(3) XML generation and KSeF 2.0 API or provider workflow

Show KSeF number, status response, herhaling queue and rejection reason inside the operational process

Test corrections, terugbetalingen, duplicate prevention and month-end cut-off

Give the accountant searchable access to XML, statuses, order references and exports

Document owner for failed submissions, API downtime, plugin updates and official KSeF changes

FAQ

Does a WooCommerce PDF invoice plugin make a Polish store KSeF-bereit?

Usually no. A PDF plugin may create a readable invoice for the customer, but KSeF readiness requires structured FA(3) data, submission through the KSeF workflow where applicable, status evidence, correction handling and archive access.

When should WooCommerce stores prepare for KSeF?

Stores with Polish B2B invoice scope should prepare before the relevant mandatory phase. Official Polish materials describe phased dates from 1 February 2026 for the largest taxpayers and 1 April 2026 for other taxpayers, with special temporary rules for very small monthly amounts.

What WooCommerce data causes KSeF problems?

Common problem fields include buyer NIP, legal name, address, VAT rate, discounts, shipping fees, currency, order references, terugbetalingen and corrections. These should be validated before invoice submission rather than fixed after rejection.

Can my accountant handle KSeF outside WooCommerce?

Possibly, but the handoff must be explicit. Decide whether WooCommerce, accounting software, ERP, middleware or the accountant creates and submits the structured invoice, and how the KSeF number returns to the order record.

Do B2C orders go to KSeF?

Do not assume one rule for every order. Separate consumer and business flows and confirm Polish tax scope with official sources or advisers. The operational point is that checkout must clearly identify which orders become B2B invoices.

What should a provider demo include?

A useful demo includes a real WooCommerce order, FA(3) validation, KSeF submission, status response, KSeF number storage, rejection repair, correction/terugbetaling handling and accountant-visible archive search.

What happens if KSeF or the connector is unavailable?

Ask for the documented failure mode: queueing, herhaling rules, who is alerted, how invoices are later reconciled, and what evidence is preserved. Do not rely on silent background herhaalpogingen without an owner.

Is this tax advice?

No. This is practical software-readiness guidance for ecommerce teams. Confirm legal scope, dates and special cases with official Polish sources and qualified advisers.

What do businesses usually ask about KSeF?

For WooCommerce + KSeF Poland integration checklist: They ask about software readiness, API integration, authentication, corrections, accountant access and ecommerce workflows.

What is the most practical KSeF risk?

For WooCommerce + KSeF Poland integration checklist: The practical risk is late discovery that permissions, corrections or invoice status handling do not match the business process.

What should I test first for WooCommerce + KSeF Poland integration checklist?

For WooCommerce + KSeF Poland integration checklist, start with submit a KSeF invoice, simulate an API rejection, create a correction because those scenarios reveal whether the workflow is practical.

What is the main risk for WooCommerce + KSeF Poland integration checklist?

The main risk is choosing software for Poland before proving the real WooCommerce + KSeF Poland integration checklist workflow.

Key regulations, formats and terms

PolandKSeFKrajowy System e-FakturPolish Ministry of Financepodatki.gov.plstructured invoiceAPI authenticationinvoice correctionsaccounting softwareVATSMEecommerceEuropean CommissioneInvoicingEN 16931Directive 2014/55/EUstructured electronic invoiceVAT automationcross-border tradeWooCommerce + KSeF Poland integration checklist

Poland — Country hub

Poland

Open country hub →

Use the country hub to see every related deadline, checklist, format guide and software comparison for this market.

Continue reading

Official sources

We prioritize official government and EU sources where available and keep last-checked dates visible for mandate-sensitive pages.