Back to Details

amz-category-renoding-fix

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Category Re-Noding Fix

分类节点变更修复

Amazon periodically re-organizes the browse tree and silently moves products to new nodes. A listing moved to the wrong node loses 30-70 percent of its organic search visibility overnight, because Amazon scores it against the wrong query set. This skill finds the wrong placement and writes the correction case.
亚马逊会定期重组浏览树（browse tree），并悄然将商品移至新节点。商品被移至错误节点后，一夜之间自然搜索可见度会下降30%-70%，因为亚马逊会针对错误的搜索词组合为其打分。本技能可找出错误位置并撰写修正工单。

When to use this

使用场景

  • Sales dropped sharply on a listing without a known cause.
  • A listing should rank for a category but does not appear in its filters.
  • Recently received a notification that a product was re-categorized.
  • Routine quarterly browse-tree audit.
  • 某商品销量急剧下降，但无明确原因。
  • 某商品应在某分类下排名，但未出现在该分类的筛选结果中。
  • 近期收到商品被重新分类的通知。
  • 每季度例行浏览树审核。

The framework. The Node Audit

框架：节点审核

Four questions to confirm a re-noding issue.
  1. What node is the listing actually in now? Look at the breadcrumb on the listing's own detail page and the category in Manage Inventory.
  2. What node should it be in? The most logical browse path a customer would use to find the product, plus what comparable competitors are in.
  3. Is the difference material? Some re-nodings are cosmetic. Others move the product out of the queries that drive its sales.
  4. What does the data show? Sessions and conversion before and after the suspected re-noding date.
If the node is wrong and the data shows the drop, file the correction.
通过四个问题确认节点变更问题。
  1. 当前商品实际处于哪个节点？ 查看商品详情页的面包屑导航以及「管理库存」中的分类。
  2. 商品应处于哪个节点？ 客户查找该商品最合理的浏览路径，以及同类竞品所在的节点。
  3. 差异是否显著？ 有些节点变更只是表面调整，有些则会将商品移出驱动其销量的搜索词范围。
  4. 数据显示了什么？ 疑似节点变更日期前后的访问量（sessions）和转化率数据。
如果节点确实错误且数据显示销量下降，即可提交修正申请。

Step by step

操作步骤

  1. Collect inputs. The ASIN, the current breadcrumb / browse node ID, the expected node, recent sessions and sales trend, and the date of the suspected change.
  2. Confirm the change. Compare the current node against the expected. Verify the drop in sessions or conversion ties to a specific date.
  3. Find the correct browse node. Use Amazon's browse tree (BTG) or look at where comparable products sit.
  4. Write the catalog correction case. Subject: "Browse-node correction needed for [ASIN]". Body: current node, requested node, business reason, before/after data.
  5. Submit through the right path. First try the self-serve fix: edit the listing's recommended browse node / item type, using the Browse Tree Guide to pick the correct node, either on the listing directly or via the Category Listings Report. If the self-serve edit does not stick, open a case. Brand Registered sellers file through Brand Registry > Manage Your Case. everyone else uses Seller Central > Help > Get Support > Catalog category. Attach a screenshot of the wrong placement and reference the correct browse node ID.
  6. Track resolution. Re-noding corrections take 5-15 business days. Watch the listing's breadcrumb and the session recovery.
  7. Run the quality check, then deliver.
  1. 收集信息：ASIN、当前面包屑/浏览节点ID、预期节点、近期访问量和销量趋势、疑似变更日期。
  2. 确认变更：对比当前节点与预期节点，验证访问量或转化率下降是否与特定日期相关。
  3. 找到正确的浏览节点：使用亚马逊浏览树指南（Browse Tree Guide, BTG）或查看同类竞品所在的节点。
  4. 撰写目录修正工单：主题："需为[ASIN]修复浏览节点"。正文：当前节点、请求变更的节点、业务原因、变更前后的数据。
  5. 通过正确路径提交：首先尝试自助修复：直接在商品列表或通过「分类列表报告」编辑商品的推荐浏览节点/商品类型，使用浏览树指南选择正确节点。如果自助编辑未生效，则提交工单。品牌备案（Brand Registry）卖家通过「品牌备案 > 管理您的工单」提交；其他卖家使用「卖家中心（Seller Central） > 帮助 > 获取支持 > 目录分类」提交。附上错误位置的截图，并注明正确的浏览节点ID。
  6. 跟踪解决进度：节点变更修复需要5-15个工作日。关注商品的面包屑导航和访问量恢复情况。
  7. 进行质量检查，然后交付结果。

