This is Sunday Supply Chain Stories, where we revisit the foundations that continue to shape how inventory moves, returns and recover value.
If you enjoy the newsletter, follow The Supply Loop on Linkedin and ask your friends to subscribe to receive the next story.
Around 1900, the Newark Public Library was dealing with a traceability and visibility problem that would eventually drive the design of modern LPNs and RFIDs technology. What they were trying to solve was: how to track and trace every book that was borrowed, from checkout to return.
Thousands of books moved in and out of the library each day, borrowed by readers, circulated across the city, and returned—or not. As public libraries shifted to open stacks, readers gained direct access to materials and volumes accelerated. The old ledger-based methods that librarians had relied on for decades could no longer keep pace with the speed and complexity of the flow.
John Cotton Dana, the librarian leading the Newark Public Library at the time, understood that the challenge was not simply about storing books. The real challenge was maintaining visibility as every individual book left the building and tracking whether it came back.
He needed to know which borrower had a specific book, how long it had been out, when it was expected back, and what condition it returned in. Without that information, inventory control weakened, recovery rates declined, and the reliability of the library's operations began to erode.
What Dana created was remarkably disciplined for the time.
Each borrower carried a registration card tied to a unique identification number. Each book carried its own card stored inside a pocket attached to the cover. At checkout, the borrower and the specific unit were linked together through a manual transaction. The borrower's number and due date were recorded directly onto the book card, creating a traceable chain of custody tied to that individual item.
When the book returned, the transaction was reversed. The card was removed, the return was recorded, and the item moved back into circulation.
Every transaction connected a person to a specific unit. Every unit carried its own history.
This tracking principle became the foundation of how the entire library operated.
By the early 1930s, libraries had already started automating the charging process. In 1930, Gaylord Brothers introduced the Model C Book Charger, an electrically operated machine that transformed how libraries recorded transactions. The machine used a borrower's registration card with an embossed metal identification number. When a book was checked out, the librarian inserted both the borrower card and the book card into the machine. The charger mechanically stamped the borrower's ID number and the return date directly onto the book card, creating a uniform, legible impression that could not be misread or altered.
This was the critical innovation. Dana's system relied on handwritten entries, which meant variation. A hastily written date could be misread. A borrower number scrawled illegibly created confusion. The Gaylord charger eliminated that variability. Every transaction produced an identical, scannable impression. A librarian at a different branch could read a card from any facility and know exactly who had the book and when it was due. Consistency across locations became possible.
The technology evolved, but the logic remained unchanged. The machine mechanized Dana's two-card system, making the existing system faster, more legible, and scalable across networked facilities.
The principle that scales
What Dana understood was simple but powerful: scalability in a variable system requires discipline at the unit level. He could not control how books were borrowed or returned but he could control how to record every transaction. When every individual unit carried its own identity and history, decisions downstream could be reliable. Consistency across locations became possible.
That principle still shapes the most sophisticated returns operations today.
The most sophisticated returns operations today apply Dana's principle through evolved technology: item-level identification that carries rich data about each unit's specific condition and performance.
Instead of a registration card in a pocket, modern operations use License Plate Numbers (LPNs) and increasingly RFID tags to create a unique identifier for every item. But unlike a simple SKU barcode, the LPN becomes a data carrier that travels with the product, collecting information about the specific flaws, damage patterns, wear characteristics, and failure modes of that individual unit.
The unit carries identity from intake. A returned jacket arrives at a receiving dock. Its condition is assessed in detail: the seam on the left sleeve is separating; the zipper has stripped threads; the fabric pilling indicates low-quality yarn; the water damage on the hem suggests a design flaw in the drainage system. Each of these observations is recorded against that jacket's unique LPN. This is Dana's principle applied: the individual unit gets its own card. Not by SKU. By the specific item and its specific condition.
The transaction establishes custody at every station. The jacket moves to a repair facility. The repair technician sees the full history of what was documented at receiving. They repair the seam, replace the zipper, and note the repair work against the same LPN. If this is the third jacket this week with the same seam failure, that pattern becomes visible across the network. Every movement through the network creates a transaction. Every transaction is recorded against the individual unit. Dana's charging system worked because every movement created a record. Modern systems work the same way.
The record informs the next decision and remains connected to the unit. The jacket then moves to inventory, where its dwell time is tracked. If it sits for 60 days because nobody is buying jackets with that specific zipper configuration, that information stays connected to the LPN. When the jacket finally reaches a resale or clearance channel, the brand's product team can pull up the complete history. They can see that 40% of returns in that style had zipper failures. They can see that jackets with water damage in the hem returned within 30 days of purchase. They can see the exact failure modes that are driving returns volume.
This is where the LPN becomes different from a simple barcode. The LPN is a feedback loop that connects what is broken in returned inventory directly back to the brand's product design, quality control, and customer experience teams. That data drives product improvements. A brand learns that their most common returns are caused by three preventable design flaws. They fix those flaws in the next production run. Returns drop by 25%. Recovery rates improve because fewer units are coming back. But more importantly, customers stop experiencing the frustration that drove the returns in the first place.
Modern brands that leverage returns data this way are treating every returned unit as a data point that improves their product. The unit carries identity not just for operational visibility, but for intelligence.
Technology is secondary. What matters is that the principle Dana understood remains constant: the individual unit carries a complete history, and that history informs every downstream decision. The difference is that modern operations can scale that principle across hundreds of facilities simultaneously, and the data flows not just to the next operations team, but back to the brands themselves so they can rebuild their products around what is actually breaking.
Modern returns operations face the same constraint Dana faced. You cannot control whether a product will be damaged in transit or held too long in inventory. You can control whether the system captures a reliable history at every step.
That means three concrete moves.
Build unit-level assessment into receiving. Condition-grade and tag every returned item individually. Connect that assessment to a specific item ID in your system, in addition to the SKU. That record becomes the baseline for every downstream decision.
Embed the workflow into your system, not your SOPs. When a disposition decision is made (repair, clean, resale, recycle), that decision should generate a task for the next station, not sit in a notebook. The system should pull the full history from the previous station and display it before the operator makes the next decision. Consistency in decision-making comes from operators having the same information, not from hoping they remember the same training.
Standardize your grading rules and routing logic across every facility in your network. If one facility uses different criteria for what counts as "like new" versus "very good," the product history becomes unreliable the moment it moves between locations. Standardization is not about being rigid. It is about making sure a unit processed in Atlanta looks the same as a unit processed in Newark so that recovery value scales consistently.
Those three moves alone close most traceability gaps. They are not revolutionary. They are the same discipline Dana embedded into a library system more than a century ago. The difference is scale. Modern networks are faster, more complex, and more distributed. The constraint is sharper because visibility gaps cost more.
But the logic is unchanged.
Visibility at the unit level enables decisions that recover value. The operator who maintains it, at scale, wins.
For practitioners: At what point in your returns flow does the grading decision actually get made, and who owns it? Is it at receiving, at the processing station, or somewhere downstream where the cost of a wrong call is already absorbed into your cost-to-serve?
Sources
Helen Thornton Geer, Charging Systems, American Library Association, 1955
Leila H. Kirkwood, Charging Systems, Graduate School of Library Services, 1961
American Library Association, Library Cards & Circulation History
Newark Public Library Archives, John Cotton Dana Papers
John Cotton Dana biography
Thank you for reading Sunday Supply Chain Stories!