Shopify EU VAT Before 2027: A ViDA Readiness Plan for OSS Stores

Build a date map before you change any tax logic

Start with four columns: what applies now, what changes on January 1, 2027, what is scheduled for July 1, 2028, and what is scheduled for July 1, 2030. The Commission says the ViDA package entered into force on April 14, 2025 and will be implemented progressively through 2035. For most Shopify merchants using OSS today, that means there is no sound reason to label every future ViDA feature as a 2027 requirement.

The near-term date is January 1, 2027. The Commission says certain legislative clarifications for users of the OSS and IOSS schemes become effective then, and its July 24, 2026 update says revised Explanatory Notes and OSS guidelines were published to reflect those changes. The Commission's 2026 work programme also describes an extension of OSS to certain B2C e-charging supplies from that date. If your store does not sell in that sector, the existence of the extension does not turn it into a new checkout requirement for your products.

The next major date is July 1, 2028, when the Commission's current timeline places important Single VAT Registration measures, including wider OSS changes and a mandatory reverse-charge mechanism for certain non-established suppliers. July 1, 2030 is the separate milestone for cross-border B2B Digital Reporting Requirements based on mandatory e-invoicing. Put those dates on the same project page so nobody on the ecommerce or finance team quietly moves a 2030 project into the 2026 backlog.

• Now through December 2026: keep current VAT, OSS and evidence processes correct under the rules that apply today.
• January 1, 2027: review the revised OSS/IOSS guidance and implement only the changes that actually affect your scheme and supplies.
• July 1, 2028: reassess Single VAT Registration changes against your establishment, stock and cross-border selling model.
• July 1, 2030: prepare separately for cross-border B2B digital reporting and mandatory e-invoicing requirements.

Do not rebuild today's OSS workflow around a 2030 e-invoicing rule

A digital-product merchant filing Union or non-Union OSS returns still needs a dependable current-period process in 2026: classify the sale, preserve the customer-location evidence used for the decision, record the taxable amount and VAT, reconcile corrections, prepare the appropriate return data and retain the underlying records. ViDA's later digital-reporting architecture does not erase those jobs today.

This is particularly important when a team hears the words 'mandatory e-invoicing' and assumes every Shopify order must immediately flow through a new EU-wide reporting rail. The Commission's ViDA timeline places the main cross-border B2B Digital Reporting Requirements on July 1, 2030. Member States can have their own domestic e-invoicing rules and may introduce obligations under the legal framework, so a merchant still needs to check the countries where it is established or registered. But the EU-level 2030 B2B milestone should not be presented as a universal September 2026 checkout requirement.

Keep the current and future workstreams separate in your system design. Your current OSS records should be accurate enough to survive a quarter close and later review. Your future e-invoicing project should have its own owner, scope and trigger dates. That separation prevents a tax roadmap from becoming a pile of half-implemented features with no clear legal date behind them.

Freeze a reliable evidence layer before January 1, 2027

The most useful ViDA preparation is boring in the best possible way: make every transaction reconstructable. A future rule change is easier to implement when you already know where the source facts live. For covered EU sales, preserve the Shopify order reference, supply date, buyer-country information used for the VAT decision, supply classification, taxable amount, VAT rate, VAT amount collected, invoice reference where applicable, and the relationship between refunds or corrections and the original order.

Do not overwrite historical facts just because a tax treatment or reporting format changes later. If a correction is made, keep the original transaction and the correction trail. That matters operationally because the Commission's ViDA material describes improvements to OSS processes, including a new correction mechanism, while the exact effective requirements must be followed from the applicable legal and administrative guidance. A clean before-and-after trail gives finance something to map into the revised mechanism instead of forcing staff to reverse-engineer what happened months later.

For stores using Vatuno, the current listing says the app turns EU orders into VAT records and flags cases where the VAT collected differs from the official rate for the buyer's country. Use that mismatch flag as an exception signal, not as permission to silently rewrite the order. Resolve why the mismatch exists, document the decision, and keep the evidence that explains the correction.

Create a correction queue instead of a quarter-end spreadsheet rescue

A ViDA-ready operating process should make exceptions visible while they are still easy to investigate. Create a queue for rate mismatches, refunds, customer-location conflicts, uncertain B2B status and transactions that may belong outside the OSS scheme you use. Give every item an owner, a reason code and a resolution state. The goal is not to predict every future portal field; it is to prevent unresolved tax questions from being buried inside a quarter total.

That approach also protects you from implementing an assumed 2027 correction format too early. The Commission published revised OSS guidance in July 2026 specifically to reflect changes from January 1, 2027. Before changing production logic, compare the final guidance that applies to your Member State of identification with your existing correction process. Record what changed, when the change applies and which historical periods remain under the older procedure.

Vatuno's quarterly OSS CSV can be one reporting output in that process. Treat it as prepared data that still needs reconciliation and the merchant's actual submission process. The current App Store listing does not say that Vatuno registers a merchant for OSS, submits a return to the tax authority or makes the VAT payment. Keep 'report prepared', 'return submitted' and 'payment completed' as separate statuses so an exported file cannot be mistaken for a completed obligation.

