Applies to Cmsmart Product Designer (NBDesigner) 2.17.0 · Updated October 2026. Covers the Modern and Visual design editor layouts. The Classic layout is marked deprecated in Settings > General and uses its own, separate translation screen instead of the workflow below.

In short

  • Outcome: open your WooCommerce print shop to non-English buyers with one storefront and one designer, not a separate site per language.
  • How it works: Cmsmart Product Designer's buyer-facing text ships in WordPress's standard translation format, so a plugin like Loco Translate or WPML turns it into any language your customers already search in.
  • What it takes: pick your target languages from real demand, translate the buyer journey end to end, and leave admin and production screens in the language your team already works in.

A multilingual product designer turns a WooCommerce print shop's t-shirts, invitations or signage into products non-English speakers can actually buy, instead of capping the market at English readers. Cmsmart Product Designer (NBDesigner) runs on WordPress's standard translation system, so a shop can open the same storefront and online editor to Spanish-, French- or Vietnamese-speaking buyers, while pricing and production stay in one language for the team.

What does staying English-only cost a growing print shop?

Cmsmart Product Designer works in any language WordPress supports, so a WooCommerce print shop stops losing non-English buyers mid-design, cuts support tickets caused by confusing English labels, and avoids running a second, duplicate store just to reach one more market.

The cost rarely shows up as one clean number. It shows up as five smaller, everyday problems:

  • Buyers abandon the designer mid-edit when they don't recognize "Add to cart," "Process," or a panel label, and your analytics just show a drop-off with no obvious reason.
  • Support tickets pile up from customers who email a screenshot asking what a button does, instead of finishing the order themselves.
  • Some shops react by cloning the entire store per language — a second WordPress install, a second plugin license, and double the work keeping products and prices in sync.
  • B2B and wholesale buyers search for a supplier in their own language first; a catalog that never surfaces in that language never gets the RFQ.
  • Staff spend time manually re-typing one-off quotes or product descriptions into a second language, order by order, instead of translating the storefront once.

Cmsmart insight: The usual mistake is treating translation as an all-or-nothing content project. The buyer-facing surface that actually blocks an order — product page, design chooser, designer panels, cart, checkout — is a short, fixed list of strings. Translate that first; translate blog posts and marketing pages later, on their own schedule.

WooCommerce product page with the Start and upload design button that a shop translates first
The product page's "Start and upload design" button and price are among the first buyer-facing strings a shop translates.

What would a multilingual product page look like for your buyers?

Cmsmart Product Designer lets a WooCommerce print shop show the exact same storefront and online editor to a buyer in Mexico City or Hanoi as it shows a buyer in Ohio, each in their own language, so nobody has to guess what a button means before they can finish a design and pay.

Picture the buyer journey once the designer speaks the buyer's language instead of yours.

Example scenario: A buyer opens your poster shop at 9pm in their own time zone. The product page reads in their language, not a machine-translated browser overlay. The chooser that asks "How would you like to design" appears the same way, in their words. They build their poster, see the price in a familiar number format, and check out — without ever emailing your support inbox to ask what a button does.

Nothing about your production changes in this picture. The buyer's print-ready PDF, the price matrix, and the order that lands in your admin queue look exactly like any other order — because only the words on screen changed, not the plugin underneath them.

Mobile WooCommerce product page a buyer in another country or time zone would open to start designing
The mobile product page is one of the same buyer touchpoints that gets translated — most international traffic to a print shop arrives on a phone.

How does Cmsmart make the product designer multilingual?

Cmsmart Product Designer ships every buyer-facing string in WordPress's standard translation format, so a WooCommerce print shop adds a language with a translation editor like Loco Translate or WPML instead of custom code, as long as the store runs the Modern or Visual design editor layout rather than the deprecated Classic one.

Four building blocks make this work:

  • A translation template. NBDesigner ships its own .pot translation template (langs/web-to-print-online-designer.pot), regenerated with every release that adds new screens — by plugin version 2.12.2 it reached 4,107 translatable strings.
  • A translation editor. Loco Translate (or WPML/Polylang for a fully localized catalog) reads that template and lets you type a translation for each string, building a language file with no code.
  • The right layout. Settings > General > Default design editor layout has to be Modern or Visual. Classic is marked "deprecated" there and relies on its own separate Frontend Translate screen, which is not part of this workflow.
  • A clean split between buyer and admin. Only the buyer-facing surface — product page, chooser, designer panels, cart, checkout — needs translating. Your admin screens, Orders list and production tools stay in whatever language your team already works in.

This is also an area Cmsmart actively maintains, not a one-time translation dump: 2.17.0 fixed the admin approval-notification email so it checks the order's status key rather than matching translated subject text, and 2.16.0 fixed AI preflight license checks that were failing on WPML sites running in directory mode. Both are examples of the plugin being built to work correctly inside a translated store, not just technically "translatable."

