Unicode (non-Roman characters) support
We have a company store that sells to the world market. Countries in Asia (Chinese/Japanese/Korean) use 2-byte, non-Roman, unicode characters in their names and addresses. These address will have last characters filtered or altered when printed. It is annoying and risky to loss, not able to print them properly. As more and more companies sells internationally, it is good to prepare ShipStation ready for world markets.
Thank you for your feedback.
ShipStation does already support unicode characters. Orders using these characters can be imported successfully and other documents, like packing slips, can print from ShipStation with these characters (see this example of an order using Kanji in the Ship To address with a packing slip in ShipStation: https://www.screencast.com/t/F0v4sm81hEls)
However, many carrier label APIs will not accept these characters when we send them with the label request, which is why they often print with the ??? in place of the characters. This is why we recommend translating the Ship To address to use Roman characters.
However, as part of our expansion into non-English speaking markets and general internationalization effort, we’ll be looking into what carriers don’t have this limitation so we can provide more thorough documentation around it later in 2021. For any carrier that does accept unicode characters and can print them on the label, this support exists already in ShipStation.
Why make this so complicated? Why suggest what we already have no choice to do, which is using a translation service manually, often after having printed a bad label.
The simple and obvious solution, which has been mentioned previously, is for ShipStation to use the Google Translate API to translate automatically.
This has been under review for 5 years. That's deceptive.
Yanni Kioupouroglou GRAFEA LTD commented
Also adding Chinese language, Royal Mail supports chinese in their labels and it is such a waste of time having to translate all the orders manually.
Yanni Kioupouroglou GRAFEA LTD commented
Also adding Chinese language, Royal Mail supports chinese in their labels and it is such a waste of time having to translate all the orders manually
I'll add that I get an error message when trying to process a label that is entirely in Japanese characters that the address needs a "first and last name". I have to copy the email address as the company name to get it to print. And if I remember correctly, when printing packing slips for customs forms the Japanese characters show up as question marks.
We frequently receive orders from Korea, Japan and China, which means the customer's addresses are in character language rather than Latin characters. We will add an English translation and leave the customer's address alone when possible, but this often means the address is too long for the shipping label.
Please add support for other character languages.
Please, add a possibility to print labels for the addresses with hieroglyphs and other unicode symbols. At least for certain shipping companies like DHL that does support them.
This should also support foreign languages
Nicolas Lopez Calza Fino commented
I ship only domestic orders but 90% of my customers are Latino/Hispanic and many have names with the Latin characters (á, é, í, ó, ú, ñ) and it looks really bad on my company not been able to print their names correctly. I have printed labels with all kind of services and ShopStatin is the only one not supporting this.
The only reason I still use ShipStation is because of the mobile app.
Hello there, we are in Canada, have the same issue but only with Purolator , not Canada Post
I'm commenting on this, as shipstation used to print cyrillic characters just fine. When we first signed up, there was no issue with replacing non-latin letters with ???
This is very disruptive and it would be great if shipstation would revert to its original handling of these, which was flawless.
So we use ZPL for our labels instead of the PDF option. We have the same problem with the ???. Generally, this would cause me to suspect that we need to install the appropriate font pack. However, if this is also happening with PDF labels then the issue is on SS Side. I'm only assuming they produce all the labels into ZPL then generate the PDF or Push the ZPL to customers like us that want it that way.
Either way, getting this fixed would be super helpful. Having the shipping labels reflect the customers information when they enter it along side english in their own language helps to ensure faster, accurate deliveries with less returns.
Peter Adams G.G. Creative commented
I agree some sort of support for foreign character is essential for any business that sends international packages. Replacing foreign characters with ? is not acceptable. If it is necessary to replace foreign characters for some carriers this should be an optional toggle in shipstation, not done automatically on import.
Jimmy Howard TrackR Inc. commented
We need to create labels with Japanese Kanji characters using DHL E-commerce and eventually FedEx. Currently ShipStation does not support these characters with their carrier integrations. DHL and FedEx support these characters through their APIs. EasyPost, Shippo, and ShipHawk all support these characters through their integrations.
Is supporting this feature being actively worked on? If not, I will need to move my company to a new shipping solution.
Crystal Arjona HOC - Tony Mei commented
When I was using the USPS or Stamps website for shipping, I was able to print western (Chinese) characters along side the English address. So I don't fully understand anyone saying that it is because of a Postal regulation.
Jeremy Turner Webgophers, Inc. commented
Any update on this? we have trouble with exporting line items and it not exporting tildes and Chinese characters
This has been under review for nine months. Isn't it time to move forward with this bug?
This idea should be merged with "Support for common foreign characters".
we want to be able to upload via mass load CSV file addresses in non English characters (Chinese, Mandarin, Japanese, etc')
Thanks for the reply. Despite the OP's description of the problem, the real issue isn't which character set is supported by ShipStation, but which characters are supported by the postal service.
As per the USPS Development Guide for their API (https://www.usps.com/business/web-tools-apis/general-api-developer-guide.htm), the only allowable charaters are from the ISO-8859-1 standard, which is essentially the first Unicode block of characters. It covers the alphabets of most Western European countries.
That leaves out Cryllic, Hebrew, Arabic and most Asian languages. That's a real problem for those of us with broad international distribution.
I think that my last post describes a good way to deal with the problem.