DevNJ Make your business ease
Column /

EU Website Requirements for Non-EU Companies: 12 Checks (2026)

Column › European websites

EU Website Requirements for Non-EU Companies: 12 Checks (2026)

A website built for customers outside Europe is not automatically ready for European customers. Translating the text is the easy part. What changes is how prices are displayed, how personal data is handled, how returns work and when customers expect an answer. These rules are decided by EU law and by the national law of each member state, and they apply to a company based anywhere once it sells to people in the EU.

This article is for companies outside the EU that are planning a website for European consumers or business customers. Chapters 1 to 12 are the twelve items to settle before you build; chapters 13 to 17 cover common pitfalls, a working order, a checklist and a summary. Everything was checked against public sources on 30 October 2026. It is general information, not legal advice, so confirm the details with a specialist or the regulator in your target country.

What you will learn The short answer
What to decide first Target countries, consumer or business, product or service (chapter 1)
Is English enough? Often for B2B; for consumers it depends on the country (chapter 2)
How to show prices VAT-inclusive totals; discounts use the 30-day lowest price (chapters 4 and 5)
Returns and withdrawal 14 days, plus an electronic withdrawal function from 19 June 2026 (chapter 6)
GDPR representative Generally required if you target EU residents without an EU establishment (chapter 8)
Where to host Not limited to the EU; transfers need a legal basis (chapter 10)
Time difference Publish hours with a time zone and a reply target (chapter 12)

1. Decide first: which countries, which customers, which offer

Three questions come before everything else: which countries you sell to, whether the buyer is a consumer or a business, and what you sell. Without them you cannot choose a language, a price format or the legal notices you need.

"Europe" is too large a unit for a website. The EU has 27 member states with different languages, VAT rates and expectations about what a consumer is told. Countries such as the United Kingdom and Switzerland are outside the EU altogether. Starting with one to three countries is cheaper and easier to run than aiming at the whole continent.

Consumers or businesses

Selling to consumers (B2C) brings in consumer protection rules almost across the board: VAT-inclusive prices, withdrawal rights, price-reduction rules. Selling only to businesses (B2B) removes many of them. The GDPR still applies to B2B, though, because a contact person's name and email address are personal data.

If one site offers both a business quote form and a shop where individuals can buy, the consumer rules apply to the consumer path. "We are B2B" is a safe claim only when the paths are fully separate.

What changes compared with a domestic site

The table below lists what a site built for your home market usually assumes, and what changes for the EU. Later chapters take each row in turn.