Keep B2C OSS, B2B VIES and future digital reporting on different decision paths

One dashboard can show all three, but they answer different questions. OSS is a reporting simplification for eligible supplies. VIES checks whether a VAT number is recognized through the EU validation service at the time of the check. Future ViDA digital reporting introduces another layer for cross-border B2B transaction reporting. Treating those as one yes-or-no tax status creates brittle automation.

Vatuno's current listing says it validates B2B VAT numbers through VIES and marks valid cross-border B2B sales as reverse charge with the required invoice note. That is useful workflow support, but a valid VIES response by itself is not proof that every transaction qualifies for reverse-charge treatment. Establishment, place-of-supply rules, the nature of the supply and other legal conditions still matter. Preserve the validation record and the facts used for the tax decision.

The same discipline applies to the EUR 10,000 threshold. Vatuno advertises threshold tracking, but the threshold is not a universal switch for every seller. The EU simplification has eligibility conditions, including establishment conditions, and applies to specified cross-border B2C supplies. First decide whether the threshold rules are relevant to the merchant; only then use a tracker as an operational alert.

Where Vatuno fits in a 2026-to-2027 readiness stack

Vatuno is a sensible fit when the store matches the work its current listing actually promises: EU VAT records for digital-product sales, country-rate mismatch checks, VIES validation, sequential PDF invoices, quarterly OSS CSV reports and threshold tracking. Vatuno is available in English. The current listing also shows German, French, Spanish, Italian and Portuguese (Portugal), so the authentic product name should not be read as a language or market limitation.

As verified on September 15, 2026, the official Shopify App Store listing shows Starter at $49 per month, Growth at $99 per month and Enterprise at $149 per month, with a 14-day free trial on each plan. Choose it because those documented functions match the evidence and reporting work you need, not because of an invented claim that the app automatically handles every ViDA phase.

The fit boundary matters. The listing explicitly frames Vatuno around stores selling digital products and explicitly advertises quarterly OSS CSV reporting. It does not advertise automatic OSS registration, tax-authority submission, tax payment, a monthly IOSS return export or guaranteed readiness for future ViDA reporting formats. A physical-goods importer, multi-country inventory operation or merchant whose core requirement is future cross-border B2B digital reporting should verify the exact product coverage before treating the same setup as complete.

Use the rest of 2026 for controlled readiness, not speculative automation

Run one rehearsal before the year changes. Take a completed month or quarter, reconcile the Shopify orders to the VAT records, inspect every mismatch, trace a refund back to its original sale, verify that the team can retrieve the location and invoice evidence, and confirm who performs the official filing and payment. If that exercise is painful, fix the evidence flow now. A new regulation date will not make a weak record trail easier to repair.

Then create a January 2027 change checklist with named owners. One person monitors the Commission and Member State guidance. One person maps confirmed rule changes to store data and finance procedures. One person validates the app/export behavior against a controlled set of orders before it is relied on for a filing period. Keep a short written decision log so the next quarter does not reopen the same interpretation from scratch.

Finally, schedule the later ViDA milestones separately. Review the July 2028 Single VAT Registration changes when your business model is close enough to make the analysis concrete, and treat the July 2030 cross-border B2B digital-reporting project as its own integration programme. The strongest readiness plan is not the one that installs the most software today. It is the one that knows which requirement belongs to which date, preserves reliable evidence, and changes production logic only when the applicable rule is clear.

• Reconcile a real period before year-end and clear unresolved VAT exceptions.
• Document which OSS scheme and transaction classes your store actually uses.
• Preserve VIES results as evidence, but keep the tax-treatment decision separate.
• Validate Vatuno exports against source Shopify orders before relying on totals.
• Review the final January 2027 guidance for your Member State of identification before changing filing procedures.
• Keep 2028 SVR work and 2030 B2B digital reporting as separate roadmap items.

Apps mentioned in this guide

Frequently asked

Does all of ViDA start on January 1, 2027?

No. The European Commission describes ViDA as a phased rollout. Certain OSS and IOSS clarifications apply from January 1, 2027, major Single VAT Registration measures are scheduled from July 1, 2028, and cross-border B2B Digital Reporting Requirements based on mandatory e-invoicing are scheduled from July 1, 2030.

Do Shopify stores need EU-wide mandatory B2B e-invoicing in 2026 because of ViDA?

The EU-level ViDA milestone for cross-border B2B Digital Reporting Requirements is July 1, 2030. Separate national e-invoicing obligations can apply earlier, so merchants still need to check the countries where they are established or registered.

Does Vatuno automatically file OSS returns under ViDA?

The current Shopify App Store listing advertises quarterly OSS reports as CSV. That is a reporting output, not a verified claim that Vatuno registers the merchant, submits the official OSS return or makes the VAT payment.

Is a valid VIES result enough to apply reverse charge to every B2B order?

No. VIES validation confirms the status returned by the EU validation service, but the tax treatment also depends on the facts and legal conditions of the transaction. Keep the validation record and evaluate the transaction separately.

Is Vatuno available in English?

Yes. Vatuno is available in English. Its current Shopify App Store listing also shows German, French, Spanish, Italian and Portuguese (Portugal).