Unfulfilled Orders, BigCommerce

​

At a glance

Number of paid orders awaiting fulfilment. Growing backlog means an operational bottleneck, customers expect 1-2 day processing, and every day an order sits unfulfilled is a day closer to a customer service ticket, a chargeback, or a negative review. The card answers the operational question every fulfilment manager asks at the start of every shift: how big is the queue right now, and is it growing or shrinking?

​

Calculation

unfulfilled_count = COUNT(orders WHERE
                      payment_status IN ('paid', 'captured', 'completed')
                      AND fulfillment_status IN ('unfulfilled', 'partial', 'awaiting_fulfillment')
                      AND status NOT IN ('cancelled', 'declined', 'refunded'))

​

Worked example

1. The backlog is 3.2 days of intake. With 70 orders per day inbound and 224 unfulfilled, the queue would take 3.2 days to clear if no new orders arrived. Operational target is 1-2 days; 3.2 days means the team is fulfilling slower than the demand.
2. Decompose the queue:
   • 47 orders are blocked on OOS items: these cannot be fulfilled until the inventory arrives or the customer is offered a substitute. Cross-reference out_of_stock_count.
   • 177 orders are ready to ship: these are the actionable backlog. At a healthy fulfilment rate of 80 orders/day, this is 2.2 days of work for the team, borderline manageable but not lean.
   • The oldest order is 9 days old: every day past the 1-2 day expectation increases the probability of a customer-service contact, a refund request, or a chargeback.
3. Why the backlog grew:
   • Demand surge: order intake may have spiked above the team’s daily fulfilment capacity (check against 30D rolling intake).
   • Capacity issue: a fulfilment-team absence, warehouse incident, or supplier delivery delay reduced output.
   • Process bottleneck: a new packaging requirement, address-validation step, or shipping-carrier issue is slowing per-order processing.
   • OOS pile-up: blocked-on-stock orders accumulating because new stock hasn’t arrived.
4. Recommended response, in priority order:
   • Hour 1: Identify the 9-day-old order and any others above 5 days. Personally email each customer with status + estimated dispatch + apology. Pre-empt the contact-centre ticket and the negative review.
   • Day 1: Sort the 177 ready-to-ship by order age (oldest first); fulfil oldest first to drain the long-tail risk.
   • Day 1-2: For the 47 OOS-blocked orders, contact each customer with options: (a) wait for restock, (b) substitute, (c) refund.
   • Day 2-3: Identify the bottleneck (capacity, process, supplier) and apply specific fix.
   • Day 7: Confirm backlog reduced to 1-2 days of intake.
   • Result: customer-service ticket volume normalises within 48 hours of clearing the long-tail; refund/chargeback risk closes; backlog returns to operational target.
5. The chargeback prevention angle. Orders unfulfilled past 7-10 days frequently trigger:
   • Customer-service refund requests (which the merchant must absorb plus shipping cost).
   • Card-issuer chargebacks (which damage the merchant’s processor reputation, increase processing costs, and risk MID restrictions).
   • Personal email outreach within 48 hours of order placement dramatically reduces both. The cost is one customer-service interaction per delayed order; the saving is the chargeback fee plus refund operational cost plus reputation cost.
6. Cross-reference cards:
   • fulfillment_rate: percentage of orders fulfilled (compare to backlog count).
   • out_of_stock_count: identifies the OOS-blocked subset of the backlog.
   • bc_aov_by_country: high-AOV orders should be fulfilled first to minimise refund exposure.
   • bc_alert_fulfilment_delay: explicit alert when the backlog exceeds the threshold.

1. Read the count. Above 50 triggers alert; above 100 is severe.
2. Decompose: ready-to-ship vs OOS-blocked vs old-tail.
3. Personally outreach the old-tail to prevent escalation.
4. Clear ready-to-ship oldest-first.
5. Identify and fix the bottleneck (capacity, process, supplier).
6. Re-audit daily until backlog returns to target.

​

Sibling cards merchants should reference together

​

Reconciling against the vendor’s own dashboard

​

Known limitations / merchant FAQs

​

Tracked live in Vortex IQ Nerve Centre