At a glance
Revenue Over Time plots your JD.com gross revenue across the trailing 90 days as an area chart, so you can see the shape of demand rather than a single snapshot. On JD this shape is dominated by the platform’s promotional calendar: the 6.18 mid-year festival, Singles’ Day on 11.11, and smaller monthly Super Brand Day pushes create sharp peaks, while the days after a festival usually dip as buyers wait for the next discount window. Reading the curve in that context is what separates a real problem from a normal post-festival lull.
Calculation
Calculated automatically from your JD.com data. The card aggregates gross revenue per day across the trailing 90 days and renders it as an area chart. Values are gross of JD commission and before refunds; the net-of-commission view lives on its own card. See the worked example below for how to read the curve.Worked example
A representative reading of Revenue Over Time for a JD.com seller. The 90-day curve to 23 Jun 26 is flat around CNY 12,000 per day for most of the window, then spikes to CNY 95,000 on 18 Jun 26 (the 6.18 festival), and settles back to roughly CNY 9,000 per day in the days after. At first glance the post-6.18 drop looks alarming, but it is the normal festival hangover - buyers who pulled purchases forward into the discount window. The real question the curve answers is whether the 6.18 peak beat last year’s; here it did, by about 20 percent, so the trend is healthy. Use Vortex Mind to overlay the prior-year festival peak, and ask Ask Viq “is the post-6.18 dip larger than usual?” to separate seasonality from a regression.Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in JD.com’s own dashboard: In JD Seller Centre, open the Business Analysis (sheng yi luo pan) section and view the revenue trend report. Set the range to 90 days and confirm the metric is gross transaction value before commission. JD’s default dashboards sometimes show a paid-vs-placed distinction; match Vortex IQ’s basis (settled order revenue) before comparing curves. Why the Vortex IQ value may legitimately differ:
Cross-connector reconciliation: pair with the orders and AOV cards to attribute a trend move to volume or basket size. For divergence investigations, use Vortex Mind.
Known limitations / merchant FAQs
Q: How often does Revenue Over Time update? The card refreshes on the standard data refresh (typically every 30-60 minutes). The most recent day’s bucket fills in as orders settle, so today’s point can rise through the day. Q: Why does my JD.com dashboard show a different curve? Usually the basis: this card plots gross-of-commission, before-refunds revenue. JD’s take-home or net-of-refunds views sit lower. Time-zone bucketing (China Standard Time vs your reporting zone) can also shift a day’s total across the midnight boundary. Q: The curve crashed right after 6.18 / 11.11. Is something broken? Almost certainly not. Post-festival dips are normal because buyers pull purchases forward into the discount window. The meaningful comparison is festival-peak vs the same festival last year, not festival vs the quiet days after it. Q: Can I customise the alert threshold? This is a trend card with no default alert (-). If you want movement alerts, configure a percentage-change threshold per profile in the Alert Rules tab so seasonal festival swings do not trip it.