Machine Translation Quality in 2026: Good Enough or Not?

By 9 min read

If you run a shop or a business site, you have probably asked yourself whether AI translation is finally good enough to publish without a translator looking over every line. The honest answer in 2026 is “often yes, sometimes absolutely not.” Machine translation quality has improved so much that the best systems now rival human translators on research benchmarks, yet the same research shows exactly where things still break. Here is what the evidence says, so you can decide which pages to automate and which deserve a human.

What the latest benchmarks actually show

The most rigorous yardstick for machine translation is the annual General Machine Translation task at the Conference on Machine Translation (WMT). Professional annotators score real system outputs, which makes it far more trustworthy than vendor marketing.

WMT24: the LLM era arrives

The 2024 findings paper carries a telling title: The LLM Era is Here but MT is Not Solved Yet. Organizers evaluated 11 language pairs and collected outputs from 8 large language models and 4 online translation providers on top of the submitted systems. A few results stand out for website owners:

  • The best systems for English to Spanish produced translations the authors described as close to flawless, making it the easiest pair in the test (WMT24 findings).
  • Claude 3.5 Sonnet was the best system overall, winning 9 of 11 language pairs (WMT24 findings).
  • Human reference translations landed in the winning cluster in only 7 of 11 pairs, although the authors note the English to Hindi reference was of suboptimal quality (WMT24 findings).
  • Speech was the hardest domain, likely because errors from automatic speech recognition carried into the translation (WMT24 findings).

WMT25: harder tests, same pattern

For 2025 the organizers deliberately picked more difficult source documents and titled their paper Time to Stop Evaluating on Easy Test Sets. They evaluated 60 systems in total, 24 of them LLMs or popular online translation services. Even on harder material, Gemini 2.5 Pro sat in the top cluster for 14 language pairs, while human references made the winning cluster in only 6 of 15 pairs (WMT25 findings).

The detail that matters most for you is the spread. The best system almost always scored 90 or higher on the 100 point scale, yet mid-tier models often scored 60 or below and the weakest could drop to 0 depending on language pair and domain (WMT25 findings). “AI translation” is not one quality level; the engine you pick matters.

Where the sources disagree

The research is not perfectly consistent:

  • Automatic scores vs. human judges. In WMT24, Unbabel Tower70B ranked first on automatic metrics across all languages but did not win across the board with human annotators (WMT24 findings). In WMT25, Shy hunyuan MT topped the automatic rankings for all but one pair, while human evaluation placed it considerably lower (WMT25 findings). Treat any vendor quality score based only on metrics with caution.
  • Literary text. WMT24 found news, literary and social content similarly difficult, while WMT25 rated literary texts the easiest. The WMT25 authors themselves caution that error-based scoring can reward translations that are technically correct but miss the author’s voice (WMT25 findings).
  • Vendor studies. Intento, a company that sells translation automation, reports that its 2025 evaluation of 46 engines across 11 language pairs found that customizing terminology, tone, formatting and consistency produced five to ten times fewer errors than the baseline (Intento). Useful, but not an independent benchmark.

Where AI translation is good enough

AI translation is reliable when three things are true: the language pair is well resourced, the text is reasonably standard and an occasional slightly awkward phrase would not hurt anyone.

Even in medicine, high-resource languages perform well. A 2024 study in Pediatrics compared ChatGPT and Google Translate with professional translators on 20 discharge instruction sets and found the machine output comparable to professional translation for Spanish and Brazilian Portuguese (American Academy of Pediatrics). A 2019 study of emergency department instructions found Google Translate 92% accurate for Spanish (PSNet).

For a typical business site that translates into German, French, Spanish, Italian or Portuguese, this means product descriptions, blog posts, FAQs and category pages are realistic candidates for AI translation with light spot checks.

Where AI translation is not good enough

Low-resource languages and dialects

Quality drops sharply once you leave the big languages. A large evaluation of GPT models across 204 languages found them underperforming traditional machine translation for 84.1% of the languages covered, with resource level the strongest predictor of quality (Robinson et al.). A 2025 study of 200 languages on FLORES-200 still found low-resource languages clearly behind high-resource ones (Song et al.).

