{"id":6373,"date":"2018-01-10T11:26:13","date_gmt":"2018-01-10T10:26:13","guid":{"rendered":"https:\/\/eurotext-ecommerce.com\/en\/?p=6373"},"modified":"2024-09-30T08:49:16","modified_gmt":"2024-09-30T06:49:16","slug":"how-does-internationalization-work-with-magento-part-1","status":"publish","type":"post","link":"https:\/\/eurotext.de\/en\/blog\/how-does-internationalization-work-with-magento-part-1\/","title":{"rendered":"How does internationalization work with Magento? \u2013 Part 1"},"content":{"rendered":"
The technical implementation of internationalization in e-commerce:<\/strong> What is the best way to go about it? What possibilities do the various shop and content management systems<\/strong> have to offer when it comes to organizing content and products in multiple languages? And what are the potential pitfalls?<\/p>\n In the first part of this series we are focusing on Magento<\/strong><\/a>. This shop system is aimed primarily at medium to large-sized companies and enjoys widespread distribution thanks to its free software and highly dedicated community. Magento expert Rico Neitzel from B\u00fcro 71a kindly agreed to discuss the shop system with us. Having worked as a developer and adviser in the Magento scene since 2006, he has a wealth of experience and background knowledge to share. In this article we discuss both the benefits and the drawbacks of Magento-based shop solutions.<\/p>\n <\/p>\n <\/div> <\/div> Magento shops are structured in clearly defined layers. While this can be a challenge for inexperienced users, it provides the perfect conditions for retailers who want to offer different country or language versions<\/strong> of their shop. In principal there are 3 layers, or so-called scopes<\/strong>: global, website<\/em> and store view<\/em>. These are hierarchically structured, with lower levels inheriting the properties of the levels above.<\/p>\n <\/em><\/strong><\/p>\n The Global<\/em><\/strong> scope acts as the basis for all Magento installations and is where the default config is made. Where the shop is to be operated is specified here i.e. the legal basis of the shop. The admin area language can also be set globally. And this of course is where all of the products are created and managed.<\/p>\n The next scope, the website<\/em><\/strong>, is where the structure of the shop is created and various things concerning taxes and prices. A classic application is to create separate B2B<\/strong> and B2C<\/strong> websites at this level. The default settings for the prices (net\/gross) can then be set separately for the two websites<\/em><\/strong>. In international shops, websites <\/em>can be used to define base currencies<\/strong>. You can, for example, set up one website for the European market which calculates in Euros, and one for the American market which calculates in US Dollars. The shipping and payment options<\/strong> and taxes<\/strong> can then also be set at the website<\/em> scope.<\/p>\n One layer that does not belong to the configuration levels (scopes) is the store.<\/em><\/strong> This is primarily used to assign categories to the different websites. It is therefore possible to set up different stores with different product ranges or structures.<\/p>\n The final layer is the so-called store view,<\/strong> which is responsible for managing the presentation<\/strong> of the shop. This is where it gets interesting for internationalization, because the presentation of the shop includes the output language, currency<\/strong>, the theme<\/strong> and a number of other features through which the various country and language versions of the shop differ.<\/p>\n By the way, it’s no mistake that currency<\/strong> can be configured at both the website<\/em> and the store view<\/em> scope. If you create an online shop that calculates in Euros<\/strong> at the website<\/em> scope, that doesn’t necessarily mean that all store views<\/em> should display Euros<\/strong> only. You may want to set up a store view<\/em> for the Swiss market within the Euro website<\/em>. The store view<\/em> would then automatically convert the Euro prices into Swiss Francs. This way, customers see the relevant currency for their country, but in the background the calculations are being made in the base currency of the website \u2013 making life a whole lot easier for the retailer.<\/p>\n
\n\n
\n
\n<\/h2>\n
<\/span>Magento’s Layer Structure<\/h2>\n