How many parts did your shop install this month that never made it to an invoice? If you're running more than 80 work orders a month and you genuinely don't know, the problem isn't your mechanics' discipline. It's that the generic system wasn't built for the way your shop actually works.
The Breaking Point
Shop management platforms like TallerOS or Vehix handle the core flow well: appointment → work order → estimate → payment. For a one-mechanic operation with twenty jobs a month, that's more than enough.
But as volume grows, that flow starts breaking at the edges. Not all at once — quietly. A part a mechanic jotted on paper because the system was slow. A commission you calculated in your head because the job type was out of the ordinary. A spreadsheet export you sent to your accountant at month-end that nobody could quite reconcile with the tax authority's records.
Picture a shop with five mechanics running a hundred work orders a month — diagnostics, routine service, warranty work, and body repair. Each job type has different labor pricing, and each mechanic earns a different percentage depending on what they're working on. The SaaS logs the orders fine. But commissions get calculated in a separate spreadsheet, parts get manually deducted from stock at the end of the day, and accounting is handled by whoever exports a file that never quite matches the format from the previous period. That's not a poorly run shop. That's a shop that grew faster than its software.
What Generic Software Gets Wrong
Automatic Parts Deduction Against the Work Order
This is the most expensive gap, and the easiest one to rationalize away. Generic systems log a part when someone enters it into the estimate. But if a mechanic pulled that part before the estimate was approved — because the car was already on the lift and the fix was obvious — that part left the shelf without leaving a trace in any system.
At month-end, the inventory difference feels like normal shrinkage. It isn't. It's money that walked out the door and never showed up on any invoice.
What actually solves this is tying the parts deduction to when the mechanic uses the part, not when an admin types it in. That means mechanics need to log from the floor — ideally from a phone — and that action needs to trigger the stock update automatically.
Supplier Pricing That's Actually Current
Generic platforms give you a "part cost" field. You fill it in manually. But if you work with two or three suppliers whose price lists change every couple of weeks, that field is always out of date by the time you close the job.
The fix is a direct integration: the system pulls the current price from your supplier when you open the work order, not after the job is done. Some suppliers have APIs. Others send updated lists by email or PDF. Not everything can be fully automated, but some level of integration is always possible and always makes a difference.
Commissions by Job Type and by Mechanic
This is the pain point that comes up most in shops with more than three mechanics. Everyone has a different arrangement, and specialized work pays differently than a routine oil change.
Generic software gives you one fixed percentage per mechanic. Everything else you calculate separately, in a spreadsheet that someone updates — or doesn't.
A custom commission module calculates the payout automatically when the work order closes. It cross-references job type with the assigned mechanic and spits out the number, ready for payroll. No magic — just a rules table the system applies on its own.
End-of-Day Closing That Actually Connects to Accounting
This is the weak spot for almost every shop management platform in the market. Some offer exports, but the format shifts, periods don't always close cleanly, and the accountant ends up doing half the work manually anyway.
What makes sense to build is a daily closing module that consolidates payments, withholdings, and invoices in exactly the format your accountant needs — or connects directly to whatever accounting system they're already using. Fewer exports. Less friction. Fewer typos that surface three months later during an audit.
What's Worth Building and What Isn't
Not every gap justifies a full custom build from scratch. A completely bespoke system — built on nothing — is expensive to make and even more expensive to maintain.
What does make sense is building on top of what already exists. If the shop uses a platform for appointments and work orders, there's no reason to throw that away. It makes more sense to add a custom inventory module that talks to it, or a supplier integration that keeps prices current, or a commission dashboard that pulls closed work orders and runs the math automatically.
That's what actually moves the needle: not replacing the system, but closing the gaps where money is leaking out.
How This Gets Started
The first step is mapping the shop's real workflow — not the one described in the SaaS manual, but the one mechanics actually follow every day. The gap between those two things is where the problem lives.
Then it's about identifying which gap costs the most. Not the most annoying one — the most expensive one. Usually it's inventory or commissions, but it depends on the shop.
With that clear, Cambalache runs a two-week Validate at a fixed price: we map the specific process, define what gets built, and deliver the scope, price, and delivery date in writing. If the project moves forward, the code lives in your GitHub from day one and there's a demo every Friday.
Nothing needs to get thrown out. You just need to know exactly where the money is slipping through, and close it for good.
