Jonathan Gustafsson
Awaiting Review

Why: Vies::resolveVatNumber() returns the stored vat_numbers row unchanged, so rows created before the address-parsing fixes (#589 postcode-space, #592 multi-line/c-o) keep their stale street/postcode/city (e.g. 457/02 instead of 45702/Hällevadsholm). Merge/deploy only helps VAT numbers never resolved before; returning customers keep getting the bad billing address.

What: One-off artisan command vies:reparse-addresses (with --dry-run) that re-fetches each vat_numbers row from VIES and re-parses it with the current parser, updating rows whose parse changed. Shared parsing extracted into Vies::fetchParsedAddress() so the command and the live path are identical. 3 command tests + 8 Vies tests green.

Remediation for the open follow-up on #8 / #16 / #17. Run after #592/#593 are deployed: --dry-run first, then for real. Re-hits VIES per row (raw string isn't stored).

Still open (not covered by this command): already-placed orders (#13314, #13478, #13467, #13546, ...) have the bad billing address copied onto them and need per-order correction separately.

vies:reparse-addresses - remediate stale stored VAT number addresses

no votes yet
Priority P2

Assigned to

Yaroslav Yaroslav

Tags

Storefront
Quick Actions
Activity
View recent activity and updates
Use arrow keys to navigate