WooCommerce Marketplace VAT Invoices: Multi-Vendor Invoice Checklist

Why marketplace invoices fail inside WooCommerce

A marketplace checkout can look simple to the buyer while the backend has multiple tax and accounting realities: one customer payment, several vendors, commission or payout records, B2B VAT fields, shipping/tax splits, and refunds that only affect part of the order.

Before buying a WooCommerce invoice plugin, confirm it can keep invoice documents and export data connected to the order, vendor, customer, and refund records. Otherwise every accountant handoff becomes manual reconciliation.

Marketplace invoice risk checklist

✓The customer receives a payment receipt, but the invoice does not explain whether the marketplace or vendor is the seller of record.

✓Vendor commission, platform fee, VAT, shipping, discount, and refund data live in separate reports that cannot be matched to the invoice PDF.

✓B2B buyers enter a VAT number after purchase by email, so the finance team manually edits invoice details outside WooCommerce.

✓Partial refunds or vendor cancellations create store-credit notes manually, with no link to the original customer invoice.

✓The accountant gets order exports, vendor payout exports, and PDF files with no shared invoice number or tax-treatment field.

✓Customers ask support for invoice copies because marketplace account pages show orders but not retained invoice and credit-note documents.

Weak setup vs marketplace-ready invoice workflow

Scenario	Weak setup	Marketplace-ready workflow
Marketplace is seller of record	The store issues a generic WooCommerce receipt while vendor payouts are handled later in spreadsheets.	The customer invoice uses the marketplace legal seller details, a dedicated invoice sequence, VAT totals, PDF retention, and a separate export for vendor commission/payout reconciliation.
Vendor is seller of record	The customer sees one checkout, but invoices are manually produced per vendor after the order is already paid.	Capture vendor identity, seller-of-record rules, invoice metadata, and customer download links so each invoice document can be matched to the order and payout records.
EU B2B buyer with VAT number	VAT numbers are stored as notes and do not reliably appear on marketplace invoice PDFs, reverse-charge wording, or accounting exports.	Collect VAT fields at checkout, keep the validation/tax-treatment reason with the invoice, print reverse-charge wording when needed, and include the fields in exports.
Refund across one vendor line	A partial refund updates the WooCommerce order total but leaves the customer invoice, vendor payout, and credit-note evidence disconnected.	Issue a linked credit note for the refunded line, preserve the original invoice, and export the invoice-credit-note relationship for bookkeeping.

Questions to ask before choosing a plugin

1Does the plugin support a clear seller-of-record workflow for marketplace vs vendor invoices?

2Can invoice numbers be separate from WooCommerce order IDs and still map back to vendor payout records?

3Can the PDF template include VAT number, company name, PO/reference fields, vendor identity, VAT totals, and reverse-charge wording where needed?

4Can refunds create linked credit notes without overwriting the original marketplace invoice?

5Can customer account pages expose invoice and credit-note downloads without support manually resending PDFs?

6Can exports include invoice number, order ID, customer VAT fields, vendor split/payout reference, VAT totals, and credit-note relationships?

FAQ

Do WooCommerce marketplaces need a different invoice workflow than a normal store?

Usually yes. A marketplace invoice workflow has to clarify seller-of-record rules, vendor identity, platform fees or commission evidence, VAT metadata, customer PDFs, refund credit notes, and accountant exports. A normal PDF receipt plugin often stops at order totals.

Should each vendor get a separate invoice sequence?

It depends on the legal seller-of-record setup. The key buyer question is whether the invoice plugin can keep invoice numbers, vendor references, customer VAT fields, and payout/export data connected instead of forcing manual spreadsheets.

What breaks first in marketplace VAT invoicing?

The first failure is usually metadata: VAT number, company name, vendor identity, refund reason, credit-note relationship, and payout reference are not stored as structured invoice fields. Once those fields are missing, PDFs and exports become cleanup work.

How does Lattice Invoices fit a marketplace workflow?

Lattice Invoices is being shaped around EU WooCommerce stores that need structured VAT data, invoice PDFs, credit notes, downloads, and accountant-ready exports. Marketplace workflows are a strong early-access use case because they expose invoice-data gaps quickly.