FULFILMENT COMMAND CENTRE
A clearer view. A better next move.
Shipment performance, service risk and the next best operational review.
SOURCE SNAPSHOT
16 Sept 2026, 17:40 (source clock)
ABFRL / ABFR | 14,510 matched shipments
Upload operational data
CSV order-detail exports are validated and activated in this workspace.
Choose or drop a CSV dataset
Required fields include Tracking ID, Client Code, Shipment Current Status, Shipment Registered Date and Last Update Time. Buyer PII is excluded from the analytical model.
The active dashboard recalculates after a successful upload. The source file itself is not stored by the standalone HTML.
Source lineage
Final customer POC order-detail CSV
- File
- OrderDetails091620261742.csv
- Source type
- Order Details CSV
- Total / ABFR rows
- 14,510 / 14,510
- Current selection
- 5,413 rows
- Snapshot freeze
- 16 Sep 2026, 17:40
- Registered-date range
- 15 Aug 2026 to 15 Sep 2026
- CSV SHA-256
- ea9081ad5575d6be9b7d3d57409aec7ab11938d4fe5a8b595b3d4f57
- Persistence
- Local browser storage (no server)
Buyer names, contact numbers and street addresses are excluded from the embedded POC dataset.
Data coverage in the current selection
Gaps remain visible rather than silently filled
- Missing EDD
- 479 / 5,413
- Invalid EDD chronology
- 0 / 5,413
- Invalid last-event chronology
- 0 / 5,413
- No configured shipment zone
- 5,413 / 5,413
- Any tracked data-quality issue
- 480 / 5,413
A date is excluded when its chronology is invalid. EDD and completion denominators therefore differ from the total number of delivered shipments. No latitude, longitude, zone or completion timestamp is invented.
Workbook rule configuration
Values below are the supplied metric thresholds. They are not a carrier contract.
| Zone | Event (h) | TAT (d) |
|---|---|---|
| Local | 48 | 3 |
| Zonal | 48 | 4 |
| National | 72 | 6 |
| Special (SZ) | 72 | 8 |
| ROI | 72 | 8 |
Unknown zone: confirmed only beyond the largest zone threshold. Intermediate ages are conditional. Rule version v1.
Snapshot clock / aging scenario
Age the unchanged snapshot forward; do not invent past statuses.
The source timezone is not supplied. Values are displayed in a fixed wall-clock convention. A later date changes aging rules only. It is not a forecast and does not update any shipment status.
Service targets, entered for demonstration
No service-specific targets have been configured.
Configure a post-code lane zone
Explicit demo assignments only. Use a verified business zone master before production.
0 assigned lane(s). 0% current-scope row coverage. Local = same city; Zonal = same state; Special = NE, Kerala, J&K and HP; National = across states; ROI = remote leftovers. The supplied Definitions sheet does not resolve precedence or provide the master needed to assign these.
Requirement-to-demo coverage
Mapped to the supplied metrics worksheet; qualification is part of the metric contract.
| REQUIREMENT | SOURCE | IMPLEMENTATION | QUALIFICATION |
|---|---|---|---|
| Shipment EDD breach | Final CSV | Open forward EDD comparison | Calculated |
| Event-based pendency | Final CSV | 48 / 72 h; unclassified zones use conservative + review queues | Zone coverage required |
| TAT-based pendency | Final CSV | 3 / 4 / 6 / 8 d; registration default, pickup optional | Clock assumption |
| Courier EDD compliance | Final CSV | Delivered Date <= EDD / eligible delivered | Actual delivery date |
| Extent of breach | Final CSV | Shipment-weighted mean days late among late delivered | Actual delivery date |
| Delivered % | Final CSV | Current DELIVERED / cohort shipments, direct Payment Mode | Calculated |
| RTO % | Final CSV | Observed return statuses | Calculated |
| Geographic analysis | Final CSV | Supplied city/state plus configured lane zone | Source plus configuration |
| Service analysis | Final CSV | Assigned and requested service fields | Source fields |
| Undelivered reasons | Final CSV | Controlled categories from failure-reason fields | Observed, not causal |
| Attempt counts / NDR | Final CSV | One-attempt and two-plus attempted-undelivered cohorts | Calculated |
| Forward pendency | Final CSV | Open forward status queue | Calculated |
| RTO >10 d | Final CSV | Open RTO from supplied RTO Date | Calculated |
Calculation dictionary
Every KPI and natural-language answer can be traced to these definitions.
Shipments
Count of source shipment rows in the active scope.
Fields: awbNumber
Delivered shipments
Shipments whose current recorded status is DELIVERED.
Calculation: Count of in-scope rows with currentStatus = DELIVERED.
Fields: currentStatus
Delivered %
Share of in-scope shipment rows currently recorded as delivered.
Calculation: Delivered shipment count ÷ eligible cohort shipment count × 100.
Fields: currentStatus, Payment Mode
Qualification: Uses the current recorded status and the configured cohort. It does not represent final courier delivery compliance.
Open EDD breaches
Open forward shipments whose expected delivery date is before the active as-of date.
Calculation: Open forward shipments with a valid EDD earlier than the active as-of clock.
Fields: currentStatus, EDD, registeredDate
Qualification: Rows with a missing or invalid EDD are excluded from the date comparison and remain visible in data quality.
EDD compliance % (proxy)
On-time share among eligible delivered shipments with valid EDD chronology.
Calculation: Delivered on or before EDD ÷ eligible delivered shipments × 100.
Fields: deliveredDate, EDD, currentStatus
Qualification: A proxy only; use the actual delivery date and eligible delivered denominator. Invalid chronology is excluded.
Extent of breach
Average days late among delivered shipments that arrived after their expected delivery date.
Calculation: Shipment-weighted mean of deliveredDate − EDD for late delivered shipments.
Fields: deliveredDate, EDD
Event-based pendency
Open shipments with no recorded event inside the applicable zone threshold.
Calculation: Elapsed time since last recorded event exceeds the configured 48 / 72-hour threshold.
Fields: lastEventTime, originPostalCode, destinationPostalCode, configuredLaneZone
Qualification: A configured lane zone is needed for exact classification. Unmapped lanes stay in conservative review queues.
TAT-based pendency
Open shipments older than the configured transit-time threshold.
Calculation: Shipment age exceeds the configured 3 / 4 / 6 / 8-day zone and service threshold.
Fields: registeredDate, pickupDate, currentStatus, configuredLaneZone
Qualification: Registration date is the default clock; pickup-based age is optional when supplied.
Courier EDD compliance
Measures on-time delivery performance for eligible shipments grouped by courier.
Calculation: Delivered on or before EDD ÷ eligible delivered shipments, grouped by courier.
Fields: courier, deliveredDate, EDD, currentStatus
Qualification: Requires actual delivery dates and valid EDD chronology.
RTO %
Share of in-scope shipments with an observed return-to-origin status.
Calculation: Observed RTO shipments ÷ eligible cohort shipments × 100.
Fields: currentStatus
Undelivered reasons
Counts observed reason categories for undelivered shipments.
Fields: currentStatus, failureReason
Qualification: Reasons are reported as observed source values; they are not treated as causal findings.
Attempt counts / NDR
Groups attempted-undelivered shipments into one-attempt and two-or-more attempt cohorts.
Fields: attemptCount, currentStatus
Qualification: Requires a supplied attempt count or equivalent source evidence.
Geographic analysis
Groups shipment performance by supplied geography and any explicitly configured lane zone.
Fields: originCity, originState, destinationCity, destinationState, configuredLaneZone
Qualification: No postal geography or lane zone is inferred when the source or configuration is missing.
Service analysis
Compares shipment outcomes by requested and assigned service values.
Fields: requestedService, assignedService, courier
- The file is a current shipment snapshot, not a complete historical event stream.
- Tracking ID and Client Reference ID are unique shipment identifiers in this snapshot.
- Actual Delivered Date is used for delivered TAT and EDD compliance when present.
- RTO Date is used as the return-cycle start when present.
- Payment Mode is sourced directly; COD amount is not used to infer prepaid shipments.
- Buyer names, contact numbers and street addresses are not embedded in the demo dataset.
- No carrier updates, refunds, reallocations or source-system mutations are executed.