Vat Laravel Package

Product Decisions This Supports

• EU market entry / expansion roadmap: Before committing to launch in a new EU country, product can scope what VAT compliance actually requires (registration, rate display, invoice fields). This package gives a cheap technical read on the rate-lookup and number-validation surface, which de-risks go/no-go sequencing across countries.
• B2B vs. B2C pricing model: The reverse-charge mechanism hinges on validating a customer's VAT number. This package makes "verified B2B customer pays net, unverified pays gross with VAT" a concrete, buildable product rule — a decision that materially changes effective pricing, margin, and invoicing UX.
• Checkout and pricing architecture: Whether to display VAT-inclusive or VAT-exclusive prices per market, and how to show tax breakdowns at cart/checkout, is a product decision this package informs by making rate lookup and gross/net math a commodity rather than custom work.
• Build vs. buy for tax: A clear "buy/integrate" signal for VAT number validation and rate lookup. The alternative — direct VIES integration, commercial tax engines (Avalara, Stripe Tax, Quaderno) — carries different cost and maintenance profiles. Having a lightweight OSS option changes the calculus for the validation + display slice specifically.
• Invoice and self-serve onboarding features: VAT ID collection with instant validation and helpful error states (invalid format, unverifiable, service down) is a retention/compliance feature. This package defines the validation vocabulary the product team can design around.
• Scope discipline on roadmap: Lets PMs explicitly separate "tax calculation for display and validation" (in scope, cheap) from "tax filing, remittance, exemption certificates, cross-border reporting" (out of scope, needs specialists). Prevents the roadmap from accidentally promising compliance it can't deliver.

When to Consider This Package

Good fit when:

• You operate in or sell into the EU and need VAT ID validation and/or per-country rate lookup in a PHP/Laravel codebase.
• You need display-grade tax math — showing correct gross/net prices, applying standard rates, handling B2B reverse charge at checkout — not filing-grade tax determination.
• You want a small, framework-agnostic dependency you can wrap in your own service layer rather than adopting a commercial tax platform.
• Your catalog is relatively simple (single tax rate per country/region, no complex product tax categories, no US-style multi-jurisdiction nesting).
• You're building the first version of EU billing and want to avoid bespoke VIES plumbing and hard-coded rate tables.

Look elsewhere when:

• You need compliance-grade tax determination: product tax categories, reduced rates per item type, exemptions, OSS/IOSS reporting, VAT returns, audit trails. Use a specialist tax engine.
• You need guaranteed uptime/SLAs. VIES is a third-party service with real reliability and latency issues; a commercial provider with caching and fallbacks is safer for high-volume checkout.
• You sell into many non-EU jurisdictions — this package is EU-specific and won't cover US sales tax, GST, etc.
• You require vendor support, indemnification, or contractual compliance assurances. MIT OSS offers none.
• Your stack isn't PHP — while the concepts are portable, the code isn't.

Adoption cautions to plan for: VIES availability should never block checkout. Design the product flow to degrade gracefully (accept the number, validate asynchronously, flag for review) rather than failing the purchase. Rate data has a freshness question — decide your policy for when cached rates must be refreshed, and who owns that.

How to Pitch It (Stakeholders)

For executives: We need EU VAT handling the moment we sell cross-border, and getting it wrong means incorrect invoices and compliance exposure. This is a small, MIT-licensed PHP component that already solves the two mechanical pieces — validating a customer's EU VAT number against the official VIES registry, and looking up current country VAT rates to compute gross/net prices. That lets us ship compliant-looking pricing and B2B reverse-charge logic in weeks instead of months, at effectively zero license cost. It is not a tax engine — it doesn't file returns, handle exemptions, or guarantee availability — so we treat it as the display-and-validation layer, and revisit a paid provider only if we expand into complex product tax categories or high-volume markets where VIES reliability becomes a checkout risk. Recommendation: adopt for the EU launch slice, wrap it behind our own internal tax service so we can swap providers later without touching product code, and budget a follow-up decision on a commercial tax platform once EU volume justifies it.

For engineering: Small, framework-agnostic, trivially wrappable in a Laravel service provider and facade. Key asks: (1) isolate it behind an internal TaxService interface so the vendor is replaceable; (2) never let VIES calls sit on the checkout critical path — validate async with caching and a manual-review fallback; (3) own the rate-refresh policy explicitly, including staleness handling and an override for edge cases; (4) write tests around rounding and boundary cases, since gross/net math errors surface as customer-visible pricing bugs. Low integration risk; the real risk is treating third-party validation as an authoritative compliance gate.