The agency problem: invoice support does not end at launch
Most WooCommerce builds test checkout, shipping, and confirmation emails. EU B2B invoice requirements often get discovered later: missing VAT fields, incorrect invoice numbers, no customer download area, or refunds without credit notes.
That creates low-margin support work for agencies. A reusable invoice workflow lets the agency sell a cleaner handoff: B2B checkout fields, invoice PDFs, credit notes, customer downloads, and accountant-ready order evidence.
Signals that your client needs an invoice workflow
Repeatable process
A better agency handoff for WooCommerce invoices
Discovery
Ask whether the store sells B2B, B2C, subscriptions, digital products, bank-transfer orders, or cross-border EU orders before selecting invoice settings.
Checkout fields
Standardize company name, VAT/BTW number, invoice email, PO reference, and optional buyer notes so client data is captured before payment.
Invoice trigger
Decide whether final invoices are issued on processing, completed, or paid status. Keep proforma and final invoice timing separate for bank-transfer clients.
Refund path
Create credit notes from refunds instead of editing old invoice PDFs. Keep the original invoice number visible in the audit trail.
Handoff
Document invoice-number format, VAT evidence fields, PDF email attachments, customer downloads, and accountant export expectations before launch.
One-off invoice setup vs. reusable agency workflow
| Area | One-off setup | Reusable workflow |
|---|---|---|
| Client onboarding | Rebuild invoice settings from scratch per client | Use the same VAT/invoice checklist for every EU WooCommerce store |
| Support tickets | Customers email the agency or client for missing PDFs | Invoice PDFs live in customer emails and My Account downloads |
| Refunds | Manual PDF edits or accountant-side corrections | Credit-note workflow linked to WooCommerce refunds |
| VAT data | Field snippets and notes differ per project | Order-level VAT/BTW fields are part of the invoice workflow |
| Launch QA | Only checkout payment is tested | Invoice numbers, attachments, downloads, and refund docs are tested before handoff |
Agency launch QA checklist
FAQ for agencies
Why should agencies care about invoice workflows before checkout goes live?
Because payment success is not the end of a B2B order. Clients still need VAT evidence, invoice PDFs, customer downloads, refund documents, and support-ready resend workflows after launch.
Is this only for Dutch agencies?
No. The checklist is useful for any agency building EU WooCommerce stores, but it explicitly includes Dutch BTW language because many Dutch webshops search for BTW factuur plugin solutions.
Can agencies use Lattice Invoices for multiple clients?
The early-access path is intended to qualify real store workflows first. Agencies should send the number of WooCommerce client stores, countries, VAT requirements, and whether a repeatable agency license is needed.
What is the fastest way to qualify a client?
Send the client store URL, country, B2B/B2C mix, payment methods, invoice-number format, VAT fields, and whether credit notes and accountant exports are required.