Product Advertising API
Developer Guide (API Version 2013-08-01)

Understand BrowseNode Results When Drilling Down

BrowseNodes are related in a hierarchy where one BrowseNode can have zero or more ancestor and child BrowseNodes, as shown in the following figure.

                    See tan example browse node.
  • This diagram shows five BrowseNodes and their hierarchy. Node A might be, for example, "Women". Node B might be "Shoes". Node C, a child of BrowseNodes A and B, might be "Women’s Shoes".

  • The numbers represent the number of items in each BrowseNode.

  • "Women's Shoes" is a subset of the two browse nodes, "Women" and "Shoes". It's possible that all 50 items in "Women's Shoes" are also in "Women."

  • When ItemSearch searches "Women", the operation returns that the node has 200 total items.

  • When ItemSearch is repeated with a BinParameter Name value that was returned in the first ItemSearch request, it is the same as running ItemSearch on a child node of "Women", which in this case is "Women's Shoes".

  • By narrowing the search to only the values found in "Women's Shoes", ItemSearch returns only items in "Women" and "Women's Shoes". The number of common items is 35.

                    See tan example browse node.

As a result, ItemSearch returns the items from "Women", which has 35 items. The change in the item count in "Women" might be confusing, but understand that ItemSearch returns only the intersection of "Women" and "Women's Shoes", which explains why the number of items in "Women" changes. Note that the item counts in other BrowseNodes can also change.

Because the number of items in BrowseNodes can change with each ItemSearch operation, the BrowseNodes with the greatest number of items can change dramatically. In the previous example, the number of items in "Women" changed from 200 to 35 after successive ItemSearch requests. Because ItemSearch returns only the top ten BrowseNodes that have the most items, the identity of the top ten BrowseNodes can change with each ItemSearch.