In my experience working with field service teams across a range of industries, the inventory setup phase is where organizations either build a solid foundation for operational visibility or create headaches that persist for months. What I typically recommend is approaching this configuration with some deliberate sequencing — the decisions you make early on will ripple through your reporting, your technicians' daily workflows, and your integration points with accounting systems.
Understanding Inventory Architecture in FieldPulse
Before diving into the configuration screens, it is worth understanding how FieldPulse structures inventory data. The platform uses a three-level hierarchy that I have seen teams struggle with when they try to retrofit their existing warehouse structure later:
- Categories — broad classifications like "HVAC Components," "Electrical Supplies," or "Consumables"
- Locations — physical or logical storage points (warehouse, van stock, customer site)
- Part Records — individual SKUs with quantities, costs, and reorder thresholds
This structure supports both centralized warehousing and distributed van stock models. In my experience, the teams that struggle most are those who try to collapse categories and locations into a single flat list — resist this temptation, even if your operation feels small today.
Step 1: Configuring Inventory Categories
Start by navigating to Settings > Inventory > Categories. What I typically recommend here is creating categories that align with how your technicians actually think about parts, not necessarily how your accounting system categorizes them.
For example, an HVAC contractor I worked with initially set up categories matching their QuickBooks chart of accounts — "Materials," "Supplies," "Equipment." Technicians could not find anything. We restructured around functional groupings: "Compressors," "Capacitors," "Refrigerant," "Thermostats." Adoption improved immediately.
To add a category:
- Click Add Category in the upper right
- Enter a Category Name (required)
- Optionally add a Description for internal reference
- Assign a Category Code if you need integration alignment
- Click Save
Categories can be nested one level deep. I have found this useful for distinguishing between, say, "Electrical — Wire" and "Electrical — Connectors" without overwhelming the top-level list.
Step 2: Establishing Inventory Locations
Next, configure your locations at Settings > Inventory > Locations. This step is frequently rushed, and in my experience it is where the most rework happens down the line.
Consider what questions you want to answer six months from now:
- "Do we have this part in stock anywhere?" — requires location tracking
- "Which van needs restocking?" — requires van-level locations
- "How much inventory is committed to upcoming jobs?" — requires reservation logic (see Reserving Inventory for Upcoming Jobs)
Common location patterns I have seen work well:
| Location Type | Example Names | Use Case |
|---|---|---|
| Central Warehouse | "Main Warehouse — North" | Primary stocking, bulk storage |
| Vehicle Stock | "Van 101 — Mike" | Per-technician mobile inventory |
| Job Site | "Customer Held" | Parts delivered ahead of technician |
| Quarantine | "QC Hold" | Defective or return-pending items |
Each location can have its own address and manager assignment. The address field drives Mobile App Deep Linking for Third-Party Navigation if your technicians need directions to restock points.
Step 3: Creating Part Records
With your structure in place, add individual parts at Inventory > Parts > Add New Part. What I typically recommend is starting with your top 50 most frequently used items rather than attempting a complete catalog migration.
Required fields:
- Part Number — your internal SKU or manufacturer part number
- Part Name — the display name technicians will see
- Category — selected from your configured categories
- Default Location — where this part is typically stocked
Fields I strongly encourage completing during initial setup:
- Unit Cost — enables job costing and margin reporting
- Reorder Point — triggers low-stock alerts
- Reorder Quantity — suggested restock amount
- Vendor — streamlines purchase order generation
The Barcode field supports scanning workflows covered in Barcode Scanning for Inventory Management. If you have existing barcode labels, enter the codes here during setup to avoid relabeling.
Step 4: Establishing Opening Balances
After creating part records, you need to establish your starting quantities. Navigate to Inventory > Adjust Stock and use the Initial Stock Entry mode — this creates adjustment records that are flagged separately in your audit trail, making it clear what was legacy data versus ongoing transactions.
In my experience, this is best done as a coordinated effort: one person reads counts aloud while another enters them. Trying to count and enter simultaneously introduces errors that become difficult to untangle later.
For larger catalogs, consider the Bulk Importing Inventory via CSV approach instead.
Step 5: Configuring Part Tracking Behavior
Return to Settings > Inventory to configure how parts flow through your operation:
Consumption Tracking: Determine whether technicians must record parts used at job completion (recommended for cost visibility) or whether inventory is managed independently.
Reservation Rules: Configure whether upcoming jobs automatically reserve inventory, preventing double-allocation. This interacts with technician availability settings — a reserved part with no available technician creates a scheduling constraint.
Negative Stock: Decide whether to allow transactions that drive inventory negative. What I typically recommend is disabling this initially; it surfaces data quality issues quickly. Once your team is disciplined about real-time usage logging, you can relax this constraint if needed.
Integration Considerations
If you are connecting to QuickBooks or another accounting system, your category and part number choices matter more than they might seem. The Connecting FieldPulse to QuickBooks article covers mapping in detail, but the key point is that FieldPulse's "Part Number" field maps to QuickBooks "Item Name/Number" — mismatches here create sync failures or duplicate records.
I have seen teams spend significant time cleaning up item mapping that could have been avoided with a thirty-minute alignment conversation during initial setup.
Common Setup Patterns
Van Stock Model: Each technician carries inventory and restocks from central warehouse. Requires location per van, frequent transfer transactions, and typically uses the mobile app's barcode scanning for rapid checkout.
Central Pull Model: Technicians request parts for each job; warehouse staff stage and load. Requires strong reservation logic and clear dispatch communication — see Using the Dispatch Board for coordination workflows.
Hybrid Model: Common consumables on vans, specialized parts centrally held. Most complex to configure but often most operationally efficient. Requires clear categorization so technicians know what to expect where.
Verification Checklist
Before declaring inventory setup complete, I suggest verifying:
- [ ] Can a technician locate and consume a part from the mobile app?
- [ ] Does the on-hand quantity decrement correctly?
- [ ] Do reorder alerts fire at expected thresholds?
- [ ] Does the Inventory Report reflect expected totals?
- [ ] If integrated, do test transactions sync without error?
Skipping this verification has, in my experience, led to situations where teams discover data inconsistencies weeks into operation — when there are hundreds of transactions to reconcile rather than dozens.
See Also
- Adding and Editing Inventory Items — ongoing part record maintenance
- Tracking Parts Used on a Job — technician consumption workflows
- Setting Low-Stock Alerts — automated notification configuration
- Bulk Importing Inventory via CSV — large-scale data migration
- Inventory Count Not Updating After Job Completion — troubleshooting common sync issues
If you are unsure which pattern fits your operation, what I typically recommend is starting with a single category and location, running through a complete transaction cycle with one or two technicians, and expanding only after that workflow is smooth. It is easier to add complexity to a working system than to debug complexity in a broken one.