Six Tickets Closed on Time. Why Did Dispatch Keep Stopping?

Six warehouse tickets closed on time. The same fault kept stopping dispatch. See how first-pass scanning can reveal trouble while the shift can still act.

At Friday’s weekly meeting, the support manager reported that all six warehouse tickets had been closed within the agreed time.

The warehouse manager brought up what had happened the day before. Two people had spent part of the afternoon relabeling every carton in a shipment by hand so it would be ready when the carrier arrived.

“Which ticket was that?” the support manager asked.

The warehouse manager pulled up a ticket titled “Dispatch stopped.” Two others were called “Printer problem” and “Barcode won’t scan.” The tickets had come from different shifts and been filed under different categories.

What did the six tickets have in common?

The support manager reviewed the technicians’ notes while the warehouse manager checked which shipments had been affected. All six were for the same customer. Every time, the cartons had stopped at the same scanner.

One detail kept coming up in the technicians’ notes. Whenever the warehouse printed labels using the previous template, the scanner could read them. That got the shipment moving again. The new template was still available, so another shift would select it for the next shipment to that customer.

What happened on Thursday afternoon?

The warehouse manager described how the stoppage began. The scanner couldn’t read the label on the first carton. The operator tried again, then moved on to the next carton. That label failed too. While the operator checked the scanner, the packing team kept labeling the rest of the shipment.

Support switched back to the previous template, and the scanner read the test label. By then, every carton had been labeled. Two people dropped the work they had planned for that shift, relabeled the cartons, and sent them back through the scanner.

The carrier collected the shipment on time. In the dispatch report, it showed up as a shipment that had gone out as planned.

When could the shift still do something about it?

As the managers went through what had happened, they saw that the operator had spotted the problem while the packing team was still applying labels. When the second label failed, the operator could have alerted the team. They could have paused labeling that shipment, checked a test label, and then carried on with the remaining cartons.

That gave them a specific place to measure performance. Of all the cartons that reach the scanner, how many pass on the first attempt? Count each carton once, however many times the operator scans it.

The warehouse manager can track that percentage by shift. For the operator, what matters in the moment is the pattern. If several cartons from the same shipment fail in succession, there’s still time to tell the packing team before the rest are labeled.

What happened to the template?

The support manager linked all six tickets to a single problem record and assigned it to the team that maintained the templates. The team took the new template out of use while they investigated, so every shift worked with the previous version.

When they compared the two templates, they found that an element on the new label was too close to the barcode. After the layout was corrected, the warehouse team printed a test batch and ran the labels through the same scanner. Only then did they put the corrected template back into use.

Where is the pulse point in your process?

At Friday’s meeting, the managers had two accurate figures. All six tickets had been closed on time, and Thursday’s shipment had gone out as planned. The first two cartons that failed to scan had told the shift something neither report captured. There was still time to stop labeling and avoid doing the whole batch twice.

In Step 7 — Pulse Points, From Chaos to Systems looks at where in a process you can see performance slipping while there’s still time to act. Pick a deadline your team regularly meets and trace the work leading up to it. Where do people first see that the work is going off track, and what can they still change at that point?

Explore From Chaos to Systems and the Business Systems Workbook