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.
| What it counts | The percentage of active listings whose full set of JD category-required attributes is populated. A listing missing any one required attribute counts as incomplete. |
| Sample type | Real-time evaluation from the JD.com integration, comparing each listing’s attributes against its category’s required schema. |
| Why it matters | Incomplete attributes push listings down JD search results, can fail feed validation, and expose listings to off-shelf enforcement. Completeness is a direct lever on discoverability and a leading indicator of compliance risk. |
| Reading the value | Higher is better; 100% means every active listing meets its category schema. A reading below the 95% safe band means a slice of your catalogue is being suppressed and should be remediated. |
| Currency | percent |
| Time window | RT |
| Alert trigger | <95% |
| Sentiment key | jd_attribute_completeness |
| Roles | owner, operations |
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
| Card | Why merchants reach for it |
|---|---|
jd_listing_quality | The broader listing-quality score completeness feeds into. |
jd_feed_validation_fail | Validation failures that missing attributes often cause. |
jd_off_shelf_24h | Off-shelf removals that incomplete attributes can trigger. |
jd_chinese_title | A parallel discoverability gap on the title side. |
jd_active_listings | The denominator: the active catalogue being measured. |
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:| Reason | Direction | What to do |
|---|---|---|
| Schema timing. JD may add a required attribute that Vortex IQ picks up before the vendor view flags affected listings. | Vortex IQ lower | Allow for schema-propagation timing. |
| Listing scope. Vortex IQ measures active listings only; the vendor view may include draft or off-shelf listings. | Variable | Match the active-listing filter. |
| Valid-value check. Vortex IQ treats a present but invalid value as incomplete; the vendor may count it as filled. | Vortex IQ lower | Confirm the value passes JD’s validation, not just presence. |