How would you like to design chooser modal with the upload and online design options a shop translates
The "How would you like to design" chooser is a short, self-contained set of strings — a good first translation target.
Modern online designer with Templates, Text, Cliparts, Photos, Elements and Layers panel labels
The Modern designer's panel labels (Templates, Text, Cliparts, Photos, Elements, Layers) carry the translatable strings; Classic layout does not use this template.
ApproachWhat it takesOngoing costBest for
Separate store per languageA second WordPress + WooCommerce + NBDesigner install, kept in sync by handDouble hosting and licenses, plus manual product/price updates foreverRarely worth it below several markets
Translate the existing designer (Loco Translate / WPML)One store; buyer-facing strings translated with a free or low-cost pluginA few hours per new language, revisited after plugin updatesMost WooCommerce print shops adding 1-4 languages
Cmsmart custom regional storefront (custom development)Cmsmart builds region-specific pricing, paper sizes, currency and layout on top of the base translationProject-based, scoped to your marketsShops standardizing on several regions or currencies at once

What's the ROI of adding one more language to your storefront?

Cmsmart Product Designer turns adding a language into a translation task instead of a development project, so a WooCommerce print shop can weigh the ROI with its own numbers: sessions already arriving in that language, today's conversion rate, and what a buyer who can read every button is worth.

BenefitHow it shows up in your businessKPI to track
Fewer abandoned designsBuyers finish a design they understand instead of leaving at an unlabeled buttonDesigner-start to add-to-cart rate, by locale
Fewer support ticketsBuyers self-serve instead of emailing a screenshot of a confusing screenTickets tagged "language" or "translation"
One catalog to maintainPrices, print specs and designer options update once, not once per language-storeHours spent syncing duplicate stores (target: zero)
Reach into real demandYou stop showing zero results for searches made in a language your analytics already show visits fromNon-English organic sessions and their conversion rate

ROI worksheet (use your own numbers):

  • Monthly sessions from the target language or country (from your analytics) × your current site-wide conversion rate = a rough floor for orders if the designer stayed English-only.
  • CSA Research surveyed 8,709 consumers in 29 countries and found 76% prefer to buy when product information is in their language, and 40% say they will not buy at all from a site in another language (CSA Research, 2020) — use that range, not a guess, when you estimate the uplift a translated designer could realistically recover.
  • Hours your team spends per month re-typing quotes or descriptions into a second language × your hourly cost = the manual-workaround cost you remove once the designer is translated once.

How do you set up a multilingual product designer?

Setting up Cmsmart Product Designer for a new language takes a translation plugin and a short checklist, not a rebuild: confirm the Modern layout, install a translator, work through the buyer-facing strings in order, and test the full design-to-checkout path before you announce the new language.

  1. Check your analytics or Search Console country/language report for where non-English traffic already comes from, and start with that language.
  2. In WooCommerce > Settings > Cmsmart > General, confirm Default design editor layout is set to Modern or Visual — Classic is marked deprecated and uses its own separate Frontend Translate screen instead.
  3. From Plugins, use the Cmsmart Product Designer row's own Translate link, or install and activate a dedicated translation editor such as Loco Translate (1 million+ active installs, 4.8 out of 5 from 452 reviews on WordPress.org); use WPML or Polylang instead if you are translating the whole storefront, not just the designer.
  4. Open the plugin's translation template and add your target language — this builds a language file from the strings the plugin ships, with no code.
  5. Translate the buyer journey in order: the product page button, the "how would you like to design" chooser, the designer's panel and tool labels, then cart and checkout.
  6. Save and build the language file, then open the storefront in that language and run through a full design, from product page to checkout, exactly as a buyer would.
  7. Leave admin, Orders and production screens in the language your team already works in — only the buyer-facing surface needs translating.
  8. If print specs differ by region — paper sizes, bleed, currency — update those per market in Printing Options and Output rather than assuming one size fits every country.
  9. Re-check the translation after each plugin update, since new features add new strings to the template.

For the click-by-click Loco Translate walkthrough — including font subsets and troubleshooting a failed translation build — see our companion guide, How to use the Loco Translate plugin to translate on the Online Product Designer.

Settings General tab confirming Modern layout before a multilingual product designer rollout, with Classic marked deprecated
Settings > General: confirm the layout is Modern before you translate — Classic is marked deprecated here.
WordPress Plugins screen showing the Cmsmart row with its own Translate link
The Plugins screen's own Translate link on the Cmsmart row is the entry point before you install a dedicated editor like Loco Translate.

What can Cmsmart build beyond basic translation?

