WordPress Multilingual Without a Plugin: 3 Real Options

By 9 min read

You want your WordPress site in a second language, but you are tired of plugin stacks that slow down the admin, break on updates and lock your content into their own database tables. Good news: making a WordPress site multilingual without a plugin is possible and often perfectly reasonable for small business sites. This guide shows you the three approaches that actually work, the code you need for the manual route and the trade-offs that decide which one fits your site.

Why WordPress does not do this on its own

WordPress core still has no built-in way to link an English page to its German or Spanish counterpart. The official WordPress roadmap lists “Multilingual” as Phase 4 of the Gutenberg project, the last phase on the list, with no timeline attached. Plans for that phase go back years: at the 2018 State of the Word, Matt Mullenweg said Phase 4 would aim to develop an official way for WordPress to support multilingual sites, as WP Tavern reported.

What about the language dropdown under Settings? The WordPress documentation for the General Settings screen describes Site Language simply as the dashboard language. It switches the language of WordPress itself, not your pages. Your content stays in whatever language you wrote it in.

So “multilingual without a plugin” always means one of three things: you structure translated pages yourself, you run one site per language or you let an external service translate the pages.

Why it is worth the effort

If you sell anything online, language is not a cosmetic detail. In a CSA Research survey of 8,709 consumers in 29 countries, 76% of online shoppers said they prefer products with information in their native language and 40% said they never buy from websites in other languages. In Germany, 57% of respondents buy only from local-language websites, the highest share in that study.

The same survey found that 65% prefer content in their language even if the quality is poor. That is a useful reminder: a solid translation that ships this month beats a perfect one that never leaves your to-do list.

Option 1: Manual language folders with pages and menus

This is the purest “no plugin” approach. You keep one WordPress installation and build each language as its own branch of pages.

Set up the structure

  1. Create a parent page called “de” (or “es”, “fr” and so on) and publish it. With pretty permalinks active, its URL becomes example.com/de/.
  2. Duplicate each page you want to translate, translate the content and set the “de” page as its parent. The German “About” page then lives at example.com/de/ueber-uns/.
  3. Create a second navigation menu for the German pages and assign it in your theme. Block themes let you place a separate navigation block in a German page template. Classic themes may need a small conditional in the header.
  4. Add a plain link to the other language in the header or footer so visitors can switch.

That last step matters more than it looks. Google’s guide on managing multilingual sites advises against redirecting visitors automatically based on what you guess their language is, because those redirects can stop people and search engines from reaching all versions. Visible links let everyone choose.

Tell browsers and Google which language is which

Two small snippets in a child theme’s functions.php handle this. The first sets the lang attribute on German pages through the language_attributes filter, which controls the attributes in the <html> tag:

add_filter( 'language_attributes', function ( $output ) {
    $german_pages = array( 48, 51 ); // IDs of your German pages
    if ( in_array( get_queried_object_id(), $german_pages, true ) ) {
        return 'lang="de-DE"';
    }
    return $output;
} );

The second adds hreflang annotations. Google’s documentation on localized versions requires that every version lists itself and all other versions. If page A points to page B but B does not point back, Google ignores the tags. A simple map of page IDs takes care of that:

add_action( 'wp_head', function () {
    $pairs = array(
        12 => 48, // English page ID => German page ID
        15 => 51,
    );
    $id = get_queried_object_id();
    $en = isset( $pairs[ $id ] ) ? $id : array_search( $id, $pairs, true );
    if ( ! $en ) {
        return;
    }
    $de = $pairs[ $en ];
    printf( '<link rel="alternate" hreflang="en" href="%s" />' . "\n", esc_url( get_permalink( $en ) ) );
    printf( '<link rel="alternate" hreflang="de" href="%s" />' . "\n", esc_url( get_permalink( $de ) ) );
    printf( '<link rel="alternate" hreflang="x-default" href="%s" />' . "\n", esc_url( get_permalink( $en ) ) );
} );

The x-default line marks the fallback page for visitors whose language you do not offer.

Where it hurts

The manual method is free and transparent, but it scales badly. Every new page means a duplicate, a translation and a new entry in your ID map. Theme strings such as “Read more” or the search placeholder stay in the site language. Blog archives, categories and shop pages mix languages unless you build separate categories too. For a brochure site with ten pages, that is fine. For a WooCommerce shop with 300 products, it is a part-time job.

Option 2: WordPress Multisite with one site per language

Multisite is part of WordPress core, so it counts as “no plugin”. You run a network and give each language its own subsite, for example example.com/de/ and example.com/fr/. Each subsite has its own pages, menus and settings, which means the dashboard language and many theme strings can follow the language of that subsite.

