States, Regions, and Prefectures, oh my! Confusion when is Numeric

CliffSCliffS Member
in Help edited October 2018
OK, everyone in America knows what a state is. So three's no problem when Foxycart returns a string like this:
<customer_state>WI</customer_state>
or
<shipping_state>WI</shipping_state>

I can figure it out to mean "WISCONSIN"

But when my customer is from Japan, I see this:

<customer_state>40</customer_state>
<shipping_state>40</shipping_state>

.... trouble! There ain't no such place as "40" in Japan.

Most likely, this number 40 is probably a lookup value for the prefecture of Fukuoka. OK, I can create and install a lookup table for the 47 Japanese prefectures.

Now how do I figure out what
<shipping_state>11</shipping_state>
means in France ?

Or
<shipping_state>17</shipping_state>
means in Portugal?


This numeric value is *NOT* a postal code, so I must not include it on the postal address.

How about if Foxycart translates these numbers into reasonable, useful text objects:

like in France, shipping_state 11 means PARIS
or in Portugal, shipping_state 17 means uh, I dunno...


EDITED by @brett to correct formatting
Comments
  • Dammit.
    I included the phrase OPEN BRACKET Shipping_State CLODSE BRACKET but the damn forum software eliminated all of them.
  • TRYING AGAIN. I really detest a forum that waste my time time learning its rules.


    OK, everyone in America knows what a state is. So three's no problem when Foxycart returns a string like this:

    OPENBRACKET Customer_State CLODSEBRACKE WI OPENBRACKET SLAXH Customer_State CLODSEBRACKE
    or
    OPENBRACKET Shipping_State CLODSEBRACKET WI OPENBRACKET SLAXH Shipping_State CLODSEBRACKE

    I can figure it out to mean "WISCONSIN"

    But when my customer is from Japan, I see this:

    OPENBRACKET Shipping_State CLODSEBRACKET 40 OPENBRACKET Shipping_State SLAXH CLODSEBRACKET


    .... trouble! There ain't no such place as "40" in Japan.

    Most likely, this number 40 is probably a lookup value for the prefecture of Fukuoka. OK, I can create and install a lookup table for the 47 Japanese prefectures.

    Now how do I figure out what
    OPENBRACKET Shipping_State CLODSEBRACKET 11 OPENBRACKET Shipping_State SLAXH CLODSEBRACKET
    means in France ?

    Or
    OPENBRACKET Shipping_State CLODSEBRACKET 17 OPENBRACKET Shipping_State SLAXH CLODSEBRACKET
    means in Portugal?


    This numeric value is *NOT* a postal code, so I must not include it on the postal address.

    How about if Foxycart translates these numbers into reasonable, useful text objects:

    like in France, shipping_state 11 means PARIS
    or in Portugal, shipping_state 17 means uh, I dunno...
  • brettbrett FoxyCart Team
    Hi @CliffS
    TRYING AGAIN. I really detest a forum that waste my time time learning its rules.
    Agreed. In our forum, the little "C" icon will wrap your text in code tags. Otherwise your brackets look like HTML, which gets stripped for security reasons. I've updated your original post with the right formatting.

    This is something we're actually aware of, and have fixed in certain situations. Can you whisper us some transactions where you've seen this so we can take a look? (It comes down to us using a 3rd party to get geographic data, and that system sometimes returns numeric data like you're seeing.)
  • bump
  • fc_adamfc_adam FoxyCart Team
    Hi @CliffS,

    Sorry for the delay - thanks for pinging us here, and for whispering those details to @brett. I've updated the ticket on our side with that data you've shared so we can ensure new changes we're working on also correct that data.
  • CliffSCliffS Member
    This problem continues. For example a recent order from Denmark, transaction nr 1564854000, shows a ship-to address with region of "85" My customer says this should be "Zeeland".

    It's as if an American ship-to address reported a state of "48" instead of Arizona.

    Please, if your software cannot make this substitution , please provide the lookup table and I can do it locally
  • fc_adamfc_adam FoxyCart Team
    @CliffS,

    I'm sorry this issue has persisted for so long. We are still working through the changes needed, but it's unfortunately taking a lot longer than we'd hoped.

    In the meantime, we can suggest turning off the postcode lookup functionality for your store. It does mean that the customer has a little extra work due to needing to enter all address fields, but it ensures that any regions that return a numerical value with our lookup always return what the customer entered. To do that, head to the "configuration" section of the Foxy administration, and uncheck the option labelled "Enable city and region lookup by postal code".
Sign In or Register to comment.