Four generations of
one inventory system

The shop

A tire shop in South Florida, family owned, in the tire business since the nineteen sixties and selling to the public since 1999. Mounting, balancing, alignments, brakes, suspension. Tires new and used. And, at the bottom of the welcome copy and nowhere else on the page, an enormous selection of rims.

Nothing on this page dates itself. The footer computes its year, so on a live server today it would claim the present, and the exhibit's clock is pinned to the last date anything in this tree was written. The tree runs from 4 January 2010 to 19 August 2012. The two screens below carry timestamps of their own.

Clone this one, change what is different

The catalog admin behind the site. This particular screen takes a product already in the catalog, copies every field, and hands you the copy to edit. That is the whole Templatizer idea, a year before Templatizer, sitting in a product I was selling to other people at the time.

This screen is version 3 of a content management product my studio sold, not something written for this shop: five other client sites were running the same build, and the admin's footer still carries the studio's name. The date is the file's own date in the archive. Note what is not here. A scan of this whole tree finds no eBay code anywhere: the catalog kept the website, and an outside vendor kept eBay.

The first time the question gets asked

A wheel inventory, separate from the catalog, with its own database and its own way in. Read the headings across the top of the grid. That row is the question this whole business turns on being asked for the first time: which numbers identify a wheel, and which ones sell it. The second icon at the top right is a barcode, and the screen you log in through says scan or enter the item number. In a tire shop. In 2012.

The table this page reads has its own creation date inside its name. Read as a timestamp it is 25 May 2012. The database file was last written on 4 June 2012 and held 341 rows of real stock, so every row you see here is invented and the headings are the real ones. This screen was very nearly published with none of its own furniture: the application was written to sit at the root of its own address, so mounted here every link it makes for itself, including the ones that pull in its own header, pointed one level too high and quietly resolved to nothing.

The spreadsheet the whole system grew out of

For three months there was no system at all. The eBay vendor was gone, the catalog did not do eBay, and the inventory lived in a spreadsheet I built by hand and kept by hand. Those three months are where the thinking happened, and eleven of its thirteen columns are still columns in the live table today.

The two saves either side of the tool are the exhibit. On 30 January it has thirteen columns, and one of them is a checkbox called Posted? that somebody had to tick to remember whether a wheel had been listed yet. The tool was written the next day. By 10 April that column is gone, because the job it existed to track had stopped being anybody's job.

Every surviving save carries one creation stamp, 2012-11-07 16:31:28, so they are a single workbook carried forward rather than separate files.

The tool exists, and it is still learning

Templatizer was written on 31 January 2013, in a day. The earliest copy of it that survives cannot be run: there is no database of any kind in that tree, of any format, so every page dies at the first query. What does survive is what it ate. Eight rim sheets are still sitting in its upload folder, and they are dated, and they are not the same shape as each other.

Five weeks apart, the sheet goes from fifteen columns to twenty eight. One Vehicle and one Years become five of each, because a wheel fits more than one car. One column called TPMPVS splits into tpms and vs, because a sensor and a valve stem are two different things. Imper becomes Imperfections plus repair, skim and, by 2015, Quality, because how bad the damage is and what was done about it are two more. That is the same work the spreadsheet was doing, still going, a year into the tool.

The code in that tree cannot be dated closer than its jQuery, which is 1.10.2, released on 3 July 2013. The sheets can: their names carry their own dates, and the eight of them run from 28 February 2014 to 6 August 2015. So this is the 2013 tool as it stood in 2015, and it is not exhibited here because it cannot be run honestly. Its database was a SQL Server store, two backups of it survive, and restoring one is the next job.

Six years of being used every day

The same tool, grown up. The home page is a board of wheels that have been described but not listed anywhere yet, with a counter for how far behind the shop is, and one button that pushes all of them at once. Down the left is every other thing the job turned out to need: a second product family, a third, an importer, a template library, an archive, an item number generator.

This copy is dated by its own working files. Thirty seven item number exports sit in it with dates in their names running from 28 May 2019 to 11 August 2020, and the upload folder carries sheets from 2019 and 2020. Its own notes say it ran on a web server in the shop until it was rebuilt as a WordPress plugin in early 2026.

What it was actually for

This is the screen the whole thing exists to produce. One wheel goes in, and out comes the listing: the title built to the character limit, the item specifics, and a block of description markup ready to paste into a marketplace listing. Describe the wheel once, in one place, then let the machine write it out however each channel wants it.

This page nearly did not make it into the exhibit. It builds its description by pulling in a separate file of template code from inside a block of script, which is legal in the original and was not something the converter handled, so the most important screen in the tool was coming out as an apology. That is fixed, and the fix is in the converter rather than in this copy.

And then it was not only wheels

A center cap is the small cover that snaps into the middle of a wheel. Look at what this screen does not ask for: no bolt pattern, no offset. It asks how many clips, and which part number is stamped on the back, because that is what identifies a cap. Same machinery, completely different questions. Bike tires, car tires, hubcaps, bumpers and emblems followed. The box across the top takes a part number and fills the rest of the form in for you, which is the first ancestor of the intake that runs today.

The database this ran on held 2,750 wheels, 4,091 bike tires, 104 center caps, 19 car tires and one emblem. Every row in the exhibit is invented, the row counts are the real ones, and there was never a customer table in it: this tool described things, it did not sell them. One file in this module is the only damaged file in the whole tree, and there is a page at its address saying so.