FieldEdge: Parts Margin and the Hidden Costs

FieldEdge tracks parts pricing and invoiced totals. It cannot show true parts margin or per-job overhead without QuickBooks vendor bills and supply house data.

FieldEdge runs dispatch, work orders, and invoicing for HVAC contractors. The price book and parts catalog work well for billing the customer. What FieldEdge does not have is the actual cost paid for those parts this week, the freight charges from your supply house, or the overhead allocation per job from QuickBooks. Without those, parts margin is an estimate based on a static price book, not a real number from real invoices. The gap is small per part and large per quarter.

What FieldEdge Reports Actually Show

FieldEdge shows parts used per job, the price book amount billed to the customer, work order status, technician assignments, and invoice totals. The dispatch board is accurate for what was scheduled. The parts list per job is accurate for what was applied. What FieldEdge stores as the cost of each part is the cost entered when the part was added to the catalog. It is not the cost on this week's supply house invoice. When supply prices move, FieldEdge does not move with them.

The Data FieldEdge Cannot See

Real parts cost lives in the vendor bills inside QuickBooks and on the statements from Ferguson, Johnstone, Baker, or whichever supply houses you buy from. Freight, fuel surcharges, and restocking fees post to QuickBooks but never make it back into FieldEdge. Overhead per job, including truck depreciation, GPS fleet costs, and insurance, sits in the QuickBooks general ledger. The actual gross margin on a job is invoiced revenue minus burdened labor minus the real parts cost from QuickBooks minus the overhead allocation. FieldEdge has the first number. The other three live elsewhere. Contractors who try to reconcile this rebuild it quarterly in Excel and the answers arrive too late to change pricing.

Questions HVAC Contractors Owners Actually Need Answered

These are the questions HVAC owners ask when reviewing margins, pricing, and vendor contracts. Each one requires FieldEdge data joined to QuickBooks and supply house data.

• What is the actual parts margin on each job after this week's supply house cost is applied?
• Which parts have lost the most margin since the catalog was last priced?
• Which supply house gives the best landed cost after freight and restocking?
• What is the full burdened cost of each install job once overhead is allocated?
• Which technicians use the most premium-priced parts when a standard part would work?
• What is gross profit per truck per month once fuel, lease, and parts are included?

How DataBlueprint Connects FieldEdge and Answers Those Questions

DataBlueprint connects to FieldEdge through its data export and to QuickBooks through the QuickBooks Online API. It also connects to supply house portals where they expose data. From those connections it builds a Knowledge Graph that joins each FieldEdge job to the QuickBooks vendor bills for the parts used, the payroll cost for the technician hours, and the overhead allocated to the period. The connections are read-only and the Knowledge Graph builds automatically. Once it is built, you ask questions in plain English. The answer engine is a private LLM running inside your own dedicated environment on AWS Bedrock. Data stays in that environment. Every answer cites the source records used to compute it. Setup runs in one business day. DataBlueprint does not replace FieldEdge. Your dispatch, work orders, and invoicing stay in FieldEdge. DataBlueprint sits on top and answers the margin questions FieldEdge cannot answer alone.

Getting Started: Connecting FieldEdge to DataBlueprint

FieldEdge connects through its data export, QuickBooks through the Online API, and supply house portals where available. All connections are read-only. Other systems can connect in the same setup window. First answerable questions usually arrive the same business day. Two practical next steps: model the impact on your margins with the ROI calculator, then read the Concepts page for how the Knowledge Graph links FieldEdge jobs to QuickBooks cost data.

Frequently Asked Questions

Does DataBlueprint change anything inside FieldEdge?

No. The connection is read-only. DataBlueprint reads work order, parts, dispatch, and invoice data from FieldEdge. It does not write, modify, or delete records inside FieldEdge.

Why does FieldEdge not show true parts margin?

FieldEdge stores the cost entered into the price book. Real parts cost lives in QuickBooks vendor bills and supply house statements and changes every week. Without joining those data sources, margin is a static estimate, not a current number.

How does DataBlueprint handle freight and restocking fees?

Freight, fuel surcharges, and restocking fees post as QuickBooks vendor bill line items. The Knowledge Graph allocates those costs back to the jobs that triggered the supply house order, so landed cost per job is accurate.

Can I see margin per truck instead of per job?

Yes. The Knowledge Graph rolls job-level cost up to the technician, truck, or branch level. You can ask for gross profit per truck per month and trace back to the underlying jobs.

Does DataBlueprint replace FieldEdge?

No. FieldEdge continues to run dispatch, work orders, and invoicing. DataBlueprint reads from FieldEdge and from QuickBooks to answer questions neither system can answer alone.