Skip to main content
Metrics type: Key Metrics • Category: Marketplace
Triggered when /upload/listings has no confirmed ack in 48h, feed is blind, all listing changes stuck.

​
At a glance

P1 alert. Fires when the Alibris outbound listings feed (/upload/listings) has not received a confirmed ack from Alibris in 48 hours. While active, every listing edit is stuck in a queue with no path to Alibris. The catalogue is frozen on the last successful cycle’s state.

​
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, 32,100 active Alibris listings, 4-hourly outbound feed cycle. Incident timeline 28 Apr 26 to 01 May 26. Cumulative impact during 56-hour outage: Six things to notice that are specific to Alibris and the Pure-FTPd feed model:
  1. 48 hours is the standard threshold but tune to your cycle. 4-hourly cycle means a 12 or 24h alert threshold is more appropriate.
  2. Alibris’s Pure-FTPd credentials don’t rotate on a schedule but partner-side network drops happen. Subscribe to Alibris developer notifications.
  3. Stockout cancellation cascade is the second-order damage. During the 56h outage, 340 books sold elsewhere were still listed as available on Alibris.
  4. The 30 to 90 day reputational tail. A 9-cancellation cluster sits in the 30D average for the next 30 days; expect “at risk” seller-standing tile through early Jun 26.
  5. The 9,200 queued repricer updates. Letting them all fire post-outage causes a one-day price-change spike; phased re-upload (1,000/hour) is gentler.
  6. Library Services / institutional buyers may be MORE forgiving than retail. Net-30 procurement cycles mean the institutional cohort doesn’t notice a 2-day outage; retail buyers do.

​
Sibling cards merchants should reference together

Feed cycle failure is the P1 operational alert. Pair with these:

​
Reconciling against the vendor’s own dashboard

Where to look in the Alibris seller dashboard: Alibris’s seller dashboard does NOT publish a feed-health view. Three indirect views help during an active alert:
  1. Sellers → Inventory → Upload History. Last N upload attempts; if most recent is >48h old, Alibris confirms it has not received your files.
  2. Sellers → Inventory → Manage. Spot-check a recently-edited listing; if Alibris shows OLD state, change hasn’t propagated.
  3. Alibris Developer Status Page (intermittent service).
Why our alert may differ from Alibris’s observations: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

The alert just fired. Next 30 minutes? (1) Test Pure-FTPd auth manually with stored credentials. (2) Check outbox staging directory for queued files >48h old. (3) Open Alibris developer status page. Alert cleared but cancellation rate still climbing. Why? Operational damage takes 7 to 30 days to age out of the rolling 30D window. Stockout cancellations during outage stay in the rolling average. Multi-marketplace, can a single network outage trip both Alibris and AbeBooks alerts? Yes if cause is at merchant data centre. Marketplace-side outages affect only one. Listing-quality / Buy Box, second-order damage? Cancellation cascade is primary. Beyond that, Listing Quality Score sees no positive signals during outage and decays slightly. Inventory-sync lag during outage, what’s the right behaviour? (a) Conservative: manually mark all Alibris listings out-of-stock. (b) Permissive: leave live, accept stockout cancellations. Most under-1,000-orders/day sellers use (b). ISBN match quality, can it cause feed failures? Indirectly. Severely malformed ISBN can cause Alibris to silently reject the entire file. Why doesn’t Alibris email me when my feed breaks? Alibris does send weekly batch emails; cadence is 7+ days. This card’s 48h threshold catches issues much faster. Rare books vs commodity, outage impact difference? Commodity bears most operational damage (high volume = many stockout cancellations). Rare books rarely produce same-day stockouts during 56h outages. When does the alert turn off vs when do I act? Alert auto-clears on next ack. But “act” until you’ve drained the outbox queue, confirmed listing states via spot-check, and proactively contacted affected buyers from the outage. Alibris-specific: Library Services / institutional cohort, more or less affected by outages? Less. Net-30 procurement cycles mean institutional buyers don’t browse daily; a 2 to 3 day outage is invisible to them. Retail buyers do browse daily; they bear most reputational damage.

​
Tracked live in Vortex IQ Nerve Centre

Feed Cycle Failure 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 or book a demo to see this metric running on your own data.