WooCommerce Invoice Plugin Setup Checklist Before Launch

Why setup matters more than the PDF template

Most WooCommerce invoice plugin comparisons focus on templates and email attachments. EU VAT stores need to go further: VAT/BTW fields must be captured before payment, invoice numbers must be predictable, refunds need credit notes, and customer downloads must keep support out of the inbox.

Use this checklist before buying, migrating, or enabling an invoice plugin. If several items are missing, the store likely needs a workflow-first invoice plugin rather than another styling add-on.

Before checkout

✓Company name, VAT/BTW number, invoice email, PO/reference, and billing country are collected before payment

✓VAT validation rules are clear: optional, required for B2B, or validated against VIES when available

✓Customers know whether the order will create a receipt, proforma, final VAT invoice, or credit note

When the order is paid

✓Invoice number is created from a clean yearly sequence, not from abandoned checkout attempts

✓Invoice date, paid date, VAT amount, tax rate, payment method, and customer VAT ID are stored on the order

✓The PDF invoice is attached to the correct WooCommerce emails and can be regenerated by an admin

After purchase

✓Customers can download their invoice from My Account without emailing support

✓Refunds create a credit note with its own number and a reference to the original invoice

✓Accountant export includes invoice number, order ID, VAT fields, PDF link, payment status, and credit-note relationship

Setup risks that cause invoice cleanup later

Risk	What happens later	Fix before launch
Only testing a happy-path card payment	Bank transfer, PayPal, Stripe refund, Klarna capture, or partial-payment orders can create invoice gaps later.	Run a setup test for each payment method before switching the plugin on for real orders.
Using order IDs as invoice numbers by default	Failed and cancelled orders can make the invoice sequence harder to explain to an accountant.	Choose a separate invoice prefix and yearly sequence such as INV-2026-000148.
Collecting VAT details in order notes	PDF templates, exports, customer downloads, and corrections become manual because the data is not structured.	Use dedicated checkout/order meta fields for VAT/BTW number, PO/reference, and invoice email.
Ignoring refunds until the first chargeback or return	The store owner edits the original invoice or sends a manual negative PDF with no audit relationship.	Define credit-note numbering and original-invoice references before launch.

Six setup tests to run before real orders

1Place one B2C order and confirm the invoice PDF shows correct VAT totals.

2Place one B2B order with company/VAT details and confirm the data appears on the PDF and export.

3Refund a paid order and confirm a credit note is created instead of editing the original invoice.

4Open My Account as the customer and confirm the invoice download link works after logout/login.

5Send a test processing/completed order email and confirm the invoice attachment is present.

6Export one month of orders and check whether the accountant can match invoice numbers, VAT totals, payments, and refunds.

FAQ

Should I complete this checklist before buying a WooCommerce invoice plugin?

Yes. It prevents buying a PDF-only plugin when the real problem is VAT/BTW checkout data, refund credit notes, customer downloads, or accountant export.

What is the most common setup mistake?

Testing only a successful card payment. EU stores also need to test refunds, bank transfers, PayPal/Stripe edge cases, customer downloads, invoice email attachments, and month-end export.

How does this relate to Lattice Invoices?

Lattice Invoices is being positioned around this exact setup path: structured VAT fields, predictable invoice numbering, PDFs, credit notes, customer downloads, and accountant-ready order metadata.

Can Lattice review my setup before early access?

Yes. Use the early-access CTA with your store URL, country, current invoice plugin, payment methods, desired invoice number format, and refund requirements.