Why ticket stores create messy invoice requests
Ticket checkout looks simple until a company buys seats for a team. The payer, attendee, procurement contact, VAT number, and invoice email can all be different. If WooCommerce only stores consumer billing fields, every B2B invoice correction becomes a manual support task.
Lattice Invoices is positioned around that operational gap: capture invoice data before payment, attach it to the order, generate VAT-ready PDFs, preserve credit-note evidence, and give the buyer a download path without another email thread.
B2B conference tickets and team passes
Invoice risk: A company buys five tickets, but the finance team later asks for a corrected legal name, VAT number, PO reference, and invoice email. If those fields were not captured before payment, support has to rebuild the invoice manually.
Lattice direction: Collect invoice details at checkout and keep them attached to the WooCommerce order, ticket lines, PDF invoice, and customer download record.
Paid workshops, retreats, and training days
Invoice risk: Events often use deposits, early-bird rates, coupons, and balance payments. The invoice workflow needs to show what was paid, what is still due, and which VAT rate applied.
Lattice direction: Use proforma/final invoice timing, payment-status evidence, due dates, and clear PDF delivery instead of sending edited PDFs from an inbox.
Refunded tickets, no-shows, and attendee changes
Invoice risk: Refunds and attendee substitutions create finance questions. A refunded ticket needs a credit-note trail connected to the original invoice, not a silent WooCommerce refund only.
Lattice direction: Require refund-linked credit notes, retained invoice PDFs, and correction notes so the customer and accountant can follow the event history.
Event invoice fields to qualify before buying
Should an event organiser buy now?
| Store signal | Priority | Best next action |
|---|---|---|
| Companies buy multiple tickets and ask for corrected invoices | High | Capture company/VAT/PO fields before payment and make them visible on the invoice PDF and accounting export. |
| Tickets are refunded, transferred, or partially cancelled | High | Use credit-note support before relying on the workflow for finance handoff. |
| Events use deposits, balance payments, or bank transfer | Medium | Check proforma timing, due dates, final invoice timing, and payment reminders before purchase. |
| The event is mostly low-value B2C tickets | Lower | Start with the setup checklist, then buy once invoice requests become a repeated support cost. |
Copy this into the early-access email
Event invoice requests are easier to qualify when ticket type, buyer type, invoice fields, and refund cases are clear before purchase.
FAQ
Do event ticket stores need a different invoice workflow than normal products?
Often, yes. Event orders include attendee names, ticket quantities, event dates, early-bird pricing, cancellations, and group buyers. The invoice workflow should preserve those event-specific details with the payment and VAT evidence.
Should VAT and PO fields be collected before or after payment?
Before payment is safer. If B2B buyers enter company name, VAT/BTW number, PO reference, and invoice email during checkout, the invoice PDF can be generated from order data instead of being corrected later by support.
What happens when a ticket is refunded?
A finance-ready workflow should create or record a credit note linked to the original invoice. The refund alone may be enough for WooCommerce stock/payment state, but it is not always enough for customer accounting.
What is the next step if event invoice requests are already recurring?
Use the €49 early-access review CTA. Send the store URL, ticket plugin, buyer type, required invoice fields, and refund cases so Lattice Invoices can qualify whether the workflow fits before purchase.