A product titled "Café Mug" displaying as "Café Mug" (or emoji turning into strings of odd symbols) is a well-known Excel quirk: Excel assumes a plain CSV is in an older encoding unless the file explicitly marks itself as UTF-8, and text with accents or emoji gets misread as a result.

The fix is a small marker at the very start of the file called a byte-order mark (BOM), which tells Excel unambiguously "this file is UTF-8." This tool writes that marker by default on every export - so if you’re seeing this problem, it’s worth checking whether the file actually came from here, or from another export tool that skips it.

No setting to turn on for this one - it’s simply on, so accented names, non-Latin scripts and emoji in product titles or descriptions come through correctly every time.

Older versions of Excel on Windows have occasionally mishandled the BOM in specific edge cases even when it’s present correctly - if that happens, opening the file through Excel’s Data → From Text/CSV import option, rather than double-clicking it, gives Excel an explicit chance to confirm the encoding itself before displaying anything.