In WMT25, translation into Maasai was described as largely unusable, with systems often producing Swahili instead. For Egyptian Arabic, systems tended to output Modern Standard Arabic rather than the dialect requested (WMT25 findings). If your audience speaks a regional variety, check that the output is actually in that variety.

Medical content

The Pediatrics study that looked fine for Spanish told a different story for Haitian Creole: potentially clinically significant errors appeared in 33.3% of ChatGPT translations and 23.3% of Google Translate translations, compared with 8.3% for professional translations (HealthDay). A 2021 study of Google translated discharge instructions, summarized by the National Center for State Courts, found accuracy ranging from 94% for Spanish down to 55% for Armenian (NCSC). Some of this research tested older tools, but none of the studies we found shows the gap for smaller languages closing.

Legal content

The NCSC’s 2025 guide for US courts states that machine translation cannot yet be relied on to convey complex information or legal concepts and that courts should never use it to convey legal or procedural information, while allowing drafts for review by professional translators (NCSC). The same guide notes US Department of Justice guidance that discourages machine translation alone even with a disclaimer. For a business site, that applies to your terms and conditions, privacy policy, warranty terms and anything contractual.

Messy input

WMT25 found that state-of-the-art systems still struggle with non-standard input, linguistic complexity, domain-specific terminology and gender agreement in some language pairs (WMT25 findings). Think slang, puns and product jargon. For brand names and product terms, a glossary helps a lot; see our guide on translating brand terminology.

What Google says about machine-translated pages

Google’s spam policies list “automated transformations like synonymizing, translating” as a form of scaled content abuse when content is scraped to generate many pages that provide little value. That policy was introduced in March 2024 and targets content made mainly to manipulate rankings, however it was produced.

In June 2025, Google told SEO consultant Glenn Gabe that its policies “do not strictly define content that has been translated by AI as spam” (GSQI). Gabe also noted that Google removed older advice about blocking auto-translated pages from its multilingual documentation. The practical reading: translating useful pages is fine, while mass-translating thin pages to grab traffic is the risk.

Good enough, review needed or human only?

The table below sorts typical website content by how much human involvement the evidence above suggests. It assumes a well-resourced language pair; for smaller languages, move everything one column to the right.

Content type Good enough with AI Review needed Human only
Product descriptions and category pages ✓
Blog posts and help articles ✓
Navigation, buttons and UI text ✓
Headlines, slogans and ad copy ✓
Checkout, shipping and returns info ✓
Health, safety or dosage information ✓
Terms, privacy policy and contracts ✓

The pattern is simple: the higher the cost of a misunderstanding, the further right a page belongs. UI text sits in the middle because short strings carry little context, so a quick check on the live page is worth it. Marketing copy sits there because, as WMT25 hinted, a translation can be error-free and still lose your voice.

How to make AI translation work on your site

You do not need a big localization budget for this:

  1. Pick the engine by evidence. The WMT spread between top and mid-tier systems is huge, so test a few pages in your target languages before committing.
  2. Keep a glossary and translation memory. A glossary targets the terminology problems WMT25 flagged.
  3. Review where it counts. Spend human time on checkout, legal and safety pages, not on your 400th product description. Our post-translation editing guide covers light vs. full review.
  4. Fix errors in context. Mistakes are easiest to spot on the live page, not in a spreadsheet.
  5. Send legal text to a professional. Use AI drafts at most as a starting point, as the NCSC suggests for courts.

This is the workflow heylingo is built around: you add one script tag, pages are translated by AI with a translation memory and you can correct any string inline on the live site, in 30+ languages, for EUR 20 per 1,000,000 translated characters per month. It does not replace a lawyer reviewing your terms and it is not meant to.

FAQ

Is AI translation better than human translation in 2026?

For some well-resourced language pairs, top systems now match human references. In WMT25, human translations made the winning cluster in only 6 of 15 pairs (WMT25 findings). That does not hold for every engine or language.

Will Google penalize my machine-translated pages?

Not for being translated. Google’s spam policy targets scaled, low-value content. Google has also said AI-translated content is not strictly defined as spam (GSQI). Translate pages that are useful in the first place.

Which languages are risky for AI translation?

Languages with little digital training data, such as Haitian Creole, Armenian or Maasai in the studies above, plus dialects like Egyptian Arabic. Have a native speaker check those before publishing.

