SubarunetOnboarded on requestSubaru warranty claim software for retailers
Quick answer: Forge is warranty claim software for Subaru retailers. It reads repair orders, matches labor to the Subaru Labor Time Guide, and flags coverage questions and claims that need a helpline call before they are filed. Forge can submit through Subarunet on its own, or hold the claim for your warranty administrator to approve first: your store decides.
Subaru asks for a coverage inquiry before the inspection, not after the repair. That single habit decides whether a warranty extension gets claimed or quietly gets written off as customer-pay, and it is the habit that slips first when the drive is full.
Where Subaru claims go wrong
Common failure modes on Subaru repair orders, drawn from Subaru's published claim requirements.
Repairs started before the coverage inquiry
Subaru's instruction on extension work is to run a Vehicle Coverage Inquiry on Subarunet to confirm eligibility before any inspection or repair begins. Done afterward, the inquiry only tells you what you should have claimed. Done first, it decides how the repair order is written.
Claims filed without the call the bulletin asked for
Some Subaru work requires contacting the claims helpline before submission. A retailer who does not know that requirement applies to a given repair submits in good faith and gets the claim returned, then spends the round trip learning what the bulletin said.
Labor times taken from anywhere but the Labor Time Guide
Subaru publishes the labor time and the claim submission information for a repair, frequently inside the bulletin that governs it. Working from a generic guide or from clocked time produces numbers that do not match, which surfaces as an adjustment rather than a rejection.
Bulletin-specific claim coding treated as ordinary warranty
Extension and campaign bulletins carry their own claim submission instructions. Filing that work under standard coding is one of the more common ways a covered Subaru repair fails to pay as expected.
How Forge prepares a Subaru claim
Forge is not live on Subaru yet. This is the workflow Forge runs at the portals it operates today, mapped to Subaru's published requirements.
- 01
Upload the repair order
Drop the Subaru repair order into Upload. There is no DMS integration project and nothing for an IT vendor to schedule. Forge reads the labor lines, part numbers, technician narrative, and punch data straight off the document, whichever DMS your store runs.
- 02
Forge checks coverage against the VIN
Coverage, open campaigns, and applicable warranty extensions are pulled for the VIN while the repair order is still open, so eligibility drives how the repair is written rather than being discovered afterward.
- 03
Forge drafts the claim and flags the exceptions
Labor lines are matched to the published Labor Time Guide operation for the repair performed, bulletin-specific claim coding is applied where a bulletin governs the work, and repairs that call for a helpline contact are raised before submission.
- 04
Forge submits, or your administrator approves first
Exceptions come back with the reason attached. Clean claims go out through Subarunet on their own, or under your administrator's review if your store keeps that step.
Subaru claim rules at a glance
Subaru warranty requirements that decide whether a claim pays as filed.
| Requirement | What Subaru expects | What goes wrong |
|---|---|---|
| Vehicle Coverage Inquiry | Run on Subarunet before any inspection or repair on extension work. | Coverage checked after the repair, when it can no longer change anything. |
| Helpline contact | A call to the claims helpline before submission where the bulletin requires it. | A good-faith submission returned, and the requirement learned the hard way. |
| Labor Time Guide | The published operation and time, often specified in the governing bulletin. | Time taken from a generic guide or from the clock. |
| Bulletin claim coding | The claim submission information published with the extension or campaign. | Bulletin work filed under ordinary warranty coding. |
| Narrative | A complaint, cause, and correction that stands on its own on audit. | A comment written for a reader who was in the shop. |
Subaru warranty terms
The vocabulary a Subaru warranty administrator works in every day.
- Subarunet
- Subaru's retailer portal. Warranty claim submission, coverage inquiry, and technical information.
- Vehicle Coverage Inquiry
- The Subarunet check confirming a VIN's eligibility. Subaru asks for it before inspection or repair on extension work.
- Labor Time Guide
- Subaru's published labor times. Bulletins routinely name the operation and claim information to use.
- Retailer
- Subaru's term for its franchised dealerships. Subaru documentation uses it in place of dealer.
- Claims helpline
- Subaru's pre-submission contact for claims where a bulletin directs the retailer to call first.
- STIS
- Subaru technical information. Bulletins, procedures, and the documents that govern extension work.
Frequently Asked Questions
- What is Subaru warranty claim software?
- Subaru warranty claim software reads repair orders and prepares warranty claims for a Subaru retailer. Forge matches labor to the Subaru Labor Time Guide and flags coverage questions and claims that need a helpline call before they are filed. Forge can submit through Subarunet on its own, or hold the claim for your warranty administrator to approve first: your store decides.
- Does Forge submit our warranty claims for us?
- Yes, if you want it to. Forge can send a claim to the portal as soon as it passes the pre-submission checks, or hold every claim for your warranty administrator to approve first. Your store sets which, so claim ownership stays exactly where you want it, and either way the repetitive entry and the checking come off the desk.
- Is Forge live on Subaru today?
- Not yet. Forge runs Ford, CDJR, and Toyota portals in production today, and Subaru is onboarded on request. Onboarding is a defined process rather than a promise: portal access, your warranty policy manual, a set of recent paid claims with their outcomes, and sample repair orders from your DMS. Tell us you are a Subaru store and we will scope it with you.
- When should a Subaru retailer run a Vehicle Coverage Inquiry?
- Before the inspection or the repair, not after. Subaru's instruction on warranty extension work is to confirm eligibility on Subarunet first, because the answer changes how the repair order is written. Run afterward, the inquiry only tells you what could have been claimed.
- Why would a Subaru claim need a helpline call before submission?
- Certain bulletins direct the retailer to contact the claims helpline before filing. The requirement lives in the bulletin governing that repair rather than in the claim screen, which is why it is so often missed by an admin working quickly and in good faith.
- Do we need a DMS integration to use Forge?
- No. There is no DMS wiring and no IT project. Your admins upload repair orders, and Forge works alongside CDK, Reynolds and Reynolds, and other DMS setups. Most dealerships are live in under an hour.
Sources
Forge has not run Subaru in production yet, so the portal detail on this page is drawn from public documentation rather than from claims we have filed.
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.