What you are looking at
Your setup: one Elementor Theme Builder template of type SureCart Product, assigned to a single product, with the SureCart Checkout Form widget inside it. I rebuilt exactly that here, then made it bilingual two different ways. Everything below is live and clickable.
Option A – one product template per language (keeps your Elementor design on the product page)
An Elementor condition points at a product post, not at “the product”. A Polylang translation is a separate post, so a second template pointed at the translation is not a conflict. Two templates, two posts, both render.
- English product page – Elementor template #544, checkout form #477 (“Name”, “Summary”, “Purchase”)
- Pagina do produto em portugues – Elementor template #545, checkout form #479 (“Nome completo”, “Resumo do pedido”, “Finalizar compra”)
Same product, same store, same price. Only the template and the form change. This needs one small code snippet, because SureCart has no Polylang integration and a fresh translation post starts empty. The snippet is in the support reply.
Option B – a separate checkout page per language (no code at all)
Leave the product page alone. Put the checkout on ordinary WordPress pages, which Polylang translates natively, and link the two pages together.
Two Elementor templates on ONE product post
I tested this too. Elementor renders only one of them and silently ignores the other. So your instinct was right – that specific arrangement does not work, and it is not the way to do the translation.
What Loco Translate can and cannot reach
- Translates by itself, no work: Pais, Telefone, Envio, Senha, Remover, Aplicar, Continuar – plus the address fields, which come from SureCart’s servers already localised (Endereco e numero, CEP, Cidade, Estado).
- Loco Translate can fill the gaps: the SureCart interface strings that have no Brazilian Portuguese translation yet, such as the shipping notice.
- Loco Translate can NEVER reach: the labels on your checkout form – Name, Email, Shipping Address, Payment, Purchase, Summary, Subtotal, Total, your custom “A Few Words to Include” field and your terms checkbox. They are saved inside the form itself, not in a language file. That is why you need one checkout form per language.
- Nothing reaches: the product name in the order summary and in emails. That lives in SureCart and exists in one language only.