Should I use ChatGPT or a dedicated translation engine?

The evidence does not crown one approach. LLMs won WMT overall, but the 2023 FLORES study found traditional machine translation stronger for most low-resource languages (Robinson et al.). Test on your own content.

Conclusion

Machine translation quality in 2026 is good enough for most everyday website content in major languages. Top systems now rival human translators on research benchmarks. It is not good enough for legal text, health information or smaller languages without a human check. Sort your pages by the cost of a mistake, automate the low-risk majority and put your review time where errors would actually hurt. If you want to compare approaches in more depth, read our take on Google Translate vs. professional translation services.

See heylingo pricing and start translating your site

Sources

JE

Written by

Jermaine builds and runs heylingo single-handedly from Germany and answers every support email personally.

More from the blog

Information pursuant to § 5 DDG (German Digital Services Act).

Jermaine J. Ernst
c/o Block Services
Stuttgarter Str. 106
70736 Fellbach
Germany

Email: info@heylingo.io
VAT ID: DE370296865

Responsible for content pursuant to § 18 (2) MStV: Jermaine J. Ernst, address as above.

Consumer dispute resolution

We are neither willing nor obliged to take part in dispute resolution proceedings before a consumer arbitration board.

Liability for content

As a service provider we are responsible for our own content on these pages under general law, pursuant to § 7 (1) DDG. Under §§ 8 to 10 DDG we are not obliged to monitor third-party information that is transmitted or stored, or to investigate circumstances that indicate illegal activity. Obligations to remove or block the use of information under general law remain unaffected. Liability in this respect is only possible from the moment we become aware of a specific infringement. As soon as we learn of such an infringement, we will remove the content immediately.

This website links to external websites of third parties whose content we cannot influence, so we cannot accept any liability for that content. The respective provider or operator of a linked page is always responsible for its content. The linked pages were checked for possible legal violations when the link was set, and no illegal content was apparent at that time. Permanent monitoring of linked pages is not reasonable without concrete indications of an infringement. If we become aware of an infringement, we will remove the link immediately.

The content and works created by the site operator on these pages are subject to German copyright law. Reproduction, editing, distribution and any kind of use beyond the limits of copyright law require the written consent of the respective author or creator. Where content on this site was not created by the operator, the copyrights of third parties are respected and such content is marked as such. If you nevertheless become aware of a copyright infringement, please let us know. As soon as we learn of an infringement, we will remove the content immediately.

Last updated 10 October 2026

Privacy policy

This privacy policy explains which personal data we process when you visit heylingo.io, contact us or buy heylingo. It also explains how data is handled when one of our customers uses the heylingo translation service on their own website.

Controller

The controller within the meaning of the EU General Data Protection Regulation (GDPR) is:

Jermaine J. Ernst
c/o Block Services
Stuttgarter Str. 106
70736 Fellbach
Germany

Email: info@heylingo.io

Please use this address for any question about data protection and to exercise your rights.

Overview

heylingo.io is a static website. When you browse it:

Personal data is processed only in the cases described below: delivery of the website by our host, images in blog posts, YouTube videos you choose to play, contact by email and the purchase of heylingo through Stripe. A separate section covers the heylingo translation service.

Hosting and server logs

heylingo.io is hosted by Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Each time you open a page, Cloudflare processes the following server log data:

Cloudflare uses this data to deliver the website to you and to protect it from attacks and misuse. We do not use it to identify you or to create user profiles.

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is the secure and reliable delivery of our website.

Cloudflare may process data outside the European Union, including in the USA. Cloudflare, Inc. is certified under the EU-U.S. Data Privacy Framework, so transfers to it are based on the adequacy decision of the European Commission (Art. 45 GDPR). Where the Data Privacy Framework does not apply, transfers are based on the EU standard contractual clauses (Art. 46(2)(c) GDPR).

More information: Cloudflare privacy policy.

Blog images and videos

Images

Images in our blog posts are loaded from assets.seobotai.com, an external image host. When you open a blog post, your browser requests these images directly from that host. The host thereby receives your IP address and the technical information that is part of every request, such as the requested file, the address of our website and your browser’s user agent.

The host needs your IP address to deliver the images. We have no influence on how the host processes this data.

The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is showing images in our blog posts.

YouTube videos

