How to Validate EU VAT Numbers on Shopify with VIES: A Safer B2B Workflow

Step 1: capture the VAT number in the context of the customer and order

Do not treat a VAT number as a loose text field that can be copied between customers. Keep the number attached to the business account and the order facts that matter to your tax decision. At minimum, your review process should be able to identify the customer, the VAT number presented, the countries involved, what was sold, and the order that used the result.

The reason is simple: validation and tax treatment are different. Two orders can present the same valid VAT number but involve different supplies or movements. Your future finance team needs to reconstruct why a specific transaction was treated the way it was, not merely prove that a number looked valid at some point.

If the customer changes its VAT number or company details, preserve the historical validation associated with prior orders instead of overwriting the evidence as though the new data had always applied.

Step 2: treat valid, invalid, and unavailable as different operational states

The European Commission describes VIES as a search engine rather than a standalone database. It queries national VAT databases and returns either valid or invalid VAT information. An invalid result can mean the number does not exist, is not activated for intra-EU transactions, or the registration is not yet finalized. Those are different possibilities with the same front-end result.

VIES can also be temporarily unavailable because national databases are being maintained or cannot respond. The Commission advises retrying later when an availability error occurs. That is not the same state as a definitive invalid response. Your workflow should distinguish 'invalid' from 'could not validate' so a temporary service interruption does not silently become a permanent customer classification.

For a valuable account that says its number is valid but VIES does not confirm it, Your Europe points to the relevant national tax authority process. National authorities can confirm whether a VAT number is valid and, depending on the process, whether it is associated with a specified name and address. Build that escalation path before the first exception appears.

Step 3: preserve evidence of the validation

Your Europe recommends keeping track of VIES validation in case of a tax control. Treat that as an accounting record, not a transient checkout message. Preserve enough information to explain which number was checked, when it was checked, what response was received, and which order relied on that check.

A timestamped validation trail is especially useful when the customer's status changes later or when a national database was temporarily unavailable. It lets finance distinguish what the store knew at the time from what VIES shows months afterward.

Automation should make this evidence easier to retain, but the operating procedure still needs an owner. Decide who reviews failed validations, how retries are recorded, and when an order moves to manual tax review instead of continuing under an assumed result.

Step 4: classify the transaction after validation instead of letting VIES make the tax decision

A valid VIES response is an important input for cross-border B2B VAT treatment, but it does not prove that every transaction qualifies for reverse charge. The correct treatment also depends on the supply, the establishments involved, where goods move or where a service is supplied, and any applicable exceptions. Validation tells you about VAT information; classification tells you what rule applies to this order.

That distinction matters when an app automates part of the workflow. Vatuno's current listing says valid cross-border B2B sales are marked reverse charge and the required note is added to the invoice. Configure and use that behavior only for transactions your tax logic says belong in that path. A green VIES result should not override contradictory order facts.

When the movement, customer status, or supply type is unclear, route the order to an exception queue rather than forcing a binary answer. A short manual review is cheaper than building a repeatable error into every similar transaction.

Step 5: keep the EUR 10,000 B2C threshold out of the B2B validation decision

The EUR 10,000 threshold is commonly discussed beside EU VAT software, but it answers a different question. It is a conditional simplification for specified cross-border B2C supplies when the relevant eligibility conditions are met; it is not a universal threshold for every EU seller and it does not determine whether a customer's VAT number is valid.

Keep the two tracks separate in your operating procedure. VIES validation belongs in the B2B status and transaction-classification flow. Threshold monitoring belongs in the relevant B2C place-of-supply analysis. A tool can surface both, but placing them on one dashboard does not make them interchangeable rules.

If your business is not established in the EU, or if your facts fall outside the threshold simplification, do not let the presence of a EUR 10,000 tracker imply eligibility. Confirm the applicable rules with the relevant authority or adviser.

Step 6: create an exception queue that staff can actually operate

At minimum, separate four exceptions: VIES returned invalid, VIES was unavailable, the VAT number and account details need confirmation, or the transaction facts do not clearly fit the configured treatment. Give each exception an owner and a visible status instead of leaving it buried in an order note.

For an invalid result, let the buyer correct an obvious typo and retry. For an unavailable service, retry later. For a disputed result, use the relevant national authority route. For ambiguous transaction facts, escalate to the person responsible for VAT classification. Preserve the resolution and the evidence used so the same issue does not have to be rediscovered at quarter end.

This is where automation becomes safer rather than merely faster. Routine valid cases can move through the defined workflow while uncertain cases remain visible instead of inheriting a guessed tax treatment.

Where Vatuno fits, and what its current listing does not promise

Vatuno's current Shopify App Store listing positions the app as an EU VAT record, invoice, and OSS-reporting tool for stores selling digital products. It advertises VIES validation, rate-mismatch flags, sequential PDF invoices, quarterly OSS CSV reports, and EUR 10,000 threshold tracking. As of September 15, 2026, the listing shows Starter at $49/month, Growth at $99/month, and Enterprise at $149/month, each with a 14-day free trial. Vatuno is available in English, German, French, Spanish, Italian, and Portuguese (Portugal).

Use that documented scope as the buying boundary. A quarterly OSS CSV is reporting support, not a claim that the app registers you for OSS, submits the return, or pays tax for you. The listing's category metadata also mentions IOSS, but the explicit reporting feature verified here is quarterly OSS CSV; do not infer a monthly IOSS-return export or every physical-goods import workflow from the category label alone.

For a digital-product store whose EU work is dominated by VAT records, VIES checks, invoice evidence, rate exceptions, and OSS preparation, the fit is clear. For imported physical goods, multiple local registrations, or tax obligations outside the EU, verify the missing workflow requirements before treating one app as a universal tax platform.

Use the four-stage mental model: validate, classify, record, report

Validation asks whether the VAT information is recognized through VIES. Classification decides the treatment of the specific transaction. Recording preserves the order, validation, invoice, and exception evidence. Reporting turns the correctly classified period into the data used for the relevant return. Keeping those stages separate prevents one successful check from being mistaken for complete compliance.

Vatuno can connect useful pieces of that process to Shopify orders, but no software removes the need to define who owns the tax decision and who performs official filing. The cleanest implementation is the one where routine cases are automated, exceptions are visible, and the final report can be traced back to order-level evidence.

Apps mentioned in this guide

Frequently asked

What does VIES validate?

VIES checks EU VAT information by querying national VAT databases and returns valid or invalid information for the VAT number. It is a search engine, not a standalone VAT-registration database.

Does a valid VIES result automatically mean I should apply reverse charge?

No. A valid VAT number is one important input, but the correct treatment also depends on the specific transaction, establishment, movement or place-of-supply facts, and applicable exceptions.

What should I do if VIES is unavailable?

Treat service unavailability separately from an invalid VAT number. Your Europe advises waiting and trying again when national databases are temporarily unavailable, while preserving the exception in your workflow.

Does Vatuno file OSS returns automatically?

The current listing advertises quarterly OSS reports as CSV. Treat that as report preparation and export support, not as a claim that Vatuno registers you for OSS, submits the return, or makes the tax payment.

Is Vatuno available in English?

Yes. Vatuno is available in English. Its current App Store listing also shows German, French, Spanish, Italian, and Portuguese (Portugal), and ShopRadar's CTA uses the real cross-border-vat-compliance slug with locale=en.