Skip to main content
Card class: HeroCategory: Ecommerce Platform

At a glance

Percentage change in number of orders placed versus the previous period. Order volume is the clearest signal of demand, declining orders usually precede revenue drops by 7-30 days. Order count strips out price and discount effects and shows the underlying transaction volume. A rising order count with falling AOV is a different story than a falling order count with rising AOV, and this card decomposes the picture so the merchant knows which of the two levers needs work.
What it countsThe percentage change in count of completed orders between the current 30-day period and the preceding 30-day period. Computed from BigCommerce orders with successful payment status. Excludes cancellations and refunds.
Sample typeBackend API data from BigCommerce orders, refreshed on the standard data refresh.
Why order count trend mattersOrder count is upstream of revenue and downstream of traffic + conversion. Falling order count by 10%+ is a leading indicator of a traffic, conversion, or competitive issue, even before revenue declines (because AOV may temporarily mask the volume drop). Track this card alongside revenue_trend and aov_trend to decompose where revenue change is coming from.
Reading the value(1) Above 10%: strong volume growth, almost always healthy. (2) 0-10%: stable demand. (3) -5% to 0%: mild softening; check seasonality. (4) -10% to -5%: investigation zone, likely a traffic or conversion issue. (5) Below -10%: alert state; demand has materially shifted, escalate. (6) Compare against same-period last year to control for seasonality.
Currencypercent change.
Time window30D vsP.
Alert triggerorder_count_trend < -5 (BAD threshold at -10%).
Sentiment keyorder_count_trend (TREND_BASED in SentimentClassifier; GOOD ≥ 0%, BAD ≤ -10%).
Rolesowner, operations, marketing

Calculation

order_count_trend (%) = (current_period_order_count - previous_period_order_count)
                        ÷ previous_period_order_count × 100

current_period_order_count  = COUNT(orders) WHERE order_date IN [today - 30d, today)
                              AND payment_status IN ('paid', 'captured', 'completed')
previous_period_order_count = COUNT(orders) WHERE order_date IN [today - 60d, today - 30d)
                              AND payment_status IN ('paid', 'captured', 'completed')

Worked example

A UK-based BigCommerce fashion store, order count trend reading on Wednesday 15 May 26.
MetricCurrent (15 Apr - 15 May)Previous (16 Mar - 15 Apr)ChangeYear-over-year (May 25)
Order count2,1032,408-12.7%1,950 (+7.8% YoY)
Sessions108,142116,540-7.2%-
Conversion rate1.94%2.07%-6.3%-
Order count trend: -12.7% (BAD threshold breached at -10%; card flags as Action Needed in red). What the trend is telling us:
  1. The headline order count drop is severe enough to trigger alert. -12.7% over 30 days, sustained, compounds to roughly -80% over a year. The card is in red and should be the morning-review priority.
  2. Year-over-year context softens the picture. Compared to the same period in May 25, order count is up +7.8%. The merchant is growing year-over-year but contracting period-over-period. This is typical for stores that ran an unusually large promotional campaign in the immediately prior period: the comparison base is artificially inflated.
  3. Decomposing the volume drop:
    • Sessions fell -7.2% (traffic issue: ad spend cut, organic erosion, or seasonality)
    • Conversion rate fell -6.3% (conversion issue: site speed regression, checkout problem, or pricing change)
    • The two compound to roughly -13% in expected orders, matching the -12.7% headline
  4. Likely causes, in priority of investigation:
    • Paid traffic cut: cross-reference gads_total_spend for the prior period vs current. If spend dropped, expect proportional traffic and order drops.
    • Site speed regression: cross-reference crux_lcp_p75 and psi_perf_score_summary. A 200ms LCP regression typically reduces conversion by 1-2 percentage points.
    • Checkout regression: cross-reference ga_cart_abandonment and ga_checkout_completion. A new checkout app or PSP integration could break the flow.
    • Seasonality: confirm against year-over-year and the prior-year same period.
    • Competitive pricing: if a major competitor cut prices in the period, basket-replacement may explain the drop.
  5. Recommended response:
    • Day 1: Decompose using the diagnostic flow above. Identify the primary driver (traffic, conversion, or competitive).
    • Day 1-3: If traffic-driven, restore ad spend or investigate organic erosion via gsc_clicks_trend.
    • Day 1-3: If conversion-driven, run a checkout flow test in incognito on mobile + desktop, validate payment gateway, validate site speed.
    • Day 7: Confirm trend slope has flattened. If still -10%+, escalate to founder review.
    • Day 14: Post-mortem on the cause with documented root cause + preventive control.
  6. What “good order count trend” looks like: order count rises 5-15%, sessions rise proportionally, conversion rate stable or rising, AOV stable. Order count growth without traffic growth means conversion improvement, the rarest and most valuable kind.
