Articles on: Frequently Asked Questions (FAQ)

File encoding issue in Stock Sync

Every feed file possesses a specific character encoding, even if files appear identical in standard text editors. By default, Stock Sync sets the file encoding to Auto, which attempts to detect the format automatically; however, if characters appear corrupted or distorted (such as question marks or strange symbols), you can manually set the exact encoding to resolve the issue.



How to Resolve File Encoding Issues


Go to App → Feed Settings → Step 1: Connection


  1. Detect File Encoding: Visit an online character encoding detector, such as ABC Tool File Encoding Checker, and upload your source feed file.
  2. Note Detected Format: Once processed, note the exact character encoding displayed by the tool (e.g., UTF-8, Windows-1252, or ISO-8859-1).
  3. Select File Encoding: In Stock Sync, navigate to Step 1: Connection, locate the File Encoding dropdown, and choose your file's specific encoding from the list instead of Auto.
  4. Save and Rerun Feed: Click Save Settings and re-run your feed to confirm that all text and special characters parse accurately.


Manually selecting your file encoding prevents character corruption when working with non-English alphabets, currency symbols, or supplier files exported from legacy software.



File Encoding Settings & Common Formats Breakdown


1. Auto Detection vs. Manual Selection

Stock Sync's Auto setting evaluates the file and defaults to the lowest compatible encoding. While this works seamlessly for standard English text, files containing accented characters, foreign alphabets, or non-standard symbols can be misinterpreted.


If your feed processes without errors but text contains garbled characters, switch from Auto to a specific encoding.


Always check the raw file directly from your supplier before re-saving it, as opening and saving in spreadsheet software may inadvertently change the encoding.


2. Common Character Encodings Reference


Encoding Type

Standard Identifier

Common Use Case / Source

Corrupted Character Symptoms

UTF-8

UTF-8

Universal web standard; multi-language catalogs with symbols and accents

Accented letters display as é, ü, or ``

Windows-1252

CP1252 / Windows-1252

Default CSV exports from Microsoft Excel on Windows systems

Smart quotes, em dashes, or euro symbols (€) become ?

ISO-8859-1

Latin-1

Western European language feeds from older server environments

Special letters fail to import or break XML parsing

UTF-16

UTF-16LE / UTF-16BE

Large enterprise exports and automated database reports

Text renders as Asian glyphs, illegible symbols, or blank fields

ASCII

US-ASCII

Basic 7-bit English plain text

Any non-ASCII character is stripped, replaced, or causes read failures



Key Rules & Technical Details


  • Default Behavior: Stock Sync defaults to Auto, which falls back to the lowest common byte structure if the header signature is ambiguous.
  • Affected Fields: Encoding problems primarily impact text fields such as Product Title, Description, Option Names, Vendor, and Tags.
Priority rule: Always confirm the exact encoding using an external file checker before modifying the setting in Stock Sync. Selecting an incorrect encoding can cause feed parsing to fail entirely.



Troubleshooting Steps


  • Issue: Product titles display replacement characters like `` or mojibake strings like é. → Solution: Your file likely uses UTF-8 or Windows-1252. Verify the file's encoding with an online detector tool and manually choose that format under Step 1: Connection.
  • Issue: The entire feed preview shows unreadable characters or Asian ideographs. → Solution: The source file is likely encoded in UTF-16 (Little Endian or Big Endian). Update the File Encoding dropdown to the corresponding UTF-16 option.
  • Issue: The feed fails immediately upon starting with a decoding error. → Solution: The file may contain mixed byte sequences or corrupt lines. Open the file in an advanced editor like Notepad++, convert the encoding explicitly to standard UTF-8, re-upload, and run the feed.



Good Articles to Continue


Updated on: 04/11/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!