Skip to main content

Find and manage repairs

Orders → Repairs opens on the List, with Board, Bench, Dashboard, Registrations, Vendor dispatches, Supplier recovery, and Warranty reserve as tabs across the top. The list and the board are the two everyday ways to find a repair and work it — the list for searching and bulk work, the board for watching where every piece sits in the process.

The Repairs list​

Go to Orders → Repairs. Each row is one repair, with these columns (several hidden by default — show them from the column selector). On a typical desktop screen every default column fits without scrolling sideways. The row checkbox and ID stay pinned at the left (the pin icon beside ID in the column selector), so on a narrower screen they stay in view while you scroll.

ColumnWhat it shows
IDThe repair number. A purple Match chip appears when any of its pieces still needs product matching.
CustomerWho the repair is for.
UnitsHow many pieces, and their product names.
IssueWhat's wrong.
CoverageOne chip per piece's coverage.
StageOne chip per piece's work stage.
SLANot started, due soon, overdue, paused, met, or missed, with a day count such as Due 18 Nov · 6 days left or Overdue 4 days. Days left round up; days overdue count whole days late. The same count shows on the board, in Bench, and in the repair's own header.
TechThe assigned technicians, as avatars showing their initials (for example MC). Hover an avatar for the technician's full name. A technician whose user account can't be found shows as a grey question-mark avatar named Unknown user with its number.
Warranty costWhat the repair costs you: its posted warranty and goodwill costs. Costs billed to the customer or claimed from a supplier aren't counted, and neither are planned costs, so a customer-paid repair shows —. Hover the (?) beside the header for the definition; the repair's Costs & billing tab has the full record.
StatusThe case's own status.
SourceWhere the claim came from, for example Portal, Shopify, or Internal. A repair started from a return receipt reads Return; hover the chip for its full name, Return receipt.
Warehouse, Sales order, RMA, Serials, ReceivedHidden by default.
CreatedThe date the case was logged, for example Nov 7, 2026. Hover it for the time as well.

A long customer, product, or issue name is cut to one line ending in …; hover the cell to read it in full.

Click a row to open that repair.

Search, filter, and save a view​

  • Search by repair number, customer, order, RMA, or serial.
  • Quick filters, plus a full Advanced Filters builder for anything more specific.
  • Saved Views — your favorites bar, and the full views manager, work the same way as everywhere else in SKU.io.
  • A Created date-range filter.
  • All / Active / Archived at the bottom of the table.
  • Right-click a row for Open repair, Open in new tab, View customer, View sales order, View RMA, Print tags, Send to vendor, and Close repair — each one disabled with a reason when it doesn't apply (there's no sales order to view, or you lack the permission).

Act on several repairs at once​

Above the table, a dashed strip reads "Tick repairs to assign, move, send to a vendor, print tags, email, close or export several at once." Select rows with their checkboxes and the bulk action bar takes that strip's place — N selected, the Selected Only / All Filtered scope toggle, the actions, and Clear Selection — without moving any rows. Or switch the scope toggle to All Filtered to act on everything your current filters match, not just the loaded page. Then, from the bulk action bar (an action that doesn't apply to your selection stays white with greyed-out text, and its tooltip says why):

  • Assign — set a technician, or unassign.
  • Move stage.
  • Send to vendor.
  • Build plating batch.
  • Print tags.
  • Email update — choose which template to send.
  • Close — skips any repair whose pieces aren't all resolved.
  • Export — see Export repairs.

Send to vendor and Build plating batch are covered in Set up and send units to a repair vendor.

The Repair board​

Click Board. Each card is one piece, not one repair — a repair with three pieces shows up to three cards — arranged in columns by work stage: Pending receipt → Triage → Diagnosing → Awaiting approval → Awaiting parts → In repair (split into On bench and At vendor) → QC → Resolved. Every column shows a live count of its cards; on every column except Pending receipt and Resolved, that count turns red once it passes 15.

Group cards into lanes by Technician or by Warehouse, or toggle My queue to see only your own. Each column loads 50 cards at a time, with Load more underneath.

Moving a unit on the board​

Drag a card to a new column, or use its ⋮ menu for the same choices without dragging. If you drop it somewhere it can't legally go yet, the card snaps back with the reason — for example "Receive the piece first — it moves to Triage when it arrives." or "Complete diagnosis and QC first." Dropping on At vendor opens Send to vendor instead of moving the card directly. If someone else moves the same card first, the board refreshes with "Someone else just moved this unit."

Scan a repair, or print its tag​

Go to Orders → Repairs → Bench. In the Scan a repair tag box, scan or type a tag code (RO-2026-00412-L2), a serial number, or a bare repair number (which opens its first open piece), then press Enter or click Open — that unit opens directly. Use the camera scans a tag with your device's camera instead. A code that matches nothing shows No repair unit matches "<code>".

A tag can be printed for a single piece from the repair itself, for a whole repair's pieces, or in bulk from the list's Print tags action — a 4×6" PDF with one tag per piece, opened in a new browser tab. Choosing zero repairs or units throws "Choose at least one repair or unit to print tags for." Unlike exporting, printing tags has no background-job fallback, so a very large bulk selection generates every tag synchronously in one request — keep a bulk print to a reasonable batch size.

Repair history on other records​

A Repairs card — search, a status filter, an Open/All toggle, and (on most of its placements) a Create repair button pre-filled with that record's context — is embedded on five other pages, each scoped to that record. Its Opened column shows the date only, for example Nov 8, 2026 — hover it for the time. Product shows the piece's name with its SKU in grey after it. The SLA column shows the same SLA chip as the main Repairs list. A closed repair reads Met or Missed; an open one shows its due date and days left, for example Due 30 Nov · 22 days left, or Not started while the clock has not begun. Hover the chip for the full due time:

  • A customer's Repairs tab.
  • A product's Repairs tab.
  • A supplier's Performance → Repairs sub-tab (no Create repair button here).
  • A serial number's Repair history.
  • A sales order's Repairs tab.

On the Product and Supplier placements, a strip above the list reads "Repair rate · last 365 days" — the share of units shipped that came back for repair, how many of those repairs had no order on file, and a link into the full Repair Rate report filtered to that product or supplier.

Next steps​

Video transcript

Open the Orders section, scroll down its long navigation menu to Repairs, then choose List. It opens as a table, with Board, Bench, and Dashboard as tabs across the top. Search by repair number, customer, order, RMA, or serial. The table narrows to the matching results. Start by clearing the search box, so every repair shows in the table. Then add a quick filter from any column instead, like SLA status. For anything more specific, it can grow into a full Advanced Filters condition. To act on several repairs together, tick the checkbox at the start of each row. A bulk action bar appears, with Assign, Move stage, Print tags, and Export. Click Board to see every piece by work stage instead — one card per piece. Dragging one into another allowed column moves it along the workflow. The repair history appears on a customer, product, supplier, serial number, or sales order page.

Last verified: