Total Failed Fulfillments Metric
Essential knowledge
Intended Audience:
Business User
Author:
Movyn John
Changed on:
19 Jan 2026
Overview
Learn about the Total Failed Fulfillments Metric in Fluent AnalyticsKey points
- Failed fulfillments require manual intervention and delay delivery
- May indicate inventory accuracy, system, or training issues
- Different failure types require different corrective actions
What it measures
Number of fulfillments with all requested items missing or unavailable.
When to use this metric
- Identify systemic operational problems
- Monitor the impact of process changes on failure rates
- Assess location-specific quality issues
- Track progress on operational improvement initiatives
How to interpret
- Good performance: Failed fulfillments should be a low %
- Potential issues: Increasing failure rates indicate process or system problems
- Benchmark guidance: Should trend toward zero; patterns need root cause analysis
Technical details
Domain:`fulfilment`Formula: COUNT(fulfillments) where status = {STATUS_REJECTED} within the selected time periodReference Filter Parameters:`from_location.ref`: Filters the metric to fulfillments assigned to the selected location`fulfilment.created_date`: Filters the metric to fulfillments created within the selected time period`fulfilment.status`: STATUS_REJECTED - Status definitions for failed fulfillments (default: REJECTED)`retailer.ref`: Filters the metric to fulfillments from the selected retailer
