In this article: what happens to the cart and checkout when translating a Tilda website, why it's more difficult than translating regular pages, and how to solve the problem correctly.
The shopping cart is the most important element of an online store. The user has selected a product, added it to the cart, started placing an order — and then sees Russian text. For a German buyer, this is a signal that the store is "not for them".
Why the cart is not translated by standard methods
The shopping cart on Tilda is a dynamic component. Its content: "Add to Cart" and "Checkout" buttons, address fields, error messages, order confirmation — all of this is generated by JavaScript in the browser.
The static HTML that a regular proxy translator sees does not contain the cart text. It appears later, when the user interacts with the page.
Result: the website is translated, but the cart is not.
What exactly needs to be translated
The entire user journey from catalog to confirmation. In the catalog: "Add to Cart" button, counter, mini-cart. On the cart page: product names, total amount, "Checkout" button. During checkout: form fields, placeholder texts, delivery and payment options, error messages. After checkout: confirmation screen and email.
The most painful part is error messages. "Enter a valid email" in Russian in a German store is not just unsightly, it's a signal that the store is unfinished.
Server-side rendering. A proxy that executes JavaScript before delivering the page to the user — it receives the page with the cart already loaded and translates all text, including dynamic content.
Customization via Tilda API. For some cart texts, Tilda provides the ability to override them through store settings — but this is a limited option.
Manually via JS replacement. A script that finds cart elements after the page loads and replaces the text. It works, but is unstable — the structure may change with Tilda updates.
Currency in the Cart
A separate task is to display the correct currency in the cart for each language version. A German user wants to see the price in euros, not rubles.
1. Add an item to the cart in each language version — are all labels in the correct language? 2. Proceed to checkout — form fields, placeholders, buttons? 3. Intentionally enter incorrect data — error messages? 4. Place a test order — on-screen and email confirmation?
Frequently Asked Questions
Why does the Tilda cart remain in Russian after connecting a translator?
The cart is generated by JavaScript in the browser after the page loads. Most translators process the server's HTML response and do not see the cart content — it appears later.
How to test cart translation before launching the store?
Add an item to the cart in the test language version and go all the way to confirmation. Check buttons, error messages when entering incorrect data, and the successful order screen.
Is it possible to show different prices for different countries without changes in Tilda?
Yes, via a proxy with currency conversion. The proxy recalculates prices on the server before the page reaches the browser — Google indexes the correct prices in the correct currency.
What to do with email order confirmation in different languages?
Email is sent via Tilda — it can be in one language. For full localization of email notifications, you need to use an external mailing service with templates in each language.
Do you need a fully translated cart on Tilda?
Multify translates the cart, checkout, and all forms — including dynamic content. Check it on your store's demo.