Warranty claim software for any DMS
Quick answer: Forge is warranty claim software that reads repair orders from any dealership management system. Because intake is the document rather than a wired connection, the system your store runs is not a gate: Forge reads the repair order, drafts the claim against your OEM portal's rules, and leaves the DMS untouched.
Warranty vendors publish compatibility lists because their intake depends on a connection someone had to build. When intake is the repair order, the list stops being the interesting question and a different one takes its place: does the tool understand what your manufacturer will and will not pay for?
What warranty work runs into on any other DMS
What a store runs into no matter which system printed the repair order, rather than anything one vendor's layout does.
Compatibility lists that decide the shortlist
A store on a system outside the big four gets used to being told it is on the roadmap. That is a fact about how the vendor built its intake, not about how hard your claims are. The work of picking the right operation, checking coverage, and writing a narrative the manufacturer accepts is identical whatever printed the document.
Integrations that have to exist before anything can start
Where intake depends on a built connection, going live means a vendor project, an IT schedule, and a dependency on your DMS vendor's cooperation and pricing. Every one of those is a place the rollout stalls, and none of them changes what the manufacturer pays for the repair.
Groups running four systems and four processes
A group that has grown by acquisition usually runs several systems at once, and ends up with a different warranty process per rooftop because the tooling forced it. The process should be one process, with the OEM portal as the thing that varies, not the DMS.
The manufacturer's rulebook, on every system
Published labor times, coverage windows, campaign requirements, and narrative rules belong to the manufacturer and are not carried by any dealership management system. Whichever one you run, someone at your store is looking them up by hand, one repair order at a time.
How Forge works alongside any other DMS
No wiring project, and nothing written back into the DMS.
- 01
Print or export it — do not scan it
Whatever your system is, have it produce the repair order as a document rather than photographing a paper copy. A print or export carries its text; a scan carries pixels, and everything on it has to be guessed at from the image. That single choice matters more to how well this works than which vendor's logo is on the software.
- 02
Forge reads the document it is given
Labor lines, operation codes, parts, the technician's narrative, and punch data are read off the repair order. Layouts differ by system, and the fields a manufacturer adjudicates against are on all of them.
- 03
Forge drafts the claim against the manufacturer's rules
Published labor times are looked up, coverage and open campaigns are checked against the VIN, the correction is written to what the manufacturer will accept, and the allowances the repair supports are surfaced rather than left for someone to remember.
- 04
One review queue, however many systems you run
Claims from every rooftop arrive in the same place, in the same shape, whatever printed them. A group running four systems reviews one queue rather than four, and a store that changes DMS next year does not change anything about this step. Clean claims file or hold for approval, and nothing is written back anywhere.
any other DMS repair orders at a glance
What changes between dealership management systems, and what does not.
| Part of the job | Changes with the DMS | Stays the same |
|---|---|---|
| Getting the repair order | Where the warranty copy prints or exports from, and what it is called. | That the document carries the labor, parts, narrative, and punch data a claim is built from. |
| Reading the repair order | The layout: how jobs are identified, where the correction sits, how parts are printed. | The fields the manufacturer adjudicates against. |
| Picking the operation | Nothing. The DMS does not publish labor times. | The manufacturer's published operation and allowance for the repair. |
| Checking coverage | Nothing. Coverage is the manufacturer's, per VIN. | Warranty start, coverage windows, and open campaigns. |
| Filing the claim | Whether your store files from inside the DMS or in the OEM portal. | That the manufacturer decides what the repair order is worth. |
any other DMS terms
The vocabulary a warranty administrator on any other DMS works in.
- DMS
- Dealership management system. The software a store runs its accounting, sales, parts, and service on.
- Warranty copy
- The copy of a repair order a store files a claim from. Named and printed differently on each system.
- OEM portal
- The manufacturer's claim system. Where the claim is adjudicated, and the thing that actually varies between your stores.
- Causal part
- The part that caused the failure. The manufacturer adjudicates against it, so it has to agree with the operation claimed.
- Correction narrative
- The written account of what was done and verified. Adjudicated alongside the codes, on every system.
- System of record
- The system that owns the truth about the repair. That is your DMS, and Forge does not change it.
Frequently Asked Questions
- Does Forge work with our DMS?
- Yes. Forge reads repair orders from any dealership management system, because intake is the document rather than a wired connection. Your administrators upload the repair order, Forge drafts the claim against your OEM portal's rules, and nothing is written back into the DMS. There is no compatibility list to be on.
- What has to be built before we can start?
- Nothing. That is the whole argument of this page. A warranty tool that reads your database has to be connected to it first, and that connection is the vendor project, the IT ticket, and the dependency on your DMS vendor's cooperation and price list. A tool that reads the repair order skips all three, which is why going live is measured in an hour rather than a quarter.
- What happens to our DMS while Forge is running?
- Nothing changes in it. Forge reads repair orders and prepares claims for the OEM portal; it does not reprice, close, post, or write to your system in any way. Your DMS stays the system of record and your accounting office reconciles against the same numbers as before. It also means there is nothing to unwind if you stop.
- Our group runs four different systems. Can we use one process?
- Yes, and that is usually the point. Because Forge does not depend on a connection into any particular system, every rooftop works the same way regardless of what it runs. What varies across the group is the OEM portal each store files through, which Forge handles per brand.
- What if our repair orders are scanned images rather than exports?
- Print or export the repair order from your DMS rather than scanning a paper copy. A scan carries no text layer, so everything on it has to be recognised from the image, and accuracy drops on exactly the fields that matter — part numbers, operation codes, and the technician's narrative. Any system that prints to PDF gives you a document Forge reads cleanly.
- Does Forge submit claims for us, or do we stay in control?
- Both are available and your store picks. Forge can file a claim as soon as it passes the pre-submission checks, or hold every one for your warranty administrator to approve first. Claim ownership does not leave the building on either setting; what comes off the desk is the retyping and the lookups that come before the decision.
Other systems
Contact
Let's get you set up.
Tell us about your dealership and your current warranty workflow. We'll reach out within one business day to schedule a personalized walkthrough.