David Brenner Thimble

My feedback

  1. 89 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    Thank you all for adding your ideas to the forum here! We’ll keep this in mind when updating our API; for now, we’d like to see what other users think about having return labels generated through the API before moving forward here.

    David Brenner Thimble supported this idea  · 
    An error occurred while saving the comment
    David Brenner Thimble commented  · 

    This would be a very, very useful addition to the API! Please re-examine this issue and move forward.

  2. 83 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    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,…

    David Brenner Thimble supported this idea  · 

Feedback and Knowledge Base