Short answer: what should appliance repair management software do?
Appliance repair management software should run every job from booking to collection in one record: customer and appliance, check-in with photos, diagnosis, quote, parts, repair, invoice or receipt, and handover. For an authorised service centre it also has to talk to manufacturer portals such as Samsung GSPN, handle warranty claims and keep customers updated without anyone picking up the phone.
If you are an independent repairer doing mostly paid jobs, a generic field service or repair-shop app is usually enough. Custom service centre software pays off when warranty work for several manufacturers dominates and your team re-enters the same job in three or four systems.
Why are authorised service centres different?
A paid repair has two parties: you and the customer. A warranty repair has at least three: you, the customer and the manufacturer, and the manufacturer sets the rules.
- Manufacturer portals. Each brand has its own service partner portal. Samsung's GSPN service partner portal is the best-known example: service orders, status updates, parts and warranty information all live there, and the manufacturer expects them to be accurate and timely.
- Repair coding. Jobs are classified with condition, symptom, defect and repair codes, often based on the industry IRIS scheme (the International Repair Coding System, which Business Central's fault reporting also implements), and claims are checked against them.
- Warranty claims and price lists. Labour, transport and parts are reimbursed under brand-specific price lists. A claim that misses a field is rejected or paid late.
- Parts logistics. Parts are ordered per brand, received, reserved for jobs, sometimes returned, and must match what the portal says was used.
- Several payers. The same job may be billed partly to the manufacturer, partly to the customer, and sometimes to an insurer or retailer.
- Fiscal rules. In many EU countries a payment from a consumer needs a fiscal receipt from a certified device, and invoices may have to be reported to the tax authority.
When this runs on a generic tool plus the portal plus a spreadsheet, every job is typed at least twice, and nobody has a single view of where a repair stands.
Fiscal receipts if you operate in the EU
The UK has no fiscal receipt system, but service centres in much of the EU must issue receipts through certified devices, and the repair software has to drive them. A few examples:
- Romania: cash and card payments from consumers go through certified fiscal cash registers connected to the tax authority (ANAF), and invoices, including those to consumers, are reported through RO e-Factura.
- Hungary: cash-register-obliged businesses use online cash registers that report to the tax authority (NAV); a transition to new e-cash registers is under way, so check NAV's current deadlines before choosing hardware.
- Germany: electronic tills must be protected by a certified technical security device (TSE) under § 146a of the Fiscal Code and the KassenSichV regulation.
In practice this means the job record decides whether a receipt, an invoice or both are issued, and sends the receipt to the fiscal device without anyone retyping amounts. Confirm the exact obligations with a local accountant for each country you serve.
Generic app, manufacturer tools or custom: what fits?
| Option | Good fit | Strengths | Limits |
|---|---|---|---|
| Generic repair-shop or field service app | Independent repairers, mainly paid work | Fast to start, bookings, job sheets, invoicing | No manufacturer portal sync; warranty claims handled outside |
| Manufacturer portal only | One brand, low volume | Required anyway, no extra cost | One brand per portal; no stock, invoicing or customer updates |
| Generic app plus manual portal entry | Two or three brands, moderate volume | Cheap software | Double entry for every warranty job; errors in claims |
| Custom service centre software | Several brands, high warranty share, ERP for parts | One record per job; portals, parts, invoices and receipts connected | Upfront cost; integration access to negotiate per manufacturer |
Be honest about the share of warranty work. If it is under a fifth of your jobs, the double entry is annoying but cheap, and a generic app is the sensible choice.
How does a connected repair workflow run, step by step?
- Booking. The customer books online or by phone. The job gets a number and a public tracking link straight away.
- Check-in. Photos, a condition checklist, accessories received and the customer's signature, on a tablet at the counter or on the technician's phone at the customer's home.
- Warranty check. Serial number and purchase date decide whether the job is warranty, out of warranty or goodwill. For warranty jobs, the service order is created in the manufacturer portal automatically.
- Diagnosis and quote. The technician records symptom, defect and repair codes. For paid repairs a quote goes to the customer, who approves it by link.
- Parts. Parts are ordered, received against the job and taken from stock, with the ERP updated. Parts used are reported to the portal.
- Repair and status updates. Every status change goes to the portal and to the customer by SMS or email.
- Billing. The manufacturer share goes into a warranty claim with the brand's labour and transport rates; the customer share becomes an invoice and, where required, a fiscal receipt.
- Collection and reporting. The customer signs for collection. Management sees turnaround times, open claims and technician performance.
Typical problems when going live: serial numbers typed differently in the app and the portal, parts codes that do not match between ERP and manufacturer, and claims rejected because a code was left empty. Validate these fields at entry, not at claim time.
Manual vs automated: how many hours does it save?
An example for a service centre closing 400 jobs a month, half of them under warranty. Replace the minutes with your own.
| Task per job | Manual | Connected |
|---|---|---|
| Re-enter job and status updates in the manufacturer portal | 10 min | 1 min (check) |
| Prepare warranty claim with codes and rates | 8 min | 2 min |
| Match parts used between ERP, portal and job | 5 min | 1 min |
| Inform the customer at each step | 6 min | 0 min (automatic SMS and email) |
| Type invoice and receipt | 4 min | 1 min |
| Total per job | 33 min | 5 min |
Fill in your own numbers:
- Jobs per month: ___ × minutes saved per job: ___ ÷ 60 = ___ hours saved per month.
- Hours per month × 11 working months × hourly cost of office staff = ___ per year.
With the example: 400 × 28 ÷ 60 is about 187 hours a month, more than one full-time person. Claims that are paid on the first attempt and fewer "where is my repair?" calls come on top.
What does service centre software cost over 3 years?
Estimates for 10 users. SaaS prices vary widely by vendor and region; custom figures are typical market ranges for a phased build, not a Raao price list.
| Option | Year 1 | Years 2–3 | 3-year total (estimate) |
|---|---|---|---|
| Generic repair or field service app, 10 users | €2,000–6,000 + setup | €2,000–6,000 / year | €6,000–18,000, plus manual portal work |
| Generic app plus custom portal connector | €2,000–6,000 + €8,000–20,000 connector | €2,000–6,000 / year + upkeep | €14,000–40,000 |
| Custom service centre software, phased | €25,000–60,000 build + €1,100–3,600 hosting | €1,100–3,600 / year + changes | €28,000–71,000 |
The custom range sits above a typical first phase for a single-workflow tool because manufacturer portals, ERP parts sync and fiscal devices are each an integration with its own rules, test cycles and failure cases. The custom option has no per-user licence and adds manufacturers as modules. It only makes sense when the hours in the previous section are real.
Our process keeps the risk manageable. A free 30-minute call tells you whether custom makes sense at all. If it does, a paid discovery workshop maps your workflow, brands, portals and fiscal setup and produces a written specification and fixed quote. The build then runs in phases, each priced and approved separately, with the first usable module live in weeks. Payment is 30% upfront and the rest on milestones, with no licence fees, and hosting and maintenance starts from €89 a month. See the custom software page for how we work.
Quoting and billing is covered in more depth in quote to invoice software.
How we did it for ServiceCore
ServiceCore runs Transilvania Service, an appliance service company that repairs appliances under warranty for major manufacturers and for paying customers.
- Online booking and public repair tracking on transilvaniaservice.ro, connected to ServiceCore through an API, plus digital check-in with photos, condition checklist and customer signature.
- Two-way sync with Samsung I-GSPN: service orders, status changes and parts used are reported automatically.
- Warranty claims to manufacturers, subcontractor commissions and labour and transport price lists per brand.
- Parts ordering, receipts, stock and transfers synced with Business Central.
- Invoices and fiscal receipts printed on Datecs printers through a dedicated Windows helper app, with ANAF company lookup and automatic email and SMS updates at every step.
The result is one system from online booking to fiscal receipt, manufacturer reporting without double data entry, and customers informed automatically at every step of the repair.