CARFAX — on the roadmap
Not built yet: your work on the vehicle history.
This one is a plan, and the page says so before it says anything else. The idea is that the film or coating you installed shows up on the vehicle's own record — proof for the next owner, and a mark of a shop that documents what it fits. None of it ships today.
- Status
- Coming soon
- Data
- Service VIN → tool
- Category
- Vehicle data
The short answer
What does the CARFAX integration actually do?
- Where it stands: Coming soon.
- Which way the data moves: Service VIN → tool.
- Push completed services to CARFAX Service History
- VIN-matched from the job's vehicle
- Automatic on job completion — no re-entry
Bottom line: CARFAX is on the roadmap. There is no adapter, no connection and no setup page — the button on the connector registers that your shop wants it, and demand is genuinely how the order gets decided. Everything described below is future tense.
Why connect CARFAX
Send service records straight to the vehicle history.
Report the PPF or ceramic work you did to CARFAX Service History, so it shows on the vehicle record — proof for the next owner and a mark of a pro shop.
Completed services would reach the vehicle record
The intent is for the PPF or ceramic work you finished to post to CARFAX Service History, so it appears on the vehicle and not only in your files. Not built.
VIN-matched from the job
The VIN is already on the job's vehicle, so the match would come from a record you keep anyway rather than from re-typing. Not built.
Automatic on completion
The intent is that finishing the job is the whole action, the way the review request already works. Not built.
What ships
What you can do once it’s connected
- 01Push completed services to CARFAX Service History
- 02VIN-matched from the job's vehicle
- 03Automatic on job completion — no re-entry
How it works
Setting it up, in order
Register the demand
The connector's button records that your shop wants this. That's the only thing it does today, and pretending otherwise would be a door with nothing behind it.
Keep the VIN on the job
Nothing to configure. Service VIN's vehicle records are VIN-first already, so the data this would need is a by-product of quoting the work.
Watch the badge
The status on this page is read from the product's own registry. When it stops saying On the roadmap, it's because something shipped.
How connecting works, written up step by step: The integrations hub: connect your tools.
FAQ
CARFAX, answered
Does Service VIN report to CARFAX?
No. CARFAX is on the roadmap and nothing is built: no adapter, no connection, no setup page. The connector exists so a shop can register that it wants it, and the badge on this page says On the roadmap rather than dressing a plan up as a feature.
When will it ship?
There's no date, and inventing one would be worse than saying so. Demand is how the roadmap order actually gets decided, which is why the button registers it rather than pretending to connect.
What can I do in the meantime?
The work is already documented inside Service VIN: the job carries the VIN, the film, the photos and the warranty, and the customer's own portal shows them that record. What's missing is the hand-off to a third party's history file, not the record itself.
Why show a connector for something that doesn't exist?
Because the alternative is a shop asking for it and nobody hearing. It's badged On the roadmap, its button says so, and no part of this page implies you can connect it today.
Or start smaller
The call you missed is the job you lost.
Every missed call answered in seconds. The quote you promised, drafted before you hang up. Booked straight into your calendar.
It answers from your real services, your real prices and your real calendar — and writes the booking into them. No migration, no data to move — it runs beside whatever you use today.
Run the whole shop.
Quotes, bookings, film inventory and the AI crew in one login. CARFAX is not connectable yet — everything else here is, on the free trial, before you decide anything.
Coming soon · Service VIN → tool