Must read stuff · No. 08
The label printer that only prints at night
A shipping label printer that jams every morning and clears itself by evening taught me something about maintenance contracts, error logs, and the difference between a machine that is broken and a machine that is telling you something you have not scheduled time to hear.

The label printer at the back of the warehouse jams at 8:40 every morning. Not 8:35, not 8:50. The first wave of pickers comes through at 8:30, the orders print in a burst, and somewhere around the fortieth label the paper feed grabs the backing sheet and folds it into an accordion. By 9:15 it has cleared itself. By the afternoon it prints clean. The warehouse manager has a name for it. He calls it the morning mood.
I was there on a Tuesday in October to look at something else entirely, a barcode scanner that had started double-reading, and I ended up standing in front of the printer for twenty minutes because the manager wanted me to see it happen. He did not want me to fix it. He wanted a witness.
What the log says
The printer keeps an error log. I pulled it. Forty-one jams in the last thirty days, all between 8:32 and 9:10, all on the same feed path, all cleared by a retry. The log calls them paper feed errors. It does not call them morning errors. It has no field for time of day, because time of day is not a printer problem.
Here is the mechanism underneath. The warehouse is unheated overnight. The paper stock sits on a shelf against the north wall, and by morning the backing sheet has absorbed enough moisture from the cold air that it curls slightly at the edge. The printer’s feed rollers are a little worn, and a slightly curled sheet is enough to make them grab two layers instead of one. By mid-morning the building has warmed, the paper has relaxed, and the same rollers handle the same stock without complaint.
The printer is not broken. The printer is reporting a condition in the room. The log has no way to say that, so it says paper feed error, forty-one times, and the maintenance contract renews on schedule because forty-one paper feed errors is within the tolerance the vendor wrote into the agreement.
The good side of the log
I want to be fair to the log. Before the log, this would have been a story the manager told at lunch. The printer is moody in the morning. Nobody would have counted the jams. Nobody would have noticed they all happened in the same forty-minute window. The log turned a complaint into a pattern, and a pattern is the beginning of a fix.
The log also protects the manager. When the vendor’s technician came out in September and found nothing wrong, the manager had forty-one entries to show him. The entries did not explain the jams, but they proved the jams were real. That is not nothing. A person who says the printer is moody in the morning gets a shrug. A person who says forty-one jams between 8:32 and 9:10 gets a service visit.
The cost of a field that does not exist
The cost is that the log records the symptom and not the cause, and the contract is written against the symptom. The vendor’s agreement says the printer is serviced when the error rate exceeds a threshold. Forty-one jams in a month is under the threshold. The printer is, by the terms of the contract, working.
So the manager does what people do when the system will not hear them. He works around it. He has the morning pickers start at 8:45 instead of 8:30. He has the paper stock moved to a shelf on the south wall, away from the cold. The jams drop to maybe eight a month. The log still says paper feed error. The contract still renews. The fix cost him a shelf and fifteen minutes of schedule, and it worked, and no one wrote it down anywhere the vendor will ever see.
I have done this myself. I have moved a server to a different room because the air conditioning cycled at the wrong time, and I did not file a ticket, because the ticket would have been closed as no fault found. The workaround is real work. It just does not appear in the system that is supposed to be measuring the work.
The counterargument
The vendor would say, reasonably, that a printer cannot know why paper curls. It can report a feed error. It cannot report humidity, shelf placement, or the overnight temperature of a warehouse. Expecting the log to explain the room is expecting the wrong thing from the tool.
That is true, and it is also the point. The log is not failing. The contract is failing, because the contract was written as if the log were complete. The vendor is not lying when it says the printer is within tolerance. The vendor is answering the question the contract asked. The manager is answering a different question, and the two of them have been talking past each other for a year.
What I might be wrong about
I might be too quick to blame the contract. A maintenance agreement that tried to account for every room condition would be unaffordable and unenforceable. At some point a business has to accept that a machine in a cold room will behave like a machine in a cold room, and the person who works in that room is the one who has to adjust. That is not a failure of design. That is the cost of running a warehouse.
And I should say the obvious thing: the manager solved it. He moved the paper. The jams mostly stopped. The printer prints. The morning mood is now an occasional bad day, not a daily event. The system did not help him, but he did not need the system to help him. He needed a witness, and he got one, and then he went back to work.
The shelf on the south wall
The paper now sits on a shelf on the south wall, next to a stack of flattened boxes and a radio that is always on the same station. The printer still jams sometimes, and when it does the manager walks over, opens the feed, pulls out the accordion, and closes it again without saying anything. The log records another paper feed error. The contract renews in March. On the north wall, where the paper used to sit, there is an empty shelf with a fine layer of dust and a strip of tape that once held a label reading PAPER. The tape is still there. The label is gone.
#Essay #smallbusiness #maintenance #warehouse #maintenance contracts #error logs #small business IT #warehouse operations #workarounds