Right Part, Right Van, Right Job: How Axolt Supplies Field Service Work Orders
How Axolt supplies field service work orders.
A field service visit succeeds or fails before the technician leaves the depot. If the right part is not on the van, the job becomes a diagnosis, an apology and a second visit.
Parts reserved for a work orderVan stock stays on the books
Service Parts Dispatcher · Example
ConnectedUnused parts returnedWarehouse confirms receipt
Axolt connects the work order, the technician, the van and the warehouse on one Salesforce platform.
The part that wasn't on the van
Every service leader knows the pattern. The engineer arrives on time, finds the fault in twenty minutes, and then discovers the replacement motor is still on a shelf forty miles away. The customer loses another morning. The business pays for a second trip, a second slot in an already full schedule, and often an SLA penalty. The technician, who did everything right, takes the blame.
The root cause is rarely a lack of stock. Most service organisations hold plenty of inventory. The problem is that the stock is in the wrong place, is already promised to another job, cannot be found in the system, or was never tied to the work order in the first place.
Why one platform matters
Axolt is a Salesforce-native ERP. It runs inventory, warehousing, procurement, manufacturing, finance and field service operations on the same Salesforce platform as your customers, cases, assets and service appointments. That matters here because parts readiness is not an inventory problem or a scheduling problem on its own. It sits exactly where the two meet.
Connected Natively
Work orders and service appointments
Van stock and home warehouses
Allocation and reservation
Batch and serial traceability
Scanning, reconciliation and returns
Purchasing and planning
This article explains how Axolt supports field service parts and inventory dispatch, so that every work order or service order has the right inventory on the job. It covers the van as a stock location, allocation and reservation, batch and serial control, barcode scanning, reconciliation and returns, traceability, and how the whole flow connects back to purchasing and planning.
Why parts readiness breaks down
Parts readiness fails in predictable ways, and almost all of them come from systems that do not share one view of stock, demand and the job.
Van stock is invisible.
Many businesses treat the van as consumed stock the moment parts leave the warehouse. The ERP no longer knows what is on board, so dispatchers order parts that are already sitting in a technician's van.
Stock is promised twice.
Without reservations, two jobs on the same day can both "see" the last unit. Whichever technician reaches it first wins, and the other job fails.
Transfers are confused with consumption.
When moving a part to a van is recorded as using it, stock disappears from the books before the work is done. Unused parts then drift back into the warehouse with no record.
Batches and serials get lost on the road.
A regulated customer asks which lot was fitted on 12 March, and nobody can say because the van was a black hole in the stock ledger.
Returns are an afterthought.
Unused parts sit in vans for weeks, are counted again at stock take, and the variance is written off.
Scheduling and inventory live in different tools.
The scheduler books the slot; the stock system is checked by someone else, later, if at all.
The cost shows up in first-time fix rates, repeat visits, emergency freight, excess safety stock held "just in case", and write-offs at every stock count. Each of these is a symptom of the same gap: the work order and the inventory are not connected at the moment it matters.
ONE SOURCE OF STOCK TRUTH
The van is a stock location, not a black hole
In Axolt, each service van is a mobile inventory location inside its home warehouse, linked to one technician or service resource. Stock in the van stays on the books, with its batches and serial numbers, until it is genuinely consumed on a job. That single design choice changes what the business can see and do:
Dispatchers see real van stock.
Before raising a transfer, they can see exactly what is already on board and what is free to use.
Each van belongs to a warehouse.
Replenishment, returns and stock valuation roll up correctly to the right site.
Each van belongs to a resource.
When a work order is assigned to a technician, Axolt knows which van and which warehouse are in play without anyone looking it up.
Stock can be free or reserved.
A part in the van is either available for any job or reserved against a specific work order. Both states are visible and reportable.
One Salesforce platform
Because Axolt is built natively on Salesforce, the van, the technician, the work order, the customer's asset and the service appointment are records on the same platform. There is no nightly sync between a field service tool and a separate ERP, and no second login for the dispatcher. When a service appointment moves to tomorrow, the parts reserved for it are still attached to the same work order.
The foundation for traceability
This is the foundation for everything else in the flow. If the van is not a real location, allocation, reconciliation and traceability all depend on manual workarounds.
SERVICE PARTS DISPATCHER
Allocating parts to the work order
Axolt's Service Parts Dispatcher takes a work order's parts requirements and makes sure each one is either reserved from stock already in the van or transferred from the warehouse and reserved, before the technician sets off.
The dispatcher selects the technician, the work date and the work order. Axolt brings in the linked van and warehouse automatically, then shows every required product with the numbers that matter:
DISPATCH MEASURES
Measure
What it tells the dispatcher
Total required
What the job needs in total
Already reserved
What is already set aside in the van for this work order
Unfulfilled
What still needs to be found
Free in van
What the technician already carries and nobody else has claimed
Warehouse stock
What the home warehouse can send
Shortage
What cannot be covered from either
From there the allocation follows a simple rule that saves money and time: use what is already in the van first, then transfer the rest.
FROM REQUEST TO RESERVATION
Reserve from the van
Free stock in the van is reserved against the work order. Nothing physically moves, and no transfer cost is incurred.
Transfer from the warehouse
For anything still unfulfilled, the dispatcher adds transfer lines from one or more warehouse locations. Each line picks a location, a batch or serial numbers where relevant, and a quantity.
Process
Axolt moves the transferred stock into the van and reserves it for the job in one transaction, with a full movement record.
Crucially, a transfer is not consumption. The parts stay on the books in the van, reserved for that work order, until the technician uses them. If the job is cancelled or rescheduled, the stock is still visible and still reserved, not written off.
Shortages are shown clearly against each line, so the dispatcher knows before the day starts which jobs are at risk and can act on them.
TRACEABILITY BY DESIGN
Batches, lots and serial numbers stay tracked
Axolt keeps batch and serial identity attached to every unit as it moves from warehouse to van, onto the job, and back again. For regulated industries such as medical devices, pharmaceuticals and healthcare equipment, this is the difference between an easy audit and a recall nobody can scope.
Batch and lot tracked products
When a dispatcher transfers a lot-tracked part, they choose the location and the batch, and Axolt shows how much of that batch is available at that location. A single requirement can be split across several batches or several locations: two from one bin, three from another, each with its own lot recorded against the work order.
Serialised products
For serialised items such as motors, controllers or medical devices, the dispatcher selects specific serial numbers through a searchable multi-select picker. The quantity is derived from the number of serials chosen, so it can never drift out of step with the serials themselves. The same picker is used when parts come back, so the serial that left is the serial that returns.
This gives operations and quality teams practical controls:
Earliest expiry first
Lot-tracked stock with the soonest expiry can be used before newer stock, reducing write-offs.
Eligible stock only
Stock that is quarantined, on hold or past its expiry should not reach a customer site.
No double selection
A serial number already chosen for one line, or reserved for another job, cannot be chosen again.
The result is that the dispatch note for a job can say exactly which lot and which serial numbers were sent, not just how many.
SCAN TO CONFIRM
Scanning at the bench and at the van
Axolt supports barcode scanning with both hardware scanners in the warehouse and mobile devices in the field, so stock is identified by scanning rather than typing.
One scan workflow, from warehouse to van
In the warehouse, a picker with a handheld scanner can confirm the location, product, batch or serial being sent to a van. On the road, a technician can scan with a mobile device to confirm what they are returning. Either way, the scan is checked against the current work order, which removes the most common causes of error:
ERRORS CAUGHT AT THE SCAN
Wrong product
the wrong product picked from a similar-looking bin
Serial keying error
a serial number keyed with one digit transposed
Wrong batch
a batch selected from a drop-down by habit rather than by what is in the hand
Duplicate return
a return counted twice because two people each recorded it
Speed at loading
Scanning also speeds up the busiest moments of the day. Loading a van for a large job with a dozen serialised parts takes minutes when each unit is scanned, and the dispatch record is complete the moment the last scan lands.
Consistency on the road
The principle is consistency. The same scanning approach works for allocation in the morning and for reconciliation at the end of the job, so warehouse staff and technicians learn one way of working, not two.
COMPLETE THE MOVEMENT
Closing the loop: reconciliation and returns
When the job is complete, Axolt reconciles what was allocated against what was actually used, and returns any unused parts from the van to warehouse stock through a confirmed receipt.
This is the step most field service operations skip, and it is where inventory accuracy is usually lost. Axolt makes it part of the same workspace as allocation, so it happens routinely rather than at quarterly stock takes.
The flow runs in four steps:
Consumption is confirmed
What the technician used on the job is recorded against the work order. Those parts leave the van and the reservation.
Unused parts are identified
Anything allocated but not used is shown, by product, batch and serial number.
The return is prepared
The actual batches and serial numbers going back are selected or scanned. Parts staying in the van for another job can be released as free van stock instead of returned.
The warehouse confirms receipt
Returned stock stays visible as pending until the warehouse counts it in. Only then does it move from the van back into warehouse stock.
Receipt is the control point
That final confirmation is important. Stock does not jump from the van to the warehouse just because a technician says it was dropped off. The warehouse receipt is the control point, and pending returns stay visible until it happens.
Discrepancies have a reason
Real life is not always tidy, so discrepancies need a proper home. If fewer units arrive than expected, the gap should be recorded with a reason, such as still in the van, damaged or missing, rather than silently adjusted. That keeps van stock, warehouse stock and work order records in agreement, and gives operations managers a clear view of where losses actually occur.
END TO END TRACEABILITY
Every movement leaves a trace
Because every reservation, transfer, consumption and return is a transaction in the same ledger, Axolt can answer "where is this part, and how did it get there?" for any product, batch or serial number.
A single serialised motor might have a history like this:
Step
Movement
From
To
Linked to
1
Transfer
Warehouse bin
Technician's van
Work order and dispatch note
2
Reservation
Van (free)
Van (reserved)
Work order
3
Return
Van (reserved)
Pending warehouse receipt
Return note
4
Receipt
Van
Warehouse
Warehouse confirmation
That traceability has direct commercial value:
Recalls are scoped in minutes
If a supplier recalls a batch, you can see which vans hold it, which jobs used it and which customers' assets now contain it.
Warranty claims are supported
The serial fitted to a customer's asset is on record, with the date and the technician.
Audits are easier
Quality and finance teams can follow a part from purchase receipt to installation without spreadsheets.
Stock takes find fewer surprises
Van stock matches the system because every movement in and out was recorded.
Because the records live on Salesforce, they also connect to the service history the rest of the business already uses. A service manager looking at a customer's asset can see which parts were fitted and when, without leaving the CRM.
ONE CONNECTED OPERATION
Connected to the rest of the operation
Parts dispatch only works if the warehouse, purchasing and planning teams see the same demand as the dispatcher. In Axolt they do, because they all run on one platform.
Warehouse management
Transfers to vans draw from real warehouse locations and bins. Returns land back in warehouse stock, ready for the next job. The warehouse team works from the same records the dispatcher created, not a printed pick list.
Procurement
Work order requirements are genuine demand. When warehouse and van stock cannot cover upcoming jobs, that shortage can feed purchasing, so buyers order against confirmed service work rather than guesswork. Axolt's purchasing tools can show buyers which demand is driving a purchase, which vendor to use and whether stock elsewhere could cover it first.
Inventory and replenishment
Van stock levels can be planned like any other location. Fast-moving consumables can be kept topped up, while expensive or serialised parts are sent only when a job needs them.
Finance
Because stock stays on the books until it is consumed, inventory valuation is accurate. Consumption is posted against the work order, so job costing reflects the parts actually used.
Field service scheduling
Work orders, service appointments and technicians already live on Salesforce. When the schedule changes, the parts reserved for the work order stay with it.
For service businesses that also manufacture or distribute, the benefit compounds. Service parts, production materials and customer orders compete for the same stock. Seeing all of that demand in one system is what stops a service job and a sales order both being promised the last unit.
AGENTFORCE AND HUMAN CONTROL
AI that prepares the work, people who approve it
Axolt's AI orchestration, built on Salesforce Agentforce, can use the same inventory, work order and van data to prepare allocations and flag problems, while people keep control of every stock-changing decision.
The value of AI in parts dispatch is not conversation for its own sake. It is doing the routine analysis a good dispatcher does every evening, faster and across more jobs. Typical requests look like this:
Prepare tomorrow's parts
"Prepare the parts for tomorrow's work orders for this technician. Use van stock first and propose transfers for the rest."
Find competing demand
"Which of tomorrow's jobs are short, and are any two jobs competing for the same stock?"
Suggest eligible batches
"Suggest batches for the missing parts, earliest expiry first."
Explain the shortage
"Explain why this work order is still short and how we can fix it."
Prepare the return
"Reconcile this completed job and prepare the unused parts for return."
Three rules make this trustworthy in an ERP:
01 · Show the working
Every proposal should state the quantities, the source locations, the batches or serials, and anything still unresolved.
02 · Confirm before stock moves
AI proposes; a person approves. Reservations, transfers and returns are only processed once someone confirms them.
03 · Use the same rules as the screen
AI should never bypass eligibility, quarantine, expiry or serial checks that a dispatcher would face.
With those rules in place, AI and voice assistance become genuinely useful for technicians too. A technician with gloves on, at the back of a van, can ask what is reserved for the next job or confirm a return without typing.
What changes for each team
Connecting parts to the work order changes the working day for everyone involved in a service visit, not just the dispatcher.
Role
Before
With Axolt
Dispatcher
Checks stock in one system and schedules in another; finds shortages on the morning of the job
Sees requirements, van stock and warehouse stock together; resolves shortages the day before
Technician
Arrives hoping the parts are on the van; calls the office when they are not
Knows what is reserved for each job; scans returns at the end of the day
Warehouse team
Picks from emailed lists; returns pile up unrecorded
Picks against recorded transfers; confirms returns with a proper receipt
Service manager
Learns about missing parts from repeat visits and complaints
Sees at-risk jobs ahead of time and tracks first-time fix
Finance
Writes off van variances at every stock take
Values van stock accurately and costs each job with the parts actually used
Quality and compliance
Reconstructs batch and serial history by hand
Traces any lot or serial from receipt to customer asset
Customer
Waits for a second visit
Gets the job fixed first time
The last row matters most. Customers do not see the stock ledger, but they notice whether the engineer finishes the job on the first visit.
FIRST TIME FIX STARTS BEFORE THE VISIT
Getting the right part on the job, every time
First-time fix is decided in the warehouse and the van, the day before the visit. Axolt connects those places to the work order on the same Salesforce platform your service team already uses.
In practice that means:
Van stock
The van is a real stock location, tied to a warehouse and a technician.
Work order reservation
Parts are reserved for the job, from the van first and the warehouse second.
Correct stock movement
Transfers are not consumption, so stock stays on the books until it is used.
Batch and serial identity
Batches and serials stay tracked from bin to van to customer site and back.
Scan confirmation
Scanning removes keying errors in the warehouse and in the field.
Confirmed returns
Unused parts come back properly, with a confirmed warehouse receipt.
Movement history
Every movement is traceable, for audits, recalls and warranty claims.
Connected planning
Demand flows to purchasing and planning, so shortages are solved before they reach the customer.
One operation on Salesforce
For service-led manufacturers, distributors, medical device companies and field service organisations, this is where an ERP built natively on Salesforce earns its place. The customer record, the asset, the work order, the technician and the part are not in different systems that need reconciling. They are one operation.
Three readiness questions
If your technicians are still arriving without the part they need, start by asking three questions. Can you see what is in each van right now? Can you see which stock is reserved for which job? And can you prove where a given serial number went? If any answer is no, that is the gap Axolt is built to close.
To see the Service Parts Dispatcher with your own products, vans and work orders, talk to the Axolt team about a tailored demonstration.
Get the right part on the job, every time
First-time fix is decided in the warehouse and the van, the day before the visit. Axolt connects those places to the work order on the same Salesforce platform your service team already uses. To see the Service Parts Dispatcher with your own products, vans and work orders, talk to the Axolt team about a tailored demonstration.