Appliance Repair Data Model — Assets & Claims | FieldCamp

How an appliance repair business runs in FieldCamp — serviced appliances and warranty claims layered on the core Job, Visit, Estimate, and Invoice records.

FieldCamp runs an appliance repair business on one connected set of records that works on day one and bends to how your shop actually operates.

Most of the work — the customer book, scheduling, dispatch, Estimates & Invoices, payments, and the parts catalog — is already covered by FieldCamp's core records. A repair business runs on that backbone the moment it signs up.

What makes appliance repair its own trade is the layer on top: the individual appliance you service across years, and the warranty claim you file to get paid. Both are added as custom records built on the same engine that powers everything else.

FieldCamp works for any size, from a single-truck operator to a multi-location franchise, residential or commercial — and everything here can be tailored.

What the core already gives you

An appliance repair shop uses most of FieldCamp's core records exactly as they ship, with no rebuild.

Customers — homeowners and commercial accounts both fit, with separate property and billing addresses, lead source, and preferred techs.
Requests — the inbound call, online booking, or home-warranty dispatch, with one-click convert to an estimate, job, or invoice.
Estimates & Invoices — including the Good / Better / Best quote for the "repair vs. replace" conversation, deposits, payment terms, and card capture.
Jobs — the work order, as a one-off, multi-day, or recurring job, with the full draft-to-paid lifecycle.
Visits — the diagnostic trip and the return "parts" trip, each with check-in location, a captured signature, photos, and logged hours.
Price Book — parts and labor with cost and price, plus truck stock, reorder thresholds, vendor pricing, and purchase orders.

On-site capture — the diagnostic checklist, the nameplate model and serial photo, and the pre-existing-damage waiver — is handled by job forms on the visit, not by extra fields.

The diagnostic checklist, nameplate capture, and the signed damage waiver are on-site job forms attached to a Visit. They are part of the field work, so the appliance and claim records stay focused on the asset and the money.

What appliance repair adds

On top of the core records, the appliance repair setup adds two records that define the trade — the serviced appliance and the warranty claim — plus two optional helpers.

Each one is a custom record built on FieldCamp's customization engine, with its own fields, its own links to the core records, and its own page layout.

Serviced Appliance

The Appliance is the central record of the whole trade — the individual unit you service across its life and many jobs.

It stands on its own so it survives independent of any single job, and it links to many jobs to build a multi-year service history.

It carries the appliance type, brand, model number, serial number, a nameplate photo, install date, warranty status, warranty expiry date, its location at the property, and notes.

Field	What it holds
Appliance type	Refrigerator, washer, dryer, dishwasher, oven/range, microwave, AC/HVAC, or other.
Brand / manufacturer	The maker of the unit, as text or a link to a Manufacturer record.
Model number	The model printed on the nameplate.
Serial number	The unit's serial.
Nameplate photo	A picture of the model and serial tag.
Install / purchase date	When the unit went in.
Warranty status	In warranty, out of warranty, extended, or home-warranty covered.
Warranty expiry date	When coverage ends.
Location at property	Where the unit sits, such as "kitchen" or "unit 4B".

An Appliance belongs to one Customer, links to the many Jobs that serviced it, and links to the Warranty Claims raised against it.

Its page is built from a header, the field group above, an asset card for serial and warranty details, a service-history list, a related table of linked jobs, a files section for the nameplate and manuals, and a timeline.

An Appliance can carry a light two-stage workflow — Active to Retired/Replaced — for shops that want to mark a unit as decommissioned. Most accounts run the appliance with no workflow at all and simply keep its history.

Warranty Claim

The Warranty Claim is the defining record of warranty and commercial work — a claim filed against a manufacturer or home-warranty company for reimbursement.

It stands on its own with its own list view and lifecycle, and links into the job and appliance it came from.

It carries the claim number, the authorization or dispatch number, the claim type, the warranty company, the date of service, the filing deadline, the labor, parts, and sublet amounts claimed, a calculated total claimed, the amount reimbursed, the required nameplate and waiver attachments, and a rejection reason.

