Custom service parts software development
A machine you delivered ten years ago is standing idle today. Whether the right part is on site tomorrow depends on three sets of records that, at most service companies, live separately: which configuration that specific unit has, which article fits it, and whether that article is in stock anywhere. Appfront builds custom software that ties the three together, for machine builders, installation companies and technical service providers.
Parts management starts at the machine, not at the warehouse
Service parts software is the administration that lets you keep supplying parts to delivered installations for years: which units are where and in which configuration, which part fits them, which successor a discontinued part has and what needs to be in stock. It is the aftercare chain, which continues for years after delivery.
On the right page? This is about the parts side of service. If your question is about the broader production process, from costing to planning, see manufacturing software. If it is about the technician themselves, with work orders and reporting on site, a field service app is the better fit. If you want a sales channel with a catalogue and customer prices, without the customer's installed machinery driving the selection, a B2B e-commerce portal is the shorter route.
The installed base as the foundation
Not a list of machine types, but a register of individual units with serial number, configuration and everything that has been changed since delivery.
Compatibility as a rule
What now lives in a parts manual per year of manufacture and in the heads of two technicians becomes a testable set of rules.
Stock with a different standard
A service part does not earn its place through turnover rate, but through what happens at the customer who is waiting for it.
Why stock models dispose of exactly the wrong parts
Trade stock and service parts look alike until you look at how they are managed. In trade, idle stock is waste: every item has to keep moving, and a low turnover rate is a signal to scale down. With service parts, the value often lies in the part that does nothing for years and is needed exactly once, at the moment a line stands still at a customer.
That is built into the tooling. An ABC analysis on revenue puts a critical drive module with one sale every four years at the bottom of category C, and the next clear-out of slow-moving stock removes it. Two years later a machine is down and the manufacturer quotes a lead time of months.
The right trade-off sets two kinds of cost against each other, drawn from different systems. Holding stock costs tied-up capital, space and obsolescence. Being unable to deliver costs lost production at the customer, express freight, a second service visit and escalation under the service agreement. The first side is in your general ledger; the second is usually recorded nowhere.
In practice that means classifying by criticality rather than by revenue, with a delivery target per class, and forecasting with methods that can handle intermittent demand, such as Croston's method from 1972, which estimates the time between two withdrawals separately from their size.
Does it fit? A question answered per unit
Serial number, year of manufacture and specification
For installations that have been supplied in variants over many years, compatibility is an administration in its own right. A machine type from 2011 has a different drive from the same type from 2016, and the unit that was retrofitted in 2019 differs from both. The parts book for the year of manufacture describes the configuration as supplied, not as it stands now.
That is why, in a working system, compatibility is tied to the unit, not to the type. For each serial number it records which conversion kits and retrofits have been carried out, and rules refer to that configuration, usually as validity from or up to a serial number range. A wrongly supplied part rarely costs just the part here; it costs a second service visit.
Replacements, successors and the last buy
Suppliers discontinue an item and supply a successor, and that chain must be traceable through your records. Replacement often works in one direction only: the new sensor fits where the old one was, while the old one no longer meets requirements on a recent machine.
On top of that comes the end of supply: how much do you still buy for the machines that will keep running for years? That is a calculation over your installed base.
What such a system needs to do in practice
Installed base with history
Every unit supplied, with serial number, location and specification, plus the changes made to it.
Compatibility per unit
Rules on serial number range, specification and conversions, so that the back office, engineers and portal all get the same answer.
Replacement and succession chains
For each relationship, whether replacement works in both directions is recorded, with a justification for the last buy.
Stock control by criticality
Classification by what happens if an item is missing, with a delivery target per class.
Ordering portal built on the customer's own machine fleet
The customer selects from the exploded-view drawing of exactly their specification. Parts that don't fit don't appear.
Parts with the engineer
Van stock as a full-fledged location, with consumption booked when the work order is closed.
Parts are a sales channel, not a by-product
At many service companies, parts deliver a substantial share of the margin, yet they are sold through the slowest channel the company has: someone phones the back office and describes the part. That description is rarely unambiguous, so an exchange of photos and type plates follows.
An ordering portal breaks that pattern as soon as it is tied to the installed base rather than to a generic catalogue. The customer works from their own machines and sees only what fits that unit. That comes with customer-specific prices, purchase order numbers and, for larger customers, ordering from their own procurement system via punchout standards such as OCI or cXML. See also Building a B2B e-commerce portal.
The portal does not stand apart from field service: whether the part is already in the engineer's van should come from the same source as the customer's order. We cover that interface in the field service app.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Standards, product data and integrations
Spare parts management has no certification of its own, but it touches frameworks that set out terminology and documentation obligations. NEN-EN 13306 defines the terms used in maintenance. NEN-EN 13460:2009 covers the documentation that should be supplied with an installation and kept up to date during its operational life; parts lists fall under it. Customers working to ISO 55001 translate that into requirements for your documentation.
Two European regulations matter in the longer term. The Machinery Regulation (EU) 2023/1230 replaces the Machinery Directive 2006/42/EC and applies from 20 January 2027, with stricter requirements for technical documentation. The Ecodesign Regulation (EU) 2024/1781, in force since 18 July 2024, works per product group through delegated acts and sets requirements on repairability, availability of spare parts and a digital product passport.
There is often more to gain on the data side than on the standards side. In the Dutch installation and building services sector, ETIM is the common classification model for technical products, and 2BA is the product database in which manufacturers and wholesalers share their data. GS1 article numbers (GTIN) help establish that three supplier numbers refer to the same part, a persistent cause of duplicate stock.
When custom isn't the answer
Mature packages certainly exist here: the parts and service modules of SAP S/4HANA Service, Microsoft Dynamics 365 Field Service, IFS or Infor have years of development behind them. For a service company with a manageable range and machines that barely differ from one type to the next, such a module is the sensible choice.
Custom software starts to pay off once your compatibility logic outgrows what the package can do, which shows in three signals. The back office maintains its own file alongside the ERP recording which variant has which part. The portal you have in mind assumes an installed base that the package doesn't know. Or you run into the limits of your supplier's roadmap.
Then there is the burden that custom software brings, and it is real. You maintain the product data, the installed base and the compatibility rules yourself: a development partner delivers the model, not the content. That calls for an owner within your organisation and a way of working in which a modification is actually reported back. A system that isn't kept up to date is riskier than no system, because people start to rely on it. That is why we more often build a layer alongside the ERP than a replacement for it. Feel free to talk us through your situation.
If you want technicians and dealers to order parts by clicking on the drawing, take a look at exploded-view drawing and parts ordering software.
If it concerns car parts that must fit a vehicle according to TecDoc, take a look at our app for TecDoc parts matching.
If you sell exchange parts with a deposit on the old core, and that core has to go back to the supplier or for remanufacturing, there is our app for registering exchange parts.
If you want to supply parts for printing presses with priority in the event of downtime, take a look at our software for printing press parts supply.
If you want to see which components and firmware each instrument contains, take a look at our software for serial number records of measuring instruments.
If your technicians order parts from the exploded-view drawing, read more about our exploded-view drawing and parts ordering app.
Signs that custom software is worth considering
- Your machines differ in specification by serial number
- The back office keeps its own compatibility lists
- Customers order based on their own installed machines
- The same part runs under several article numbers
- Stock decisions are currently based on turnover rate
Frequently asked questions about service parts software
For some service companies, that is the right choice: packages such as SAP S/4HANA Service, Microsoft Dynamics 365, IFS or Infor have mature item and inventory management. It falls short in two places. A bill of materials per type has no lines for serial number ranges and modifications already carried out. And an ordering portal based on the customer's machine fleet assumes an installed base that the package does not maintain.
By turning the question around: not which type this item belongs to, but which configuration this particular unit has now. For each serial number, the system records the specification the machine was delivered with and what has been changed since. Compatibility is captured as rules over that configuration, for example valid from a certain serial number or only with a specific controller. That distinction between as-delivered and as-maintained is something a parts book organised by year of manufacture cannot give you.
Not by turnover rate: an ABC analysis based on revenue always puts an item needed once every four years at the bottom, as a candidate for disposal. For sporadic demand there are other methods, such as Croston's method from 1972, which estimates the time between two withdrawals separately from their size. More importantly, the standard differs per item: for a part that brings a production line to a halt, you manage on availability, whereas for a cosmetic defect the customer can wait.
The source code, the database and the documentation are yours, and we put that in writing up front. We build on mainstream technology and deliver the build environment and deployment process with it, so that another party can take over. More important still is what you keep in your own hands: the item data, the installed base and the compatibility rules are your business knowledge. A development partner can be replaced; a rule set built up over years cannot simply be recreated.
Yes, provided you accept that cleaning up that data is the real project and the software is the tool. The same pattern almost always recurs: one physical part under several numbers, an installed base that was maintained until someone stopped, and compatibility knowledge in the heads of two engineers. We therefore start with the critical top: the machine types that weigh most heavily in your service agreements, small enough to validate manually and large enough to test the model.
That depends on the quality of the installed base behind the portal. If the customer has to work through a general catalogue, you merely shift the risk of a wrong choice from your sales support team to them. If they work from their own machines, with the exploded view of their specific configuration, a large part of that risk disappears. Where doubt remains, the order first goes to your service department as a request.
Related services
Manufacturing software
For costing, production planning and the bills of materials of your machines. See custom manufacturing software development.
Field service app
For the engineer on site: work orders, checklists and reporting parts used. See field service app development.
B2B e-commerce portal
For a business ordering channel with catalogue and customer prices, without installed base logic. See B2B e-commerce portal development.
Want to tackle your parts administration?
Tell us what your machine fleet looks like, where the compatibility knowledge currently sits and which decisions you make on gut feeling. We will help assess whether your current package can handle this or whether a custom layer alongside it makes sense, even if the outcome is that you don't need to build anything.