Output format

输出格式

undefined
undefined

Category Re-Noding Fix. [ASIN]

Category Re-Noding Fix. [ASIN]

Current node: [breadcrumb / node ID] Should be: [breadcrumb / node ID] Suspected change date: [date]
Current node: [breadcrumb / node ID] Should be: [breadcrumb / node ID] Suspected change date: [date]

Impact

Impact

Sessions before: [n/day] After: [n/day] Drop: [%]
Sessions before: [n/day] After: [n/day] Drop: [%]

Case to file

Case to file

Subject: Browse Tree Guide correction for [ASIN] Body:
  • Current placement: ...
  • Requested placement: ...
  • Business reason: ...
  • Data attached: sessions and conversion before/after the change
Subject: Browse Tree Guide correction for [ASIN] Body:
  • Current placement: ...
  • Requested placement: ...
  • Business reason: ...
  • Data attached: sessions and conversion before/after the change

Submission path

Submission path

  1. Self-serve: edit recommended browse node / item type via the listing or Category Listings Report, using the Browse Tree Guide
  2. If that fails: Brand Registry case (if enrolled) or Seller Central > Catalog support case
undefined
  1. Self-serve: edit recommended browse node / item type via the listing or Category Listings Report, using the Browse Tree Guide
  2. If that fails: Brand Registry case (if enrolled) or Seller Central > Catalog support case
undefined

Worked example

示例

A kitchen-tool ASIN suddenly drops from 80 sessions a day to 22, ad spend flat. Investigation: the breadcrumb shows the product was moved from "Kitchen and Dining
Cookware and Bakeware > Specific subcategory" to a generic "Home and Kitchen" parent node a week ago. Comparable competitor products sit in the original subcategory. Case filed with sessions data attached. Corrected within 8 days, sessions recover to baseline.
某厨房工具ASIN的日访问量突然从80降至22，广告支出保持平稳。调查发现：一周前，商品的面包屑导航显示其从「Kitchen and Dining > Cookware and Bakeware > Specific subcategory」移至通用的「Home and Kitchen」父节点。同类竞品仍位于原子分类中。提交附上访问量数据的工单，8天内完成修正，访问量恢复至基准水平。

Quality check

质量检查

  • The current and expected nodes are documented, not described vaguely.
  • The drop is tied to a specific date by data, not assumed.
  • The expected node is justified by comparable competitor placement.
  • The fix is attempted self-serve first (listing / Category Listings Report via the Browse Tree Guide), then escalated to the right case channel (Brand Registry or Catalog support) if needed.
  • Resolution is tracked to confirm recovery.
  • 已明确记录当前节点和预期节点，而非模糊描述。
  • 通过数据将销量下降与特定日期关联，而非主观假设。
  • 预期节点的合理性已通过同类竞品的位置佐证。
  • 首先尝试自助修复（通过浏览树指南在商品列表或分类列表报告中操作），若失败则升级至正确的工单渠道（品牌备案或目录支持）。
  • 已跟踪解决进度以确认恢复情况。

Common mistakes

常见错误

  • Blaming the listing. Spending days rewriting bullets while the issue is a browse-node move.
  • No before/after data. A correction case without sessions data is dismissed.
  • Wrong submission path. Filing under generic support instead of the Brand Registry case path or the Catalog category in Seller Central.
  • One-off thinking. Amazon re-nodes multiple SKUs in one wave. check the whole catalog when one is found.
  • 归咎于商品本身：花费数天时间重写商品描述要点，而问题实际是浏览节点被移动。
  • 无变更前后数据：未附上访问量数据的修正工单会被驳回。
  • 提交路径错误：在通用支持渠道提交，而非品牌备案工单路径或卖家中心的目录分类渠道。
  • 孤立思考：亚马逊会批量变更多个SKU的节点。发现一个节点错误时，需检查整个商品目录。

Built by Jay GPT Pro

由Jay GPT Pro开发

Part of Amazon Pro Skills. Production-grade skills for serious Amazon sellers. Free and open. Built by Jay Margaliot.
I share a new AI play for Amazon sellers every week, free, in my WhatsApp group. Join here: https://chat.whatsapp.com/ILX65p1yWcaIG3c9WGHpTY
属于Amazon Pro Skills系列。为专业亚马逊卖家打造的生产级技能。免费开源。由Jay Margaliot开发。
我每周会在WhatsApp群组中分享一个面向亚马逊卖家的新AI玩法，完全免费。点击链接加入：https://chat.whatsapp.com/ILX65p1yWcaIG3c9WGHpTY