Field	What it holds
Claim number	The claim's reference number.
Authorization / dispatch #	The number the warranty administrator requires.
Claim type	Manufacturer, home-warranty company, or extended plan.
Warranty company / administrator	The payer, as text or a link to a Manufacturer record.
Date of service / completion	When the work finished — drives the filing countdown.
Filing deadline	The date the claim must be filed by.
Labor / parts / sublet claimed	The amounts claimed in each bucket.
Total claimed	Labor plus parts plus sublet, calculated for you.
Amount reimbursed	What the payer actually returned.
Nameplate photo · signed waiver	The required claim attachments.
Rejection reason	Why a claim was turned down, if it was.

A Warranty Claim belongs to the Job it came from, the Appliance that was serviced, and the Customer, and it can point at the Manufacturer that pays it.

Its page is built from a header, a status banner for approved or rejected, the field group above, a money summary of claimed versus reimbursed, a files section for the waiver and nameplate, a link back to the parent job, a timeline, and a record history.

Manufacturer and Parts on Order

Two optional records round out the setup:

Manufacturer / warranty company — a small shared list of OEMs and home-warranty companies (GE, Samsung, Whirlpool; American Home Shield, Cinch, 2-10) so claims and appliances point at one deduped payer record instead of free text. It holds the payer name, type, claims portal link, claims phone and email, the filing window in days, and reimbursement notes. Skip it if the shop does almost no warranty work and keep the maker as text on the appliance.
Parts on Order — a light record under a Job for the special-order part that drives a return visit. It holds the part, quantity, vendor purchase-order number, an order status from "to order" through "received", the expected arrival date, and the cost. Many shops do not need it — core inventory purchase orders and a job's on-hold stage already cover the "waiting for parts" case.

How these records connect

The Appliance sits at the center: a Customer owns many appliances, and each appliance is serviced across many Jobs and carries the Warranty Claims raised against it.

The claim ties the job, the appliance, and the payer together so the money and the asset stay connected.

FieldCamp stores the claim, its authorization number, and its attachments as the system of record. Sending the claim to a manufacturer or home-warranty portal stays a manual or portal step — FieldCamp holds the record, it does not file the claim for you.

The warranty claim lifecycle

The Warranty Claim moves through an approval workflow with its own stages and guardrails, so a claim cannot advance until the required information is captured.

A claim starts as Draft, becomes Filed once it leaves your shop, and ends at Reimbursed when the payer settles. A rejected claim can be reopened and revised back to draft.

Each move has guards drawn from the stages and workflows engine:

File claim

Moving from draft to filed requires the authorization number and date of service, plus the nameplate photo. On the warranty path it can also require the signed damage waiver.

Mark reimbursed

Closing the claim requires the amount reimbursed, with an optional confirmation prompt.

Reject

Rejecting a claim requires a rejection reason, so the record always says why.

The claim can also create itself. When a job marked as warranty work reaches Completed, FieldCamp can open a draft claim automatically, and it can notify the office as the claim is filed, approved, or rejected.

Date-based reminders — alerting you a set number of days before a filing deadline — come from FieldCamp's separate workflow automation product, not from the claim record itself. The claim stores and shows the deadline; the reminder is configured alongside it.

Residential vs. commercial

The same records serve both residential and warranty/commercial work. The difference is configuration — which stages, fields, and links are required — not a separate set of records.

The switch is a service-type marker on the Job (residential, commercial, or warranty), paired with toggles on the claim workflow that turn the warranty requirements on or off.

Residential

A homeowner pays by card on site, and the warranty claim is rarely used — most work is out-of-warranty cash repair. The Appliance record still earns its keep as the repeat-customer history. Parts are often truck stock and the job is a one-trip fix.

Warranty / commercial

