Why architecture WooCommerce invoices are different
A paid architecture checkout can be a simple product in WooCommerce, but the finance workflow behind it is usually not simple: B2B billing, VAT numbers, PO references, project codes, deposits, retainers, partial refunds, and accountant exports all matter.
The strongest sales path is to collect invoice-ready data before payment, set expectations for deposit/final-invoice documents, and keep credit notes connected to refunds instead of sending corrected PDFs manually.
Deposits and retainers need invoice language before the work starts
Architecture studios often sell paid discovery calls, concept packages, deposit payments, drawing reviews, or retainer blocks before a full project is scoped.
Better workflow: Separate proforma/payment-request wording from final paid invoices and keep both connected to the WooCommerce order.
B2B clients need PO numbers, company VAT data, and project references
A buyer may pay through WooCommerce but need the invoice issued to a company, property developer, municipality, landlord, or finance department.
Better workflow: Collect company/legal name, VAT/BTW ID, invoice email, PO/reference, project address, and billing country at checkout instead of by email later.
Scope changes and cancellations create correction work
Design projects can change after payment: a feasibility study becomes a bigger package, a permit review is cancelled, or part of a deposit is credited.
Better workflow: Use linked credit notes and correction records instead of overwriting PDFs or editing invoice numbers manually.
Feature checklist before choosing an architecture invoice plugin
| Requirement | Why it matters for architects |
|---|---|
| Project reference fields | Capture PO number, project name, property address, and invoice email before payment so the PDF is finance-ready. |
| Deposit/proforma workflow | Issue payment-request language for deposits and final invoice language after the WooCommerce order is paid. |
| Sequential invoice numbers | Keep invoice numbering separate from WooCommerce order IDs so accountants can audit architecture project revenue cleanly. |
| VAT/BTW and reverse-charge metadata | Store VAT ID, billing country, VAT rate, VAT amount, and exemption/reverse-charge wording where relevant. |
| PDF attachments and My Account downloads | Attach invoice PDFs to order emails and give clients a download path without asking the studio admin team. |
| Refund credit notes | Partial refunds, cancelled consults, and corrected project deposits should create linked credit notes. |
Common architecture invoice scenarios
Paid feasibility call
Risk: Client pays personally, then asks for a company invoice with project reference after checkout.
Workflow: Ask for company/VAT details and project reference before payment; attach the PDF to the completed-order email.
Concept package deposit
Risk: The studio needs deposit wording before work starts and a final invoice after the payment clears.
Workflow: Use proforma/payment-request copy before payment and a final paid invoice when the order status changes.
Developer or municipality invoice
Risk: Accounts payable rejects the invoice because a PO number, department, or project code is missing.
Workflow: Add PO/reference fields and carry them into invoice metadata, PDF output, and accountant export.
Cancelled review or changed scope
Risk: A partial refund is processed, but the invoice PDF no longer matches the accounting trail.
Workflow: Generate a linked credit note for the refunded amount and keep the original invoice immutable.
Conversion shortcut
Turn architecture invoice edge cases into a prefilled €49 review request.
If the store has deposits, retainers, PO references, project codes, B2B VAT fields, or refund corrections, send those details before buying. The fit-check email gives Lattice the exact workflow needed for early-access qualification.
FAQ
Can architecture studios use WooCommerce for paid consultations and still issue proper VAT invoices?
Yes, if the checkout collects invoice-ready business fields and the invoice workflow keeps VAT data, invoice number, payment status, PDF delivery, project reference, and corrections connected to the order.
Should project details appear on the invoice PDF?
Only finance-safe details should appear by default: project code, property reference, package name, or PO number. Sensitive notes, design comments, and internal scope discussions should stay out of the PDF.
Why is an architecture invoice workflow different from a normal product invoice?
Architecture and design studios often combine deposits, retainers, B2B billing details, PO numbers, project references, scope changes, partial refunds, and accountant exports. That is more than a generic PDF receipt problem.
What should an architecture studio send before requesting Lattice Invoices early access?
Send store URL, country, what you sell through WooCommerce, deposit/retainer workflow, VAT/B2B fields, PO/project reference needs, invoice-number format, refund frequency, and accounting handoff process.