Skip to content

Checkout Tax ID Fields

Magento 2.4.7 – 2.4.9 Luma Hyvä

Merchants shipping across borders often must capture a buyer's tax identification number – a VAT or EORI number for the EU, PAN for India, CPF for Brazil, RFC for Mexico – before an order can be fulfilled or invoiced. Checkout Tax ID adds exactly the right field to the checkout, for exactly the right countries, with no custom code.

You define rules in the admin panel: pick one or more countries, give the field a label and tooltip, choose how it is validated (exact length, a length range, or a custom pattern), and decide whether it is required. When a customer selects a matching shipping country, the field appears automatically in the checkout. The submitted value is saved to the order alongside a snapshot of its label, shown on the order detail page, and available as an optional, filterable column in the Sales → Orders grid.

The extension ships with ten ready-to-use rules (India, Brazil, Indonesia, Mexico, Saudi Arabia, South Korea, Turkey, Vietnam, Bangladesh, and a combined EU + Great Britain EORI rule) that you can edit, extend, or remove. A separate Residential / Commercial mode lets a single country present two independent fields – for example a private-customer identifier and a business EORI number – each with its own label, validation and required flag.

Checkout Tax ID is a rule-based, deterministic, on-premise extension. It uses no external services, sends no data off-site, and adds a single dedicated database table without modifying native Magento sales tables. It works on the Luma theme and on Hyvä Theme storefronts that run the native Magento checkout.

Key Features

  • Rule-based configuration of checkout tax-ID fields, fully from the admin panel
  • Per-country targeting; one rule can cover many countries
  • Separate Residential / Commercial fields per country
  • Ten pre-configured rules (India, Brazil, Indonesia, Mexico, Saudi Arabia, South Korea, Turkey, Vietnam, Bangladesh, EU + GB EORI)
  • Validation by exact length, length range, or custom pattern
  • Value saved to the order with a label snapshot
  • Opt-in, filterable, sortable Tax ID column in the Orders grid
  • One dedicated database table; native sales tables untouched
  • No external services, no data sent off-site
  • Fully translatable

Versions

v1.2.2 Aug 25, 2026

FAQ

Selling across borders usually means collecting a buyer's tax identification number before the order can be invoiced or cleared: a VAT or EORI number in Europe, PAN in India, CPF in Brazil, RFC in Mexico. Adobe Commerce and Magento Open Source have no built-in way to ask for the right one in the right country, so the field is normally added by a developer, per country, in code. This extension moves that decision into the admin panel. You describe the field once as a rule – which countries, what label, how it is validated, whether it is required – and the checkout shows it to the customers it applies to. Adding a country stops being a deployment.
- **You ship to countries that require a tax ID.** The extension ships with ten ready-made rules – India, Brazil, Indonesia, Mexico, Saudi Arabia, South Korea, Turkey, Vietnam, Bangladesh, and a combined EU + Great Britain EORI rule – so the common cases work before you configure anything. - **The number has to reach the order.** The submitted value is stored with the order together with a snapshot of the label it was collected under, so an invoice raised months later still shows what the customer was actually asked. - **Different countries need different fields.** One rule can cover many countries, and each rule has its own label, tooltip, validation and required flag. - **Private and business buyers need different numbers.** Separate Residential / Commercial mode presents two independent fields for the same country – for example a personal identifier for consumers and an EORI number for companies.
- **Your storefront runs Hyvä's own Magewire checkout.** The field is added through the standard LayoutProcessor plugin chain, which the native Magento checkout provides. Hyvä Theme is supported when it runs the native checkout, for example through Hyvä Luma Checkout; the Magewire checkout is not. - **You need the number verified against an official registry.** This extension validates the shape of a value, not its existence – see the last question. If your compliance process requires a live VIES or equivalent lookup, you need a service that performs one. - **You are on Magento 2.4.6 or earlier.** Supported versions are 2.4.7 – 2.4.9 on PHP 8.1 – 8.5. - **You need the field driven by the billing country.** Rules match on the shipping country the customer selects.
- **Rules in the admin panel.** Each rule names one or more countries, the field's label and tooltip, its validation and whether it is required. No template or code changes. - **Three validation types.** Exact length, a length range, or a custom regular expression per rule – enough to describe most national formats without a service call. - **A field that appears on its own.** When the customer selects a shipping country covered by an active rule, the field appears in the checkout shipping step. In Separate mode a Residential / Commercial switch appears first and the field reconfigures to the chosen block. - **The value on the order.** Stored with a label snapshot, shown on the order detail page in the admin panel, and available as an opt-in Tax ID column in Sales → Orders with server-side filtering and sorting. - **Ten pre-configured rules**, editable or removable like any rule you add yourself. - **Fully translatable** – every label, tooltip and field name. - **One dedicated table.** The extension adds `webramos_checkout_tax_id_data` and changes no native Magento sales table.
- **It does not check a number against any registry.** Validation is by length or pattern only. The extension makes no external calls of any kind and sends no data off-site, which is the same reason it cannot ask VIES whether a VAT number is real. A well-formed but fictitious number will pass. - **It does not calculate or change tax.** The value is collected and stored; nothing in your tax rules, totals or invoices reacts to it automatically. - **It does not touch the customer account.** The number is collected per order, not saved to a customer profile or reused on the next checkout. - **It does not add the field anywhere but the checkout shipping step** – not to the billing step, the customer account, or the admin order-create screen. - **It does not support Hyvä's Magewire checkout**, as noted above.

Reviews

No reviews yet. Be the first to share your experience.

Sign in to write a review.