Item Typical home-market assumption What changes for the EU
Language One language is enough Choose by country and audience; consumers trust local language
Prices Whatever your home rules say VAT rates by country; discounts use the 30-day lowest price
Personal data Your national privacy law GDPR, even without an EU establishment, if you target EU residents
Cookies A notice is often enough Non-essential cookies need prior consent
Returns Set by your own terms A statutory 14-day withdrawal right and an electronic withdrawal function
Business details Your home legal notice Member-state rules; the German Impressum is the best-known example
Enquiries Office hours by phone and email Time difference; a stated reply time becomes a trust signal
Decide countries and customers, choose languages, set prices and legal notices, then decide how personal data is handled. Each step depends on the one before. 1. Market 1 to 3 countries 2. Language English or local 3. Prices VAT, withdrawal 4. Data GDPR, hosting Each step depends on the one before it
Figure 1: The order of decisions for an EU-facing website (DevNJ's working order; no figures)

2. Language: when English is enough and when it is not

"Is English enough?" is the usual first question. The answer depends on the buyer, the product and the country. Some sales work well in English alone; others will not be trusted without the local language.

What the numbers say

The European Commission's survey "Europeans and their languages", fielded in September and October 2023 with almost 27,000 respondents across the 27 member states, found that 47% of Europeans can speak English. That is five percentage points more than in 2012 and the highest share for any foreign language, yet less than half. It was published on 21 May 2024.

That figure is an EU-wide average. The gap between countries is large, so "everyone speaks English" does not hold as a planning assumption.

Where English alone tends to work

Situation English only? Why
Specialised B2B (components, software, machinery) Often enough Buyers are used to English documentation
Deals handled by an English-speaking contact Enough English is the working language inside the buyer
Consumers in countries with wide English use Often enough English is common across the population
Customers who already follow your home-market culture Often enough They are used to English-language sources

This table is DevNJ's own reading and does not describe legal language requirements. "Enough" means a deal or purchase is likely to go through in English. Even then, replies and forms work better the closer they are to the customer's language.

Where local language is worth adding

For consumer sales and high-value service sign-ups, local-language pages are a trust signal. Guidance from the Dutch Chamber of Commerce (KVK) says French consumers prefer to shop on a French-language web shop and expect customer service in French. In countries where English is less widely used the effect is stronger.

France also has a language law, the Toubon law. A law firm's analysis describes it as covering most information exchanged with consumers in commercial dealings, while noting that French courts limit it to providers based in France or situations where the targeted consumers are in France. It also says enforcement has centred on products affecting health and safety. That analysis dates from 2015, so current practice may differ.

For a website aimed at French consumers, French is the safer choice on both legal and commercial grounds. For other countries, check with the authority or a local adviser before you sell.

Specialised B2B often works in English; consumer sales are better with the local language; in countries with strong consumer language habits, such as France, local language is close to essential. English works Local advised Local near-needed Specialised B2B Consumers e.g. France
Figure 2: A rule of thumb for language choice (DevNJ's reading; not a statement of legal language requirements)

Translation quality and machine translation

The most common mistake when adding a language is publishing raw machine translation. A readable translation may be fine for product descriptions or an about page, but text that carries responsibility, such as prices, returns and personal data notices, should be reviewed by a native speaker. KVK's guidance makes the same recommendation.

Every added language also multiplies maintenance. A change to a price, a promotion or the terms has to be made in every language. Starting with English plus the local language of your most important country, and expanding after you see results, is easier to sustain.

3. Domains and URLs: making the country and language clear

Once languages are chosen, the URL structure comes next. Whether you add a /de/ folder or register a country domain changes both your running costs and how you appear in search.

Approach Example Suited to Watch out for
Language folders under your main site example.com/de/ Adding languages step by step Plan the structure from the start
Country-specific domain example.de Serious commitment to one country Domains and operations multiply with each country
Separate site per market de.example.com Different offers per market Highest maintenance cost

Whichever you choose, link the language versions of each page to each other so search engines can offer the right version, and put a visible language switcher on the page. Redirecting visitors automatically by browser language alone can stop them from reaching the page they wanted.

The European Data Protection Board (EDPB) lists the use of a top-level domain of an EU member state (such as .de) among the factors that can show an intention to offer goods or services to people in the EU. A country domain therefore also bears on the GDPR question in chapter 8.

4. Prices: VAT-inclusive totals and tax by destination country

Even if your home market already shows tax-inclusive prices, EU VAT rates differ by country, so the total for the same product changes with the destination. This chapter covers consumer price display and the VAT questions a non-EU seller meets first.

Show consumers the total price

The EU's consumer information portal (Your Europe) says consumers must be clearly told the total price including taxes and extra charges before they buy goods or services. A price that grows at checkout through delivery or fees should be avoided.

The same guidance sets out further rules.

Item Rule (Your Europe guidance)
Total price Show it including taxes and all additional charges
Pre-ticked boxes Extras such as express delivery must not be pre-selected; a pre-ticked box is not consent
Card surcharges No extra charge for paying by credit or debit card (with exceptions for some cards and corporate cards)
Currency conversion If you offer to charge in the customer's home currency, state the mark-up over the European Central Bank rate; the customer can decline

Many shops add delivery and payment fees on the last page. For EU consumers the expectation is that the total is visible from the start.

VAT: three situations a non-EU seller meets

VAT is complicated and depends on how you sell. The summary below follows KVK's guidance; for a specific transaction, consult a tax adviser.

How you sell Key point in KVK's guidance
An EU business selling to EU consumers Up to €10,000 a year (distance sales of goods and digital services combined) it may charge its home VAT; above that, the customer's country VAT. The One Stop Shop (OSS) allows one return
A non-EU business supplying services to EU consumers The non-Union OSS scheme is available
Goods shipped from outside the EU Import VAT is always due. Consignments up to €150 need an electronic declaration, and the Import One Stop Shop (IOSS) lets VAT be collected at the point of sale

If you ship goods directly from outside the EU, who pays VAT and where feeds straight into your displayed price. Whether you use IOSS or leave the customer to pay at import changes the total you show. The conditions for IOSS, such as when an intermediary is needed, should be checked with the tax authority of the member state concerned.

Duty and fees on parcels

KVK's guidance says that for e-commerce shipments of up to €150 from outside the EU, a fixed import duty of €3 per product type applies from 1 July 2026, and from 1 November 2026 a handling fee of €2 per product type applies to all e-commerce shipments, including those above €150. This affects how you build price and shipping for small direct-to-consumer orders.

These figures come from the KVK page checked on 30 October 2026. Details change often, so check current customs guidance for your destination before you ship.

Prices on B2B-only sites

A site that sells only to businesses commonly shows prices without VAT. But if any path lets a consumer buy, that path needs the VAT-inclusive total. A quote-only design that shows no prices avoids the question entirely.

5. Sale prices: the lowest price of the previous 30 days is the reference

Many shops show a "regular price" struck through next to a "sale price". For EU consumers this presentation has clear rules.

What the Omnibus Directive decided

The Price Indication Directive (98/6/EC) was amended by the Omnibus Directive ((EU) 2019/2161). When you announce a price reduction, you must show a prior price, and that prior price is the lowest price you applied during a period of at least 30 days before the reduction.

On 26 September 2024 the Court of Justice of the EU confirmed the point in a case referred by a German court. A reduction announced as a percentage, or as a promotional statement stressing the advantage, must be calculated from the lowest price of the previous 30 days. Merely stating a prior price is not enough; it must be the real basis of the reduction.

A worked example

The numbers below are hypothetical and only illustrate the rule.

Period Price (€) Display
40 to 20 days ago 60 Regular price
19 days ago to yesterday 50 Temporary reduction
Sale day 45 You want to say "20% off"

The lowest price in the previous 30 days is €50, so the discount is calculated from €50, not €60. €45 is a 10% reduction from €50, so "20% off" is not allowed. "25% off the regular price of €60" would not match the 30-day rule either.

Common display Problem Fix
Strike through an old high price and show a percentage The 30-day lowest price is not the base Calculate from the lowest price of the previous 30 days
Stack step-by-step reductions to show a bigger discount Member states treat this differently Check the rules of each target country before designing it
No record of past prices You cannot show the reference price Log the price for every day

Enforcement differs between member states. Some authorities have issued stricter guidance, for example refusing to accept alternative labels such as "reference price". Check the rules of your target country from official sources.

What to prepare before running a sale

Following the rule needs a daily price history. If your shop software does not keep one, you cannot show the base afterwards. Deciding at build time that the shop stores price history avoids rework.

6. Returns and withdrawal: 14 days, and the withdrawal button

In many countries a seller decides the return policy. For EU consumers, the law sets a right of withdrawal that a trader cannot remove through its terms.

The 14-day right of withdrawal

Your Europe states that consumers who buy online have a 14-day right of withdrawal. It lets them cancel without giving a reason, with exceptions depending on the product or the nature of the service. The starting point of the period and who pays return postage are set in detail by the directive and national law.

A trader must tell the consumer before purchase that the right exists and how to use it. A "no returns" notice cannot simply be copied onto a site for EU consumers.

The withdrawal button from 19 June 2026

From 19 June 2026, distance contracts concluded online with consumers need an electronic withdrawal function. It comes from Directive (EU) 2023/2673, and a trade commentary describes these requirements.

Item Content (trade commentary)
Application date 19 June 2026, with no transition period
Scope Online distance contracts with consumers where a withdrawal right exists
Button label Clear and easy to find, such as "withdraw from contract here"
Flow Two steps: a statement form, then a confirmation button
Acknowledgement Sent without delay on a durable medium such as email

Some member states prescribe the wording, and how far each has transposed the directive differs. The table rests on a vendor's blog, so confirm it against the law of your target country.

How this differs from a domestic shop

A typical shop points to a return form or a contact address, and does not have to complete the withdrawal on the site. For an EU-facing shop you build a path from the order history or the confirmation email into the withdrawal procedure. This is a system requirement, not a design choice, so check at the quotation stage that it is included in the build.

May 2021 a Dutch fine for not appointing a representative; July 2023 the EU-US framework adequacy decision; September 2024 the Court of Justice ruling on sale prices; June 2025 the EAA starts; July 2025 the ODR platform closes; June 2026 the withdrawal button; November 2026 a handling fee on all e-commerce shipments. 2021.5 €525,000 fine, no representative Dutch authority 2023.7 EU-US framework adequacy Transfers to US providers 2024.9 Court ruling on sale prices 30-day lowest price is the base 2025.6 EAA starts to apply 28 June 2025 2025.7 ODR platform closes 20 July 2025; remove the link 2026.6 Withdrawal button required From 19 June 2026 2026.11 Handling fee, all web orders From 1 November 2026; above €150 too
Figure 3: Dates that affect an EU-facing website (sources: European Commission, KVK and commentary; checked 30 October 2026)

7. Business details: your home legal notice is not enough

Most countries require some business details on a website. In the EU, member-state law sets what must be shown, so a plain translation of your home notice may fall short.

An example of required items: Germany

Section 5 of the German Digital Services Act (DDG) requires providers of commercial digital services to keep the following information easy to recognise and directly reachable at all times. German-language sites call it the Impressum.

Item Content (DDG section 5)
Name and address Business address; for companies, the legal form and representatives
Contact Including an email address for fast electronic contact
Register Commercial register entry and number
Authorisation The supervisory authority where a licence is needed
Regulated professions Chamber, title and professional rules
VAT number Where one is held

Germany is only one example; other countries have comparable rules. For sites aimed at German-speaking customers an Impressum page is standard practice. Whether the act applies directly to your business depends on factors such as where you are established, so confirm with an adviser for the target country.

What non-EU companies should watch

Your company registration numbers and tax identifiers will not match the EU's formats. Do not leave a field blank because your country has no equivalent; give the closest accurate information, such as your national company number. An adviser can tell you which of your identifiers can stand in.

A business address is also public contact information. If your office is a home address, decide whether it is acceptable to publish before you add it.

Remove the dispute-resolution link

Older EU-facing sites had to link to the EU Online Dispute Resolution (ODR) platform. The platform was discontinued on 20 July 2025. The European Consumer Centre Finland states that new complaints stopped in March 2025 and that user data is deleted. Check terms and footers for a leftover link.

8. GDPR: when it reaches you, and the EU representative (Article 27)

The GDPR is where non-EU companies are most often surprised. It can apply even when you have no establishment in the EU.

The test is intention to offer

The GDPR applies to a non-EU business that offers goods or services to people in the EU (Article 3(2)). The EDPB guidelines list factors that can show such an intention.

Factor (EDPB guidelines) Example
Mention of the EU or a member state "Delivery to Germany"
Advertising Paid search or campaigns aimed at EU audiences
Contact details A dedicated address or phone number reachable from an EU country
Domain A member-state domain such as .de, or .eu
Delivery Delivery to EU member states
Language or currency A language or currency other than your home one that is used in the EU

The same guidelines say that mere accessibility of a website from the EU, or use of a language common in your own country, is not enough by itself. The test is whether several factors together show an intention to target people in the EU.

A company profile site that is simply visible from Europe is normally outside the rule. A site that prices in euros, has German pages and delivers to Germany should be treated as in scope.

The EU representative: when you need one

A non-EU business subject to the GDPR must designate a representative in the EU in writing (Article 27). The representative is a contact point that supervisory authorities and individuals can approach in addition to, or instead of, you.

Question Answer (Article 27 and the EDPB guidelines)
Form of appointment A written mandate
Where One of the member states where the people you target are; if many are in one state, that state is recommended
Who A person or organisation in the EU, often a law firm or consultancy; it cannot also be your external data protection officer (DPO)
Disclosure Tell individuals who the representative is, for example in the privacy notice
Exemptions Occasional processing with no large-scale special-category data and unlikely risk; public authorities

The exemption is narrow. A shop that takes orders continuously is not "occasional".

On 12 May 2021 the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) fined Locatefamily.com €525,000 for breaching Article 27. The company had no EU establishment and had not appointed an EU representative. According to the authority's announcement, the base fine was set within a range of €300,000 to €750,000, and the company was ordered to appoint a representative within twelve weeks. It is an example of a fine imposed for not appointing a representative, which is a useful benchmark when you weigh your own position.

What the privacy notice must say

Where the GDPR applies, the privacy notice states what data you collect, for what purpose, on what legal basis, who receives it and how long you keep it, how people exercise their rights of access, correction and deletion, and how to reach your representative. A translated domestic notice is usually missing these items.

9. Cookies: consent for anything non-essential

In many places a cookie notice with a "continue" button is the norm. In the EU, Article 5(3) of the ePrivacy Directive requires prior consent for cookies and similar technologies other than those strictly necessary for the service the user asked for. Advertising and analytics tags are normally on the consent side of that line.

The EDPB has issued guidelines on the technical scope of this provision (2/2023, final version of 16 October 2024), explaining that it can reach not only cookies but other ways of accessing information on a device, such as pixels and fingerprinting.

What the consent screen must do

Item What to do
Choices Present "accept" and "reject" with equal prominence
Pre-ticked boxes A pre-ticked consent is not valid
Before consent Do not fire non-essential tags before consent
Withdrawal Keep an easy way to change the choice at any time

How you configure analytics to respect consent is a topic of its own that depends on the measurement method. For this article, remember that "measure nothing until consent is given" is the baseline for the EU.

How this differs from a domestic site

Many sites outside the EU show no consent banner at all. Extending such a site to the EU often leaves tracking tags firing before consent. Before you build, list the tags you use and sort them into essential and non-essential.

10. Where to host, and moving data across borders

Many companies assume that "because of the GDPR our servers must be in the EU". That is a misconception. The GDPR does not restrict where a server is located. What needs a basis is transferring personal data of people in the EU out of the EU.

Adequacy decisions

The European Commission's adequacy list includes Japan, Korea, Switzerland, the United Kingdom, Canada (commercial organisations), the United States (commercial organisations taking part in the Data Privacy Framework) and several other countries. For Japan the page links to a first periodic review report published on 4 April 2023, and for the UK it shows decisions renewed on 19 December 2025.

If your country is on the list, transfers from the EU to you have a ready basis. If it is not, you will rely on other tools such as standard contractual clauses. An adequacy decision is not an exemption from the GDPR itself: your obligations remain, and what the decision covers is the transfer basis.

Using US services

Most sites use US cloud or analytics tools. The EU-US Data Privacy Framework received an adequacy decision on 10 July 2023. On 3 September 2025 the EU General Court dismissed a challenge to it (case T-553/23). An appeal has been discussed in commentary and the position may change, so check whether each provider participates in the framework and keep a fallback basis such as standard contractual clauses.

Hosting options

Location Strengths Watch out for
Servers in the EU Fast for EU visitors; fewer transfer questions Decide how you will manage the servers from your own time zone
Servers in your home country Reuses your existing operations Slower for EU visitors; you must explain the transfer basis
A content delivery network (CDN) in front Fast for visitors worldwide Check whether the CDN provider touches personal data

Some rules of thumb:

  • For a mostly static company site, configuration and a CDN matter more than the server location
  • If you keep customer or order data, decide where the database lives first
  • A business customer may require EU hosting in a contract. That is a contractual matter, not a legal one

Choose the location for speed and ease of operation as well as for the legal position.

11. Accessibility: check whether the EAA applies to you

The European Accessibility Act (EAA) has applied since 28 June 2025. Businesses that offer e-commerce, booking, banking, passenger transport, e-books and similar services to EU consumers must make their sites and apps usable by people with disabilities.

Situation In scope?
E-commerce or online booking for EU consumers May be in scope
A company information site only Normally outside the service categories
A site aimed only at consumers outside the EU Reads as out of scope
B2B-only dealings Reads as out of scope
A microenterprise (under 10 staff and turnover or balance sheet at or below €2 million) offering services Exempt

This is only an outline. The exact scope, the WCAG AA technical standard, cost ranges and why overlay widgets do not make a site compliant are covered, with primary sources, in a separate article: Redesigning Your Website for the European Accessibility Act.

If you are building a new EU-facing site, making WCAG 2.2 AA a requirement from the start costs less than repairing it later.

12. Enquiries: time zones and how to write opening hours

The last item sits outside the site itself: whether you can answer European customers during your own working day. Decide this before you build. How enquiries turn into deals differs between regions too, which we cover in our article on B2B enquiry flows.

How much of the day overlaps

The EU spans several time zones, and clocks changed on 29 March and 25 October in 2026. The overlap between your working day and a customer's depends on your offset. Assuming both sides work 09:00 to 18:00, the overlap is the nine working hours minus the offset, and it disappears at nine hours or more.

With both sides working 9 to 18, a 0-hour difference gives 9 shared hours, 3 hours gives 6, 6 hours gives 3, 8 hours gives 1, and 9 hours or more gives 0. Shared working hours by offset 0 h 9 h 3 h 6 h 6 h 3 h 8 h 1 h 9 h 0 h Row labels: time difference. Numbers: shared hours.
Figure 4: Shared working hours when both sides work 9:00 to 18:00 (DevNJ's calculation; EU summer time ran from 29 March to 25 October 2026)

A company eight hours away from its customers shares one hour of the day with them. That is not enough for live phone or chat support as the default.

How to write opening hours

"Open 9:00 to 18:00" does not say in which country's time. A European customer will not convert it for you, so always state the time zone.

How it is written Example Verdict
No time zone Open 9:00 to 18:00 Unclear; avoid
Your own time zone only 9:00 to 18:00 (your local time) Forces the customer to convert
Both time zones 9:00 to 18:00 (your time) / 10:00 to 19:00 (CET) Clear; check the numbers when clocks change
A reply target Replies within one business day Sets expectations without promising speed

Publishing a reply-time target is usually the most realistic way to bridge a time difference. An enquiry that arrives in a customer's morning can be read in your day and answered before their next morning.

Use the form to narrow the request

A time difference makes every round trip slow. Design the form so that the first message contains what you need.

  • Make country, company and request type (quote, support, data request) selectable
  • Let the customer choose a reply language
  • Provide fields for attachments and URLs so the situation arrives in one message

Data requests have a deadline

Under the GDPR, a request from an individual to access or erase their data must be answered without undue delay and at the latest within one month of receipt. For complex or numerous requests the period can be extended by two further months, but you must tell the person about the extension and the reasons within the first month.

Your enquiry channel therefore needs a way to catch data requests rather than letting them sit in a shared inbox during holidays or absences.

13. Where businesses most often trip up

Of the twelve items, these are the ones businesses outside the EU overlook most often.

Pitfall What happens How to avoid it
Publishing a plain translation Price, return and privacy text does not fit EU assumptions Have native speakers and an adviser check text that carries responsibility
Showing prices without VAT Consumer total-price rules are not met Show the VAT-inclusive total for consumers
Striking through an old price to show a discount The 30-day lowest price is not the base Keep price history and calculate from the lowest price
Writing "no returns" A trader cannot remove the withdrawal right Explain the right and build the withdrawal function
Assuming EU hosting solves everything Transfers and the representative question remain Check the transfer basis and the representative separately
Firing tracking before consent Measurement without consent List the tags and hold non-essential ones until consent
Opening hours with no time zone Customers cannot tell when you are reachable State the zone and a reply target

14. What not to do

Some habits that feel natural in a home market are hard to undo later.

Do not Why
Paste machine-translated terms or return text as-is Errors in text that carries responsibility lead to disputes or regulator attention
Collect EU personal data without checking whether you need a representative A fine was imposed in a known case for not appointing one
Leave the ODR platform link in place The platform closed on 20 July 2025
Pre-tick consent or paid extras A pre-ticked box is not consent
Run a sale without a price history You cannot show the reference price
Use template legal pages (terms, Impressum, privacy notice) unchanged They will not match how your business actually works

15. A working order: decide first, then build

This is the order we suggest for an EU-facing site.

  1. Decide the market. Choose one to three countries and consumer or business customers.
  2. Decide the languages. For each country, decide whether English is enough or a local language is needed.
  3. Decide prices and VAT. Consumer totals include VAT; if you ship from outside the EU, check import VAT and IOSS.
  4. List the legal notices. Business details, withdrawal rights, terms and privacy notice, adapted to each country.
  5. Decide whether the GDPR and a representative apply. Use the tables in chapter 8 to test intention and exemptions.
  6. Decide hosting and measurement. List the hosting location, the tags in use and the consent screen.
  7. Add accessibility requirements. Check whether the EAA applies and, if so, require WCAG 2.2 AA.
  8. Decide how enquiries work. Opening hours, reply targets and who watches for data requests.

Working in this order shows what will drive the cost before design or build begins. Two local languages, a withdrawal function and a stored price history are examples of items that change a quotation directly.

16. Checklist

Before launch, confirm each of these.

  • Target countries and consumer or business focus are written down
  • Languages are chosen per country, and native speakers reviewed text that carries responsibility
  • Language versions of each page link to each other
  • Consumer prices show the VAT-inclusive total
  • Import VAT and duty are settled if you ship from outside the EU
  • Sale displays use the lowest price of the previous 30 days as the base
  • A daily price history is stored
  • The right of withdrawal is explained and an electronic withdrawal function exists
  • A business details page meets the rules of the target country
  • No link to the ODR platform remains
  • The GDPR and the representative question have been assessed and recorded
  • The privacy notice covers data types, purposes, retention, rights and the representative
  • Non-essential cookies do not fire before consent
  • Hosting location and the transfer basis are documented
  • EAA scope has been checked and, if applicable, WCAG 2.2 AA is a requirement
  • Opening hours show a time zone and a reply target
  • Someone can handle a data request within one month

17. Summary

  • An EU-facing website is not a translation of a domestic one; start from country, customer and offer
  • 47% of EU citizens can hold a conversation in English, so add local languages for consumers where needed
  • Consumer prices include VAT, and a sale is measured against the lowest price of the previous 30 days
  • There is a 14-day withdrawal right and, since 19 June 2026, an electronic withdrawal function
  • If you have no EU establishment and target EU residents, consider a GDPR Article 27 representative
  • There is no rule to host in the EU; you need a basis for transferring data out of the EU
  • For enquiries, state a time zone and a reply target to align expectations

If you are not sure where to start, begin with steps 1 and 2 of chapter 15 inside your own team: once the country and the customer are settled, the work and the assumptions behind a quotation become clear. Our range of work is on the services page, and you can ask about an EU-facing site on the contact page.

Sources used

GDPR and international transfers

Consumer law, prices and VAT

Language, business details and time

Related article

All sources were checked on 30 October 2026. Rules and tax treatment change, so confirm the current position with official guidance and a specialist before you sell. This article is not legal advice. Parts of the 26 September 2024 judgment, the withdrawal function and the EDPB guidelines could not be reached on the EUR-Lex legal database automatically, so they were checked through law-firm and vendor commentary and reproductions. Figures 1, 2 and 4 were made by DevNJ; the dates in figure 3 follow the sources above.

FAQ

Is an English-only website enough for European customers?
For specialised B2B sales, English alone often works. For consumers it depends on the country, and local-language pages usually build more trust. The European Commission's 2023 survey found that 47% of EU citizens can hold a conversation in English, so fewer than half. Pick the countries first, then choose the languages.
Does a non-EU company need an EU representative under GDPR Article 27?
Generally yes, if the GDPR applies to you because you offer goods or services to people in the EU and you have no EU establishment. The exemptions are narrow, such as occasional low-risk processing. A site that can merely be opened from the EU is not enough to trigger the rule. What matters is whether you intend to target EU residents.
Do I have to show prices including VAT on a website for EU consumers?
Yes, when you sell to consumers. The total price including taxes and extra charges must be clear before purchase, and VAT rates differ by country. Pure B2B sites commonly show prices without VAT, but if a consumer can buy through any path on the site, show the VAT-inclusive total for that path.
Do I have to host my website in the EU to comply with GDPR?
No. The GDPR does not require servers to be in the EU. It regulates transfers of personal data out of the EU, which need a legal basis such as an adequacy decision or standard contractual clauses. Choose the hosting location for speed and for how easily you can explain your transfers, not out of a fear of a rule that does not exist.
How should I handle customer enquiries from a different time zone?
Do not promise real-time answers. State your opening hours with the time zone, give a reply-time target such as one business day, and use a form that collects the details in the first message. Data subject requests under the GDPR have their own deadline of one month, which can be extended by two further months in complex cases.
Does the European Accessibility Act apply to my company if I am outside the EU?
It can. If you provide covered services such as e-commerce or online booking to consumers in the EU, you may be in scope, unless the microenterprise exemption applies. A corporate information site, or a site aimed only at consumers outside the EU, or a purely B2B offer, is normally outside the six service categories. We cover the conditions in a separate article.

Planning a site that has to work in both markets?

Get in touch

Contents