The Night Shift That Was Not on Any Schedule

I did inventory reconciliation for a distribution warehouse, which is a boring job that occasionally hands you a genuine ghost story, and then punishes you for looking at it.

The work was simple in shape. The scanners logged everything. Every pallet that moved got a timestamp, a location, and the ID of the handheld unit that scanned it. At the end of each week I matched the physical counts to the digital trail and flagged anything that did not line up. Ninety-five percent of the job was staring at numbers until a wrong one stood up and waved.

The wrong numbers started standing up around 3am. Not every night. Two, maybe three nights a week, there would be activity in the logs during a window when the warehouse was closed. No crew. The building was on a skeleton schedule then, cost cutting, day shift only, doors locked and alarmed from 8pm to 6am. And yet, scattered through those locked hours, scans. Pallets moved from receiving to the racks. Neat. Correct. Exactly the work a competent night crew would do, on nights there was no night crew.

I checked the obvious things first, because I am not interested in ghosts, I am interested in explanations. Clock drift on the scanners. A timezone bug. A batch process dumping delayed timestamps. I ruled them out one by one. The scans were live, individual, human-paced, forty seconds to a couple minutes apart, moving physically through the building in a sensible path. It was the pattern of a person walking the floor doing their job. It was just a person who was not supposed to exist.

The handheld unit doing it was scanner 14. Scanner 14, per the equipment log, had been damaged and pulled from service the previous year. It was supposed to be in a bin in the cage, dead. I went and looked. The bin had a scanner 14 in it, cracked screen, clearly not powering the elegant 3am ballet in my reports. And yet the logs kept coming from scanner 14, from inside the building, on nights the building was empty.

I did what you are supposed to do. I documented it, cleanly, unemotionally, and I took it to my supervisor. I expected interest. Missing product is a problem, but so is product being handled by nobody, and either way the numbers were the numbers. My supervisor looked at my report for a long time and then said we should "loop in" the ops manager. That was the last normal conversation I had there.

Over the next two weeks the temperature changed. My questions stopped getting answers. A meeting got scheduled and then unscheduled. Someone from a regional office I had never dealt with asked me, in a friendly voice that was not friendly, why I was "spending so much time on scanner data outside my scope." I said it was exactly my scope. That, I think, was my mistake.

They let me go on a Thursday. The reason given was a "reduction aligned to operational needs," which is a sentence built specifically to mean nothing you can grab onto. My counts were accurate. My reviews were fine. When I asked, directly, whether this was about the night logs, the HR person paused half a second too long and said, "This is a business decision." I have been in enough of those rooms to know a half second.

I still have my last export, the one I saved to my personal drive the day before my access died. Scanner 14, 3:07am, receiving to rack B12, one pallet, forty-one seconds later the next scan, B14, moving down the aisle in the dark. I do not have a tidy ending. I got walked out. The scans, as far as I know, are still happening. Somebody is still working those nights. I hope they are getting paid better than I was.