The recommendation here is to run multiple stores + Klaviyo accounts… Shopify Markets is in Beta now, the benefit is to sell to multiple markets from one store. Therefore, the recommendation seems to be a bit outdated, since the benefit of Shopify Markets is to sell internationally from one single store. As far as I understood, it is more ore less the same technology and options Shopify offers today but bundled differently.
We currently run our store in EN but are about to add DE as a second language. Customer marketing+forms and so on has to be bilingual too.
Is there a Best Practice approach how to run (lists, flows, forms, content, ...) in multiple languages without unnecessary overhead?
Our Product Team is still exploring how this new Shopify Market feature will play a role in interacting with Klaviyo. At present, it is still best practice to run one Klaviyo accounts per Shopify store until we have further results on the new feature. @Dov also has a great explanation of why linking only one store per Klaviyo account is still recommended in the following Community post:
Since this feature is still in Beta, I would also suggest reaching out to Shopify to see if they can provide any further details regarding this feature. If you haven’t already we also offer a great Academy course on running a mulinational business that may help you on your way to launching a new store!
Once our Product Team has any further news or update after scoping out the Shopify market feature, we’ll be sure to share the news publicly!
I’ve also got a number of clients asking for this feature. Any update from Klaviyo would be welcome.
The best solution I’ve found so far is to create a custom product catalog, together with custom tagging of customers by the locale Shopify designates. This has a bunch of cons though, and is not that simple to get off the ground. For example, you generally have to use custom product blocks instead of the built in ones, to be able to access localised pricing information contained within a custom product feed.
Any updates here regarding how to solve Shopify markets + Klaviyo when you have the markets on the same domain name but each market is localized in separate sub folders?
I am trying to understand what exactly is needed for Klaviyo to work flawlessly using Shopify Markets. 1. Customer lists: Except the customer lists, that we perhaps can filer using the “locale” parameter, so we have unique campaigns for each country.
2.Product catalog: We would also need a unique product catalog for each country, with the correct domain URL for each market, but also the description language as well as the correct price and currency for each Market as these will change in between markets, since the VAT is different between countries.
By clicking “Accept All Cookies,” you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
Privacy Preference Center
Your Privacy
Strictly Necessary Cookies
Performance Cookies
Functional Cookies
Targeting Cookies
Site Analytics
Your Privacy
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Privacy Notice
Strictly Necessary Cookies
Always Active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
Performance Cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Functional Cookies
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
Targeting Cookies
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Site Analytics
These cookies record your visit to our website, and are used to track your visit including information such as: web page interactions (clicks, hovers, focus, mouse movements, browsing, zooms and other interactions), referring web page/source through which you accessed the Sites, heatmaps and scrolls, screen resolution, ISP, and statistics associated with the interaction between device or browser and the Sites. If you are accessing our Services with a European IP address, you have been asked to consent to the use of these cookies (you are free to deny your consent).