Some blog posts contain YouTube videos. They are not loaded when you open the page. No data is sent to YouTube until you click “play”. Only then is the video loaded from youtube-nocookie.com.

YouTube is operated by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Once the video is loaded, Google receives at least your IP address and the address of the page. Google may also store information on your device or read it from your device, for example cookies, and may process data about how you use the video. Google may process data in the USA; Google LLC is certified under the EU-U.S. Data Privacy Framework.

The legal basis is your consent, which you give by clicking “play” (Art. 6(1)(a) GDPR and, for storing and reading information on your device, § 25(1) of the German Telecommunications and Digital Services Data Protection Act, TDDDG).

Your consent applies only to the video you start. You can withdraw it at any time with effect for the future: do not start any further videos and close or reload the page. You can delete cookies set by Google in your browser settings.

More information: Google privacy policy.

Contact by email

If you email us, we process your email address, your message and any other information you provide, such as your name or company. We use this data only to answer your request.

If your request relates to a contract with us or to concluding one, the legal basis is Art. 6(1)(b) GDPR. Otherwise the legal basis is Art. 6(1)(f) GDPR; our legitimate interest is answering requests sent to us.

We delete the data once your request has been fully dealt with, unless statutory retention obligations apply (see “Retention”).

Purchasing heylingo via Stripe

You sign up for heylingo through Stripe Checkout, which you reach via a payment link on heylingo.io. Invoices, your payment method and cancellation are managed in the Stripe Customer Portal. There is no user account on heylingo.io.

The payment provider is Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland. Stripe processes the data you enter during checkout and in the customer portal. This includes your name, email address, billing address, company name and VAT ID if you provide them, your payment details, and transaction and invoice data.

You enter your payment details directly with Stripe. We do not receive your full card or account details.

We receive from Stripe the data we need to manage your subscription and bill your usage, such as your name, email address, billing details and payment status. To bill you, we report your usage (the number of translated characters) to Stripe.

The legal basis is Art. 6(1)(b) GDPR, because the processing is necessary to conclude and perform the contract. We keep invoices and accounting records to meet our retention obligations under German commercial and tax law. The legal basis for this is Art. 6(1)(c) GDPR.

Stripe also processes some data under its own responsibility, for example to prevent fraud and to meet its legal obligations as a payment provider. Stripe may transfer data to Stripe, Inc. in the USA, which is certified under the EU-U.S. Data Privacy Framework.

More information: Stripe privacy policy.

The heylingo translation service

This section is for our customers and for visitors to websites that use heylingo.

Our role

heylingo makes a customer’s website multilingual. When a customer uses heylingo, we process the content of the customer’s website on the customer’s behalf. For any personal data of visitors to that website, the customer is the controller and we act as a processor (Art. 28 GDPR).

If you visit a website that uses heylingo, please read that website’s privacy policy and send requests about your data to its operator.

Customers can request a data processing agreement under Art. 28 GDPR at info@heylingo.io.

In the visitor’s browser

The customer adds the heylingo script to their website. The script shows a language switcher and picks the visitor’s preferred language. It stores the chosen language in the visitor’s browser (localStorage) so the website appears in that language on later visits. The script sets no cookies.

The entry stays in the browser until the visitor deletes it. Storing it is limited to what is strictly necessary for the language function the visitor uses (§ 25(2) no. 2 TDDDG).

Translation

To translate a page, the script sends the page’s text to our translation service. Because the visitor’s browser connects to the service, the service also receives the visitor’s IP address and the technical information that is part of every request.

Page text usually contains no personal data. If a page does contain personal data, for example names on a team page or text shown only to a logged-in user, this text is sent to us as well. The customer decides on which pages the script runs.

Text that is translated for the first time is translated by AI. For this we use a large language model of Anthropic PBC, USA, through its API, as a sub-processor. Transfers to Anthropic are based on the EU standard contractual clauses (Art. 46(2)(c) GDPR).

Each translation is stored in a translation memory for that website. Later visitors receive the stored translation, so the same text is not sent to the AI provider again.

The translation service and the translation memories run on servers of netcup GmbH in Germany.

Inline editing

Customers can correct translations directly on their live website. This edit mode can only be used by the site owner. Corrected sentences are stored in the translation memory and are never re-translated.

