Problem identified: The Quable PIM allows you to manage multilingual content through translations, but it has no functionality dedicated to the specific management of markets or countries.
Approach not recommended: As a customer PIM administrator, it may seem intuitive to use languages to distinguish data by country, such as the date of availability of a product in France versus the United States. This approach would involve creating a text field that would be enriched with a date in the French language (fr_FR) and another in American English (en_US).
Why is this approach inappropriate? Language management (i.e. translation) should not be confused with country management.
Format problem: In our example, the fact that the attribute is translatable text does not guarantee the correct format of the date.
Country and marketplace specificities: Data specific to a country is no different from data specific to a marketplace. For example, the description of a product on an e-commerce site and on Amazon may vary, requiring two separate attributes. The same applies to country-specific data, which is not a simple translation.
Fear of complexity: You might fear that the number of attributes will become too great. However, thanks to the attribute access functionality, this won't impact on your users' experience. Better still, it will enable access to be managed efficiently for each national team, improving the management of content specific to each market.