At a glance
Daily order count plotted as an area chart over 90 days. The trend version of Total Orders. Where Total Orders gives you point-in-time numbers, this card shows the daily shape, peaks, troughs, weekly seasonality, and the long-term direction.
| What it counts | DATE_HISTOGRAM COUNT(_id) per day across every order in the 90-day window. |
| VAT / tax treatment | n/a, count metric. |
| Shipping | n/a. |
| Discounts | n/a. |
| Refunds | Not deducted (refunded orders count on placement date). |
| Cancelled / voided orders | Included (the order existed; cancellation is a downstream state). |
| Currency | n/a. |
| Channels / sources | All channels contribute. Channel-shape patterns: web orders cluster around lunch / evening peaks; POS clusters around store-open hours; marketplace orders distribute more evenly across the day. Multi-channel stores see a smoother trend than single-channel. |
| Day-of-week effects | Most BC stores see weekend dips on weekday-categories (B2B, office supplies) and weekend peaks on weekend-categories (homewares, fashion). The 7-day rolling average smooths these effects; the daily bars expose them. |
Incomplete orders | Included by default. They represent customer-intent events; for “successful orders only” trend, exclude status = Incomplete. |
| Multi-currency | The trend is the same regardless of currency mix; count is currency-insensitive. |
| B2B Edition | B2B order placement clusters around month-end (procurement cycles); single-month windows can hide this rhythm. The 90-day view typically shows the pattern. |
| Time window | 90D (rolling 90 days, daily granularity) |
| Alert trigger | None at this card; sentiment key order_count_trend is monitored at the Total Orders and BC Alert Revenue Drop levels. |
| Roles | owner, marketing, operations |
Calculation
Worked example
A US homewares brand on BigCommerce Pro, 90-day window from 13 Jan 26 to 12 Apr 26.| Period | Avg orders/day | Notable peaks | Trend direction |
|---|---|---|---|
| 13 Jan 26 to 26 Jan 26 | 198 | 320 on 22 Jan (clearance flash sale) | Declining (post-holiday tail) |
| 27 Jan 26 to 9 Feb 26 | 224 | 280 on 8 Feb (Spring catalogue launch) | Rising |
| 10 Feb 26 to 23 Feb 26 | 235 | 410 on 14 Feb (Valentine’s) | Stable+ |
| 24 Feb 26 to 9 Mar 26 | 248 | 290 on 5 Mar (mid-week spike) | Stable |
| 10 Mar 26 to 23 Mar 26 | 232 | nothing notable | Slight decline |
| 24 Mar 26 to 6 Apr 26 | 218 | 380 on 28 Mar (Spring launch promo) | Concerning |
| 7 Apr 26 to 12 Apr 26 | 210 | 320 on 11 Apr (bank-holiday weekend) | Continued decline |
- The 90-day shape: peak around mid-Feb, gradual decline since. The store’s typical-day order count fell from 248 (peak) to 210 (recent), a 15% decline in 6 weeks. Concerning trend even though no individual day looks alarming. The 90-day shape is what catches slow declines that single-period summaries miss.
- Campaign spikes are clearly visible. Valentine’s, Spring launch, and the 11 Apr bank holiday all show as 1.5-2x baseline days. Healthy responsiveness to promotions; problematic if the underlying baseline is falling between promotions.
- The 28 Mar Spring launch peak (380 orders) was a single-day surge but the days after it didn’t sustain. Compare against the 14 Feb Valentine’s peak which was followed by a multi-day elevated baseline; the Spring launch retained less. That’s a customer-quality signal: the launch acquired campaign-driven first-time buyers who didn’t return.
- The mid-week 5 Mar spike (290) with no apparent campaign driver is suspicious. Almost always one of three causes: (a) a viral social post / influencer mention, (b) a competitor outage that pushed traffic to you, (c) a leaked discount code being aggregated. Investigate via BC Top Coupons and social listening.
- Day-of-week pattern visible underneath the trend. Most homewares stores see Saturday and Sunday as peak ordering days; weekends in this trend cluster 30-50% above weekdays. Healthy seasonality, not a problem.
- Compare 30-day rolling avg to 30-day rolling avg from prior period, smooths out daily noise. A 5%+ rolling-avg decline is real; under 5% is noise.
- Cross-reference Customer Acquisition Trend. Order trend declines driven by new-customer drops are top-of-funnel; driven by repeat-customer drops are retention.
- Pair with BC Channel Revenue Mix. Drops usually concentrate in 1-2 channels.
- Audit campaign cadence. If campaigns were running steadily and have stopped, the baseline reflects the no-campaign reality, the question becomes whether your campaign cadence is sustainable as the always-on state.
- Check the BC Incomplete Rate trend. Rising incomplete with falling orders = checkout friction is the cause.
Sibling cards merchants should reference together
| Card | Why pair it with Orders Over Time |
|---|---|
| Total Orders | The point-in-time summary. This card shows the daily shape; that one shows current vs prior. |
| Revenue Over Time | Same shape, different axis. Together they show whether order growth = revenue growth or AOV-shift. |
| Total Revenue | Revenue context. Order trend up + revenue trend up at same rate = volume growth; rates diverging = AOV moved. |
| Customer Acquisition Trend | New-customer trend. Pairing with order trend shows whether growth is driven by new or returning. |
| BC Channel Revenue Mix | Channel decomposition. |
| BC Revenue by Hour | Intra-day shape. Daily trend + hourly view = full temporal picture. |
| BC Weekend Weekday | Day-of-week aggregation. Strong weekend / weekday patterns visible here. |
| BC Alert Revenue Drop | Real-time alarm when this trend dips abruptly. |
Reconciling against the vendor’s own dashboard
Where to look in BigCommerce Control Panel: Analytics → Sales → “Orders over time” chart shows the daily order trend. The granularity is daily by default; switch to hourly for intra-day view (Plus / Pro). Standard plan stores need to compute manually from the order export. Why our number may legitimately differ from BC Analytics:| Reason | Direction |
|---|---|
Incomplete order treatment. We include them; BC Analytics typically excludes. | Vortex IQ HIGHER bars |
| Cancelled / Declined orders. Included here, may be excluded in BC Analytics. | Vortex IQ HIGHER bars |
| Time zone. UTC vs store TZ; daily bars at the boundary shift. | Boundary effects |
| Sync lag. Recent days are preliminary until end-of-day. | Vortex IQ slightly LAGS for today |
| Channel coverage. Both views aggregate every channel; differences are sync timing. | Same direction |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
google_analytics.ga_purchases_trend | GA4 purchase event trend should track shape | GA4 misses 10-25% of orders; absolute level differs but shape aligns. |
stripe.stripe_charges_trend | Stripe-side charge count trend | Stripe sees only successful captures; this card includes Incomplete and Declined. |
shopify.orders_over_time(planned)adobe_commerce.orders_over_time(planned)