Repairs overview
Restock tracks repairs in two places, using the same repair lines in both:
- Inside a buy order — log what you fixed on a device you bought, so the cost rolls into that device's cost basis.
- On the Repairs screen — a job of its own, either on devices already in your inventory or on devices a customer brought in.
One repair, one or more devices
A repair can cover several devices at once — a customer's phone and their tablet on the same job. Each device keeps its own repairs and its own totals, and the repairs table shows the model and IMEI / serial on every line so you can always tell which device a repair was for.
You choose what you're repairing first:
- I own this device — it's in your inventory. The repair is a cost, and it raises that device's cost basis. Nothing is charged, because nobody is billing you for work on your own stock.
- I'm repairing for a customer — their device, not your stock. You record what you charge, and see the profit. It never enters your inventory or your stock counts.
That choice applies to the whole repair. To do both, create two repairs.
Repair lines
A device can have as many repair lines as it needs. Each line records:
| Field | What it means |
|---|---|
| What's being repaired | Picked from your Repair Types library, grouped by device family |
| Part cost | What you paid for the part. Optional. |
| Amount charged | What the customer pays for that repair |
| Profit | Calculated for you: amount charged − part cost |
Profit updates live as you type, per line and as a total across the device.
Repair Types
Every organization starts with a library of around 30 common repairs — screen, battery, charging port, HDMI port, and so on — grouped into Phone / Tablet, Laptop / MacBook, Console and Other.
Edit it under Business Settings → Repair Types: add your own, rename, or deactivate ones you don't offer. Deactivating hides a type from the dropdown without touching repairs that already reference it.
Repair tickets
A repair ticket works like a buy order. Choose one of two starting points:
📦 Repair an inventory item — pick a device you already own. Repair costs raise that device's cost basis, so your profit when it sells accounts for the work you put in.
🆕 New repair (customer's device) — take in a walk-in. You enter the device manually (IMEI optional), and it is recorded for repair history only.
A device brought in by a customer is not added to your inventory. It never appears in stock counts and can never be sold. Only its repair history is kept.
Statuses
Tickets move through Needed → In Progress → Waiting on Parts → Ready for Pickup → Completed.
A repair marked Skipped is work you decided against. It never counts toward cost, profit, or the customer's invoice.
Invoices
When you mark a ticket Completed and left "Generate a repair invoice" ticked, a customer receipt becomes available to download from the ticket.
It lists each repair and what the customer is charged.
Your part costs never appear on the customer's invoice — only what they are being charged.
Repairs in your analytics
Repair work feeds your overall profit, but the two kinds are counted differently, on purpose:
- A customer's device brings in money that no sale records, so what you charged and what the parts cost are both added to your revenue and expenses.
- Your own inventory is already accounted for — a repair raises that device's cost basis, so it shows up in your profit when the device sells. Counting it again would double-count the same money.
The upshot: repairs on customer devices show up as extra profit straight away, while repairs on your own stock show up when you sell the device.
Who did the repair
Each repair records who did it. Leave it as Myself for work done in-house, or pick the shop or technician you sent it to.
That list comes from your customers: anyone marked Repair Store or Technician on the Customers page appears in it. A customer can hold several types at once, so the shop you buy from can also be the shop that fixes your screens — mark them as both and they show up wherever they belong.