How to translate the discount title for other country (Impulse Theme)

My store is a chinese language based website. And I am currently expanding my store to other countries (English language), however, i cannot find the field to transalte the discount title in english. Can anyone help me?

It should be translated into “2 products: Extra 10% OFF”

Hi @Tom090897 ,

Thank you for reaching out to the Community!

As @Small_Task_Help has mentioned, I’d recommend using an app to help translate your shop. Please feel free to check out the Shopify App Store for a complete list of translation apps, as this will help to ensure everything is correctly populating for other countries and languages. The Shopify Translate & Adapt app is a popular one used by merchants that will assist with this.

Please let me know if you have any other questions.

Did you manage to solve this?

Hi, discount title are NOT in translate app, or I couldn’t find them even with CSV export. Where to translate this? Thanks

Hi @Tom090897 :waving_hand:

This one’s tricky because discount titles are a known blind spot — they don’t show up in Translate & Adapt or in CSV exports, which is exactly why you couldn’t find the field. You’re not missing anything; Shopify just doesn’t expose them there.

The reason: the discount title comes from your discount code/automatic discount settings, not from theme content, so it isn’t pulled into the translation tools.

A few things that actually work:

  1. Create a separate discount per market/language. Make a duplicate automatic discount, set its title to “2 products: Extra 10% OFF,” and limit it to your English-speaking countries under the discount’s Countries setting. Each market then shows its own title.
  2. Check the Impulse cart code. If the label is being rendered by the theme (not the raw discount object), you may be able to translate it via the theme’s locale files (Edit code → locales → en.default.json). Search for the discount/cart string there.

If neither fits, splitting the discount by country (option 1) is usually the cleanest fix since it avoids code edits entirely.

Hope that points you in the right direction — let me know which route you want to try!