What scattered parts status looks like
"Is my part in yet?" is one of the most common questions an independent auto repair shop answers, and one of the hardest to answer quickly. The service advisor checks a supplier portal, then a sticky note on the monitor, then walks back to ask the technician who placed the order. The customer, who already approved the repair, waits on hold or drives by to ask in person. Meanwhile the car sits on a lift or in the lot, taking up space the shop needs for the next job.
Writing estimates and getting approvals is one part of the job. TwoQM covered that path in service requests and estimate approvals. This article is about what happens after the customer says yes and the part is not on the shelf: special orders, back orders, wrong parts, returns, and the status everyone needs to see. TwoQM builds custom software, automation, and connected systems for auto repair shops when the tools they already pay for leave that status scattered.
Here is an original example, not a TwoQM client and not a measured result. A four-bay shop orders a transmission control module from a dealer parts counter and brake components from two local suppliers. One part is back-ordered, but that news arrives by phone to whoever answered. Another arrives with the wrong connector and goes into a corner for return. The advisor tells the customer "Thursday," the technician thinks "next week," and the owner finds the unreturned part a month later when the supplier credit is no longer available.
No one did anything careless. The shop simply had no single place where an order's status lived.
Give every special order a record tied to the repair order
The fix starts with treating each special-order part as its own small record, attached to the repair order and the vehicle, not to a person's memory. Each record should hold:
The part description and number, and the supplier it was ordered from
Who ordered it and when
The promised date, and where that promise came from (supplier portal, phone call, email)
The current status
The core charge or deposit, if any, and whether the customer paid it
Notes on substitutions, fitment questions, or a second source
The repair order then shows, at a glance, whether it is waiting on parts and which ones.
Use a short, shared list of statuses
Statuses only help if everyone uses the same words. Keep the list short enough that a busy advisor will actually update it:
Quoted. Price and availability checked, not ordered yet.
Ordered. Order placed, with a promised date.
Back-ordered. Supplier delayed it; new date recorded, or "unknown."
Received. On the shelf, checked against the repair order.
Wrong or damaged. Not usable; a return is started.
Returned. Sent back, with the return or credit reference.
Installed. Used on the vehicle.
When a status changes, the record keeps the date and who changed it. That history answers most disputes without anyone digging through a phone log.
Decide what the customer sees
Customers do not need the supplier name or your cost. They need to know whether you are waiting, how long, and whether anything changed. Choose what is visible to them:
"Your part is ordered. The supplier's current estimate is Thursday."
"Your part is back-ordered. We will update you by Friday with a new date or an alternative."
"Your part is in. We expect to finish the repair today."
These updates can go out by text or email in English or Spanish, depending on the customer's preference, or appear in a simple status page they can check. The point is that the message comes from the same record the advisor sees, so the shop never gives two answers to one question.
Connect suppliers where it makes sense
Some suppliers offer order confirmations by email, online portals, or data feeds. Where they do, connected systems can pull order numbers and dates into the parts record instead of retyping them. Where a supplier only works by phone, the advisor still logs the call on the same record. The goal is not to replace your shop management software or your supplier relationships. It is to stop the status from living in five places.
Do not lose returns and cores
Wrong parts and cores are where money quietly disappears. A good parts record makes returns visible:
A daily list of parts marked "wrong or damaged" that have not been returned
Reminders before a supplier's return window closes, using the terms you record for each supplier
Core charges collected from customers matched to cores sent back
None of this requires new rules. It uses the return terms you already have and keeps them in front of the right person.
Automation first, then AI drafts a person reviews
Ordinary automation does most of the work: flag a repair order when a promised date passes, alert the advisor when a part is received, remind someone about pending returns, and send the customer an update when status changes.
AI fits where the language is messy. It can summarize a long supplier email about a delay into one line for the parts record, or draft a customer message explaining a back order in plain words. A person reviews the draft before it is sent, and AI does not change orders, promise dates, or approve substitutions.
Where to start this week
Pull every repair order currently waiting on parts. For each one, write down who ordered the part, the promised date, and where that date came from. Count how many answers required asking someone. Then agree on the status list above, or your own version, and decide which statuses customers should see.
If your shop wants parts status that advisors, technicians, and customers can all trust, TwoQM can scope it around your suppliers and the shop software you already use. Pricing explains how business apps, systems, and custom software are scoped.
Tell Us How Your Shop Tracks Parts · Explore TwoQM connected systems