Parts ordering still takes ten minutes per ticket because the job is actually five jobs stacked on top of each other, and most shops do them in four different windows. You decode the VIN in one place, look up the labor time in a second, search the parts catalog in a third, then retype the part number, the cost and your markup into the estimate in a fourth. Nothing is wrong with your service writer. The sequence is wrong. When the VIN, the MOTOR labor times, the parts catalog and the estimate all live on one screen, picking a part puts a priced line on the ticket, and the ten minutes turns into about one.
What actually happens between the VIN and the purchase order?
Walk the real sequence. Not the version in the software demo. The version at 8:40 in the morning with three cars in the lot and the phone ringing.
- VIN. The writer types or scans the VIN. Year, make, model, engine. Sometimes the engine option is ambiguous and they go look at the car.
- Labor time. Open the labor guide. Search the operation. Find the right line, the right note, the right combination of overlap.
- Part choice. Open the parts catalog. Retype the vehicle, because the catalog does not know what the labor guide knows. Search the part. Compare three suppliers.
- Price. Take the cost. Apply the markup. Maybe from a printed matrix taped to the desk. Maybe from memory.
- Back to the estimate. Type the part number, description, cost, sell price, quantity. Repeat for the hardware, the fluid, the shop supplies.
- Order. Go back to the supplier, build the cart again, place the order, write down the PO number somewhere.
Six steps, and the vehicle gets identified three separate times. That is the whole problem in one sentence.
Where exactly do the minutes leak?
Re-entering the vehicle
Every tab that does not share a VIN costs you thirty to sixty seconds and one chance to pick the wrong engine. Pick the wrong engine and you do not lose a minute, you lose a return trip and a credit memo.
Labor time lookup as a separate errand
If your labor guide is a different login, the writer either goes and gets the number or guesses it. Guessing is faster today and expensive this quarter. Published MOTOR times belong in the same screen where the line is being written, not in a browser bookmark.
Catalog tab hopping
Three suppliers, three carts, three price screens. Comparing availability across them by eye is where the biggest chunk of the ten minutes goes, and it is the part a writer cannot do while a customer is standing at the counter.
Manual markup
This is the quiet one. A writer under pressure rounds. A fifteen dollar part gets sold at thirty because thirty is a round number, when your matrix says it should be forty two. Nobody notices on one ticket. Everybody notices at the end of the month.
Typing the part back onto the ticket
Copy, paste, copy, paste. Part numbers with letters and dashes. Then the same numbers again into the supplier cart to actually order. Two chances to fat finger a digit.
What does it look like when it all lives in one screen?
In Pista the ticket starts from the VIN and a sentence. The AI service writer turns "2019 F-150, pulling right, noise over bumps" into a drafted repair order with the right operations on it. The vehicle is already identified, so the labor guide and the catalog already know what car they are looking at.
From there, PartsTech parts ordering is inside the estimate, not beside it. Your suppliers, your account pricing, live availability. You pick the part, the line lands on the ticket with the cost, the sell price and the description already filled in. MOTOR labor time attaches to the operation at the same moment. You order from the same screen and the PO stays attached to the ticket.
Then you talk to the RO. Ask it to add a brake fluid flush, or to re-quote with the economy line, or to split the job into a today ticket and a next visit ticket. You do not go find another screen.
| Step | Four separate tools | One screen in Pista |
|---|---|---|
| Identify vehicle | Typed 3 times | VIN once |
| Labor time | Separate login or a guess | MOTOR times on the line |
| Parts search | Hop between supplier sites | PartsTech inside the estimate |
| Pricing | Mental math or a taped sheet | Parts matrix applies automatically |
| Put it on the ticket | Copy and paste | Click, line is written |
| Send to customer | Export, attach, email | Text with photos, approve on the phone |
How does a parts matrix protect gross margin?
A parts matrix is a set of markup rules by cost band. Cheap parts carry a higher multiplier because the handling cost is the same whether the part is nine dollars or nine hundred. Expensive parts carry a lower multiplier so the ticket stays sellable. Set it once and it runs on every line your writers build, including the ones they build at 5:45 on a Friday.
That is the mechanism behind the 68.9% gross margin shops running Pista see. Not a sales tactic. A default. The matrix prices the line before anyone has a chance to round down, and the reports show you margin by ticket, by writer and by job type, so a leak shows up in days instead of at tax time.
The second protection is accuracy. Published labor times mean the hours on the ticket match the hours in the bay. A matrix on parts plus a real labor guide is most of your gross profit, decided before the car goes on the lift.
What does the time actually buy you?
Say you write twelve tickets a day and you save eight minutes on each one. That is more than an hour and a half back at the front counter, every day. That hour and a half is the difference between a digital inspection that gets sent with photos and one that gets summarized over the phone, and between a declined job that gets a follow up text and one that disappears.
It also changes who can write a ticket. When the parts, the labor time and the pricing are handled by the system, a newer writer produces the same estimate as your best one. Across 3,200+ customers managed and 2,600+ repair orders written on Pista, that consistency is what owners notice first.
The answered phone matters too. The phone system with an AI receptionist sits inside the ticket, so the call about the part that was supposed to arrive today does not pull a writer off the screen they are already in.
Ten minutes per ticket is not a staffing problem. It is four logins pretending to be one workflow.
What to do this week
- Time three tickets. Stopwatch from VIN entry to purchase order. Write down where the writer switched tabs. You will have your answer in twenty minutes.
- Pull last month's parts margin by cost band. Look at everything under fifty dollars in cost. That is where rounding lives.
- Write your matrix down. Four or five cost bands with a markup for each. Even on paper, it beats memory.
- Check that your labor times are published, not habits. If your writers are quoting from experience, you are selling last year's prices.
- See it on one screen. Book a call and have a Pista expert build an estimate on one of your real VINs. Setup runs 24 to 48 hours, migration is free, and the first 30 days are free. Pricing is $149, $299 or $499 per shop per month with unlimited users.