--- title: Parts & Procurement url: https://opero.pro/product/parts collection: products --- *From symptom to spare-part order, in one conversation.* Diagnose a fault in the agent, identify the right SKU, generate the order — purchase orders, warranty checks, stock validation all built in. ## Key capabilities - SKU resolution from photos - Warranty / contract aware - PO generation - Supplier catalogues Wrong-part returns on industrial spares are high enough to appear as a named line item on dealer P&Ls. The catalogue is rarely the problem. The seam that fails is between what the technician thinks failed and what the catalogue calls that failure — and closing it by hand, across OEM part numbers, regional SKU variants, and supersession chains, takes longer than the repair itself. ## From symptom to order, in one conversation The technician describes the symptom. The [Knowledge Agent](/product/knowledge) narrows to the likely failed component using model and serial scoping, the same way it handles any diagnosis question. The parts module takes that identification and pre-fills the order: right SKU, right cross-reference, right OEM catalogue, right warranty and contract treatment. Dealer-stock-aware means the system checks your warehouse before drafting the order. It does not promise next-day delivery from a location that does not hold the part. If stock is absent, it routes to the next-nearest warehouse or flags for supplier order — the parts manager sees the full picture before a commitment goes out. Cross-reference and supersession are handled at retrieval time, not at order time. When a part number has been superseded across OEM catalogues or carries a different regional SKU, the agent resolves the correct current number before the PO is drafted. A parts manager who has hand-corrected supersession errors knows what that step is worth. ## A forklift with a hydraulic creep A Mitsubishi Logisnext dealer. A counterbalance forklift in for a standard service. The technician describes hydraulic creep on the lift cylinder — slow drift under load, audible hiss at full extension. The Knowledge Agent narrows the diagnosis to the tilt-cylinder seal kit, scoped to the cylinder variant fitted to that chassis by model year. The parts module pulls the SKU — in this case a kit with four line items across two sub-assemblies — confirms one unit in dealer stock, then checks the customer's contract: paid maintenance agreement, in warranty for parts, no co-pay on seal kits under this service interval. The agent drafts a PO with the correct line items, the contract reference, and the stock location attached. The parts manager reviews it, adjusts the labour line, and approves. The PO goes out signed by a human in under a minute. Nothing about that minute required the parts manager to open the OEM catalogue, call the warehouse, or look up the customer contract separately. ## By the numbers Dealers who deploy parts ordering alongside the Knowledge Agent report first-time-right rates improving by 20–35 percentage points in the first quarter — measured as orders that did not generate a return, a re-order, or a warranty dispute. The range is wide because it depends heavily on catalogue quality at the start. The Nize Equipment deployment follows a similar pattern; their parts pilot is described in the [full case study](/case-study/nize-equipment). ## What you control Whether the agent places orders unattended: default is no. Every PO draft requires a named human to approve before it is transmitted. That is not a limitation — it is the cost-of-error gate. A wrong part ordered at scale is more expensive than the seconds it takes a parts manager to confirm. Per-line confirmation thresholds, spend limits, and which warehouses count as in-stock are all configurable per dealer location. Which customers see which catalogues — OEM-only, multi-brand, preferred-supplier — is access-controlled at the customer level, not the catalogue level. Every order draft and every approval action is written to the audit log with timestamp and user. ## What it connects to ERP connections cover SAP, IFS, and Microsoft Dynamics as the stock-of-record source. OEM parts feeds — where the catalogue lives — connect directly; the agent does not re-key part numbers from a PDF. Dealer warehouse-management systems provide real-time stock counts. When the warehouse system your operation uses is not on the standard list, it connects through the same integration layer that handles the rest of the corpus. Full connector list at [Integrations](/product/integrations). ## Where to look next - [Knowledge Agent](/product/knowledge) — the diagnosis engine that identifies the failed component and hands the identification to the parts module. Parts without diagnosis is a catalogue search; parts with diagnosis is an order. - [Construction & Material Handling](/industry/machinery) — dealer-stock patterns, OEM catalogue structures, and the call-volume benchmarks that show where parts identification breaks down at scale. - [Procurement use case](/use-case/procurement) — the procurement-lead view: how PO approval gates, spend thresholds, and audit trails fit into existing procurement policy.