The diagnostic flow:
  1. Read order count trend %. Below -10% triggers alert.
  2. Decompose into traffic × conversion (sessions × conversion rate ≈ orders).
  3. Identify which leg is moving and target the specific upstream card.
  4. Confirm against year-over-year to control for seasonality.
Rapid-response playbook:
Time horizonAction
First 1 hourRead trend %. Decompose into traffic × conversion.
First dayIdentify primary driver, run checkout flow test.
First weekRestore the broken leg.
Day 14Post-mortem and preventive control.

Sibling cards merchants should reference together

CardWhy merchants reach for it
revenue_trendRevenue trend; orders × AOV.
aov_trendAOV trend; the other leg.
total_ordersAbsolute order count for the current period.
ga_traffic_trendSessions; orders are downstream of sessions × conversion.
ga_conversion_rateConversion rate; the other leg of the funnel.
failed_orders_trendFailed orders trend; declined payments mask demand.
gads_total_spendAd spend; primary driver of paid order volume.

Reconciling against the vendor’s own dashboard

Where to look in the BigCommerce control panel: Analytics → Orders for the order count over a date range; Analytics → In-Store Insights → Orders for BC’s own time series. Why the Vortex IQ count may differ from BC’s dashboard:
ReasonDirectionWhat to do
Cancelled orders. BC may include cancelled orders in totals; Vortex IQ excludes them.BC higherApply “Excludes cancelled” filter.
Test orders. BC may include test orders.BC higherApply is_test = 0 filter.
Period boundary. BC defaults to calendar months; Vortex IQ uses 30-day rolling.VariableUse BC custom date picker.
Channel filter. Vortex IQ profile may filter to one channel.VariableMatch channel filter.
Cross-connector reconciliation:
  • shopify.order_count_trend, adobe_commerce.order_count_trend: same metric on other platforms.
  • ga_purchase_count: GA-recorded purchases; should be within ±3% of BC orders. Larger gaps indicate tracking issues.
Quick rule for support tickets: check cancelled, test, period, channel, in that order.

Known limitations / merchant FAQs

Q: Order count is down 12% but our marketing campaigns haven’t changed. What’s going on? The change usually traces to one of: (a) site speed or checkout regression caused by a recent release or app install (run a checkout test in incognito), (b) seasonality the period-over-period comparison hasn’t accounted for, (c) a competitive event (major competitor sale or new product launch). Check the diagnostic flow above and cross-reference site speed and competitor calendar. Q: We had a huge BFCM campaign last month and now order count looks negative. Is this a real problem? Almost certainly not. BFCM and other peak-promotional periods inflate the prior-period base. Look at year-over-year comparison and the prior 90-day baseline. Many stores set the BAD threshold less aggressively for stores with high promotional volatility (BAD = -15% instead of -10%). Q: Order count is rising but revenue is falling. How is that possible? Falling AOV more than offsetting rising volume. Common causes: (a) a discount pulled forward many lower-value orders, (b) a category mix shift toward lower-priced items, (c) a free-shipping threshold dropped that allowed smaller-basket orders to convert. Cross-check aov_trend and discount_dependency. Q: How long does it take for an order count drop to show in revenue? Usually 7-21 days. Order count moves first because it captures all transactions immediately; revenue trend lags slightly because high-AOV outlier orders smooth the early decline. Treat order count trend as the leading indicator and revenue trend as the confirming indicator. Q: Should we set a tighter alert threshold? For stable-volume stores (subscription, repeat-heavy DTC), yes, set BAD around -5% because the baseline is more stable. For seasonality-heavy stores (gifting, fashion), keep BAD at -10% or even -15% to avoid alert fatigue. Q: Why does this card not include refunded or cancelled orders? Order count trend tracks demand. Refunded orders represent demand that was satisfied (the order was placed); they are counted. Cancelled orders represent demand that was withdrawn before payment, so they are excluded. The distinction matters: a high cancellation rate is a separate signal (cancellation_rate) and should not contaminate the demand-volume measure. Q: We see flat order count week-to-week but the trend says -10%. How? The trend is 30-day rolling vs the prior 30 days. As the rolling window moves forward, the comparison base changes. A store with a strong week 30 days ago can show negative trend even if current weeks are flat, the strong base is rolling out. Look at the unsmoothed daily series via orders_over_time to see the underlying pattern. Q: How does order count trend relate to ad spend? Closely. Most paid-traffic-led ecommerce stores see a near-linear relationship between ad spend and order count (with a 3-7 day lag). A 20% ad-spend cut typically produces a 12-18% order count drop within two weeks. If your store sees a much larger or much smaller response, it suggests either organic baseline strength (smaller drop) or paid dependency (larger drop).

Tracked live in Vortex IQ Nerve Centre

Order Count Trend is one of hundreds of KPI pulses Vortex IQ tracks across BigCommerce 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 or book a demo to see this metric running on your own data.