The live count of orders sitting in a Pending status, the queue of sales that have started but not yet confirmed payment or received a first action.
At a glance
A Pending order in OpenCart is one that exists but has not yet cleared its first gate, typically awaiting payment confirmation from an offline method (bank transfer, cheque, cash on delivery) or a callback from an online gateway. A small, stable backlog is normal. A spike usually means a payment callback is failing, a gateway is down, or an offline-payment queue has been left unattended. This card watches the level so you can tell “business as usual” from “money is stuck”.
| What it counts | The number of orders whose current status is Pending. |
| Order source | Order records live in oc_order; the current status is held there and the full status history in oc_order_status / the order-history table. |
| What “Pending” means | An order awaiting payment confirmation or a first action. Offline methods (bank transfer, cheque, COD) sit here until the merchant confirms receipt; online gateways sit here until a success callback arrives. |
| Missing-status orders | OpenCart also has an order-status of 0 (incomplete / abandoned checkout) that is distinct from Pending. Those are not counted here; see Failed Orders (24h). |
| Currency / value | This card counts orders, not money. OpenCart stores order totals and tax separately and supports multiple currencies, so a value view is handled by Revenue at Risk (live). |
| Multi-store | Orders carry a store_id. By default this card counts Pending orders across every storefront on the install. |
| Time window | RT (live snapshot) |
| Alert trigger | > 2x the 30-day average |
| Roles | owner, operations |
Calculation
Worked example
A German homeware store on OpenCart 4.x taking both card payments (online gateway) and bank transfer (offline). Its 30-day average Pending backlog is about 18 orders at any moment. The snapshot is taken at 10:00 on 21 Mar 26.| State | Pending orders | Notes |
|---|---|---|
| Awaiting bank transfer (normal) | 16 | Customers who chose transfer, payment not yet received |
| Awaiting card-gateway callback (normal) | 3 | Should clear within minutes |
| Card-gateway callbacks failing since 08:30 | 27 | Stuck, callback URL returning errors |
| Pending Orders (this card) | 46 | 2.5x the 30-day average of 18 |
- 46 against a baseline of 18 trips the alert. The card fires at more than twice the 30-day average, and 46 is 2.5x. Without the baseline, 46 might look like a busy morning; against history it clearly is not.
- The cause is a broken callback, not slow customers. Sixteen bank-transfer orders pending is normal trading. The 27 card orders stuck since 08:30 are the anomaly: the gateway’s success callback is failing, so paid orders never advance out of Pending. Those customers were charged but their orders look unconfirmed.
- Offline and online pending need different handling. Bank-transfer pending clears when the merchant reconciles the bank feed and confirms receipt. Card-callback pending clears when the integration is fixed and the callbacks replay. Treating both as one queue hides the real problem.
- Money is quietly stuck. Every card order trapped in Pending is cash taken but unfulfilled. The companion Revenue at Risk (live) puts a currency figure on the pile so the owner can see the exposure, not just the count.
Sibling cards merchants should reference together
| Card | Why pair it with Pending Orders |
|---|---|
| Processing Orders | The next stage in the lifecycle. Pending that never becomes Processing is the warning sign. |
| Order Processing Backlog | The aggregate view of unfinished work across statuses; Pending is one feeder into it. |
| Failed Orders (24h) | Pending that fails payment outright lands here. A rising failure count drains the Pending queue the wrong way. |
| Revenue at Risk (live) | Puts a dollar value on orders stuck in Pending too long. |
| Order Status Distribution | Shows Pending as a share of all statuses, so you can see whether the queue is proportionate. |
| Platform Error Spike or Extension Conflict | A broken payment callback often shows up here too, explaining a Pending spike. |
Reconciling against OpenCart
Where to look in the OpenCart admin: Sales → Orders, then filter the Order Status column to “Pending”, gives you the same queue this card counts. Each order’s history tab (backed byoc_order_status and the order-history table) shows when and why it entered Pending. Reports → Sales → Orders can summarise counts by status over a period. For payment-method context, System → Settings (and each payment extension’s configuration) tells you which methods land orders in Pending by design.
OpenCart admin views that look like the same number but aren’t:
- Sales → Orders with no status filter counts every order, not just Pending.
- The Dashboard “orders” tile is usually a recent-period count, not a live Pending level.
- Orders at status
0(incomplete / missing) are abandoned or never-confirmed checkouts, a different bucket from Pending. They appear only when you enable “missing orders” visibility.
| Reason | Direction of divergence |
|---|---|
| Timezone. Vortex IQ reads on a UTC cadence; OpenCart timestamps follow the store timezone. A snapshot taken mid-callback can differ by a sync interval. | Cosmetic timing shift |
Multi-store. Orders carry a store_id; this card counts across all storefronts unless filtered. An admin filtered to one store will show fewer. | Card higher than a single-store admin view |
| Status-name customisation. OpenCart lets you rename or add statuses. If “Pending” has been renamed or a custom pre-payment status added, the mapping may need adjusting. | Either direction |
Incomplete vs Pending. Status 0 (incomplete) is excluded here but can appear in some admin lists. | Card lower than a list that includes incompletes |
| API / DB sync lag. An order that just entered Pending may not yet be reflected. | Self-resolves at next sync |
Known limitations / merchant FAQs
Is a Pending order the same as an abandoned cart? No. An abandoned or never-confirmed checkout sits at OpenCart’s status0 (incomplete / missing), which is a separate bucket. A Pending order is a real order awaiting payment confirmation or a first action. See Failed Orders (24h) for the failure side.
Why is my Pending count always non-zero?
If you accept offline payment methods (bank transfer, cheque, cash on delivery), orders legitimately sit in Pending until you confirm receipt. A steady, modest backlog is normal. The alert keys off a sudden jump above twice the 30-day average, not the mere presence of pending orders.
Pending spiked but my sales did not, what happened?
Most often a payment-gateway callback is failing, so paid card orders never advance out of Pending. Check the gateway’s own dashboard: if it shows successful charges that OpenCart still marks Pending, the callback URL or integration is the culprit.
I renamed my order statuses, will this still work?
OpenCart lets you rename and add statuses freely. The card maps to the Pending status as configured for your install; if you have renamed it or introduced a custom pre-payment status, the mapping may need a one-time adjustment so the right status is counted.
Does this count orders across all my storefronts?
Yes by default. Orders carry a store_id, and the card sums Pending across every storefront on the install unless you filter to one store. An admin view filtered to a single store will naturally show fewer.
How do I clear a stuck Pending queue?
For offline payments, reconcile against your bank feed and confirm receipt to advance each order. For online payments, fix the failing callback and replay or manually advance the affected orders. Once the underlying status changes in oc_order, the count drops at the next sync.
Should I worry about the dollar value, not just the count?
Yes, and this card deliberately counts orders, not money. Pair it with Revenue at Risk (live), which puts a currency figure on orders that have been stuck too long.