Add Parts and Materials

How to add parts and materials to your pricebook with pricing, cost tracking, SKU codes, and unit configuration.

Written by Chloe NguyenUpdated over a month ago2 min readBeginner

What this guide covers

This guide explains how to add parts and materials to your pricebook. Parts represent physical items like "Water Heater 50gal" or "HVAC Filter 20x25x1" that you sell or install as part of a job.

Before you begin

You need Admin or Owner permissions.
Gather the part name, customer-facing price, and internal cost.

Adding a part

Navigate to /pricebook.
Click the Parts tab.
Click Add Part in the top-right corner.
Fill in the required fields:
- Part Name -- a clear, customer-facing name.
- Description -- details about the part, including brand or model number.
- Default Price -- the unit price charged to the customer.
- Unit -- "each," "box," "linear foot," or custom.
Optionally set:
- Cost -- your internal purchase cost (not shown to customers).
- SKU -- stock-keeping unit code for inventory reference.
- Category -- organize with related items.
Click Save.

Screenshot: The Add Part form with fields for name, description, price, cost, SKU, and unit.

Why track cost

The Cost field is optional but strongly recommended. When set:

JobsiteOn calculates part margins on reports.
You can see which materials are most profitable.
Profitability analysis includes both labor and material costs.

SKU codes

SKU codes help you:

Cross-reference parts with your supplier catalog.
Quickly identify items when reordering.
Search for parts by code in addition to name.

Tip: If you source the same part from multiple suppliers at different costs, create one pricebook entry with your average cost. Update it quarterly when supplier pricing changes.

What happens next

The part appears in the pricebook list immediately and is searchable in the line-item form on quotes and invoices.

Note: The customer sees the Default Price on quotes and invoices. The Cost field is internal only and never appears on customer-facing documents.

Did this answer your question?