Your shop in other languages
Bang! Cart has no language system of its own, and does not need one. If your site runs WPML or Polylang, that plugin decides which language a visitor sees, and Bang! Cart follows it - for its own wording and for yours.
There are two kinds of text in a shop. Bang! Cart's own wording - "Your basket is empty", the "Checkout" button when you have not renamed it, the error messages - and the wording you typed: product names, descriptions, the labels you gave the buttons, the names of your postage services. Both can be translated, in different places.
Bang! Cart's own wording
Every piece of the plugin's own text is translation-ready in the normal WordPress way. If a translation exists for your site's language it is used automatically; where none exists yet, WPML › String Translation, Loco Translate or a .po file in the plugin's /languages folder will do it. The text domains are bang-cart-for-stripe and, for Pro, bang-cart-pro, and each plugin ships a .pot template.
The wording you typed
Everything a customer reads that you wrote yourself is handed to WPML or Polylang the moment either is active - there is nothing to switch on in Bang! Cart. Open the plugin's strings there and you will find, under the group Bang! Cart:
- each product's name and description (products synced from Stripe too - the Stripe text is the original)
- the Add to basket, Sold out and Checkout button labels and the basket heading, whether you changed them or kept the defaults
- each postage zone's name, its service names ("2nd Class", "Next day"), its collection note and its over-limit message and link text
- the sale banner message
- the closed-shop message
Type a translation for any of them and that is all. On a page in that language the Add to basket buttons, the basket drawer, the postage choices in it and Stripe's checkout page all show the translation; on a page in the original language, the original. Where you have not translated something, the original shows - a product you have not got round to yet is never blank.
A description's bold, italic, links and lists carry over if you keep the same tags in the translation; the Products page shows you the tags it uses.
In WPML
String Translation is part of WPML's Multilingual CMS and Agency plans, not the Blog plan.
- Go to WPML › String Translation.
- Filter by domain Bang! Cart. If the list is empty, load any page of your WordPress admin once and come back - that is when the strings are registered.
- Translate the ones you want. Each is named for what it is:
product-jar-name,zone-uk-service-2,button-add.
In Polylang
- Go to Languages › Translations.
- Filter by group Bang! Cart.
- Translate the ones you want and save.
What stays in one language
- Variant names - Size, Colour and their values - and the labels of anything Pro asks the customer.
- The order emails. They go out in the shop's own language, to you and to the customer. Stripe's own receipt follows the customer's language.
- The admin. Products, Settings and the rest always show your originals, so you can never save a translation over them by mistake.
Stripe's checkout page
Stripe shows its checkout in the customer's browser language by itself. The product names and postage choices Bang! Cart sends it are the translated ones, so the page reads as one piece. Your Orders page and Reports still recognise the product by its id, whichever name went to Stripe.
With Pro's checkout on your own site, translate your checkout page too (Polylang: the + beside it in the Pages list; WPML: its translation editor) and put the same [bangcart_checkout] shortcode on the translated page. The basket's Checkout button then opens the page in the visitor's language, and the form on it is in that language as well. Without a translated page the original checkout page is used.
If a translation does not show
- It shows on the page but not in the basket. The basket asks your site for prices as the customer changes it, and tells it the page's language each time. If something on the site blocks those calls, the basket cannot work at all - see REST API blocked.
- The string is not listed. Only text that exists is listed - an empty description has nothing to translate - and new text is registered the next time any admin page loads.
- You renamed a product. In WPML the translation is kept and flagged for review, because strings are keyed by the product's id. Polylang matches on the text itself, so a renamed product needs its translation typed again. Changing a product's id makes it a new product to both.
Still stuck?
Write to me and it is me who answers, not a ticket queue. Tell me what you expected and what happened instead.


