At a glance
Orders / Day is a fulfilment metric tracked from Alibaba data. It plots the daily count of B2B orders over time, giving operations a clean read on demand rhythm and the dispatch load each day brings. The card sits in the Fulfilment category and pairs with shipment-backlog and on-time-delivery siblings, because daily order volume sets the pace the warehouse has to keep. Cross-reference the related cards listed below for context.
| What it counts | The number of B2B orders placed per day across the trailing 30-day window, rendered as a line chart. Computed from the latest available order data and refreshed on the standard data refresh. |
| Sample type | Backend API data from Alibaba, refreshed on the standard data refresh. |
| Why it matters | The metric appears in the Fulfilment category and complements the sibling cards listed below. Daily order count drives staffing, packing, and dispatch planning, and a sudden spike or slump is an early operational signal. |
| Reading the value | Read the line for trend, weekday patterns, and spikes. Compare recent days to the running average to spot demand shifts. Cross-reference siblings for the full diagnostic picture. |
| Currency | count |
| Time window | 30D |
| Alert trigger | - |
| Sentiment key | ali_orders_per_day |
| Roles | owner, operations |
Calculation
Vortex IQ counts B2B orders by the day they were placed across the trailing 30-day window and plots each day as a point on the line. The chart makes weekday cycles, spikes, and slumps visible at a glance. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A representative reading of Orders / Day for a typical Alibaba supplier. Suppose the line runs at roughly 9 to 12 orders per weekday and 3 to 5 over weekends for most of the period. On 12 Mar 26 it jumps to 27 orders in a single day, well above the running average. The operations owner sees this immediately, checks whether a promotion or a large distributor RFQ converted, and pulls extra packing capacity forward so the spike does not turn into a dispatch backlog and a late-delivery problem. For deeper investigation of what drove the spike, use Vortex Mind to trace upstream causes; for natural-language exploration such as “why did orders jump on 12 Mar 26”, ask Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
total-transactions | Sales sibling: total order count this daily line aggregates. |
pending-shipment-waiting-seller-send | Fulfilment sibling: dispatch backlog that order spikes can create. |
on-time-delivery-rate | Fulfilment sibling: delivery rate that volume surges put at risk. |
gmv-over-time | Revenue sibling: GMV trend that order volume drives. |
average-order-value | Sales sibling: AOV that pairs with order count to explain revenue. |
Reconciling against Alibaba Seller dashboard
Where to look in Alibaba’s own dashboard: Open the Alibaba Supplier workbench, go to Trade then Order Management, and filter by order date to count orders per day, or use the data and analytics section for an order-trend view. Confirm period boundaries and filter settings match the Vortex IQ profile to reconcile cleanly. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses a 30-day rolling window by default; the workbench may use calendar periods. | Variable | Match the period range. |
| Time zone. The workbench uses the account time zone; Vortex IQ aligns to merchant reporting time zone, which can move an order to a different day. | Marginal | Confirm time zone match. |
| Filter scope. Profile-level filters (channel, B2B only, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. |