The Complete Guide to Running a Tire Storage Program

Seasonal tire storage looks simple from the outside. A customer drops off four tires in April, you put them somewhere, and they come back in October to swap. In practice, a storage program is one of the most operationally demanding things a small shop can run. Every set has to be found in minutes on the busiest day of the year, every customer has to be reminded at the right time, every invoice has to make sense across seasons of different lengths, and every tire has to be handed back in the condition it arrived in, with proof. Shops that treat storage as an afterthought tend to discover the problems all at once during the first changeover rush, when the rack is full, the phone is ringing, and nobody can remember which shelf holds the sedan set that was dropped off in a hurry last spring.

We built TireKeepr because we watched shops fight those problems with whiteboards, index cards, and spreadsheets that lived on one person's laptop. This guide is not a sales pitch. It is the operating manual we wish those shops had before their first busy season. It walks through the six areas that decide whether a storage program is profitable and calm or chaotic and expensive: how you record where each set lives, how you document the condition of what you are holding, how you time and communicate the changeover, how you price and bill it, how you handle the sets nobody comes back for, and how you choose tools that hold up as the program grows. Each section links to a deeper article on our blog, so you can go as far as your situation requires.

Intake and Rack Location: Knowing Where Every Set Lives

The single most common failure in tire storage is not damage or theft. It is simply not being able to find a set quickly. A shop with 200 sets on the rack has 800 tires, and if each set takes fifteen minutes to locate, a full changeover day becomes a long afternoon of technicians walking aisles with a flashlight. The fix starts at intake. Before a set goes anywhere, it needs a unique identifier that ties the customer, the vehicle, and the four tires together, and that identifier has to be written down in the same moment the tires are placed on a specific shelf. Doing it later, from memory, is where errors creep in. A good intake process takes a couple of minutes per set and pays for itself many times over when the fall rush arrives.

Rack positions should be named in a way that anyone can read without training. A simple scheme that combines aisle, bay, and shelf level works for most shops, and the labels should be physical, large, and durable enough to survive a season of tire dust and forklift bumps. The tag on the tires themselves should carry the same identifier as the record, plus the customer's last name and the vehicle, so that a set that gets moved by mistake can still be traced back. Many shops also mark the position of each tire on the vehicle (left front, right rear, and so on) at removal, which makes reinstallation faster and keeps rotation patterns intact. The labeling system you choose matters less than using it consistently every single time, by every person who touches the rack.

Tracking location in a spreadsheet or on paper works while the program is small. It breaks when two people update it, when a set gets moved during a reorganization, or when the person who knows the system is out sick during changeover week. Dedicated tracking, whether that is a simple database or purpose-built storage software, gives every set a live location that updates when it moves, and lets any staff member look up a customer by name, plate, or phone number and walk directly to the right shelf. The goal is a shop where the newest hire can pull the correct set in under two minutes without asking anyone. Our articles on tracking rack positions and on choosing a labeling system go deeper on both the physical and the digital side of the problem.

Condition Records: Tread Depth, Inspection, and Proof

Storing a customer's tires means taking custody of something typically worth several hundred dollars and, in the case of premium winter sets, considerably more. When that set comes back out, the customer will look at it with fresh eyes and remember it as newer than it was. Without a record of the condition at intake, every disagreement becomes your word against theirs, and the customer usually wins that argument in the shop's own lobby. The most useful condition record is tread depth. Measured at intake and again at reinstall, across all four tires and ideally at the inner, center, and outer grooves, it tells the customer exactly how much life is left and tells you whether anything changed while the set sat on your rack.

Tread depth history serves a second purpose that is easy to overlook. A customer who sees their winter set drop from a healthy depth toward the replacement threshold over three seasons has been given an honest, documented reason to buy tires from you rather than from a discount website. Nothing sells a replacement set like a chart the customer watched you build. The same record protects you when a tire that was already worn at intake is later presented as damaged in storage. Add a quick note on visible sidewall condition, any plugs or repairs, the DOT date code, and the pressure at intake, and you have a complete picture that takes about two minutes per set to capture and can save an hour of argument later.

