Amazon Voice of the Customer and NCX Rate: An Operator Guide

Account health is measured at the account, suppression happens at the ASIN

A seller called us in February with a clean Account Health page. Order Defect Rate 0.4 percent, late shipment rate under 1 percent, no policy violations. Two of their four bestselling ASINs had been deactivated the previous week. Nothing on the Account Health page had predicted it, because the signal that mattered lived in a different dashboard entirely.

Voice of the Customer, under the Performance menu in Seller Central, reports customer experience at product level. Each ASIN carries a CX Health rating from Excellent down through Good, Fair, Poor and Very Poor, driven by its negative customer experience rate. Sustained Very Poor status is what triggers listing level action, and it can happen while every account level metric stays green. If your monthly account review only covers the Account Health page, you are watching the wrong instrument.

What the NCX rate actually counts

NCX rate is the share of orders for an ASIN that produced a negative customer experience. The inputs are broader than returns alone. Returns with a negative reason code count, as do customer service contacts about the product, refunds, A-to-z claims and negative product reviews. That breadth is the point: Amazon is trying to capture disappointment, not just physical returns.

Amazon does not publish a universal cutoff, and the practical threshold varies by category. As a working rule, treat anything above roughly 3 to 5 percent as the zone where CX Health degrades in most Indian categories, while remembering that the denominator is doing a lot of work. An ASIN with 20 orders and one defect reads at 5 percent and means almost nothing. An ASIN with 4,000 orders at 2.2 percent is a real and expensive problem hiding behind a comfortable looking number.

This is why the correct sort order is by NCX order count, not by NCX rate. Rate ranking pushes your low volume listings to the top of the list and buries the SKU that is generating 90 unhappy customers a month at a rate that looks acceptable.

The five reasons and what each one really means

Voice of the Customer shows the top negative experience reason per ASIN. Reading that reason correctly determines whether the fix costs you an afternoon or a production run.

• Product not as described. This is almost always a listing defect rather than a quality defect. The buyer received exactly what you shipped and expected something else. The fix is bullet one, the dimension or scale image, and the size chart. Cheapest fix available and the fastest to show results.
• Defective or damaged. Split this by fulfilment channel before doing anything. If damage clusters in FBA orders, it is transit and packaging, so review prep and box selection. If it appears evenly across channels, it is a manufacturing or batch issue, and you should pull the batch codes.
• Wrong item received. Look at variation parentage and catalogue mapping first, because a mislinked child ASIN sends buyers a size or colour they did not order. In FBA, also check whether commingled inventory is in play.
• Late delivery. Not a product problem at all. Either handling time is set too optimistically for the SKU or the fulfilment channel is wrong. Moving high NCX self shipped SKUs to FBA often solves this line item on its own.
• Missing parts or quantity. Nearly always a pack composition mismatch, where the title says pack of two and the carton contains one, or an accessory shown in an image is not in the box. Audit title, image and actual pack together.

A weekly cadence that clears the dashboard

Give this 45 minutes a week and it stays clear. Monday, export Voice of the Customer alongside your returns reports, both the FBA customer returns report and the seller returns report, and join them on ASIN. Voice of the Customer tells you the platform view. The returns report tells you what the customer typed in free text, which is where the real diagnosis usually sits.

Rank by NCX order count and take the top ten. Tag each with one of the five reasons above, assign a named owner and a date, and record the current NCX rate as a baseline. Then do the thing most sellers skip: set a check four weeks out. The metric is trailing, so only orders placed after your change carry the improvement, and judging a fix at day seven will make you undo work that was going to succeed.

One more rule belongs in this cadence. Pause or heavily cut advertising on any ASIN rated Poor or Very Poor. Spending on a listing with a known defect is paying to accelerate the very experience that is going to get it suppressed, and it raises the return volume that drags your account level metrics with it. Restart the spend when CX Health recovers to Fair or better.

What good looks like after a quarter

Sellers who run this properly usually find the same shape in their data. Roughly half of the top NCX reasons turn out to be listing accuracy problems that cost nothing but attention. A quarter are packaging problems concentrated in one or two SKUs. The remainder are genuine product or supplier issues that need a sourcing conversation, and those are worth knowing precisely because a marketplace defect rate is a very expensive way to discover a batch problem.

The output you want after ninety days is not a perfect dashboard. It is a short, stable list of ASINs you have decided to keep despite a structural defect rate, priced accordingly, with advertising sized to match, and no surprises arriving by email on a Friday evening.