A term Rabehni uses, not an industry-standard term. We use it because this category has no common name, and without a name it does not get measured.
Order Limbo
An order in limbo has not reached a final state (delivered, returned, failed or cancelled) and has not moved operationally within a period you set, such as 24, 48 or 72 hours. It is neither a success nor a failure: it is an order that has stopped.
An order is in limbo when both hold:1. status ∉ { delivered, returned, failed, cancelled }2. hours_since_last_status_change > threshold
Why it needs a name
Most reports split orders three ways: delivered, returned, cancelled. A stopped order is in none of them, so it vanishes from the reports, yet it stays in the denominator and lowers every rate you calculate.
Worse, it looks like a shipping problem when it is not. Shipping never saw this order.
Choosing the threshold
There is no single right number. It depends on your operating cycle:
If you confirm the same day. It catches delays early and raises more alerts.
A reasonable starting point for most stores.
If you have weekly days off or confirmation passes through more than one stage.
Start wide, then tighten: begin at 72 hours, see the size of the queue, then lower it. Start at 24 hours on a slow operation and you will drown in alerts that are not faults.
How to measure it in your store
- Pick a closed creation period, for example last month.
- Exclude orders in a final state.
- For the rest, find the last time the status changed.
- Count those past your threshold.
- Divide by the period's total orders.
Important: measure from the last status change, not the creation date. An order with a confirmation attempt yesterday has not stopped. An order created a month ago that nobody touched has.
Worked example
| In a final state | 820 |
| Open and moved within 48 hours | 60 |
| Open and stopped for over 48 hours | 120 |
Those 120 are not a confirmed loss, but they are not work in progress either. As long as they sit in the denominator, your delivery rate stays lower than the truth.
The common mistake
Reading this queue as "future orders". An order stopped for weeks is not a deferred request: the customer has probably bought elsewhere or forgotten. Ignoring it makes the "orders in progress" number keep growing without ever turning into money.
FAQ
Should I cancel these orders?
Cancelling cleans the reports but hides the cause. It is more useful to treat them as a queue with an owner and a response time, and record each one's reason when it closes. Those reasons tell you whether the problem is confirmation, stock or the customer.
Is this the same as cart abandonment?
No. Cart abandonment happens before the order exists. Order limbo happens after the customer has actually ordered, which is what makes it more expensive.
Is this a recognized term?
No, it is a term we use at Rabehni. The concept (stopped orders) is known in operations, but it has no common name, which makes it hard to measure and follow up.
Last updated: