At a glance
Required-Attribute Completeness measures the share of your JD.com listings that have every category-required attribute filled in. JD runs strict, category-level attribute schemas: each category defines a set of mandatory properties (material, model, specification, certification fields and so on), and a listing missing any of them is deprioritised in search, can fail feed validation, and is at risk of being taken off-shelf. This gauge is the single number that tells you how exposed your catalogue is to attribute-driven suppression, and how much search surface you are leaving unclaimed.
Calculation
For each active listing, the card looks up the required-attribute schema for that listing’s JD category and checks whether every mandatory attribute is populated with a valid value. A listing is complete only when none of its category-required attributes are blank or invalid. The gauge value is:completeness % = (listings with all required attributes filled / total active listings) x 100
Because JD’s schemas vary by category and change over time, a listing that was complete last week can become incomplete when JD adds a new required attribute to its category. The card re-evaluates against the current schema on every refresh, so it catches schema changes as they land.
Worked example
A representative reading for a POP marketplace seller on JD.com. On 19 Mar 26 the gauge reads 91%, below the 95% safe band. Of 1,200 active listings, 108 are missing at least one required attribute. Drilling in shows the gap is concentrated: 70 listings in a single electronics category are missing a newly required certification field that JD added two days earlier, and the rest are scattered older listings missing a material or specification value. The fix is largely a bulk operation: populate the certification field across the 70 affected listings in one feed update, then work the long tail. After the bulk fix and a feed resync, completeness climbs to 97% by 21 Mar 26, clearing the alert and restoring the suppressed listings to normal search ranking. To find which categories most recently changed their required schema, use Vortex Mind; to ask which specific attributes are missing most often in plain English, use Ask Viq.Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in JD.com’s own dashboard: JD flags incomplete or sub-standard listings in the product-management and listing-quality areas, and the category-required attribute schema is visible when you edit a product. Reconcile by spot-checking a sample of listings the card marks incomplete against the required fields JD shows in the product editor for that category. Why the Vortex IQ value may legitimately differ:
Cross-connector reconciliation: read this with the feed-validation and off-shelf cards to see attribute gaps turning into validation failures and removals. For divergence investigations, use Vortex Mind.