Inventory Management for Auto Repair Shops
A busy independent repair shop runs on parts it does not keep on the shelf: most jobs need components that are special-ordered from three or four vendors, delivered the same day, and installed before the car leaves the bay. When a starter, a set of pads, or a wheel bearing is on the wrong shelf, mislabeled, or stuck on a vendor backorder, the vehicle sits, the bay clogs, and a comeback or a lost sale follows. This guide shows how to build a hosted inventory system that tracks stocked parts, special orders, core charges, and vendor returns the way an auto shop actually works.
The problem
- Parts live in three places at once — a bin, a vendor delivery truck, and an open repair order — and nobody can say for sure what is really on hand versus already promised to a job.
- Core charges pile up as unclaimed cash: a $60 alternator core or a $300 cylinder-head core gets set on a shelf, the roughly 30-day return window lapses, and the shop eats the deposit.
- The same part number supersedes, splits by trim or engine, or fits four different vehicles, so a naive count says you have the part when it will not actually bolt onto the car in the bay.
- Defective and over-ordered parts wait weeks for an RMA and restocking terms, tying up cash while nobody tracks which vendor still owes a credit.
What you’d build
Every stocked part with on-hand quantity, bin location, last cost, and min/max reorder points. When a fast-mover — brake cleaner, common filters, bulk oil — drops below its minimum it flags for reorder, so a tech is never mid-job without it. Non-stock, special-order parts are tagged separately so they never inflate your shelf count.
Raise a purchase order to any vendor straight from a repair order, so every ordered part is tied to the car and the job it is for. Track each line as ordered, backordered, or received, scan or key it in on arrival, and reconcile the count and cost against the vendor invoice before it ever hits a bin.
Capture the refundable core deposit the moment a core part goes on a ticket, start a return-window countdown, and log the credit when the dirty core goes back to the vendor. Warranty and defective returns get their own RMA status so a returned part never silently re-enters sellable stock.
The data model
A day in the system
- A service advisor opens a repair order for the car in the bay, capturing the VIN and year/make/model so every part is checked against real fitment, not just a name.
- The tech lists what the job needs; the advisor searches the catalog to see what is on the shelf versus what must be ordered, and at what cost from which vendor.
- In-stock parts are pulled from their bin, the on-hand quantity drops, and each line lands on the repair order priced through the parts matrix rather than a flat markup.
- Anything not stocked is dropped onto a purchase order tied to that repair order and sent to the chosen vendor; backordered lines are flagged so the advisor can quote a realistic promise time.
- When the delivery driver arrives, parts are received against the PO, on-hand counts go up, and the quantity and price are reconciled line by line against the vendor invoice.
- If a part carries a core, the deposit is itemized on the ticket, the old core is bagged and shelved, and a return-window countdown starts against that vendor.
- Dirty cores and any defective parts go back on the next vendor run, and the system logs the core credit or RMA so the shop actually recovers the deposit.
- At close each week a cycle count reconciles a slice of the shelf, and reorder and dead-stock reports show what to restock and what to send back before it goes obsolete.
Where AI trips up
- Core charges are not just a line item. California's Bureau of Automotive Repair requires them to be separately itemized on the estimate and invoice, and the deposit stays a live liability until the core is returned, usually within about 30 days. Treat a core as ordinary revenue and you both break disclosure rules and lose the refund.
- Fitment is not one-to-one. A part number can supersede to a newer number, split by trim or engine, or fit several different vehicles, so tie parts to a VIN or year/make/model and never assume a matching count means the part will actually bolt on.
- Most parts are special-ordered per job, not warehoused. If the build models everything as shelf stock, phantom inventory appears and the system thinks you hold a water pump you have never stocked. Flag stock versus non-stock parts explicitly.
- A returned part must not silently re-enter sellable stock. Defective returns go back under an RMA and may carry a restocking fee, and over-orders may be non-returnable. Track vendor, RMA status, and credit owed separately from on-hand quantity.
- Parts have no single fixed price. Markup runs on a cost-tier matrix, and the same part's cost changes with each PO, so store last cost (or average cost) per receipt and price through the matrix — hardcode a list price and margin quietly bleeds away. Also decide when quantity decrements, on pull or on repair-order close, or a voided job double-counts.
- Parts catalog with on-hand quantity, bin location, last cost, and min/max reorder alerts, with stock versus special-order clearly separated.
- Order-to-vendor flow raised from a repair order, with ordered / backordered / received status and invoice reconciliation.
- Core deposit tracker with a return-window countdown and credit reconciliation per vendor.
- Full accounting, general ledger, and payroll — keep v1 to parts and cores and let the books stay in your accounting tool.
- Live vendor catalog and pricing integrations (WorldPac, NAPA, O'Reilly punch-out) — start by adding parts and costs manually.
- Barcode scanners and label-printing hardware — a typed or copy-pasted part number ships v1; add scanning once the flow is proven.
FAQ
How is this different from a full shop-management suite like Tekmetric, Shopmonkey, or Mitchell 1?
Those are broad all-in-one suites priced per technician seat. With ybuild you describe the lean inventory and core-tracking workflow your shop actually uses and get a running system tuned to your bins, your vendors, and your matrix — hosted on ybuild and served on your own domain, used standalone or alongside whatever you already run.
Can it track core charges and actually get my deposits back?
Yes. Every core is captured when it goes on a ticket, with a return-window countdown per vendor and a status of owed, returned, or credited, so a $300 head core never quietly expires on a shelf.
Does it handle multiple suppliers and price comparison?
Yes. Each part links to a vendor with its account number, terms, and delivery cutoff, so you can see who stocks a part, at what cost, and who still owes you a return credit.
Can several advisors and techs use it at the same time?
Yes. Managed authentication gives each person a login and a role, so the front counter, the parts manager, and the techs all see the same live counts without stepping on each other.
Can I bring in my existing parts list?
Yes. Import your current parts, costs, and bin locations from a spreadsheet to seed the catalog, then keep it live as you order and receive — all stored in a managed database behind your own domain.
Sources
- Core Charges Explained — Bureau of Automotive Repair (California) — Official regulator: core charges must be disclosed and separately itemized on the estimate and invoice.
- Inventory and Stock Management Best Practices for Auto Repair Shops — Tekmetric — Distinguishes stocked parts from just-in-time special orders and how to categorize each.
- Auto Parts Inventory Management: Best Practices — Shopmonkey — ABC analysis, min stock levels from sales history, and reorder points for a repair shop.
- What is a Core? — NAPA Auto Parts — Vendor-side explanation of cores and the refundable deposit shops must return to recover.
Describe it, go live on your own domain in one pass — hosted, full-stack, no server. Free to start.