Your Dashboard Is Green—So Why Are Customers Still Chasing Orders?

The morning dashboard looks reassuring. Warehouse productivity is on target. Orders are leaving on time. Carrier performance is within tolerance.

Then the customer service team starts receiving calls.

“Where is our order?”

“Will the missing items arrive today?”

“Why were we told it had shipped when the carrier hasn’t collected it?”

These calls do not automatically mean the dashboard is wrong. They may mean it answers a different question from the one the customer is asking.

The dashboard asks: Did each part of the operation meet its target?

The customer asks: Will I receive what you promised, when I need it?

Understanding that gap is a useful starting point for improving delivery reliability.

A series of successful steps can still produce a disappointing order

Consider an illustrative example.

A customer orders ten product lines for delivery on Thursday, ahead of a planned maintenance shutdown. The warehouse dispatches nine lines on Wednesday. The tenth is awaiting replenishment.

The warehouse records the available goods as dispatched on time. The carrier delivers the nine lines within its agreed transit time. The remaining item arrives on Friday.

Depending on how the measures are defined, both the warehouse and carrier could meet their targets. Yet the customer could still be unable to complete Thursday’s planned work.

The missing line may be a small part of the order’s value, but a critical part of its purpose.

This is why reviewing individual measures is only part of the task. We also need to understand how those measures connect to the customer commitment.

Five places where the picture can become misleading

1. The clock starts after the customer has already been waiting

A dispatch measure might start when an order is released to the warehouse. That can be useful for understanding warehouse performance, but it may exclude time spent waiting for stock, approval or order clarification.

If the customer’s delivery commitment was made earlier, that waiting time still matters.

The question to ask is: Which event starts the clock, and does it reflect the promise we made?

2. The measure counts the wrong unit

An operation might report performance by order line, shipment, pallet or complete order.

Each view has a purpose. They can also tell different stories.

Delivering most lines on time may produce a strong line-level result while leaving several customers with incomplete orders. Conversely, a complete-order measure can hide which products repeatedly cause failures.

The aim is to use the measures together and understand what each one reveals.

3. A revised date replaces the original promise

Updating a delivery date helps teams plan. Problems arise when the latest date quietly becomes the only date used to assess performance.

An order can then appear on time against a revised commitment even though the customer has experienced a delay.

Keep the original commitment, subsequent revisions and the reasons for change visible. A customer-requested change should also be distinguishable from a delay caused by the operation.

4. “Dispatched” means different things to different teams

Does dispatched mean picked, packed, labelled, loaded or physically collected?

A completed warehouse transaction may not prove that goods have entered the carrier’s network. Similarly, an estimated arrival time is different from confirmed delivery.

Clear event definitions help teams avoid treating an internal status as evidence of a completed handover.

5. The average hides a recurring problem

Overall performance can remain within target while a particular customer, product group, route or delivery window performs poorly.

That makes the headline useful for direction, but insufficient for diagnosis.

Breaking down the result can reveal whether the same customers are repeatedly absorbing the disruption.

Start with a customer commitment you can trace

Before adding another dashboard, select a manageable sample of orders that generated customer chasing or missed commitments.

For each order, reconstruct the journey:

• What did we agree to supply, and by when?
• Was that commitment feasible when it was made?
• When did stock, information or capacity become a constraint?
• When was the risk first visible?
• When did someone take action?
• What did the customer actually receive, and when?
• What information did the customer receive along the way?

Include some successful orders for comparison. They can help distinguish a recurring weakness from an isolated event.

The purpose is to find where the commitment became vulnerable and whether the operation had a practical opportunity to respond.

Connect the promise, the risk and the response

A useful operational view brings together three things.

The promise: what the customer expects, including quantities, completeness and delivery timing.

The risk: what could prevent that promise from being met, supported by sufficiently current information.

The response: who needs to decide or act, by when, and what options are available.

For example, a stock shortage becomes more useful as an operational signal when it is connected to affected orders, their delivery commitments, replenishment timing and the person responsible for the next decision.

An alert that says “stock is low” leaves much of the work to the user. A view that identifies a threatened customer commitment gives the team a clearer basis for prioritisation.

That still requires judgement. Alternatives might include expediting replenishment, agreeing a substitution, changing an allocation or discussing a partial delivery with the customer. The right response depends on feasibility, cost and the customer’s needs.

Treat customer chasing as evidence

Customer enquiries can reveal gaps that operational measures miss.

A delivery may arrive on time, yet the customer may still chase because tracking is unavailable, messages conflict or nobody has confirmed a revised arrangement.

It helps to distinguish between:

• A delivery commitment that was missed.
• A commitment that became uncertain.
• A delivery that succeeded but was poorly communicated.

These situations may need different improvements.

Reducing enquiry volumes alone is a weak definition of success. The aim is to reduce the uncertainty and failures that cause customers to chase, while keeping it easy for them to contact you.

Test a focused improvement before widening the scope

Choose one customer group, product family or delivery flow where the issue is visible and the team can influence the outcome.

Agree the definitions and establish a baseline. Measures might include:

• Delivery performance against the original customer commitment.
• Order completeness where it matters to the customer.
• Customer chasing contacts relative to order volumes.
• Time between identifying a delivery risk and making a decision.
• Additional transport, handling or expediting costs.

Check whether an improvement in one measure creates a problem elsewhere. Sending more partial deliveries, for example, may bring some goods forward while increasing cost and disruption for the customer.

Use the pilot to test whether earlier visibility and clearer ownership lead to better decisions. More alerts are not, by themselves, evidence of improvement.

A better question for the next performance review

When a dashboard is green but customers are still chasing, it is worth asking:

Can we trace our reported performance back to the promise each customer received?

That question can expose gaps in definitions, handovers, information and accountability. It can also show where existing measures are useful and where an additional view is needed.

The value of a dashboard comes from the decisions and actions it supports—and whether those actions improve the customer’s experience.