Andrew Erickson is the founder of Inventory Hero. He has spent years working with Amazon FBA sellers on demand forecasting, restock planning, and the cash flow side of running a private-label brand. Inventory Hero exists because every spreadsheet-based inventory system he tried eventually broke — usually right before Q4.
The item type keyword (the item_type_keyword attribute) is a backend catalog field that identifies what your product is in Amazon's taxonomy, using values like business-and-store-sign-holders or travel-garment-bags. Amazon's developer documentation describes item type keywords as the values used to place ASINs in the correct place in its category graph. Each ASIN carries exactly one, and Amazon derives the browse node from it.
How do I find my product's item type keyword?
Request the Category Listing Report in Seller Central under Reports > Inventory Reports. It lists your SKUs with a Product Type column and an Item Type Keyword column. Access to that report has to be enabled by Seller Support, so open a case first if you do not see it. You can cross-check what the value should be with the Product Classifier in the Add a Product flow, or against the Browse Tree Guide for your category.
Is the item type keyword the same as the browse node?
No. The item type keyword is a text value that describes the product; the browse node is a numeric ID for a storefront category. Amazon assigns the browse node from the item type keyword, so they are linked but not identical. A listing has one item type keyword, and changing it is the usual mechanism for changing the browse node.
Does the item type keyword affect my Amazon fees?
Indirectly and only sometimes. Referral fees are set by the product category Amazon assigns, and most categories sit around 15% with a range of roughly 8% to 17%, so a category change can move that percentage. Amazon's fee categories do not always match the storefront category you see, so verify the actual number in the Fee Preview or the fee section of your listing rather than assuming. FBA fulfillment fees are driven by size tier (dimensions and weight), so a reclassification alone does not normally change them.
Can Amazon change my item type keyword without telling me?
Sellers have reported exactly that in Seller Central forums, including item type keywords flipping to unrelated values after a listing edit or a compliance flag. Those reports cluster in 2020 to 2023 rather than recently, so treat it as a real but intermittent risk rather than a guaranteed universal policy. Audit your own values on a schedule and you will know either way.
The Amazon item type keyword (the item_type_keyword attribute) is a single backend catalog field that tells Amazon what your product actually is, using values like business-and-store-sign-holders. Amazon's developer documentation says item type keywords "are used to place new ASINs in the appropriate place(s) within the graph."1 Your browse node is derived from it, and Amazon's own seller guidance is that "the right categorization placement helps customers find your products more easily when browsing and searching on Amazon."2 Here is how the pieces actually fit, where to look yours up, and why a change you did not make shows up in your forecast before it shows up anywhere else.
It is a controlled-vocabulary text value on your listing that names the specific kind of product you are selling. Not a search keyword you optimize, and not something shoppers ever see.
Item Type Keyword
A backend Amazon catalog attribute (item_type_keyword) holding one enumerated value that identifies what a product is within Amazon's taxonomy. Valid values are defined per product type and marketplace, and Amazon derives the listing's browse node from it.
The valid values are not free text. They come from the enumerated list published in your product type's schema for a given marketplace, the same vocabulary surfaced in the Browse Tree Guide and in the Seller Central listing flow.1 Amazon's own guidance is to "select the most specific accurate term for optimal placement."1
Two mechanics drive everything below. A listing carries one item type keyword, not several. And the browse node follows from it, which is why changing the item type keyword is the normal lever for moving a product. Amazon's seller-facing instruction for a category change is literally to "update the Item Type Keyword field in the Product Details tab."2
Five related things get used interchangeably in seller groups and they are not the same. This is the table to keep.
Concept
What it is
Form
Who sets it
What it controls
Item type keyword
The specific thing your product is
Text value from an enumerated list (travel-garment-bags)
You submit it; Amazon can override
Placement in the catalog graph, and the browse node derived from it
Browse node
A node in Amazon's storefront navigation tree
Numeric ID assigned by Amazon
Amazon assigns, usually from the item type keyword
Where shoppers find you when browsing and filtering
Recommended browse node
The field where you request a node
Numeric ID in a flat file column
You submit it as a request
A suggestion, not a guarantee of placement
Product type
The listing template your ASIN uses
Code such as LUGGAGE, HOME_BED_AND_BATH
You submit it; Amazon can override
Which attributes are required, optional, or valid on the listing
Category
The shopper-facing label
Human-readable path
Amazon
How the product reads to a buyer, and the fee category Amazon applies
The distinction that trips people up: product type controls which fields exist on your listing, and the item type keyword controls where the listing sits. Both come out of the same classification decision, which is why a reclassification often changes both at once and suddenly your flat file has attributes you have never heard of.
The rule of thumb circulating among sellers is that the last segment of your live category path should match your item type keyword, and when it does not, you are leaking traffic.3 That is a heuristic from a practitioner newsletter rather than published Amazon guidance, but it is a fast, free check and it costs nothing to run.
Three places, in the order I would actually use them.
1. The Category Listing Report. Seller Central > Reports > Inventory Reports > Category Listing Report, then Request Report. It returns your SKUs with a Product Type column and an explicit Item Type Keyword column, which is the fastest way to audit the whole catalog at once.
The catch is that this report is hidden by default on most accounts and has to be switched on by Seller Support. The path to ask: Help > Get Support > Selling on Amazon > "Or browse for the issue in the menu" > Investigate other product, listings, inventory issues, then in Describe Your Issue ask them to activate the Category Listing Report on your account. Sellers commonly report a turnaround of a few hours to about a day, and access granted for roughly a week at a time before you have to ask again.4 Open that case now, before you have a problem.
2. The Product Classifier. In the Add a Product flow, it walks you from the top of the category tree down to the specific node and product type Amazon thinks your item belongs in. Use it as the "what should this be" reference, then compare it against what the report says the listing actually is. Amazon points sellers here rather than to raw Browse Tree Guides because the classifier carries current values.5
3. The live detail page. Read the breadcrumb on your own ASIN and the Best Sellers Rank category lines. This is the shopper-facing view, and it is the one that tells you whether a backend change actually landed on the front end.
Three things, in descending order of how much they probably cost you.
Search discoverability. Amazon says correct categorization helps customers find your products when browsing and searching, and it names the item type keyword as the field you change to fix a category.2 What Amazon does not publish is the stronger version of that claim, the one you will hear in seller groups: that Amazon gates which queries a listing is eligible to rank for by its category, so a wrong node keeps you out of the race entirely regardless of your copy. Vendor and practitioner sources assert that mechanism directly.36 I have not found an Amazon document that states it. Treat the direction as well supported and the hard gate as unproven, and note that either version points to the same action: get the value right.
Browse and filter placement. If your ASIN is not mapped to the right node, it does not appear in the filtered views and category browse paths shoppers use.6 Lower impact than search, but it is real traffic, and this one is directly observable. Go look.
Fee category, sometimes. This claim gets overstated, so be precise. Referral fees are set by the product category Amazon assigns, most categories sit at 15%, and the full range runs roughly 8% to 17%.7 A category change can move that percentage. But Amazon's fee categories do not always line up with the storefront category you see, so never infer your rate from a breadcrumb. Read the actual number in the Fee Preview or the fee section of the listing. FBA fulfillment fees, by contrast, are driven by size tier (dimensions and weight), so a reclassification on its own does not normally change what it costs to ship the unit. If your fulfillment fee moved, look at your measured dimensions first.
Sellers report it, and have for years. Treat that as the honest framing, not "Amazon announced a policy."
The corroboration is real but seller-side. Seller Central forum threads describe item type keywords flipping to unrelated values: one seller's school and office supply variations landed across eleven product types and six categories, with values like "hair coloring agent" and "chairs," and another had item type keywords rewritten across a brand-registered catalog after intellectual property flags.89 Amazon's moderator guidance in those threads was to push a full flat file update to override the existing values.8
Now the part that cuts the other way, because it should. Those threads cluster in roughly 2020 to 2023. The 2026 wave of attention traces largely to Kevin King's Billion Dollar Sellers newsletter, which reported that a February 26, 2026 flat file change to the browse tree guide "quietly reshuffled prototypes and item type keywords," and that Amazon's classification now leans on your title, bullets, and description rather than your stated preference.3 I could not confirm that against a Seller Central help page, and I could not find a corresponding wave of 2026 forum complaints either. If a February change had reshuffled item type keywords across the catalog, six months is long enough that the forums would be loud about it. They are not. That absence is a data point, and it argues for a narrower reading: this is an intermittent, account-level and edit-triggered failure mode, not an ongoing catalog-wide event.
What is confirmable, and enough to act on: the attribute exists, it is load-bearing, and when it does move you will not get an email about it.
A reclassification does not just cost you sales this week. It corrupts the demand history you forecast from, because your sales record no longer reflects the search eligibility you have today.
Here is the shape of it. The numbers below are illustrative, not measured: they are there to show the mechanic, not to claim a typical impact size. Say a SKU runs a sales velocity of 40 units a day, a 45-day supplier lead time, and 10 days of safety stock. The reorder point math is real and you can run your own numbers in the reorder point calculator:
Reorder point = daily velocity x (lead time + safety days)
Scenario (illustrative velocities)
Daily velocity
Lead time + safety
Reorder point
True demand
40
55 days
2,200 units
Refit to post-reclassification sales
26
55 days
1,430 units
If velocity settles at an invented-but-plausible 26 a day and you do what a disciplined operator does (refit the forecast to recent sales), you order about 35% less. Then the catalog issue gets fixed, demand snaps back, and you are short at the reorder point with 45 days of lead time in front of you. The reclassification cost you weeks of sales; the forecast you built on top of it costs you a stockout, which has its own ranking consequences on the way back.
This is the general contaminated-history problem, and it is not unique to catalog drift. A Buy Box loss, a lapsed campaign, or a competitor launch all poison a forecast the same way. Our Amazon inventory forecasting guide covers how to quarantine those days. The item-type-keyword-specific contribution is knowing to look for the cause at all, which is the next section.
Here is the checklist I would run, cheapest and most likely first. Stop when you find the cause.
Price and Buy Box. Did your price move, did a competitor undercut you, or did you lose the Buy Box? Check Featured Offer status on the listing. This is the cause more often than anything else.
Availability. Did you go out of stock, or did units move to reserved or stranded status? Reserved and stranded units are invisible to shoppers but still on your inventory report.
Suppression and compliance. Open Account Health and the Listing Quality Dashboard. Suppressed listing, compliance flag, or a variation family that broke apart? This is a binary check that takes a minute, which is why it goes near the top even though it is a less common cause.
Catalog attributes. Pull the Category Listing Report and compare item type keyword, product type, and browse node against your last snapshot, or against what the Product Classifier says the product should be. Check the title and bullets for an unauthorized contribution too, since a copy change is a plausible reclassification trigger. This is the step almost everyone skips.
Advertising. Did a campaign run out of budget, lose a bid position, or did a bulk change go out? Pull the campaign's daily spend and impressions, not just ACoS.
Reviews and rating. Did the star rating drop, or did a negative review land in the top slot?
Seasonality and the category. Is the whole category down? Compare against last year's same weeks before you conclude the problem is yours.
Step 4 is the one most seller checklists leave out, which is exactly why catalog drift goes undiagnosed for a quarter. Run it on sales velocity per SKU, not account totals, because a single reclassified child in a variation family gets averaged into invisibility at the parent level.
Fixing is a flat file job more often than a UI job. In the forum threads above, Amazon's own moderator guidance was that a full update pushed through a category flat file is what overrides the existing values, and sellers there report that a Seller Central UI edit frequently does not stick.8 If the browse node itself is wrong rather than the item type keyword, there is a self-service browse node change request in Seller Central help that sellers report is often resolved same day.9 If neither works, open a case with your correct classification, the Product Classifier path, and two or three comparable ASINs already sitting in the node you want.
How long before you should panic. Amazon's guidance on category changes is to allow 24 to 48 hours for the change to take effect after you update the item type keyword.2 A flat file itself processes in about 15 to 30 minutes, and the detail page usually catches up within a day. Amazon does not publish a recovery timeline for search placement after a category correction, so there is no documented number to hold you to. The practical read: give the front end two days to reflect the new category, then judge velocity off the days after that. Do not re-cut a purchase order off the depressed rate while the fix is still propagating, and do not conclude the fix failed until the breadcrumb on the live page has actually changed.
Then close the loop so it does not happen twice:
Snapshot the Category Listing Report with the date, and diff it against the last one. Quarterly is enough for most catalogs; monthly if you have been burned before.
Watch the SKUs you edited. Significant title, bullet, or attribute edits are a plausible trigger for automated reclassification, since Amazon's classifier reads that copy, so check the category two weeks after any listing rewrite.3
Bake it into restock planning. Add a catalog check to whatever cadence you already run for restock planning, so it happens whether or not something looks wrong.
The item type keyword is one text field on a listing nobody looks at, which is exactly why it is worth twenty minutes a quarter. It is not a growth lever. It is a floor you can fall through without hearing a sound.
Amazon SP-API developer documentation, "Get recommended browse nodes or item type keywords" (accessed August 2026). developer-docs.amazon.com/sp-api/docs/get-recommended-browse-nodes-or-item-type-keywords. Note on attribution: this page documents the item_type_keyword field as it appears in the product type schema returned by the Product Type Definitions API (getDefinitionsProductType), not a standalone API operation of that name. Source of the quoted definition, the guidance to "select the most specific accurate term for optimal placement," the enumerated per-product-type and per-marketplace values, and the distinction between item type keyword strings and numeric recommended browse node IDs. ↩↩2↩3
Amazon Seller Central forums, official Amazon post by Cooper_Amazon, "Is your product correctly mapped this Prime Day?" (2025). Source of "the right categorization placement helps customers find your products more easily when browsing and searching on Amazon," the instruction to update the Item Type Keyword field in the Product Details tab to change a category, and the 24 to 48 hour window for a category change to take effect. This is the closest thing to a primary Amazon statement linking categorization to discoverability; it does not state that category gates query eligibility. ↩↩2↩3↩4
Billion Dollar Sellers Newsletter (Kevin King), issue dated June 29, 2026, billiondollarsellers.com. Source of the "last word of your category path should match your item type keyword" rule of thumb, the report that a February 26, 2026 flat file change to the browse tree guide "quietly reshuffled prototypes and item type keywords," and the claim that title, bullets, and description are now key attributes used for classification. This is a practitioner newsletter, not Amazon documentation. The classification-policy claim could not be confirmed against a Seller Central help page, and a search of Seller Central forums in August 2026 did not surface a corresponding cluster of 2026 seller reports. Treat it as reported rather than established.
Category Listing Report access, path, and contents, per multiple seller-facing walkthroughs (Zentail help center; Feedvisor; ecommerceChris; AMZ Advisers; accessed August 2026): Seller Central > Reports > Inventory Reports > Category Listing Report, containing Product Type and Item Type Keyword columns. Access is enabled on request via Help > Get Support > Selling on Amazon > browse the menu > Investigate other product, listings, inventory issues. Reported turnaround ranges from a couple of hours to about a day, and reported access windows from about seven days to a month. Both vary by account and neither is documented by Amazon. ↩
Amazon Product Classifier, available in the Seller Central Add a Product flow. Described in seller-facing documentation (accessed August 2026) as Amazon's recommended way to find the correct product type and browse node because it carries current values, in preference to raw Browse Tree Guide files. ↩
"Amazon Browse Nodes Explained: Why Your Brand Isn't Showing in Search," sellercandy.com (2026). Source of the point that an ASIN not mapped to the correct node will not appear in filtered category views, and of the practitioner assertion that category placement constrains search visibility. Vendor blog, not an Amazon primary source. ↩↩2
Amazon referral fee percentages, as held in Inventory Hero's reference-data registry (fba.referral.standardRate, 15%, effective 2024-01-15, re-verified 2026-08-10) sourced from Amazon Seller Central pricing, sell.amazon.com/pricing. Registry note: "Varies by category, roughly 8% to 17%." Confirm your own SKU's rate in the Fee Preview or the fee section of the listing, since Amazon's fee category does not always match the storefront category shown in the breadcrumb. ↩
Amazon Seller Central forums (UK), "Amazon Routinely Change Product Types & Categories | Catalog Has Become a Mess," seller thread with Amazon moderator reply (thread posted 2022, moderator reply 2023). Source of the eleven-product-types-across-six-categories report, the "hair coloring agent" and "chairs" examples, and the Amazon moderator recommendation to push a full flat file update to override existing attribute values. ↩↩2↩3
Amazon Seller Central forums (US), "Item Type Keyword Classification - Randomly changed" (thread posted circa 2020, ongoing) and "Reclassification, Browse Nodes, and Solutions." Source of the report that item type keywords were rewritten on brand-registered ASINs following intellectual property flags, the note that an ASIN carries a single item type keyword and that replacing it is the mechanism for changing the browse node, and the peer-shared self-service browse node change request in Seller Central help. ↩↩2