{"section":"known-issues","requestedLocale":"en","requestedSlug":"geocoordinates-data-cant-be-informed-for-some-cultureinfo","locale":"en","slug":"geocoordinates-data-cant-be-informed-for-some-cultureinfo","path":"docs/en/known-issues/Checkout/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md","branch":"main","content":"## Summary\n\n\n\nSome \"cultureInfo\" options, like \"en-ZA\" (South Africa) are generating issues along with the \"geoCoordinates\" property from the checkout service.\nThis information is used from calculating shipping options to defining a \"regionId\" (the sellers that covers an address).\nThe sent information will be refused, generating errors or simply being ignored deppending on the API.\nIt seems to be related with the decimal and thousands separator for certain \"cultureInfo\" – for \"en-ZA\" it seems related to the thousands separator being a blank space, although their decimal separator is a comma, as used in other countries.\n\n\n\n## Simulation\n\n\n- to have a store configured with \"en-ZA\" as \"cultureInfo\" (defined on the trade policy)\n- to try calculating a regionId on its API or even retreving SLAs (shipping options) on a simulation request\n\n\n\n## Workaround\n\n\nThere's no direct workaround to use the correct \"cultureInfo\", but you can try to find alternative options that behave as the expected option.\nNote that the \"cultureInfo\" mainly defines the language, but also the formatting for numbers, dates, and curency, including the curency symbol position."}