Skip to main content
Solved

Merchant Center CSV Import

Drazen
Forum|alt.badge.img+2

Hi, 

I’m trying to do an CSV product import with the Merchant Center import functionality. 

I’m having issue with localised set attributes. I tried multiple combinations but I didn’t find a working example for localised set/text field. 

Attributes are defined as text, localised and set, e.g. “specifications” attribute. 

I tried the following: 
 

attributes.specifications.en.*.key 

attributes.specifications.key

attributes.specifications.en.1.key

attributes.specifications.en.



 

Any help would be welcome. 

Regards, 
Drazen

Best answer by Drazen

Actually I managed to get it working: 

 

..., attributes.specifications.*.en , ...
..., First English specification.   , ...

or 

..., attributes.specifications.1.en, attributes.specifications.2.en ,...
..., First English specification.  , Second English specification.  ,....



But a recommendation would be to improve the error reporting, I had another error in the import and I just got “Invalid json” error or something like that so it was hard to see whats the issue (think it was a missing mandatory field) 

Regards, 
Drazen

View original

Lily
Forum|alt.badge.img+2
  • Lily
  • Community Manager
  • August 12, 2024
https://giphy.com/gifs/AppleTV-apple-tv-appletv-tamacti-WOliLGRz7TJtGAazTp

 

Cavalry is on its way @Drazen! 

Drazen
Forum|alt.badge.img+2
  • Drazen
  • Going Places
  • August 12, 2024

Actually I managed to get it working: 

 

..., attributes.specifications.*.en , ...
..., First English specification.   , ...

or 

..., attributes.specifications.1.en, attributes.specifications.2.en ,...
..., First English specification.  , Second English specification.  ,....



But a recommendation would be to improve the error reporting, I had another error in the import and I just got “Invalid json” error or something like that so it was hard to see whats the issue (think it was a missing mandatory field) 

Regards, 
Drazen

Lily
Forum|alt.badge.img+2
  • Lily
  • Community Manager
  • August 12, 2024
Drazen wrote:

Actually I managed to get it working: 

 

..., attributes.specifications.*.en , ...
..., First English specification.   , ...

or 

..., attributes.specifications.1.en, attributes.specifications.2.en ,...
..., First English specification.  , Second English specification.  ,....



But a recommendation would be to improve the error reporting, I had another error in the import and I just got “Invalid json” error or something like that so it was hard to see whats the issue (think it was a missing mandatory field) 

Regards, 
Drazen

Thanks for the update, and I’ll forward your feedback to the team 😊

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
© 2025 commercetools GmbH - All rights reserved