Repair-shop ERP · built in Sweden, hosted in the EU
RepairX takes a device in at the counter, moves it through diagnosis, estimate approval and repair, pulls the right part from the right branch, and invoices the customer — without anyone retyping a thing.
Live demo — type your own intake line and watch it parse
Quick intake
Parsed ticket
Today
94%
Repairs completed
last 9 days
The messy middle
Repair shops rarely fail at repairing things. They lose money in the gaps between the counter, the bench, the stock room and the books — and every gap is filled by someone retyping something.
Which device is waiting for a part, which is waiting for a customer to say yes, and which was promised for today — that knowledge sits with whoever is in the workshop. When they are off, the answer to “is my phone ready?” is a guess.
Screens are taken off the shelf and written down later, or not at all. The spreadsheet says four, the drawer has one, and the customer was quoted a same-day repair on a part that is already in someone else’s device.
A counter sale, a repair invoice and the email thread about both live in three systems. Nobody can answer what a customer is actually worth, or what a branch actually earned, without an evening of copy-paste.
RepairX closes the gaps by making them the same record. One ticket carries the device, the estimate, the parts it consumed, the payment and the customer it belongs to.
What it does all day
The surface is deliberately quiet — a few fields, a clear board, obvious next actions. Everything that makes a repair business hard to run is handled behind it.
Every repair moves through stages you define — intake, diagnosis, waiting for approval, in repair, quality check, ready. The board shows the whole workshop at a glance and records how long each stage actually took.
Kanban board · stage timing · assignment
A device is an asset, not a line on a ticket. The same phone coming back next year arrives with its own history: what was replaced, by whom, under which warranty, and what the customer was charged.
Serialised assets · warranty tracking
Send an estimate by SMS or email and the customer approves it from a link — no account, no app. The approval is recorded server-side with the time, address and device it was signed from.
Tokenised approval links · signed audit trail
Consuming a part on a repair moves stock at that branch, records the serial and prices the line. Parts below their minimum surface in one list, with a purchase order one click away.
Per-branch stock · serials · low-stock reordering
Accessories, out-of-warranty work and repairs share one register. Split payments, store credit, gift cards and loyalty all settle against the same customer, with VAT handled the way Swedish accounting expects.
POS · split payments · store credit
One record holds every repair, every sale, every device and every message. When someone calls, whoever picks up can answer without asking which branch they visited last time.
Unified history · wallet · canned replies
One repair, end to end
This is ticket RX-2418 as the workshop sees it. Step through the stages — the ticket, the estimate, the part it consumes and the invoice are all the same record, so nothing is entered twice.
Repair in progress
iPhone 14 Pro OLED (OEM)
SCR-IP14P-OEM · serial #A7741
on hand
Labour · 38 min of 45 min estimated
84%
Consuming the part writes the stock movement, the serial and the technician onto the ticket in one action — nothing is reconciled by hand at the end of the day.
Activity
Ticket created
09:12Walk-in · Södermalm · by Elin Lund
Device matched to asset
09:14Same iPhone repaired 12 Mar 2025
Diagnosis completed
10:38Digitiser dead, battery healthy
Estimate sent
10:52SMS + email with approval link
Customer approved
11:26Signed online · logged with IP + device
Part consumed
13:05SCR-IP14P-OEM · serial #A7741
AI where it saves keystrokes
RepairX uses AI in the four places where a repair shop loses the most time to typing — and nowhere else. Every suggestion lands in an ordinary editable field, marked as a suggestion, and nothing is written to your books until a person confirms it.
The same treatment marks every AI-assisted field in the product, so it is always obvious which values a person entered and which ones were proposed.
Type what the customer said. RepairX fills the customer, device, IMEI, fault and a priced repair, then asks only for what is genuinely missing.
Photograph the delivery note. Lines are read, matched to existing SKUs by article number or name, and the ones it is unsure about are flagged for review.
Incoming mail is scored for spam, matched to an open ticket or an existing customer, and turned into a lead with the fields already extracted.
Describe a device being sold to you and get a defensible purchase price with the condition factors that produced it, ready to accept or overrule.
The rest of the business
A repair shop is not only repairs. Switch between the modules the same way your staff do — every one of them reads from the same customers, the same parts and the same branch.
Stock is per branch. The catalogue is shared company-wide.
| Part | SKU | Södermalm | Cost | Status | |
|---|---|---|---|---|---|
| iPhone 14 Pro OLED (OEM) | SCR-IP14P-OEM | 5 / min 4 | 2 890 kr | In stock | |
| iPhone 13 battery (OEM) | BAT-IP13-OEM | 2 / min 6 | 420 kr | Below minimum | |
| Galaxy S24 AMOLED assembly | SCR-SGS24-OEM | 3 / min 3 | 3 120 kr | In stock | |
| Water-resistant adhesive seal | ADH-UNI-WR | 41 / min 20 | 38 kr | In stock |
One company, many counters
Multi-branch is not a tier you upgrade into once it hurts. Locations, per-branch stock and company-wide catalogue are in the data model from the first ticket — so opening the next shop is an afternoon, not a migration.
Parts, services and prices are defined once for the company. Stock, tickets, sales and cash are counted at the branch that actually holds them.
A technician who covers a shift in another branch sees that branch’s work without a second login. Managers switch branches from the top bar; the numbers follow.
Revenue, turnaround and margin per branch, per technician and per repair type — the same figures the branch manager sees, added together.
Trust and tenancy
A repair shop's system holds customer identities, device identifiers and payments. That deserves more than a filter in the front-end and a promise.
Each company is its own tenant with row-level grants. A request crafted by hand cannot read another company’s rows, because the filter is not in the browser — it is on the row.
People are invited by email and given a role. Access is revoked per person and every issuance is on the record. A code that spreads by screenshot is not a way to control a billing boundary.
Tickets, payments, sales, purchase orders and customers are written by a server function that re-derives the company from a verified membership — a client cannot claim to belong somewhere it does not.
When a customer approves an estimate from a link, the address, the device and the moment are recorded server-side. The customer is told before they sign, and the record cannot be edited from the browser.
RepairX runs on infrastructure hosted in the EU. Group customers can have a dedicated instance. Exports are yours to take at any time, in a format you can actually read.
Screens update as the data changes rather than when someone remembers to refresh, and long lists page instead of stopping silently at the first hundred rows.
Who it is for
RepairX does not have a small version that runs out of room. What changes as you grow is how much of it you switch on.
Two or three people, one counter
You already know every device on the bench. What you want back is the hour a day spent writing the same information into three places, and an answer when a customer asks where their phone is.
Two to ten branches
The second location is where spreadsheets break. Stock moves between shops, staff cover shifts, and you need to know which branch is actually profitable — not which one is busiest.
Regional operators and partners
Many counters, shared suppliers, and reporting that has to survive an audit. Roles decide who can price, who can discount and who can see the whole group.
Pricing
Charging by user makes shops share logins, and shared logins ruin the record of who did what. So RepairX charges for the location and lets you give everyone their own account.
Annual billing gives you two months free.
One location, everything that runs it.
Excl. VAT · billed monthly · cancel any time
Several branches under one roof.
Excl. VAT · billed monthly · cancel any time
30 days, all of it, no card
Create a company, invite the person who actually takes devices in, and run a genuine ticket from intake to invoice. If it does not fit how your shop works, you will know by closing time.