Does HublerX calculate OTIF the same way our retail customers do?

HublerX can be configured to match the OTIF definition used by each customer — some measure on requested delivery date, others on confirmed delivery date; some measure by order line, others by shipment. The OTIF calculation is set per customer so the HublerX score matches what the customer reports.

How does HublerX know a delivery is at risk before it misses?

HublerX tracks the fulfilment timeline for every confirmed order — the work order completion time, quality clearance duration, picking time, and truck transit time. When any step falls behind the timeline required to meet the delivery window, HublerX calculates the projected delivery time and flags the risk if it exceeds the window.

Can HublerX integrate with customer portals to receive OTIF scorecards?

Where customer portals provide OTIF scorecards via EDI or API — as Reliance Retail, D-Mart, and major modern trade customers do — HublerX can ingest the scorecard and reconcile it against the internal fulfilment record. Discrepancies between the customer's OTIF score and the internal record are surfaced for review.

How is the root cause categorisation done — manually or automatically?

HublerX assigns the root cause category automatically based on which step in the fulfilment chain caused the delay — if a work order was late, the root cause is production; if a quality hold was raised, the root cause is quality; if the truck was delayed, the root cause is logistics. The automatic categorisation covers the majority of cases; coordinators can override the category where the automated assignment does not reflect the actual cause.

OTIF Improvement Workflow

HublerX tracks every confirmed customer order from production schedule to delivery confirmation — flagging OTIF risks before the delivery window closes and identifying the root cause of every miss so the next delivery does not repeat it.