The changeover appointment itself generates records worth keeping. Torque values applied at reinstall, the pressure each tire was set to, whether a TPMS relearn was performed, and who did the work all belong in the file. If a wheel comes loose weeks later, the difference between a documented torque procedure and a shrug is enormous. Keep photographs where practical. A single wide photo of the set at intake, with the tag visible, is cheap insurance against almost every kind of dispute. Our articles on tread depth history and on changeover appointment records cover what to capture, how to store it so it can actually be found later, and how to present it to customers in a way that builds trust instead of feeling like paperwork.

Timing the Changeover and Reminding Customers

Changeover season is defined by weather, not by the calendar, and that makes it hard to schedule. Winter tires are built from compounds that stay pliable in cold temperatures and wear quickly in heat, so leaving them on into a warm spring shortens their life. Summer and all-season tires lose grip as temperatures fall, so swapping too early in autumn exposes the customer to a cold snap on the wrong rubber. The practical rule most shops use is to watch sustained daily temperatures rather than picking a fixed date, and to give customers a window rather than a deadline. That window is different in Minnesota than it is in Tennessee, and it can shift by weeks from one year to the next, which is exactly why a fixed reminder date on a wall calendar keeps failing.

The reminder is where storage programs quietly succeed or fail. A customer who is reminded at the right moment books an appointment, gets their tires swapped, and stays on the rack for another season. A customer who is not reminded either forgets entirely, shows up during the peak week with no appointment, or drifts to a competitor who happened to send a text first. Reminders should go out in waves: an early notice that the season is approaching, a booking prompt when the window opens, and a nudge to anyone who has not scheduled as the window closes. Text messages tend to be read faster than email, but the channel matters less than the timing and a clear call to action that leads directly to a booking.

Manual reminders are a real workload. Calling 200 customers takes days, and it is exactly the kind of task that gets pushed aside when the shop is busy, which is precisely when it matters most. Automating reminders from your storage records, so that everyone with a set on the rack receives the right message at the right stage, removes that burden and makes the reminder feel like a service rather than a chore. Spreading appointments across the full window also protects your capacity. A shop that can shift even a fraction of its changeovers out of the peak week gains slack for walk-ins and repairs. Our articles on the safe timing of the winter-to-summer swap and on the best ways to remind customers cover both the weather logic and the communication mechanics.

Pricing and Billing a Storage Program That Pays for Itself

Tire storage is often priced as an afterthought, either bundled free with a changeover or set at a round number someone picked years ago. Neither approach reflects the real cost. Storage consumes floor space that could hold something else, labor at intake and retrieval, racking and tags, insurance exposure, and the administrative time to track and remind. When you add those up, a seasonal storage fee that seemed generous can turn out to be a loss. The right price comes from an honest accounting of your own costs, a look at what nearby shops charge for comparable service, and a decision about what role storage plays in your business: a profit center on its own, or a retention tool that earns its keep through changeover labor and tire sales.

Billing gets complicated when seasons do not line up. A customer who drops winter tires in March and picks them up in November has used more of your rack than one who swaps in late April and returns in early October, yet a flat per-season fee charges them the same. Some shops accept that as the cost of simplicity. Others move to monthly billing, a base fee plus a per-month extension beyond a set number of months, or an annual plan that covers both changeovers and the storage between them. Each model changes customer behavior. Monthly billing encourages prompt pickup. An annual plan smooths cash flow and keeps the customer for the year. The article on billing fairly across a long season walks through the trade-offs in detail.

Whatever model you choose, the invoice should be predictable and easy to explain. Customers accept storage fees readily when they were told the price at drop-off, saw it in writing, and were not surprised at pickup. Collecting payment at intake rather than at retrieval reduces disputes and reduces the odds of a set being left behind because the customer does not want to pay to get it back. Tie the billing to the same record that tracks the set's location and condition, so that when the customer calls, whoever answers can see what they owe, what was paid, and when the set is due out. Our guide on how much to charge for seasonal storage gives a framework for arriving at the number rather than guessing.

