Unable to specify recommended browse nodes via the Listings API

[jlevers]

How can I specify a recommended browse node via the Listings API? Despite the XML-to-JSON attribute mapping file mapping the XPath Message/Product/DescriptionData/RecommendedBrowseNode[1] to /attributes/recommended_browse_nodes/0/value, I'm not seeing the recommended_browse_nodes attribute in any product type JSON schema that I've downloaded.

Is there some way to specify the browse nodes via the Listings API? If not, why is there a mapping for the browse nodes field in the mappings file?

I can see this issue was raised before (#2314) and was closed without a response.

[jawheral]

Hi @jlevers,

I was able to find the recommended_browse_nodes attribute on multiple Product Type schemas in EU. Can you provide more information on the region/marketplace where you are experiencing the missing attributes?

Best,
Jawher
Selling Partner Developer Services

[jlevers]

Interesting. I've tried a number of different product types in NA (US marketplace), and none of them have recommended_browse_nodes in them, but when I tried the EU (GB marketplace) some of those same product type schemas did have the recommended_browse_nodes attribute. Is there some sort of account restriction that could prevent schemas retrieved with my NA seller ID from having that attribute?

[jawheral]

Hi @jlevers,

Please provide me an example Product Type that has a recommended_browse_nodes in the UK marketplace but not in the US.
I will then double check this and get back to you once I have more information.

Best,
Jawher
Selling Partner API Developer Services

[jlevers]

LUGGAGE and SHOES are both examples that, for me, only show recommended_browse_nodes in the UK but not in the US. Thanks!

[jawheral]

Hi @jlevers,

For the US marketplace, the placement works differently and there is no recommended_browse_nodes attribute in product types. The item_type_keyword has to be specified for the placement of listings.

Best,
Jawher
Selling Partner API Developer Services

[jlevers]

Huh, ok. I'm pretty sure that via POST_PRODUCT_DATA it's possible to send a RecommendedBrowseNode tag – do you know why that's no longer available using the JSON_LISTINGS_FEED?