Alerts for Order Processing Backlog.
At a glance
A live alarm that fires when orders awaiting action build up faster than your team is clearing them. It compares the current count of orders sitting in a pre-fulfilment state against your own 30-day baseline, and escalates when the pile grows beyond twice your normal level. A backlog usually means a warehouse, payment-capture, or staffing bottleneck that will turn into late shipments and customer-service load if left alone.
Calculation
Calculated automatically from your WooCommerce data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A self-hosted WooCommerce supplements brand normally ships same-day. Over a bank-holiday weekend the warehouse closes but orders keep flowing. The operations lead gets a Key Metrics alert on the morning of 14 Mar 26.
Four things to notice:
- The baseline is the store’s own normal. The trigger is not a fixed number; it is twice this brand’s typical
processingcount. A store that normally carries 5 orders would fire at 11, while this one fires at around 90. The relative baseline is why the same card works for a side hustle and a high-volume seller. - The backlog compounds over a closure. Each day the warehouse was shut, paid orders kept arriving and none cleared, so the pile grew 46 to 91 to 148 to 162. The card fired on the first day it crossed 2x and stayed lit until the catch-up shift drained it. This is exactly the early warning a planned-closure backlog needs.
- It cleared when the work was done, not on a timer. The alert resolved once the live count dropped back under the baseline after Monday’s catch-up shift. The card tracks reality, not a fixed cooldown.
- Pair it with processing time. A persistent backlog drags up Avg Processing to Completed Time. If that sibling is also climbing, customers are now waiting noticeably longer, which is when refund and chargeback risk starts to rise.
Sibling cards merchants should reference together
Reconciling against WooCommerce
Where to look in WooCommerce Admin: WP Admin → WooCommerce → Orders and click the Processing filter tab to see the live count this card is built on. The number in parentheses next to “Processing” is your current backlog. Switch to Pending payment to see the leading-indicator pile. WooCommerce → Reports → Orders gives a historical view to sanity-check your normal baseline. Other WP Admin views that relate to this alert:- Orders screen status tabs (Processing, Pending payment, On hold): the parenthetical counts are the raw inputs. Add Processing plus Pending for the closest match to the backlog this card watches.
- WooCommerce → Home → Stats: shows orders that need attention but uses the Analytics module’s framing, which can differ slightly.
- A fulfilment plugin’s dashboard (ShipStation, Order Desk): these often define “awaiting fulfilment” differently and may exclude on-hold orders.
Known limitations / merchant FAQs
Why does it compare against my own average instead of a fixed number? Because a “backlog” means something different for every store. Forty pending orders is a crisis for a one-person operation and a quiet Tuesday for a high-volume seller. Triggering at twice your own trailing 30-day average means the alert is meaningful whatever your scale, and it adapts automatically as your business grows. Will a genuine sales spike fire this even though nothing is wrong? Yes, and that is often useful. A flash sale or a viral moment that doubles yourprocessing pile will fire the card, which is a prompt to staff up fulfilment before shipments slip. Read it alongside Total Orders: a backlog driven by a real order spike is a capacity prompt, not a process failure.
Does it include on-hold orders?
Not as the core signal. The backlog is built on processing (paid, needs fulfilment) with pending as a leading indicator. on-hold is a separate payment-awaiting pile tracked by On-Hold Orders. Watch both during a payment-method problem.
My store auto-completes orders, so I never see a backlog, is that a problem?
If you auto-flip orders straight to completed (common for digital goods or some subscription setups), they never sit in processing and this card stays quiet by design. That is correct behaviour for fully automated fulfilment. The card is most useful for stores with a physical pick-pack-ship step.
The alert cleared but my warehouse is still behind, why?
The card watches order status, not physical reality. If your team marks orders completed before they actually ship, the backlog clears in WooCommerce while parcels still sit on the dock. The fix is process discipline: only mark completed when the parcel is genuinely dispatched, so the card reflects the truth.
Why did the count freeze for a few hours?
Most likely a self-hosted host was unreachable during a poll, so the live count went stale until the next successful sync. Check WooCommerce → Settings → Advanced → REST API to confirm the Vortex IQ key is active and your host status page for any outage.