Deletion

When a customer cancels, the script stops translating and the website shows its original language. The website’s translation memory, including manual corrections, is deleted 30 days after the cancellation takes effect.

Retention

We keep personal data only as long as it is needed for the purpose it was collected for, unless a statutory retention obligation applies. While such an obligation applies, we use the data only for that purpose.

Your rights

You have the following rights regarding your personal data:

To exercise your rights, email info@heylingo.io. If your request concerns a website that uses heylingo, please contact the operator of that website first, as it is the controller. We support our customers in answering such requests.

Right to object

Where we process your data on the basis of Art. 6(1)(f) GDPR, you can object to the processing at any time on grounds relating to your particular situation (Art. 21 GDPR). We will then stop processing your data, unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves to establish, exercise or defend legal claims.

Right to lodge a complaint

You can lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the EU member state of your habitual residence, your place of work or the place of the alleged infringement. The authority responsible for us is Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg (the State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg).

No automated decision-making

We do not use automated decision-making, including profiling, within the meaning of Art. 22 GDPR. The AI used by heylingo translates text; it does not make decisions about people.

Changes to this policy

We update this policy when our services or the legal requirements change. The current version is always available on heylingo.io. The date of the last update is shown at the end of this policy.

Last updated 10 October 2026

Terms of service

These terms of service govern the use of heylingo, a service that makes websites multilingual. heylingo is offered to businesses only.

1. Scope and parties

These terms apply to all contracts for the use of heylingo between Jermaine J. Ernst, c/o Block Services, Stuttgarter Str. 106, 70736 Fellbach, Germany, email info@heylingo.io (“we”, “us”) and our customers (“you”).

heylingo is offered exclusively to entrepreneurs (Unternehmer) within the meaning of § 14 BGB. These are natural or legal persons or partnerships with legal capacity who conclude the contract in the exercise of their commercial or independent professional activity. Consumers are not our target group. By concluding a contract, you confirm that you are acting as an entrepreneur.

Your own terms and conditions do not apply, even if we do not expressly object to them, unless we have agreed to them in text form.

2. The service

heylingo makes your website multilingual. You add one script tag to your website. The script shows a language switcher, selects the visitor’s preferred language, stores the chosen language in the visitor’s browser, sends the page’s text to our translation service and replaces it with the translation.

Text that has not been translated before is translated by AI (a large language model) and stored in a translation memory for your website. Later page views receive the stored translation.

All languages supported by heylingo are included. The currently supported languages are listed on heylingo.io.

You can correct translations directly on your live website, in an edit mode that only you as the site owner can use. Sentences you have edited manually are never re-translated.

There is no user account or dashboard on heylingo.io. Invoices, your payment method and cancellation are managed in the Stripe Customer Portal.

For the term of the contract, you receive a non-exclusive, non-transferable right to use the heylingo script on your website. All other rights to heylingo remain with us.

We may use subcontractors to provide the service, in particular for hosting and AI translation. We may develop heylingo further and change its features, provided the core function described in this section is preserved and the change is reasonable for you.

3. Conclusion of the contract

The description of heylingo on heylingo.io is not a binding offer.

You sign up through Stripe Checkout, which you reach via the payment link on heylingo.io. By completing the checkout, you make a binding offer to conclude the contract. We accept it by activating your subscription, which normally happens immediately after checkout.

The contract language is English. These terms can be viewed, saved and printed on heylingo.io at any time.

4. Prices and billing

heylingo has one pricing model: pay per use. The price is a monthly price per one million translated characters, as listed on heylingo.io (currently EUR 20 per 1,000,000 characters per month). It includes all supported languages.

The characters counted for a month are the characters of the translated text that heylingo keeps for your website in its translation memory, across all target languages. Page views and the number of visitors do not affect the price.

Billing runs through Stripe as a metered subscription. Your usage is billed monthly in arrears and charged to the payment method you stored with Stripe. Invoices are available in the Stripe Customer Portal.

All prices are net prices. VAT is added where applicable.

We announce price increases by email at least 30 days before they take effect. A new price applies from the first billing month after it takes effect. As you can cancel at any time, you can avoid a price increase by cancelling before it takes effect.

If a payment fails, we may suspend the service after notifying you until the outstanding amount has been paid. During a suspension, your website shows its original language.

