Skip to main content
Card class: 🦸 Hero * Category: Fulfilment & Operations * Chart: gauge

​
At a glance

COUNT(orders WHERE current_state IN (4,5)) / COUNT(orders in paid states 2,3,4,5,9,11) over date_add window.
What it measuresCOUNT(orders WHERE current_state IN (4,5)) / COUNT(orders in paid states 2,3,4,5,9,11) over date_add window.
Formatpercent
Time window30D vsP
Alert trigger<92% (industry baseline), driven by sentiment_key: fulfillment_rate
Sensitivity bandhigher is better - good at/above 95, bad at/below 90
Rolesowner, operations
Data typeAPI-derived

​
Calculation

COUNT(orders WHERE current_state IN (4,5)) / COUNT(orders in paid states 2,3,4,5,9,11) over date_add window.
PrestaShop order classification uses the order-state machine: paid = current_state in (2 Payment accepted, 3 Processing, 4 Shipped, 5 Delivered, 9 Backorder paid, 11 Remote payment accepted); shipped/fulfilled = (4, 5); refunded = (7, 15); cancelled = (6); payment error = (8). Read live from the PrestaShop Webservice API and snapshotted nightly into the Nerve Centre KPI store.

​
Why it matters

Fulfilment Rate is part of the PrestaShop executive pulse in Vortex IQ Nerve Centre. Vortex Mind investigates automatically when this card breaches its sensitivity band, and Ask Viq can explain the movement in plain English with a citation back to this card.