> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Orders / Day, JD.com > Orders / Day for JD.com stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Marketplace](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Orders / Day** is the daily heartbeat of your JD.com store, the order count plotted day by day across the window. It is the fastest way to read demand rhythm: weekday-versus-weekend patterns, the run-up to JD's signature 618 and Singles Day (11.11) festivals, and the sharp spikes that follow a flash promotion or a homepage feature. For an operations lead it doubles as a capacity gauge, because every order on this line becomes a parcel that has to clear the JD ship-deadline and protect the Logistics DSR. It sits in the Fulfilment family and reads best beside the pending-shipment, dispatch-rate, and SLA cards below. | | | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The number of orders placed each day over the window, plotted as a daily time series. | | **Sample type** | Backend API data from JD.com, refreshed on the standard data refresh. | | **Why it matters** | Daily volume is both a demand signal and a fulfilment-load signal. Spikes around 618 and 11.11 or after a promotion warn operations to staff up before the dispatch backlog threatens the SLA; a quiet stretch flags a demand or ranking problem early. | | **Reading the value** | Read the line for shape, not just level: rising trend, weekly seasonality, and festival spikes. Overlay it mentally against pending shipment to judge whether dispatch capacity is keeping pace with intake. | | **Currency** | count | | **Time window** | `30D` | | **Alert trigger** | `-` | | **Sentiment key** | `jd_orders_per_day` | | **Roles** | owner, operations | ## Calculation Orders are bucketed by their order-placement date in China Standard Time and counted per day across the window, then plotted as a line. Cancellations that occur on the same day net out; returns posted later do not retroactively reduce the original day's count, so the line reflects order intake rather than net settled orders. Festival days and promotion days appear as their true raw spikes rather than being smoothed. ## Worked example *A representative reading of **Orders / Day** for a typical merchant on JD.com.* Suppose the line averages around 140 orders a day, with gentle weekend lifts, then spikes to 620 on the morning a flash promotion goes live and stays elevated for two days before settling. The spike is healthy demand, but cross-referencing the pending-shipment card shows the dispatch backlog doubled during those two days and the SLA compliance gauge dipped a point. The read is clear: the promotion worked, but fulfilment capacity lagged the intake, so the next promotion needs warehouse staffing planned against the expected daily peak rather than the monthly average. For deeper investigation, use Vortex Mind to correlate daily order spikes with dispatch backlog and SLA dips; for natural-language exploration, ask Ask Viq "what was my peak orders-per-day during the last promotion and did the SLA hold". ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | | [`jdc_pending_ship`](/nerve-centre/kpi-cards/jd-com/pending-shipment) | Fulfilment sibling: the dispatch backlog that builds when daily orders outpace capacity. | | [`jdc_pop_dispatch_rate`](/nerve-centre/kpi-cards/jd-com/pop-self-fulfilled-dispatch-rate) | Fulfilment sibling: whether self-fulfilment kept pace with the daily intake. | | [`jdc_logistics_sla`](/nerve-centre/kpi-cards/jd-com/jd-logistics-sla-compliance) | Fulfilment sibling: the delivery promise that a volume spike can put at risk. | | [`jdc_orders`](/nerve-centre/kpi-cards/jd-com/orders) | Sales sibling: the total order count this line breaks down by day. | | [`jdc_revenue_over_time`](/nerve-centre/kpi-cards/jd-com/revenue-over-time) | Revenue sibling: the revenue trend that mirrors the order trend. | ## Reconciling against the vendor's own dashboard **Where to look in JD.com's own dashboard:** JD's Seller Centre shows daily order trends in its sales and traffic analytics views. Confirm the chart counts placed orders (not paid or shipped orders, which JD sometimes splits out) and that the date range matches the Vortex IQ 30-day window. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | --------------------------------------------------------------------------------------------------------------- | --------- | -------------------------------------- | | **Order status basis.** Vortex IQ counts placed orders; JD may chart paid or shipped orders on a separate line. | Variable | Match the order-status definition. | | **Day boundary.** Vortex IQ buckets by China Standard Time placement date; confirm the vendor uses the same. | Marginal | Confirm the day cut-off and time zone. | | **Cancellation handling.** Same-day cancellations net out here; the vendor may show gross placed orders. | Marginal | Confirm cancellation treatment. | | **Period boundary.** Vortex IQ uses a 30-day rolling window; JD often defaults to calendar months. | Variable | Match the date range. | **Cross-connector reconciliation:** read alongside pending shipment and dispatch rate to judge whether daily intake is outrunning fulfilment capacity. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Orders / Day update?** The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations), so the current day's bar fills in through the day. For real-time signals, force a manual refresh from the dashboard. **Q: Why does my JD.com dashboard show a different daily count?** The common causes are the order-status basis (placed vs paid vs shipped), the day boundary and time zone, and how same-day cancellations are treated. Match those before assuming a real divergence. **Q: Today's bar looks low. Is something wrong?** The current day is still accumulating, so its bar will be partial until the day closes. Compare a complete prior day rather than the in-progress one before concluding demand has dropped. **Q: Can I customise the alert threshold?** This card has no default alert because daily volume is informational. You can add a sensitivity rule in the Sensitivity tab to be notified when daily orders move beyond a chosen band, for example to flag a demand cliff. *** ### Tracked live in Vortex IQ Nerve Centre *Orders / Day* is one of hundreds of KPI pulses Vortex IQ tracks across JD.com and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.