Fixed Market Price Columns in CSV Not Working After Summer '25 Update (Markets → Catalogs)

Topic summary

Shopify’s Summer 2025 update renamed Markets to Catalogs and appears to have broken CSV-based market-specific pricing imports. Users report inconsistent behavior: some products import with correct per-market pricing (e.g., Price / US, Price / UK columns), while others default to base pricing across all markets despite identical CSV structure.

Key Issues:

  • Native CSV import through Products page no longer reliably processes market price columns
  • Some products show different variant counts across catalogs (e.g., 100 variants in EU, only 60 in US)
  • Shopify support has provided conflicting information, claiming the feature should still work

Workarounds Identified:

  • Import CSVs directly through Markets > Catalogs > [specific market] > Import instead of the main Products import
  • Use the catalog-specific export template format (example screenshot provided)
  • Avoid rows with multiple images or blank cells when using catalog imports
  • Third-party tool Matrixify now supports both old Markets and new Catalogs pricing

Major Concern:
For stores with large catalogs (23+ markets, 1.5M+ inventory lines), the new system exports 23 separate files taking 2+ hours, making bulk price management extremely difficult compared to the previous single-file workflow. One user reports the issue may be partially resolved, with price edits now syncing to country catalogs.

Summarized with AI on October 25. AI used: claude-sonnet-4-5-20250929.

HI all,

Since the Summer 2025 update where Shopify changed Markets into Catalogs, my product uploads using CSV with market-specific pricing (e.g., Price / US, Included / US, Price / UK, etc.) have started behaving inconsistently.

I’ve been using this method for years with no issue. Now:

  • Some products are imported and priced correctly per market.

  • Others imported with the same CSV structure, ignore the market pricing and apply the EU base price across all markets (US and UK included).

Shopify support has not provided an answer. They incorrectly claimed I changed my store plan (I didn’t) and blamed Matrixify (which I haven’t used since a free trial in Nov 2024 and have never used to import or manage products).

Support also confirmed via chat that CSV with market columns should still work, but it clearly doesn’t work consistently.

Has anyone else experienced this?

  • Did the update silently break CSV support for catalogs?

  • Is there a new way we’re supposed to handle per-market pricing?

Any insight or confirmation is appreciated.

Chloe

2 Likes

Faced the exact same issue today and have been selling products at wrong prices because of this :roll_eyes:

The only fix I see is to overwrite the outdated catalog with an extra CSV import through: Markets > Catalogs > [your market] > Import.

I would appreciate some clarifications on this change as well :thinking:

Thanks

Hi @ChloeFrankc !

While I am not able to comment on the issue you are facing with your Shopify Import itself, I just wanted to let you know that Matrixify now has a feature that allows to update the pricing in both the old Markets and new Catalogs. The app is equipped to be able to handle this and our support is also on hand to help if you run into any issues.

We do offer tutorials and documentation on this on our website and if you reach out to our support at support@matrixify.app we can help guide you on how you can set your Import up!

1 Like

Oh wow, so it’s not just me.

Support told me they haven’t seen this issue before either. They said I should either update prices in each market manually (like you said) or keep importing CSVs through the product page — even though it’s not working properly.

It’s a pain, especially with 300 products. I also noticed some products show fewer variants in certain catalogs — like 100 in EU but only 60 in US. Have you had that too? And do you know if we can add variants directly in the catalog?

shopify support is totaly out of the picture.

importing the clasic way, through the native import/export… doesnt react.

i tried adding columns (in my case PRICE / ROMANIA; INCLUDED / ROMANIA) it doesnt work

the method i had succes with was creating a csv with the export example in the “markets” zone.

you can export a sample csv… just like in the native way

ive build a csv using those columns, it uploads fast, it update prices, also included/excluded… but be aware if you have products with more than one pic… it skips those rows.

so be careful only to use handle with sku and price, no blank cels.

in the big picture i think it will help, as it grows the matrix of a product but there is a bug or it is built like this on purpose… we will find out

the only sure thing is shopify advisors are out of their league

if your file looks like this… it will go through perfectly

I came across this issue a few weeks ago.

This unannounced change to market pricing makes seeing and updating market prices much more difficult and impossible to manage for large catalogs.

Previously I could download a single product, edit and upload again in less than 1 minute if needed. Now I can not even see the price of a product across our 23 markets in one place.

Our total market inventory lines run 1.5m lines or more. So today I tested a download. It took over 2 hours.

Then when downloaded it was 23 separate files totaling 223MB.

We sometimes would have sales in specific markets on specific brands. This would be run off formulas based on the base price. I could before export a brand and edit pricing with a preformulated formula for each market. This can no longer be done without significant additional work.

At this point I am going to have to create my own system to automatically output the relevant new feed style from the old export style because the new export is useless.

This is possibly one of the worst “improvements” Shopify have made.

I think problem is solved by shopify in the way that, me with only one catalog… when i edit the price… it gets editet in the country catalog as well. try it out. they may have found the bug that made csv editing imposible