What the repair shop software does

ServiceCenterSoft carries a repair from the minute a customer puts a device on the counter to the minute they collect it and pay. Below is what the software does along that path, with links to the detail, and an honest list of what it does not do.

A day in a repair shop

9:10. The first customer arrives with a phone. The front desk fills in one form: model, the fault in the customer's words, the state of the case, what came with it, serial number, due date. Prints the job sheet, the customer signs and leaves.

10:30. A technician opens the list, sees what is on them and takes the most urgent one. Opens it up and builds the estimate: "replace flex cable" × 1 at the price from the work list, the part from stock. Sets the status to "waiting for a part" (repair workflow).

11:00. The request for the cable is emailed to the supplier from inside the software. Now it is not "waiting for a part" but a specific repair held up since a specific date (spare parts).

12:00. The estimate goes to the customer for approval — by email or Telegram, with a link. The customer opens it on the phone, sees every line and the total and presses "I agree". The job card now says "customer approved" — no "how much will it be?" call needed.

14:20. Yesterday's laptop is finished. A button sends the customer an email and a Telegram message with the amount, the address and the opening hours. The "any news?" call never happened (notifications).

17:45. The customer collects the laptop and pays the balance left after the deposit by card. The front desk records the payment and sets a closing status — the handover date fills itself in.

At month end. The owner opens the report and sees what was handed over, how much of it was received, what each technician is owed and what the service kept after parts and staff shares (reports).

None of that is typed twice: each step takes its data from the one before.

Intake and documents

One form on one screen, the customer found by any digits of their phone, a new one created on the spot. "Copy the last one" books an identical repair in seconds. Job sheets and certificates print on A4 with your logo and the details of the branch that took the device in, and you edit the form yourself. More about the intake form →

Repair workflow

Your own statuses in your own colours, a work log with author and time, internal comments, overdue dates in red, quick filters and a filter that lives in the page address. Change history across eleven fields answers "who did this". More about the workflow →

Estimate and payment

The price of a repair is built from lines: what was done, how many, at what price, and the amount. The base comes from the device price list, the warranty price list or your own figure; a labour line is picked from the work list with its price, a part from stock. The estimate can be sent to the customer for approval: they open the link, see every line and press "I agree" or "I decline", and the answer shows up on the job card and in its history. There can be several payments — a deposit and the balance — and the software shows what is still due. The same estimate prints on the completion certificate.

Spare parts

Stock by quantity that changes only through movements: received, used in a repair as an estimate line, written off, stocktake. Purchase and selling price, the cost inside every repair, minimum stock with a "running low" filter, a supplier directory. Requests are tied to a job, supplier emails go from the software, and "Arrived" receives the part into stock at once. More about stock →

Customers

A ready email in the customer's language rather than yours. Their own portal showing only their repairs, read-only. The mail log shows what failed to send, and why. More about notifications →

Money, people and branches

Each technician's earnings for any period, broken down by estimate lines; the manager's share of money received; payouts and the balance still owed. Branch statistics: taken in, done, handed out, in progress, waiting for parts, in storage — plus revenue and the service's profit. Reports export to CSV. Permissions are checkboxes, and each person sees exactly what they should. Reports → · Branches and rights →

Reference lists: the software adapts to you

Almost everything other systems hard-code is a reference list here, maintained by you. There are more than ten of them, built on one mechanism: statuses, repair types, repair categories, devices, work items with prices, brands, suppliers, payment types, partners, customer labels, rates, cities.

Which means the software does not impose somebody else's workflow. If your status is called "queued for diagnosis", that is what it will be called. If you have five repair types rather than three, you create five. A new brand is a line in a list, not an email to the developer.

An entry that jobs still refer to cannot be deleted: otherwise old repairs would show blanks where the status or the device used to be.

Which kind of service

The core is the same but the work differs, so each case has its own page with the detail: phone repair, home appliance service, computer repair, authorised service centre.

What the software does not do

Collected in one place so you do not go hunting, and do not feel let down after paying:

• No SMS — they cost money. The email, a Telegram "ready" message and the customer portal are what works.
• No charts and no net profit after rent and taxes. The software calculates the service's profit after parts and staff shares, but it does not know your other costs. Reports export to CSV.
• No exchange with manufacturers' portals.
• No mobile app — though everything works in a phone browser.
• No callout planner with a map and a route.
• No on-screen signature and no sending the job sheet to a messenger.
• The ready email does not go out by itself on a status change — it is sent with a button.

Some of this will appear, some will not. If one of them is what you need, write to us — it counts as custom work.

Who this is not for

Better said now than refunded in a month.

• Chains of dozens of locations with separate legal entities, consolidated reporting and a warehouse with barcodes and transfers between locations. This is built for a shop with one to five locations.
• Anyone who needs integration with a manufacturer portal, an accounting package or a till. There is no data exchange.
• Field teams who need an app with routing and technician geolocation.
• Businesses that are not repair. A salon, a clinic, a tailor — those have their own entities, while everything here is built around a device, a job sheet and a serial number.

If your case is on that list, do not spend time on the demo. If it is not, the demo takes ten minutes and costs nothing.

What you need to start

A browser and an internet connection. The software runs on our server: nothing to install, update or administer, and we handle the backups. It opens on the front desk computer, on the owner's laptop and on a phone.

What it costs

One price for the whole shop: no charge per employee, per seat or for a second location.

You can try all of this yourself in the demo — no registration needed.

Frequently asked questions