At a glance
Brand Authorisations Expiring in 30 Days counts the brand authorisations on your JD.com account that are due to lapse within the next month. JD blocks listings the moment their brand authorisation expires: an out-of-date authorisation removes every listing under that brand from sale and drops your brand-authorisation coverage below the safe band. Renewal paperwork takes time, so an expiry that surprises you is days of lost revenue and a coverage dip you could have avoided. This hero card is the early-warning queue: the authorisations to renew now, before JD enforces against them.
| What it counts | The number of held brand authorisations with an expiry date inside the next 30 days. |
| Sample type | Real-time evaluation from the JD.com integration, reading expiry dates on held brand-authorisation records. |
| Why it matters | When an authorisation lapses, JD blocks every listing under that brand and your coverage drops, which can trip the account-health alert. Renewing ahead of expiry avoids both the revenue loss and the compliance hit. |
| Reading the value | Zero means nothing is due to lapse this month. Any positive value is a renewal to-do list; open it to see which brands expire when, and how many listings each protects. |
| Currency | count |
| Time window | RT |
| Alert trigger | >0 |
| Sentiment key | jd_expiring_brand_auths |
| Roles | owner, operations, finance |
Calculation
The card reads the expiry date on every valid, in-date brand-authorisation record held on the account and counts those whose expiry falls within the next 30 days from today. Authorisations that have already expired are not counted here - they have already dropped out of coverage and belong to the brand-authorisation coverage card. This card is strictly forward-looking: it counts what is about to lapse so you can act before it does. Each entry typically carries the brand, the expiry date and the number of active listings that depend on that authorisation, so renewals can be prioritised by the revenue at stake.Worked example
A representative reading for a POP marketplace seller on JD.com. On 22 Mar 26 the card reads 3. Opening it shows three authorisations due to lapse: one brand expiring on 28 Mar 26 that protects 40 active listings including two of the store’s top sellers, a second expiring 05 Apr 26 covering 12 listings, and a third expiring 18 Apr 26 covering a single low-volume listing. The priority is obvious: start the renewal for the 28 Mar 26 brand immediately, because its lapse would block 40 listings and likely drop coverage below the 98% safe band within a week. The second can follow once the first is in train, and the third, protecting one minor listing, is low priority. By renewing the high-value authorisation on 25 Mar 26, well ahead of its expiry, the seller avoids any coverage dip or off-shelf event. To rank expiring authorisations by revenue at risk rather than by date, use Vortex Mind; to ask which top sellers depend on a soon-to-expire brand in plain English, use Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
jd_brand_auth_coverage | The live coverage figure this card stops from dropping. |
jd_account_health | The tripwire a lapsed authorisation would trigger. |
jd_off_shelf_24h | The removals that follow if an authorisation lapses unrenewed. |
jd_revenue_at_risk | The revenue exposed if expiring authorisations are not renewed. |
jd_listings_expiring | A parallel expiry watch on the listing side. |
Reconciling against the vendor’s own dashboard
Where to look in JD.com’s own dashboard: JD lists held brand qualifications with their validity dates in the brand-authorisation / qualification management area. Reconcile by checking that the expiry dates the card reads match the validity end dates JD shows for each held authorisation, and that the 30-day horizon lines up with today’s date. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Horizon definition. Vortex IQ counts the next 30 days from today; a vendor view may list all upcoming expiries regardless of horizon. | Vortex IQ lower | Filter the vendor list to the next 30 days. |
| Renewal sync. A renewal processed in JD may not have synced when Vortex IQ refreshed, so a renewed authorisation may still show. | Vortex IQ higher | Allow for renewal-sync lag, then refresh. |
| Grace period. JD may apply a grace window past the stated expiry that the card does not assume. | Variable | Confirm any grace period with JD. |