Article

Add Hindi to Shopify and keep translations current

For solo Indian Shopify merchants, compare free translation routes, review Hindi before publishing and maintain wording after English edits.

Editorial illustration for Add Hindi to Shopify and keep translations current: a document represents the research briefing. Not documentary evidence.

For an Indian Shopify merchant who can review Hindi, adding a second storefront language need not mean another app subscription. Keep a satisfactory existing translation setup; otherwise, prepare reviewed wording with Translate & Adapt or a human-supplied CSV, then publish Hindi deliberately. Shopify supports both routes, but later English edits still need a Hindi review.

As of November 21, 2026, Shopify lists Translate & Adapt as free. Here, ₹0 means additional monthly app subscriptions—not a free Shopify store, free translation labour or guaranteed translation quality.

Consider an illustrative Indian homewares shop: one nontechnical owner, an existing paid English-language Shopify Basic store, 30 products, desktop access and the ability to check Hindi. These are planning assumptions, not a customer case. The goal is understandable, maintained product and service information. Existing Shopify and domain charges, connectivity, equipment, review time and any commissioned translation or theme work remain separate.

Which translation workflow fits your shop?

Choose by wording control, preparation effort, extra cost, content coverage and who will revisit changes. For this owner, manual entry is a sensible starting point if writing Hindi is manageable. A spreadsheet suits a batch handoff to a translator; a machine first pass suits someone able to check every important statement.

The side-by-side app editor supports human review. The native CSV route needs supplied translations; exporting a file does not generate them. The options below are workflows for the same task, not a ranking of translation quality.

Workflow / best fit

Extra app cost

Meaningful limit

Review

Upkeep

Keep a sufficient existing setup

No new subscription assumed

Existing terms and coverage still apply

Retain a working approval process

Keep a named owner

Manual entry: owner can write or approve Hindi

₹0 with Translate & Adapt

Field-by-field effort; coverage gaps remain

Approve wording before saving live changes

Revisit relevant English edits

Supplied CSV: batch work or translator handoff

No translation app required; labour may cost extra

File matching and overwrite choices matter

Review the file before import

Track changed rows and retain exports

Automatic first pass: owner can check the output

₹0 within the account allowance

Country, language-slot and content limits

Prepare initially while Hindi is unpublished

Separate machine updates from human-maintained text

Do not add another tool simply to obtain an AI feature. If the current setup covers your pages and its review process works, keep it. If nobody can verify the Hindi, obtain suitable help or defer publication; machine output does not remove that requirement.

What must your store support before adding Hindi?

Shopify’s multilingual requirements allow up to 20 storefront languages on Basic. That is store capacity, not 20 automatic translations. Check a compatible active theme, an enabled language selector and language-specific URLs. Shopify-built free themes are compatible; ask a third-party theme developer about your version. Hindi is among the provided theme and checkout languages.

List the translation tools already installed and identify which one maintains each part of the shop. Avoid having two processes change the same wording without an owner. A new app is unnecessary if the native CSV workflow meets your needs.

Before installing Translate & Adapt, inspect its current data-access disclosure. On November 21, it lists owner contact information, contributor email and device-related information, and broader store permissions covering products, pages, themes, notifications, navigation and translations. Access is not confined to product descriptions.

Under Shopify’s terms, merchants remain responsible for their store materials, including tool-created content, and for necessary rights and consents. Customer-data processing is governed by the applicable terms and linked data policies. This product-copy workflow needs no customer records in the translation handoff.

How do you add Hindi while keeping English?

First settle the English source wording. A translator cannot resolve an uncertain product dimension or delivery promise for you. Make a list of the products, navigation labels, service pages and messages the Hindi experience must cover.

Follow Shopify’s language setup:

  1. Open Settings > Languages > Add language.

  2. Select Hindi, then Next.

  3. Select the intended existing domain or domains, check their listed markets, then Done.

  4. Keep English as the store default and Hindi unpublished during preparation.

Treat the 30-product catalogue as a work list, not a time estimate. Variants, theme wording, navigation and service information add separate review work. Begin with a representative product to establish consistent terminology, then complete the rest before describing the Hindi catalogue as reviewed.

How should you prepare the translations?

Can you write or approve the wording yourself?

For manual editing, open Apps > Translate & Adapt, select Hindi and the relevant resource, enter the translation and Save. A resource’s More actions > Localize provides another documented entry point; some resources expose Localize directly.

Use the English and Hindi side by side. Keep product names, measurements and variant labels consistent. A short terminology sheet can record preferred wording and terms that should remain unchanged. That is an owner-maintained aid, not a feature that certifies translation quality.

Would a spreadsheet handoff be easier?

For CSV preparation, use Settings > Languages > Export and select Hindi. Choose All content for an initial batch, or Outdated or Untranslated content for follow-up work. Supply wording in Translated content, preserve the other columns and save with comma delimiters.

Return to Languages > Import. Choose deliberately whether to overwrite existing translations, review the import summary and confirm. Check the emailed confirmation for failures or skipped content. Keep a dated export as a translation record—not a complete store backup.

What automatic allowance applies in India?

As checked on November 21, 2026, India falls under Shopify’s two-language automatic allowance, normally without Auto-sync. The exception is an account displaying Translate now: Shopify says that control indicates eight-language and Auto-sync eligibility, even outside the listed countries. Used automatic-language slots cannot be reassigned, and removing a language does not reset them.

