Field Service Inventory Management: Vans, Sites, Warehouses

A job can only be fixed on the first visit if the parts it needs are in the van when the technician leaves. The first-time fix rate is the share of jobs completed on the first visit, with no return trip. Skills and time also affect it, but parts availability is the part stock control can change.

Salesforce Field Service reflects this. Its documentation lets you add products required to a work type, a work order (Salesforce's record for one job) or a work order line item, so the assigned technician arrives with the right equipment (Salesforce Help: Track Required Inventory in Field Service). The record knows what the job needs. The question is whether the van holds it.

A hypothetical example, with round numbers for illustration only: 100 jobs a week, 10 need a return trip for a missing part, and each return costs 2 technician hours. That is 10 × 2 = 20 technician hours a week, the equivalent of half a full-time technician.

According to the Aquant 2025 Field Service Benchmark Report, which analyzed 21 million service events from 157 service organizations, fully resolving a service ticket costs on average 34% more than a single work order, because return visits, truck rolls, parts and labor all add to the bill.

Field service inventory management is tracking, moving and counting the parts technicians need across every place a part can sit. List those places first: the central warehouse, each regional depot, each van, and each customer site where you leave stock. Give each one a name, an owner and a rule for how stock enters and leaves.

Two rules keep the record honest. A part is in exactly one location at a time. It changes location only through a booked transfer, or when a job uses it.

Our inventory visibility shows stock levels for each product across multiple warehouses or locations, so the service team and stores read the same number. Our inventory visibility guide explains which number to quote before you promise stock. Stock left at a customer's site is a special case. Our guides to consignment inventory and vendor managed inventory cover it.

Salesforce Field Service already gives you the building blocks: locations, product items, transfers and a record of the parts used on each job. Many teams then need a stock-control layer on top. It shows what is already committed to other jobs, which location can supply a part, and when to restock. We supply that layer natively on Salesforce.

What does Salesforce Field Service cover?

As of November 2026, Salesforce's documentation lists these inventory tasks: tracking required inventory, tracking consumption, transferring inventory (including serialized items), requesting inventory, tracking shipments and tracking returns (Salesforce Help: Common Field Service Inventory Management Tasks). Three ideas matter here:

• Location and product item. A location is a place stock lives, such as a warehouse or a service vehicle. A product item (ProductItem) is a product held at a location.
• Product transfer. A product transfer (ProductTransfer) records a move of stock between two locations.
• Products consumed. A products consumed record records a part used on a work order.

These are Salesforce's features, not ours.

How does a Salesforce-native tool like Arka Inventory connect the two?

Our stock records are Salesforce records you can report on beside opportunities. The method on this page needs four things from the stock side:

• Multiple warehouses.
• Transfers between them.
• Commit Inventory, to commit, allocate and reallocate stock.
• Inventory alerts, for items approaching or falling below minimum stock levels.

We also support lot, batch, expiry-date and serial-number tracking. See how we work with Salesforce.

Our recommendation: decide which system owns each count before you start. If both the job record and the stock record can change a van's quantity, you will have two numbers by Friday.

Build each van kit from the parts your jobs actually use, then set a minimum and a top-up level for every line. Some teams call this truck stock or bin stock. The idea is the same. Pull the last three months of job records for each job type, and start from what was used, not from a supplier's suggested list.

Van inventory management starts with this table. The quantities are illustrative only. Replace them with your own usage.

Our formula for each line: minimum = average units used between two restocks + a buffer you choose. Top-up level = minimum + average units used between restocks. A hypothetical case: a technician uses about 6 fuses between weekly restocks. With a buffer of 2, the minimum is 8 and the top-up level is 14.

Decide what not to carry as well. Keep high-value and slow-moving parts at the warehouse or depot and reserve them to the booked job. Carry fast-moving, low-cost lines on the van. A part used twice a year does not belong on every van; a part used every week does. The same rule decides whether a serial-numbered unit rides on one specialist van or waits at the depot. Our lot and serial tracking records stock by batch, expiry date and serial number.

Our inventory alerts notify you when items approach or fall below minimum stock levels, so a number triggers the top-up, not memory. Our guide to low stock alerts covers how to set them.

Reserve the parts the moment the job is booked, so no other job or van can take them before the technician leaves. A reservation ties a quantity of a part to one job. Without it, two jobs can count on the same last unit.

Run it in four steps:

Commit Inventory commits, allocates and reallocates stock against demand, so a unit promised once is not promised again. You can allocate or reallocate stock against a delivery date as plans change.

Commit Inventory commits stock against demand records in Salesforce. Ask us how your job or work order records fit.

Record each part on the day it is used, before the next job starts, and restock only by transfer. A part logged at the end of the week is missing from the record for a week. Every reservation made in between relies on a wrong number.

The usual objection is that technicians will not log parts. Make logging the shortest route. Let them pick from the van's own list, not a free-text box, and scan where they can. Salesforce Field Service records the used part as a products consumed record on the work order (Salesforce Help: Common Field Service Inventory Management Tasks).

Every movement is a transfer with a from-location, a to-location and a quantity:

• Top-up: warehouse or depot to van, booked before departure.
• Return: van to warehouse, for unused, faulty or surplus parts.
• Van-to-van: book a loan at handover. An unbooked loan makes both vans wrong.

Our warehouse management supports transfers between warehouses, with barcode-based receiving and put-away. Salesforce Field Service can transfer serialized inventory (Salesforce Help: Common Field Service Inventory Management Tasks).

Count every van once a week, a few vans a day, and compare the count with the system quantity. Treat each difference as a cause to find, not a number to overwrite. Overwriting hides the cause, and it comes back.

Vans have two causes that warehouses rarely have: parts used but not logged, and transfers not booked. For each gap:

1. Look for unbooked movements since the last count: loans, swaps, parts collected from a depot by hand.
2. Compare the jobs the van's technician closed since the last count with the parts logged.
3. Ask the technician the same day, while the jobs are fresh.

Fix the habit, not just the quantity. Count on the same day each week, with vans parked at base. Our guides to cycle counting and inventory discrepancy causes cover the count method and adjustment rules. This page covers only what is specific to vans.

Track first-time fix rate, van fill rate, parts not logged, stockouts at job and dead stock in vans. Together they show whether parts are the problem and where the fault sits. Calculate each weekly.

Set your baseline before you change anything. Calculate all five for four weeks, then judge change against your own numbers. Job mix, region and kit differ too much for a shared benchmark. Build the stock-side numbers as reports in Salesforce, since our stock records are Salesforce records.

Run these eight checks this week. Each has an owner and a pass or fail test.

To see this set up on your own Salesforce org, see how it works.

This week, do two things: list your stock points, and build one van kit with a minimum and a top-up level for every line. Then let the five numbers decide what to fix next. If stockouts at job are high, fix the kit or the reservation step. If parts not logged is high, fix logging and transfer booking before you adjust any quantities. Count on the same day each week for four weeks before you judge any change.

To see this run on Salesforce, book a demo with our team. Bring your list of stock points and a typical van kit, and we will show you how multiple warehouses, transfers, Commit Inventory and inventory alerts work together, so service and stores read the same numbers.