Hi @coleatkinson — just checking in to see if there are any updates regarding the Markets compatibility warning that some apps are receiving, even without any active warnings or deprecated endpoints.
I’ve also sent you an email for more details.
Linking the original thread here for reference: Markets compatibility warning while installing
Thanks in advance!
@Kevin_Sieger @coleatkinson Great topic, these points are so basic yet so important. While the first point is not a deal breaker, the second point renders markets almost useless. As Kevin mentioned, TWINT has a market share of 67% and other countries also have their preferred payment methods.
Now, for a store based in the US or in any other country but selling globally, how do you offer their preferred payment methods? For example, if you go to your US based store (which has South Africa as a market) > payments > add payment method and search for PAYJUSTNOW, you will not find it. PAYJUSTNOW is huge in South Africa, but you cannot sell to us here since your store is based in the US. If you change your store address to South Africa, you can then use PAYJUSTNOW but then you are unable to use payment gateways for other countries…
We simply need the option to use and filter in/out payment gateways and shipping methods for each market.
@KyleG-Shopify Hey can you possibly take a look at this problem we are having? Restricting payment methods by store address instead of by market is really reducing the value of markets and means additional stores are necessary instead of using markets.
Hi everyone, we posted another update, adding some clarity around compatibility with the new Markets. Please let me know if this helps answer some of the questions on this thread and if you have further questions: Update: release of the new Shopify Markets and related APIs
Hey @Evaldas_Raisutis - thanks for the question. We added an updated post here to hopefully bring some clarity: Update: release of the new Shopify Markets and related APIs
To answer your questions directly:
Note: this only applies to the Markets and Catalogs APIs. Other APIs are unaffected by the new version of Markets.
Great, thanks for the clarification 
Hi Cole, just checking on any updates for market-specific third party payment gateways as you mentioned it is being thought about. This is key for selling internationally. Arguably the most important thing that is now missing from markets.
@coleatkinson while working on migrating our returns process to code our business owns, I noticed that Markets as a concept associated with a customer or order has been removed. How should merchants expect to identify Market orders for separation? Best I can see is using locale and keeping an internal running list, make multiple calls to string that together to a market, or inferring from Shipping Address.
I cant find any directions in the docs that relate to the change, just that the fields are deprecated in future apis.
Hey @coleatkinson really appreciate all the improvements that came with new markets dev preview and the docs that have come with it.
One issue we are running into when helping some of our International clients with PIM integrations to Shopify is the ability to include or exclude specific variants from a market catalog entirely. Is this on the radar or being thought about by the markets team? Would be more than happy to talk through or detail out the use case more if needed.
Thanks
Hi Kevin, please can you vote for this feature here : 3rd party Payment Gateways For Markets
Hello Cole,
I’ve noticed that all the different Shopify functions extension API’s seem to be deprecating any method of identifying the market localization.
For instance, the Cart and Checkout Validation Function API , Discount Function API and Cart Transform Function API
I am left wondering what viable alternative there will be for identifying a market or getting market metafields inside of function extensions? Function extensions don’t have access to the Admin API to use e.g. the market(), markets() or marketByGeography() queries to deduce a market or to get market metafields, etc. Should we be considering sunsetting any function-based features that rely on Shopify Markets?
We have a number of features that currently rely on markets and market metafields, here’s some examples.
It does not seem like it will be possible to achieve any of the above using Shopify markets in the future. There are potential workarounds, we could switch to a country-based approach and use shipping country for Cart and Checkout Validations, and localization.country for the other use cases (As long as that form of localization is not deprecated as well). This would certainly change the data structure requirements since market metafields would no longer be viable to save configurations (It seems only shop metafields will be available to function extensions so a reference table structure will be needed)… but it’s a potential alternative.
So my question is, considering the Function API’s have all deprecated the localization.market query are we correct in assuming we should stop relying on markets or market-based data for any functionality tied to Shopify Function Extensions?
Hey folks 
- we’re going to close out this thread for now as most have completed their migrations over to the new Markets Framework. If you have any additional questions, please feel free to reach out to our Developer Support team at help.shopify.com and we can assist.