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.