> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Late Order Processing Queue, Alibris

> Late Order Processing Queue for Alibris stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained)  •  **Category:** [Marketplace](/nerve-centre/connectors#connectors-by-type)

## At a glance

> Live alert table listing every Alibris order whose `dispatch_due_by` deadline has passed without a confirm-shipment event. Each row is an SLA breach in progress; the longer it stays, the larger the seller-standing damage and the higher the buyer-complaint risk.

|                                        |                                                                                                                                                                                                                                              |
| -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it counts**                     | `COUNT(orders WHERE dispatch_due_by < NOW() AND dispatch_confirmed_at IS NULL AND status NOT IN ('CANCELLED', 'REFUNDED'))`. Maintains a row per order with order ID, buyer, ISBN, deadline, hours overdue, listed price.                    |
| **API endpoint + report**              | Computed locally from the Alibris Inbound Orders feed joined to outbound confirm-shipment events. Recomputes every 4 hours; alert state updated in real time when confirm-shipment event lands.                                              |
| **Severity**                           | **P1**. Each row directly damages [Dispatch SLA Compliance](/nerve-centre/kpi-cards/alibris/dispatch-sla-compliance), drives seller-standing tier, drives search rank, drives revenue.                                                       |
| **What it doesn't count**              | Cancelled, refunded, vacation/holiday-paused orders. Orders that confirmed shipment 5 minutes ago even if 20 minutes late (closed late-dispatch records).                                                                                    |
| **Why separate from Pending Dispatch** | [Pending Dispatch](/nerve-centre/kpi-cards/alibris/pending-dispatch) shows ALL undispatched orders (workload view). This card shows only orders past their deadline (alert view).                                                            |
| **Fees / commission**                  | Not applicable directly. Indirect: SLA breaches cumulate into seller-standing demotion suppressing search rank.                                                                                                                              |
| **Refunds / cancellations**            | Cancelling instead of shipping moves to [Cancellation Rate](/nerve-centre/kpi-cards/alibris/cancellation-rate), but doesn't avoid penalty.                                                                                                   |
| **Currency**                           | Not applicable.                                                                                                                                                                                                                              |
| **Common reasons**                     | (1) Inbound feed lag ate dispatch budget (\~24%); (2) Staff absence / sickness (\~21%); (3) Stockout deferred (\~18%); (4) Confirm-shipment late by feed cadence (\~17%); (5) Volume spike absorbed pick capacity (\~12%); (6) Other (\~8%). |
| **Multi-marketplace overlap**          | Independent per marketplace. Alibris Library Services orders have longer dispatch windows; institutional flag delays the breach trigger.                                                                                                     |
| **Time window**                        | `RT` (refreshed every 4 hours minimum).                                                                                                                                                                                                      |
| **Alert trigger**                      | `any order past dispatch_due_by`.                                                                                                                                                                                                            |
| **Roles**                              | owner, operations.                                                                                                                                                                                                                           |

## Calculation

Calculated automatically from your Alibris 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 US bookseller, 666 orders/month average on Alibris, 2-business-day handling. Snapshot 01 May 26 09:00 UTC.

| Order ID   | Hours overdue | ISBN          | Title                | Buyer  | Listed price | Risk class               |
| ---------- | ------------- | ------------- | -------------------- | ------ | ------------ | ------------------------ |
| AL-1234521 | 1.4h          | 9780393327748 | Beloved (Norton)     | US     | \$12.20      | Low                      |
| AL-1234438 | 5.1h          | 9780486282114 | Common Sense (Dover) | US     | \$7.40       | Low                      |
| AL-1234307 | 9.8h          | 9780521296137 | Cambridge academic   | UK     | \$44.00      | Medium (institutional)   |
| AL-1234189 | 16.2h         | 9780375702709 | Vintage classic      | US     | \$9.80       | Medium                   |
| AL-1234044 | 28.4h         | 9780300100037 | Yale academic        | US-LIB | \$38.00      | High (institutional)     |
| AL-1233897 | 41.0h         | 9780198569060 | Oxford rare          | DE     | \$180.00     | High (rare)              |
| AL-1233762 | 56.8h         | 9780226458045 | Chicago academic     | US-LIB | \$52.00      | Critical (institutional) |

Card reads **7 orders**; alert is firing.

Six things to notice that are specific to Alibris and the book trade:

1. **The 7 late orders represent 1.05% of monthly volume but disproportionately impact SLA.** Each costs \~0.15 percentage points on a 666-order/month seller. SLA at 95% drops to 93.95%.
2. **Triage by hours-overdue, not by order date.** AL-1233762 is 56.8h late and AL-1234521 is 1.4h late; the former needs immediate intervention, the latter just needs to ship today.
3. **The 3 institutional orders (AL-1234307, AL-1234044, AL-1233762) are P0 institutional risk.** Library Services buyers escalate slowly but have long memories; chronic late-dispatch on academic procurement gets you filtered out of library-buyer search.
4. **The 1 rare-book order (AL-1233897, \$180 Oxford) is high reputational impact.** Rare-book buyers leave detailed feedback. Ship today with courier upgrade.
5. **Confirm-shipment-late vs actually-late.** Investigation showed AL-1234438 and AL-1234189 actually shipped on time but the confirm-shipment cron only runs daily at 23:00 EST. Move to hourly.
6. **The \$343 of revenue across 7 orders isn't the headline.** Seller-standing damage (search-rank suppression) far exceeds direct revenue exposure. Library Services exclusion if it persists is a much larger downstream loss.

## Sibling cards merchants should reference together

Late order processing is the active-breach view. Pair with these:

| Card                                                                                                 | Why pair it with Late Order Processing Queue    |
| ---------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
| [Dispatch SLA Compliance](/nerve-centre/kpi-cards/alibris/dispatch-sla-compliance)                   | The aggregate metric this card feeds into.      |
| [Pending Dispatch](/nerve-centre/kpi-cards/alibris/pending-dispatch)                                 | Leading indicator.                              |
| [Avg Time to Process (hrs)](/nerve-centre/kpi-cards/alibris/avg-time-to-process)                     | Distribution view.                              |
| [Inbound Orders File Lag](/nerve-centre/kpi-cards/alibris/inbound-orders-file-lag)                   | Cause check; lag eats budget before order seen. |
| [Last Successful Upload](/nerve-centre/kpi-cards/alibris/last-successful-upload)                     | Outbound-confirm side.                          |
| [Cancellation Rate](/nerve-centre/kpi-cards/alibris/cancellation-rate)                               | Companion budget.                               |
| [Total Revenue](/nerve-centre/kpi-cards/alibris/total-revenue)                                       | Downstream impact.                              |
| [AbeBooks Late Order Processing Queue](/nerve-centre/kpi-cards/abebooks/late-order-processing-queue) | Peer marketplace.                               |

## Reconciling against the vendor's own dashboard

**Where to look in the Alibris seller dashboard:**

1. [**Sellers → Manage Orders → filter by Late**](https://www.alibris.com/sellers/orders). Row-level audit; Alibris highlights overdue rows.
2. [**Sellers → Performance Dashboard**](https://www.alibris.com/sellers/performance). Aggregate seller-standing.

**Why our alert may differ from Alibris's UI:**

| Reason                          | Direction                                          | Why                                                       |
| ------------------------------- | -------------------------------------------------- | --------------------------------------------------------- |
| **Refresh cadence**             | Ours every 4h                                      | Alibris real-time; this card lags up to 4 hours.          |
| **Time zone**                   | Boundary effects                                   | Alibris uses US Pacific Time on .com; connector uses UTC. |
| **Outbound-confirm latency**    | Ours can show late even when Alibris shows shipped | Run cron every 15 minutes.                                |
| **Vacation/holiday handling**   | Ours can show false breaches                       | Vacation-day sync requires connector configuration.       |
| **Cancelled-but-not-yet-acked** | Ours can briefly show cancelled rows               | Up to 30-minute propagation.                              |

**Cross-connector reconciliation:**

| Card                                                                                                | Expected relationship             | What causes legitimate divergence                          |
| --------------------------------------------------------------------------------------------------- | --------------------------------- | ---------------------------------------------------------- |
| [`abebooks.ab_alert_late_processing`](/nerve-centre/kpi-cards/abebooks/late-order-processing-queue) | Same fulfilment, different queue. | Each marketplace sets its own dispatch\_due\_by.           |
| [`amazon.amzn_alert_late_processing`](/nerve-centre/amazon/amzn_alert_late_processing)              | Strictest peer.                   | Amazon's clock starts at payment; Alibris at confirmation. |
| [`shopify.unfulfilled_orders`](/nerve-centre/kpi-cards/shopify/unfulfilled-orders)                  | Different model.                  | DTC has no third-party SLA threshold.                      |

***

<details>
  <summary><em>Marketplace-peer documentation cross-reference</em></summary>

  * [`abebooks.ab_alert_late_processing`](/nerve-centre/kpi-cards/abebooks/late-order-processing-queue)
  * [`amazon.amzn_alert_late_processing`](/nerve-centre/amazon/amzn_alert_late_processing)
</details>

## Known limitations / merchant FAQs

**The alert just fired with 7 orders. What do I do in the next hour?**
(1) Sort by hours-overdue descending; address worst breaches first. (2) Spot-check institutional / rare orders; ship today with courier upgrade. (3) Identify cause per breach; don't bulk-cancel.

**Why does Alibris penalise me here when the book actually shipped on time but my confirm-shipment was late?**
Alibris can only see what your outbound feed tells them. Run outbound-confirm cron every 15 minutes minimum.

**Multi-marketplace, can I avoid this by selling exclusively on Alibris?**
Single-marketplace concentration carries 3 to 5x the platform-failure risk. Operational discipline (tight cron, daily ops review) is the right answer, not channel concentration.

**Listing-quality / Buy Box impact, recovery time after a breach cluster?**
Each breach hits SLA for 30 days. If cumulative drops below 95%, search-rank demotion within 24h; demotion lifts 7 to 14 days after returning above. Total recovery 30 to 45 days.

**Inventory-sync lag, false positives?**
Yes. Confirm-shipment cron schedule mismatched with warehouse pack times produces false-late readings. Run cron every 15 minutes during business hours.

**ISBN match quality, can it cause late dispatches?**
Indirectly. Wrong-ISBN-against-physical-book causes warehouse delays at picking.

**Rare books vs commodity, breach impact difference?**
Per-breach financial weight 30 to 80x higher on rare. ALWAYS triage rare-book breaches first.

**When does the card auto-clear?**
Each row clears on confirm-shipment event. Whole card empty when no row is past dispatch\_due\_by.

**Is there ever a reason to cancel rather than ship a late order?**
Yes if book on inspection is materially worse than catalogued. Use *Out-of-stock* reason on Alibris.

**Alibris-specific: Library Services / institutional buyers, special handling?**
Yes. Institutional cohort has long memories; chronic late-dispatch on academic procurement risks filtered-out from library-buyer search filters. Treat institutional orders carefully even if their dispatch window is longer.

***

### Tracked live in Vortex IQ Nerve Centre

*Late Order Processing Queue* is one of hundreds of KPI pulses Vortex IQ tracks across Alibris 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.
