Weave Code
Nova Vat Validation Laravel Package
napp/nova-vat-validation
A Laravel Nova field for validating VAT numbers, letting you check EU VAT IDs directly in Nova forms and resources. Helps keep company and customer records accurate by flagging invalid or malformed VAT numbers with clear validation feedback.
EU VAT field for Laravel Nova
Frequently asked questions about Nova Vat Validation
- How do I install napp/nova-vat-validation in a Laravel Nova app?
- Install the package with Composer and attach the field to your Nova resource definitions. Confirm Nova, Laravel, and PHP constraints first because the package/repository naming mismatch and low adoption make compatibility review important. Persist the VAT value in a nullable database column or reuse an existing one.
- Which Laravel, Nova, and PHP versions are supported?
- The provided context does not list explicit version constraints, so check the package composer.json before dependency approval. Nova major-version coupling is a main risk, and if it targets an older Nova release you should plan to fork, vendor, or wrap the validation logic. Test against your exact Nova, Laravel, and PHP stack in staging.
- Does this package validate VAT numbers against VIES?
- It is described as validating EU VAT numbers, and the assessment notes that feasibility depends on whether validation calls VIES synchronously. The context does not confirm server-side versus client-side behavior, so verify this in a staging spike. Test valid, malformed, and non-EU VAT inputs plus timeout behavior.
- What happens if VIES is unavailable or times out?
- The context flags VIES outage or timeout as a key failure mode but does not specify the package's fallback behavior. Verify timeout handling in staging and define a fallback procedure for admin users. For production use, consider caching, retry/backoff, and stored validation results.
- Is the VAT number normalized or stored in a canonical format?
- This is unclear from the provided context and is listed as a key question to resolve. Before enabling the field broadly, confirm whether it normalizes input and whether the stored value matches the canonical VAT format. Avoid schema assumptions until normalization behavior is tested.
- Does it store validation status or timestamps for audit?
- The assessment raises audit trail concerns and asks whether validation status and timestamps are stored. The context does not confirm built-in audit fields. If auditability matters, add your own validation-status and timestamp columns or wrap the validation flow.
- Is napp/nova-vat-validation safe to use in production?
- It can serve as a tactical Nova admin convenience, but adoption is very low and maintenance risk is elevated. Avoid making it a critical compliance dependency without an internal owner. Use a feature flag, start with one low-risk Nova resource, and monitor for one to two sprints.
- Can I use this package for customer-facing checkout VAT validation?
- It is best suited to Laravel Nova back-office forms, not high-volume or customer-facing validation. Synchronous VIES calls can add latency and are subject to external rate limits and outages. For checkout or onboarding, prefer a dedicated validation service or an internally owned VIES client with caching and observability.
- How should I test this Nova VAT field before rollout?
- Run a staging spike with representative valid, malformed, non-EU, and edge-case VAT numbers. Verify VIES timeout and failure behavior, storage format, and Nova form behavior. Then attach the field to one low-risk Nova resource behind a feature flag and monitor before expanding.
- Are there alternatives if the package is abandoned or incompatible?
- You can fork or vendor the package, wrap the validation logic yourself, or use a dedicated VAT validation service or VIES client. The main decision is whether you need only a Nova UI field or an owned VAT validation service with caching and audit storage. Review license and dependency weight before choosing.
Weaver
How can I help you explore Laravel packages today?