Beyond translating labels, Cmsmart builds the parts a growing international store actually needs next: synced multilingual product content, region-specific pricing and print specs, and right-to-left layouts — custom development scoped to the markets you're actually entering, not a generic bundle.

  • Full WPML/Polylang integration. Growing past a translated UI usually means product names, descriptions and template collections need to be translated and kept in sync across languages, not just the designer screens. Cmsmart builds that sync for your store.
  • Region-specific pricing and print specs. Currency, tax and paper or size defaults that switch automatically with the buyer's country inside the same price matrix, instead of one price list for every market. Cmsmart builds that logic for your store.
  • Right-to-left (RTL) layout support. Arabic- or Hebrew-speaking markets need the designer's panels mirrored, not just the text flipped. Cmsmart builds RTL layout work for your store when a market calls for it.
  • Geo-based language and currency redirect. A buyer lands in their language and currency automatically instead of hunting for a switcher. Cmsmart builds that detection and redirect for your store.
  • Professional-translation and glossary workflow. Print terminology (bleed, safe zone, gang sheet, price matrix) needs to stay consistent across languages in a way raw machine translation won't guarantee. Cmsmart sets up that workflow for your store.

We scope this the same way as any Cmsmart project: discovery call, solution design, milestone sprints, QA on every language you add, launch, then ongoing support — see how we run ecommerce projects, or the full scope of this work on our product designer customization service page.

Plan my multilingual storefront

Why work with Cmsmart on international expansion?

Cmsmart has run WooCommerce and web-to-print projects since 2012 as a Netbase JSC division, with 6,300+ client projects, 1,800+ live stores and clients in 80+ countries — real-world experience in exactly the regional and language variety a multilingual designer has to handle.

Cmsmart is rated 4.2 out of 5 on Trustpilot (404 reviews) and has delivered 4,600+ projects since 2012. The audience this reaches keeps growing with the platform underneath it: WooCommerce runs 47.5% of all e-commerce sites whose platform is known (W3Techs, 2026). Browse related delivery work on our project case studies, or see the plugin itself on its Cmsmart Product Designer product page. If your settings need a wider review before you add a language, our product designer settings guide covers every admin screen field by field.

Frequently asked questions

Does translating the designer slow down the site or break templates?

No. Translation only swaps the text strings the plugin and your translation editor manage; it does not touch the templates, cliparts or the designer's rendering code, so performance and existing designs are unaffected.

Can I translate just one language and leave the rest in English?

Yes. Loco Translate and WPML both let you add one language at a time. A store can stay English-only for most visitors and offer a second language only to the market you've chosen to open first.

Do my staff need to read every language I add for buyers?

No. Admin screens, the Orders list, Create PDF and the rest of production stay in whatever language your team already uses — translation applies to the buyer-facing storefront and designer, not the backend.

Is the old Classic layout's built-in Frontend Translate still supported?

Classic layout is marked "deprecated" in Settings > General as of 2.17.0, and Cmsmart has stopped developing new features for it. New stores should use Modern or Visual layout and the Loco Translate / WPML workflow described above.

How is this different from a browser's automatic translation?

A browser's machine translation runs on every visit, can mistranslate print terms like "bleed" or "gang sheet," and is invisible to search engines. A plugin-built language file is translated once, stays consistent, and lets that language version get indexed and found in search.

How long does a first multilingual rollout usually take?

Translating the core buyer journey with Loco Translate is typically a short, one-time task per language once you know which strings matter; a fully synced multilingual catalog with region-specific pricing is a scoped custom development project, sized to how many markets and languages you're opening at once.

What business problems does an English-only product designer create?

The page lists abandoned designs at unlabeled buttons, extra support tickets for translation help, shops duplicating their site per language, and staff manually re-typing quotes for non-English buyers as the costs of staying English-only.

What would a multilingual product page look like to a buyer?

The page describes a scenario where a buyer sees the product page, the designer, and the checkout interface in their own language throughout the purchase, without any change to how the backend or production process runs behind the scenes.

What custom development options exist beyond basic translation?

The page describes further custom work such as WPML or Polylang integration, region-specific pricing, right-to-left layout support, geo-based redirects, and professional translation workflows for stores that need more than a single added language.

How do I pay securely?

Contracts and payments go to the company, Netbase JSC: plans are paid through PayPal; services are invoiced by Netbase JSC under a written proposal and paid by bank transfer to Netbase JSC's company account or by PayPal Business. Cmsmart (Cmsmart Ecommerce) is the ecommerce brand of Netbase JSC, a company based in Hanoi, Vietnam.

How do I contact Cmsmart or get a quote?

Message the Cmsmart team on WhatsApp at +84 937 869 689 or email project@cmsmart.net; the contact page at cmsmart.net/contact lists every channel, and Request a quote (cmsmart.net/project-proposal) sends a project brief. Customers with a licence open a ticket from the dashboard.

Further reading