What you need to know before you start

The official guide to creating a network asks you to back up your files and database, confirm pretty permalinks work, deactivate all plugins and then add WP_ALLOW_MULTISITE to wp-config.php. After that, a Network Setup screen appears under Tools where you choose between subdomains and subdirectories.

That choice has restrictions. According to the network preparation guide, you cannot pick subdirectories if your installation has been running for more than a month, because of conflicts with existing permalinks. Subdomains, in turn, need wildcard DNS for on-demand sites and do not work when WordPress sits in a subfolder, on localhost or on an IP address. On shared hosting, you may have to ask your host for help with these requirements.

The trade-offs

Multisite gives you clean separation, but nothing connects the subsites. WordPress does not know that the German “Kontakt” page and the English “Contact” page belong together, so you still add hreflang links yourself (the snippet above works across sites if you hardcode full URLs instead of page IDs). You also maintain every page twice. Some hosts and themes handle Multisite less gracefully than a single site. It is a strong choice when your language versions really differ, such as separate teams, products or legal texts per country.

Option 3: A translation script or proxy

The third route skips WordPress content management entirely. You add a translation service’s script tag to your theme (through a child theme or the theme’s header area) and the service translates your pages for visitors. Some services work as a proxy in front of your site instead of a script.

This approach shines when you have many pages, frequent updates or other platforms besides WordPress. You write in one language and the translations follow. It also means no duplicated pages and no ID maps.

There are two questions to ask any vendor before you sign up.

  1. Does each language get its own URL? Google recommends different URLs for each language version instead of switching the language through cookies or browser settings, partly because Googlebot usually crawls from the USA without sending a language preference. If a script only swaps text on the same URL, search engines may never see your translations.
  2. What does the translated page look like after rendering? Google renders JavaScript with a headless Chromium, but content that is not visible in the rendered HTML cannot be indexed.

Quality also deserves a thought. Google’s spam policies name automated translation among the techniques that count as scaled content abuse when the pages provide little value to users. Machine translation is fine as a starting point, but someone should review the pages that matter most.

heylingo is one example of this category: you add one script tag, it translates into 30+ languages with AI and a translation memory and you can correct wording inline on your live site. The price is EUR 20 per 1,000,000 translated characters per month. Ask about the URL setup for your languages before you commit, as you would with any script vendor.

Comparison: which approach fits your site

The table below sums up how the three options differ for a typical small business site.

Manual language folders Multisite Translation script or proxy
Extra software None None (core feature) External service
Setup effort Low for few pages Medium to high Low
Ongoing effort Every page twice Every page twice Mostly review
Theme strings translated No Partly, per subsite Usually yes
Separate URLs per language Yes Yes Depends on vendor
hreflang Your code Your code Ask the vendor
Best for Small brochure sites Distinct country sites Larger or fast-changing sites

If your site has a handful of pages that rarely change, the manual route costs you nothing but an afternoon. Multisite makes sense when each language version is really its own business. Once you publish weekly or run a shop, the maintenance load of the first two options usually outweighs the convenience of avoiding a service. For a broader view of tools and pitfalls, see our guide to common website translation mistakes.

FAQ

Can WordPress translate my content without a plugin?

Not by itself. The Site Language setting changes the dashboard language, not your pages. You either create the translated pages yourself, run one subsite per language or connect an external translation service.

Is the manual method bad for SEO?

No, as long as each language has its own URL, the lang attribute is correct and your hreflang tags point both ways. Google’s guidance favors separate URLs per language, which the manual method gives you by design.

Should I redirect visitors to their language automatically?

Google advises against automatic redirects based on a guessed language because they can hide versions from users and crawlers. Offer clear links to each language instead and let visitors choose.

Does Multisite work with an existing site?

Yes, but with limits. If your installation is older than a month, you can only use subdomains, not subdirectories. Back up everything and deactivate plugins before you enable the network.

When will WordPress support multilingual sites natively?

Nobody knows yet. The official roadmap lists multilingual support as Phase 4 without a date, so plan with the tools available today.

Conclusion

Making WordPress multilingual without a plugin comes down to how much manual work you are willing to carry. Language folders with a few lines of PHP are ideal for small, stable sites. Multisite suits businesses whose language versions are truly separate. A translation script or proxy takes the duplication off your plate, as long as you confirm that every language gets its own URL. Pick the option that matches your page count and update rhythm, then work through our website localization checklist before you announce the new languages.

Want your WordPress site in 30+ languages with one script tag? See heylingo pricing.

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