// any language  ·  any encoding

Import product names in any language without breaking a single character.

Most budget importers turn anything that isn't plain English into junk. Accented letters become é. Japanese becomes イヤ. Simple Importer Pro by Apps that Smack! reads the encoding, converts it to clean UTF-8, and keeps every character exactly as you wrote it.

// what mojibake actually is

The same product name, read two ways.

Mojibake happens when text saved in one encoding gets read as another. The bytes are fine. They're just being misread. Here is the repair, row by row.

Read wrong
Read right
Écouteurs sans fil
FrenchWindows-1252
Écouteurs sans fil
イヤホン
JapaneseShift-JIS
イヤホン
Ðаушники
RussianWindows-1251
Наушники
網烬耳机
ChineseGB18030
网线耳机
Ακουστικά
GreekUTF-8 misread
Ακουστικά

// every script, intact

"Wireless headphones," written the way your customers read it.

A real product title in every script the importer handles. Each one lands in WooCommerce exactly like this, accents, tone marks, and direction included.

Japaneseワイヤレスイヤホン
Chinese, Simplified无线耳机
Chinese, Traditional無線耳機
Korean무선 이어폰
RussianБеспроводные наушники
Arabicسماعات لاسلكية
Hebrewאוזניות אלחוטיות
GreekΑσύρματα ακουστικά
Thaiหูฟังไร้สาย
GermanKabellose Kopfhörer
PolishSłuchawki bezprzewodowe
CzechBezdrátová sluchátka

// what happens on import

You don't set the encoding. It figures that out.

  1. 01

    Detect

    The importer inspects the actual bytes of your file, not the file extension or a guess. It identifies the encoding, including a byte-order mark if one is present.

  2. 02

    Convert

    Everything is converted to clean UTF-8 in memory before a single product is written. Legacy encodings like Shift-JIS and GB18030 become standard Unicode.

  3. 03

    Preserve

    Names, descriptions, attributes, and categories all keep their original characters. What was in your file is what lands in your store.

// the encodings it reads

Built for the files real suppliers send.

Export a feed from an older ERP or a regional supplier and you'll meet these encodings fast. The importer handles them so you don't open the file in three programs trying to guess.

If your file is already clean UTF-8, nothing changes. If it isn't, this is the difference between a finished import and an afternoon of find-and-replace.

  • UTF-8The modern standard
  • UTF-16 LE / BEWith byte-order mark
  • Shift-JISJapanese legacy
  • GB18030Chinese national standard
  • Windows-1251Cyrillic legacy
  • Windows-1252Western European legacy

// questions

Mojibake, answered.

Why does my import turn Japanese or Chinese text into garbled characters?

The text was saved in one encoding (like Shift-JIS or GB18030) and read as if it were another (usually Windows-1252). The bytes get reinterpreted as the wrong characters, which is mojibake. Simple Importer Pro detects the original encoding and converts it to UTF-8 before writing anything, so the characters survive.

Do I need to know the encoding of my file?

No. The importer detects it from the file itself. This matters most with supplier feeds and exports from older systems, which are frequently in legacy encodings you'd otherwise have to identify by hand.

Does it handle right-to-left languages like Arabic and Hebrew?

Yes. Arabic and Hebrew import intact. The importer preserves the characters exactly, and WooCommerce and your theme handle the right-to-left display.

What about accented European text, like French or Polish?

Handled the same way. Accents, diacritics, and special letters (é, ñ, ß, ł, č) come through cleanly whether your file is UTF-8 or a Windows legacy encoding.

// stop fighting your spreadsheet

Import once. Read it everywhere.

Simple Importer Pro by Apps that Smack! reads any major encoding, converts to clean UTF-8, and imports products, posts, pages, and media from CSV, XLSX, JSON, and XML. One-time $249, no subscription, with 6 months of priority support included.

Walk in faith. Build with craft. Charge fairly.