A part can be available in a warehouse, allocated to a visit, used on a job or returned. Those events should not be collapsed into a single quantity field. The stack must distinguish the work record from the stock movement and its financial interpretation.
This guide selects component boundaries. It does not calculate job cost, advise on accounting or rank inventory systems.
Component roles for parts
| Component | Record it owns | Interface question |
|---|---|---|
| Item catalogue | Identifiable product or part | Which identifier do job and stock records share? |
| Stock capability | Location and recorded movement | What changes when a part is used or returned? |
| Work-order system | Part associated with performed work | Is allocation distinguished from actual use? |
| Ledger or ERP finance | Financial interpretation | Which approved event reaches finance? |
An available catalogue item is not necessarily stock on hand. Name the participant who maintains starting quantities and corrections.
A native-inventory candidate
Dynamics 365 Field Service documents warehouses and inventory, purchasing and returns. Its model includes warehouse records and work-order products. Confirm product types, permissions and the proposed integration with finance or an external ERP.
This is a candidate where the service platform can own the required stock responsibility. The documentation is not a claim that every stock requirement is covered or that an external ERP connection is automatic.
The existing inventory system remains the baseline if it already has an accountable item and movement record. Adding native field-service inventory creates a second stock copy unless the interface and authority are defined. A controlled reference to stock may be simpler than duplicating all quantities.
Evaluate a part moved between locations
Use a fictional part in a warehouse and a technician location. Transfer it, associate it with a work order and record only part of the quantity as used. Ask the supplier to show the movement record and the job context separately.
Then return an unused part to another location. Inspect which participant records the return and how the quantity is reconciled. A technician comment does not automatically establish a stock movement.
Finally, change an item description. Confirm whether the job’s historical context remains understandable and whether the catalogue change affects another system. Do not infer consistent identifiers from matching labels.
Consolidate when the stock responsibility is modest
Native inventory can be proportionate for a service operation with straightforward locations and movements. A separate ERP may be justified by a named procurement, pricing or inventory requirement. Define the operating reconciliation before the technical connection.
The minimum field-service stack covers the wider job and ledger map. Browse the Field Service hub for adjacent component decisions.