In Apps > Translate & Adapt, select Hindi and use Auto-translate, or Translate now if eligible. Leave Publish [language] after translation unselected wherever offered. Review the result before making Hindi visible.

Eligible Auto-sync is off initially and runs weekly, not immediately; the first run can wait up to a week. Other stores must rerun Auto-translate after edits. Automatic translation fills missing text and refreshes outdated machine wording, but some theme text only receives missing entries. Merchant legal policies are excluded. These are documented automation limits, not a human approval queue.

For an owner who requires approval before every later change, the practical choice is reviewed manual or CSV updates. Do not enable unattended changes to published wording and assume a review step will intervene.

What needs checking beyond product descriptions?

Review meaning, not just whether Hindi text exists. Shopify falls back to the default language when a translation is missing, so publishing Hindi can still leave English passages visible.

Use this acceptance checklist for the homewares shop:

  • Products: compare materials, dimensions, included items, care instructions and variant names with the approved source information.

  • Service information: check delivery areas, timing, returns conditions, contact details and policy wording without adding promises.

  • Navigation and layout: check menus, buttons, readable Hindi lettering, line wrapping and switching back to English once published.

  • Completeness: record every unresolved field and who will correct it. A good-looking sample page does not establish coverage across all 30 products.

Translate & Adapt’s content limitations include product images, Shopify Forms, collection filters, manual-payment instructions, tags and third-party content not exposed through supported translation resources. Ask the theme or app provider about a specific gap; another subscription is not automatically the answer.

Lettering inside a product photograph is a separate task. Manual localization can replace supported theme media with localized files, but that is not automatic rewriting of product-image text. For preparing accurate images, see the Shopify product-photo guide.

Shopify provides Hindi defaults for supported theme, checkout and certain privacy-related content. That does not establish that your customized policy wording is translated. Compare the actual policy with its approved original and arrange a competent review where needed. The supported-language list explains those defaults.

How do checkout and order emails fit in?

According to Shopify’s checkout and notification guidance, checkout follows the customer’s browsing language. Where notification translations exist, order emails follow the language used for the order. Inspect customized wording separately.

For a notification, open Settings > Notifications, select the message and choose Localize. Edit its Hindi fields in Translate & Adapt and Save. Then open the notification’s Preview and select Hindi from the language menu. Check links and factual promises as well as appearance.

For checkout wording that does not appear as expected, confirm the supported editing route with Shopify or the relevant provider. Do not infer that a notification editor can change every checkout field.

Localized order notifications are also not proof that recovery messages or third-party marketing emails are configured correctly. The Shopify abandoned-checkout email guide addresses reminder setup as a separate task.

When should you publish Hindi?

After reviewing the prepared wording, use Settings > Languages, open the menu beside Hindi and select Publish. Publication makes the language available to customers; it is not an approval certificate.

Once live, inspect the Hindi storefront, representative products, navigation, language switching and the route into checkout. Complete the remaining catalogue checks and revisit the saved notification previews. Resolve gaps before treating the rollout as complete.

Initial preparation while Hindi is unpublished should not be confused with a private approval environment for later edits. For changes to an already published language, prepare and approve replacement wording outside the live fields before saving or importing it.

How do you keep Hindi current after English edits?

The operating rule is simple: review Hindi after every English edit. For a solo shop, the owner who changes a product description should also record what its translation needs. Prioritize factual changes affecting what customers receive or what the shop promises.

Shopify’s content statuses distinguish Translated, Outdated and Untranslated. Outdated flags a source-language change; Translated only means wording exists. Neither means a person has approved its accuracy.

Shopify says manually written translations are preserved during automatic updates. This protects corrections from overwrite, but it does not keep them factually current. Human-controlled wording creates a human maintenance obligation.

The CSV update rules have a related catch: new or replacement imports become manual translations and are not automatically refreshed. Identical imported text is skipped; reimporting it neither clears Outdated nor converts existing machine text into manual content. Reading and accepting machine wording alone is not a documented protection against future updates.

A simple spreadsheet is enough for a change log. Use these columns:

  • Product or page, field, and the English change with its date.

  • Hindi action needed and the proposed replacement wording.

  • Reviewer and review date, tied to the English version checked.

  • Saved or imported status, followed by the live-check result.

For example, if the approved English listing changes the set contents, reopen that exact Hindi field before treating the update as complete. Identify the affected statement, review its replacement and check the live result; the rest of the translation may not need rewriting.

Use Outdated and Untranslated exports to find outstanding work, then reconcile them with the log. If unchanged Hindi still accurately expresses an edited English source, record that review rather than reimporting identical text to manufacture a clean status. Keep a dated export after accepted changes.

Before relying on the process, rehearse one source-text change without intentionally putting incorrect product facts live. Check that you can identify the affected Hindi field, record the decision and verify the saved result. No customer message or live order is needed for that rehearsal.

What if a translation is wrong or the setup no longer fits?

Correct the affected wording deliberately. If wider problems require hiding Hindi, understand Shopify’s removal options: unpublishing retains translations but removes domain assignments and makes language URLs return 404. Deleting the language permanently deletes its translations. Changing the store default deletes existing translations for the new default. None is a routine review switch.

Keep the setup while the owner can review changes and its coverage meets the shop’s needs. Seek help for a defined gap—such as an unsupported widget or policy wording—not for an assumed sales benefit. The useful result is a Hindi shopping experience someone can keep accurate, not merely another language marked as published.