5. Your obligations

You must hold all rights needed to have the content of your website translated, stored and displayed, including in translated form.

You grant us a non-exclusive right to process, translate, store and deliver your content and its translations, to the extent necessary to provide heylingo. This includes the right to have our subcontractors do so. The right is limited to the term of the contract and the deletion period in section 8.

You must not use heylingo for unlawful content, in particular content that infringes the rights of third parties or violates criminal law.

You are responsible for integrating the script correctly, as described by us, and only on websites that you operate or are authorised to operate.

You must not misuse heylingo. In particular, you must not:

If a third party asserts claims against us because of content on your website or because you breached these terms, you indemnify us against these claims, including the reasonable costs of legal defence. This does not apply if you are not responsible for the breach.

6. AI translations

Translations are produced automatically by AI. We do not review them before they are shown on your website.

Machine translations may contain errors, omissions or wording that does not fit the context. We provide machine translation, not a reviewed or certified translation.

You should review translations, especially where errors can have legal or financial consequences, such as legal texts, prices, product information and safety notices. You can correct any translation in the edit mode on your website.

You are responsible for all content published on your website, including its translations.

7. Availability

We aim to keep heylingo available and working, but we do not guarantee a specific availability or uptime. Interruptions can occur, for example due to maintenance, updates or disruptions at our subcontractors.

If heylingo is unavailable, your website shows its original language. As you pay only for translated characters, no charges arise for text that is not translated.

8. Term and cancellation

The contract starts when it is concluded and runs for an indefinite period.

You can cancel at any time in the Stripe Customer Portal or by email to info@heylingo.io. Usage up to the effective date of cancellation is billed.

We can cancel the contract with 30 days’ notice by email.

The right of both parties to terminate for good cause without notice remains unaffected. Good cause for us exists in particular if you are in default of payment despite a reminder, use heylingo for unlawful content or seriously breach your obligations under section 5. In these cases, we may instead suspend the service for your website.

After the contract ends, the script stops translating and your website shows its original language. We delete your website’s translation memory, including manual corrections, 30 days after the contract ends. We recommend removing the script tag from your website.

9. Data protection

We process personal data in accordance with the GDPR and our privacy policy.

When you use heylingo, we process the content of your website on your behalf. For any personal data of visitors to your website, you are the controller and we act as your processor. A data processing agreement under Art. 28 GDPR is available on request at info@heylingo.io.

You are responsible for meeting your own data protection obligations towards the visitors of your website, in particular for informing them about the use of heylingo in your privacy policy.

10. Liability

We are liable without limitation for intent and gross negligence, for injury to life, body or health, where we have given a guarantee, and under the German Product Liability Act (Produkthaftungsgesetz).

For slight negligence, we are liable only for breach of an essential contractual obligation. This is an obligation whose fulfilment makes the proper performance of the contract possible in the first place and on whose fulfilment you may regularly rely. In that case, our liability is limited to the damage that is typical for this type of contract and foreseeable when the contract was concluded.

Otherwise, liability for slight negligence is excluded. Strict liability for defects that already existed when the contract was concluded (§ 536a(1) BGB) is also excluded.

These limitations also apply in favour of our vicarious agents and subcontractors.

11. Changes to these terms

We may change these terms for a valid reason, in particular because of changes in the law or case law, or changes to heylingo. We will notify you of changes by email at least 30 days before they take effect.

You can object to the changes within this period. If you do not object, the changed terms are deemed accepted. We will point this out specifically in our notice. If you object, the contract continues on the previous terms, and we may cancel it in accordance with section 8.

This procedure does not apply to changes to the main obligations of either party. Price changes are governed by section 4, changes to the service by section 2.

12. Final provisions

German law applies, excluding the UN Convention on Contracts for the International Sale of Goods (CISG).

If you are a merchant (Kaufmann), a legal entity under public law or a special fund under public law, or if you have no general place of jurisdiction in Germany, the exclusive place of jurisdiction for all disputes arising from this contract is the competent court for Fellbach, Germany. We may also bring an action at your general place of jurisdiction.

If any provision of these terms is or becomes invalid, the remaining provisions remain valid. The invalid provision is replaced by the statutory provisions.

Last updated 10 October 2026