Forgotten Sets, Abandoned Tires, and Liability

Every storage program accumulates sets that nobody comes back for. The customer sold the car, moved out of state, changed shops, or simply forgot. Over several seasons those sets can fill a meaningful share of your rack, each one occupying space you could sell to a paying customer. The problem is that you cannot simply dispose of them. The tires still belong to the customer, and in many states a shop that discards or sells a customer's property without following a defined process can expose itself to a claim. The rules vary by state, so it is worth confirming what applies where you operate, but the common thread is documented notice to the customer over a reasonable period before anything is done with the property.

The best defense is a storage agreement signed at intake. It should state the fee, the season or term, what happens if the set is not collected by a defined date, how the shop will attempt to contact the customer, and what the shop may do with the set after that process runs its course. A clause like this is not hostile to customers. It sets expectations, and the customers who read it are the ones who tend to pick up on time. Pair the agreement with a record of every contact attempt: the date, the channel, and the result. When a set has been on the rack past its term, the sequence of reminders, notices, and a final written warning is what allows you to act with confidence rather than hoping nobody ever asks.

Operationally, forgotten sets should be visible rather than buried. A storage system that flags overdue sets, shows how long each has been on the rack, and tracks the notice process makes it easy to run a monthly review instead of discovering a wall of dusty tires during a reorganization. Some shops offer a small incentive for prompt pickup, or convert long-overdue sets into a paid extension when the customer finally surfaces. Others make it a policy to call every overdue customer personally, which often recovers a relationship as well as the rack space. Our article on what to do when a customer forgets their stored set covers the notice process, the documentation, and the customer conversation, and the changeover records article explains what to keep on file.

Choosing Tools That Scale From Ten Sets to Five Hundred

Every storage program starts with whatever tool is closest to hand. For a shop holding a couple dozen sets, a spreadsheet with columns for customer, vehicle, position, intake date, and fee is entirely adequate, and pretending otherwise would be dishonest. The trouble arrives with growth and with staff turnover. At a hundred sets, the spreadsheet is being edited by three people, the reminder list is a separate file, the tread depth readings are on paper in a drawer, and the billing lives in a point-of-sale system that does not know a tire set exists. The information is all there, but it is scattered, and the person who knows how the pieces fit together is the one you cannot afford to lose.

The move to dedicated software is worth making when the cost of the scattered system, measured in lost sets, missed reminders, and unbilled storage, exceeds what the software costs. That point arrives earlier than most shops expect, because the losses are invisible until someone counts them. The features that matter are not exotic. You want a single record per set that holds location, condition, customer contact, agreement, billing status, and history. You want reminders driven by that record, so nobody has to remember to send them. You want a search that works from a plate, a phone number, or a name. And you want reporting that shows how full the rack is, what is overdue, and what revenue the program is actually producing.

Be skeptical of tools that promise to do everything. A general shop management system may have a storage module that was added as a checkbox, and a spreadsheet template sold online may be nothing more than a spreadsheet with formatting. Ask how the tool handles a set that moves shelves, a customer with two vehicles, a season that runs long, and a staff member who needs to look something up on a phone in the aisle. We built TireKeepr around exactly those questions, and we are honest that it is not the right fit for every shop. Whatever you choose, the articles on rack tracking, reminders, and long-season billing describe the workflows any tool should support, and they make a good checklist to bring to a demo.

More guides on this topic

Further reading from the TireKeepr blog, each answering one specific question in depth.

A tire storage program succeeds on discipline rather than on cleverness. Every set gets an identifier and a recorded position at intake. Every set gets a tread depth reading and a condition note. Every customer gets a reminder at the right time, a price they were told in advance, and an invoice that matches. Every forgotten set is flagged, contacted, and resolved through a documented process instead of quietly gathering dust in a corner. None of that requires special software when the program is small, but all of it becomes hard to sustain by hand as the rack fills up. Use the articles linked throughout this guide to build the workflow first, then choose the tools that let you keep it running when the busiest week of the year arrives and the phone will not stop ringing.