The honest summary
The WooCommerce PDF Invoices and Packing Slips plugin is the most-installed free invoice plugin for WooCommerce. It works. It renders simple Latin-script invoices reliably, has a large extension ecosystem, and is genuinely fine for the audience it was built for.
It renders through DOMPDF, mPDF, or TCPDF. Those three PHP-based PDF engines share the same architectural limitation: they cannot lay out complex scripts (Indic, Arabic, Hebrew, Thai, Khmer) correctly. The maintainers have publicly acknowledged this on the WordPress.org support forum.
Paperbolt renders through Chromium running on our infrastructure. Your WordPress install makes a small API call. The Chromium engine handles complex scripts the same way Chrome does, with no font installation. It also emits validator-passing structured e-invoices on the Pro tier.
If your customers do not read complex scripts and you do not face an e-invoicing mandate, the incumbent is fine. If either applies to you, the rendering pipeline matters.
Feature matrix
| Capability | Paperbolt | WooCommerce PDF Invoices |
|---|---|---|
| Free WordPress plugin | yes | yes |
| WooCommerce order invoices | yes | yes |
| Packing slips | yes | yes |
| Sequential invoice numbers | yes | yes |
| Pure-PHP rendering | no, cloud | yes (DOMPDF / mPDF / TCPDF) |
| Chromium rendering | yes | no |
| Indic, Arabic, Hebrew, Thai, CJK | yes, no config | not without third-party add-ons and font packs |
| Modern CSS (Flexbox, Grid) | yes | partial |
| Webfonts via @font-face | yes | partial |
| Validator-passing Peppol BIS 3.0 | yes (Pro) | no |
| Validator-passing ZUGFeRD / Factur-X | yes (Pro) | no |
| Works on shared hosting | yes (no PHP fonts) | yes if DOMPDF runs |
| Theme-update-resistant | yes, renderer in cloud | mostly |
| Custom numbering rules | yes (Pro) | yes (paid extension) |
| Async bulk generation | yes (Pro) | yes (paid extension) |
Pricing
| Plan | Paperbolt | WooCommerce PDF Invoices |
|---|---|---|
| Plugin | Free | Free |
| Free generation tier | 100 PDFs/mo | unlimited (runs locally) |
| Lowest paid | $9/mo Starter (500 PDFs, branding off) | $79/year Pro Bundle (extensions) |
| Validator-passing e-invoicing | $19/mo Pro | not available |
The pricing models are different because Paperbolt processes PDFs in the cloud (per-PDF cost) while the incumbent processes them on your server (per-license cost). At low volume, the incumbent's free tier is unbeatable. At high volume, the incumbent's Pro extensions stack quickly. At any volume where the multilingual or regulatory features matter, the cost comparison is not the deciding factor.
When the incumbent is the right choice
- You sell in English, French, German, Italian, or Spanish to a non-EU customer base.
- Your host runs DOMPDF fine, you have already configured your fonts, and the output looks correct.
- You want the simplest possible setup: install, activate, done.
- You do not face an EU e-invoicing mandate.
- You generate few enough invoices monthly that a per-PDF cost would be silly.
When Paperbolt is the right choice
- Your customers read in non-Latin scripts. The DOMPDF / mPDF / TCPDF engines cannot handle Indic, Arabic, Hebrew, Thai, or Khmer correctly. This is a known architectural limitation publicly acknowledged by the incumbent plugin maintainers. Paperbolt renders through Chromium, which handles all of these natively.
- You face the Belgian B2B mandate (2026-01-01), the German mandate (2027-01-01 / 2028-01-01), or Saudi ZATCA Phase 2. The Pro tier emits validator-passing structured XML.
- Your shared host cannot install the 30-MB Unicode font packs the PHP engines need for complex scripts.
- You want your invoice templates to use modern CSS (Flexbox, Grid, custom webfonts) and have them render pixel-identically to your browser preview.
- Theme updates have broken your invoices in the past and you want the renderer decoupled from your site code.
What we will not claim
We will not claim Paperbolt is better for English-only WooCommerce stores on cheap hosting. The incumbent free plugin is excellent at that, runs locally, and has been refined over a decade. If that describes you, install it; you do not need a cloud rendering API.