Free tire inventory spreadsheet template (CSV/XLSX)
Download a free CSV and XLSX tire inventory template with the 14 columns a small shop needs, and see where plain spreadsheets fall apart.
Fourteen columns. That's the sheet you can build in twenty minutes and still be using two years from now, if you keep it to that. Most shops that try to track inventory on paper or in their head lose track of what's actually on the rack within a month. A sheet fixes that, as long as it has the right columns and nothing extra.
We built one so you don't have to start from a blank grid. Grab it here: tire-inventory-template.csv or tire-inventory-template.xlsx. Same 14 columns in both, pick whichever your computer opens faster. Open it, delete our sample rows, and start typing your own rack. Ten minutes in, it should already look like your shop, not a blank form.
The 14 columns, and why each one earns its place
A spreadsheet with forty columns never gets filled in. One with five is missing the column you need the day a customer asks whether you still have that take-off from Tuesday. Fourteen is the number that survives a Saturday rush, and it's close to what most point-of-sale and shop-management tools ask for on their own intake forms, which isn't a coincidence.
| Column | Why it's there |
|---|---|
| Rack location | So a tech walks straight to it instead of searching the pile |
| Size | What customers actually search for |
| Brand | Some buyers only want certain brands |
| Model | Matters more on new tires than used |
| New or used | Changes everything else on the row |
| DOT | Age, and proof of what you sold |
| Tread depth | Required for any used tire you grade |
| Condition grade | A, B or C, so a phone call gets a straight answer |
| Source | Take-off, trade-in, batch, or walk-in |
| Lot ID | Ties a tire back to the batch it came from |
| Cost | What you paid, even if it's zero |
| Price | What it's tagged at |
| Date added | Flags stock that's been sitting too long |
| Sold date | Empty until it isn't |
Skip any of these and you'll rebuild the column later, usually while someone's waiting at the counter.
A filled-out row, start to finish
Picture an actual row instead of an empty one. Rack B2. Size 225/65R17. Brand whatever's stamped on the sidewall, say Michelin. Used. DOT read straight off the tire and logged the day it came in. Tread measured across three points and the lowest one entered: 6/32" on this one, because that's the number that matters if a customer asks. Grade B, since it's even wear with no repairs but it's not fresh off a take-off pile. Source: trade-in. Cost: whatever you gave the customer in credit, even if that's zero. Price: your number, tagged and matching what's chalked on the sidewall. Date added: today. Sold date: blank, until it isn't.
That's fourteen fields, filled out in under a minute once it's a habit. The habit is what makes the sheet worth anything six months from now, not the column headers themselves.
What the template won't do
It won't do everything. It won't stop two people from editing at once and overwriting each other's work without warning. It won't take a photo of the tire for you. It won't tell you a size is sold until someone remembers to type it in, and it won't notice when that same person forgets. Those gaps are the reason this page has a second half.
Where a spreadsheet starts to break
A sheet works fine for the first fifty tires. Past a couple hundred, on two phones, with two people, it starts to fight you.
- Two phones editing the same file means one person's changes get overwritten by the other's, silently.
- No photo means no way to prove condition after the sale, or find a specific tire again from a picture.
- No "sold" event means a size shows as available long after it's already on someone's car. A customer drives over for a tire that's gone.
- No matching for how people type a size. "225/65/17" and "2256517" read as different tires to a spreadsheet, even though they're the same one to a customer.
None of that means stop using a spreadsheet. It means know where the ceiling is before you hit it.
Moving from the sheet to something that tracks a sale
You don't have to retype two hundred rows to switch. Most shop software, DuroBay included, takes a CSV import: point it at your file, match the columns once, and the rows land in the system with rack locations intact. What changes after that is the "sold" part. Instead of hunting for a row and deleting it, you tap sell, and the count updates itself everywhere it's shown.
That's the one thing a plain sheet structurally can't do on its own: react to a sale in real time, across every device looking at it, and update the same row everyone else is looking at without anyone touching a formula. DuroBay adds that layer on the same 14 columns you already keep, plus a rack view and a photo per tire, and it's free to start at /login.
Before you commit to either one
- Under a hundred tires, one person at the counter: a sheet is fine. Use ours, and don't feel behind for sticking with it.
- Two people touching inventory, or customers asking for sizes by phone daily: the "sold" gap will cost you a sale eventually, usually on a Saturday when it stings the most.
- Somewhere in between, most shops keep the sheet for a while after they've outgrown it, mostly out of habit, and switch once the first double-sold tire actually happens.
- Either way, keep the fourteen columns. They're the same ones a bigger system will ask for on day one.
Compare what a receipt looks like once a sale is logged against the invoice template, and see how pricing a used tire plugs into the same cost and price columns above.
Common questions
Is the tire inventory template actually free?
Yes. Both the CSV and XLSX versions are free to download, no account or sign-up required. Delete our sample rows and start typing your own rack.
What's the difference between the CSV and the XLSX file?
Same 14 columns in both. The XLSX opens with column widths and formatting already set in Excel or Google Sheets; the CSV opens plain in almost anything, including older software.
Do I have to use all 14 columns?
You can add more, but don't remove rack location, size or sold date. Those three are the ones a working sheet can't function without.
How do I move from a spreadsheet to shop software without retyping every row?
Most shop software, including DuroBay, imports a CSV directly. You match the columns once and the rows land in the system with rack locations intact.
What counts as the 'source' column for a used tire?
Take-off, trade-in, batch lot, or walk-in. Writing it down now saves a conversation later when a customer asks where a tire came from.