The manufacturer or home-warranty company pays, so the Warranty Claim is the core of the job, filed with an authorization number against the payer. The appliance's warranty status drives whether the work is billable or claimable, the signed waiver is usually required, and OEM parts are more likely special-ordered for a return visit.

Because the split is a marker on the job plus workflow toggles on the claim, you require the waiver and authorization number only on the warranty path — with no duplicate set of records to maintain.

The crew side flexes the same way. A single-truck operator runs one tech across every Visit; a multi-location franchise assigns Visits across teams and locations using the same Job and Visit records.

Built for any size. A one-person repair shop and a multi-location warranty operation run on the same backbone. The Appliance and Warranty Claim records, the approval workflow, and the parts-on-order helper are there whether you run one truck or fifty.

Built on the customization engine

Everything above is built from the same engine that powers the rest of FieldCamp — nothing here is a one-off.

The Appliance, Warranty Claim, Manufacturer, and Parts on Order are custom objects and fields, the claim's approval lifecycle is a stage and workflow with required-field and required-attachment guards, and each record page is assembled from record layouts.

That means the model is a starting point, not a ceiling: add your own fields, rename or reorder the claim stages, and arrange each page to match how your shop actually runs.

Jobs

The work order the claim and parts attach to — line items, scheduling, and status from draft to paid.

Visits

The diagnostic and return trips, with dispatch lifecycle, signatures, and on-site forms.

Estimates & Invoices

Good / Better / Best repair-vs-replace quotes and the invoices and payments that follow.

Custom objects & fields

How the Appliance and Warranty Claim records are built on FieldCamp's engine.

Coming from Housecall Pro

Most appliance repair shops on Housecall Pro can bring their structure into FieldCamp directly — customers, the jobs and appointments, estimates and invoices, the price book, and the service plans all have a home here.

The difference is that in FieldCamp you own and shape the model, rather than fitting your shop to a fixed one. You also get a place to track the appliance itself as an asset and the warranty claim as its own record.

In Housecall Pro	In FieldCamp	Notes
Customer	Customers	The homeowner or commercial account, with separate property and billing addresses and service history.
Job	Jobs	The work order — one-off, multi-day, or recurring, from draft to paid.
Estimate / Invoice	Estimates & Invoices	Quoting with Good / Better / Best for repair vs. replace, deposits, and payments.
Schedule / appointment	Visits	The diagnostic trip and the return parts trip, with dispatch, check-in, and sign-off.
Price Book (services / materials)	Price Book	Parts and labor with cost and price, truck stock, and vendor pricing.
Employees / technicians	Team Members	Carry skills and service areas, and are the target for job and visit assignment.
Service Plan / recurring service	Service Agreements	The recurring plan, with visit frequency, renewal date, and plan price.
Appliance serviced	Equipment	The individual unit, tracked as an asset with a multi-year service history.
Warranty coverage	Warranties	Coverage tied to the appliance, with expiry tracking — plus a warranty claim record for reimbursement work.
Payment	Recorded on the Invoice	Partial and full payments, with overdue tracking and card capture.
Parts on a job	A line item, or the Parts on Order helper	Special-order parts that drive a return visit are tracked on the job.

What you gain. In Housecall Pro the structure is set for you — the objects, their fields, and how they relate are fixed.

In FieldCamp every one of those records is yours to rename, extend, restage, and relayout, so you can match your old setup first and then go past it with custom objects and fields and your own stages and workflows.

The appliance-as-asset and the warranty claim are two records most shops add right away.

One honest difference. Housecall Pro ships built-in service plans with a recurring-billing engine that charges the card on file on its own schedule.

FieldCamp models the plan itself as a Service Agreement that schedules the next maintenance Job and carries the renewal date and plan price; the recurring billing runs through the standard invoice flow rather than a separate subscription engine.

In return, FieldCamp adds the appliance-as-asset and the warranty claim — structure Housecall Pro keeps lighter — so the unit's history and the reimbursement money each get their own record.

If automatic subscription charging is central to how you bill, plan that part of the move deliberately.