Repairs and service history by serial number
The customer asks: Each repair, test and spare part kept against the unit's serial number, from intake to hand-over, with the unit's whole service history in one place
- Verdict: Ready, with limits (4)
- Door: Manifest · area: Documents and print › Your own records, fields and buttons
- Recipe: Repairs by serial number
- Sample: S58 — Repairs by serial number (pp_rpr)
- Checked: 2026-10-29 · bench
What you build
A repair as your manifest's own record type, kept against a Serial No: the item and its warranty date read from the serial, the customer and their phone read from the customer, the fault, the condition at intake, the tests and their results, the work done and the parts fitted with their own serials. A workflow Received → In repair → Ready to collect → Collected (or Cancelled) and a save rule that then locks everything the slip prints, on every door. Every repair is listed under its serial number, its customer and the sale that paid for it; a print format gives the repair slip with a unit tag; a report lists the open repairs by the date promised; a field on Stock Entry names the repair a Material Issue's parts went to.
Limits
- The app holds no charge: the till charges the repair as a service item, and the repair names the sale. A quote the customer approves first, or a deposit, is a version of your own.
- The repair is written in iVendNext Desk; a till key that takes a unit in at the till is a version of your own.
- Store staff need Read on Serial No, which the retailer gives them, so the form shows the serial's item and warranty date.
- A manifest's notification goes only to the retailer's own users: telling the customer the unit is ready is the retailer's own Notification.
Tell the customer
Each repair is recorded against the unit's serial number, from the counter to the hand-over, with the tests, the work and the parts; the unit's whole history is one list under its serial, and the customer gets a slip.
What next
- Tell the customer the 4 limits above, and write them into the proposal.
- Follow the recipe: Repairs by serial number.
- Copy the sample: S58 — Repairs by serial number (pp_rpr), and change it.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
- Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.
Install it on your sandbox the way the shop's administrator will; the checker refuses a manifest that declares code.
Related needs
- When a maker recalls units by serial number, find the serials sold and the customers who bought them, and stop the rest being sold — Ready, with limits (6)
- Donated goods taken in with the donor's details, by kind and condition, and a donor receipt given at intake — Ready, with limits (3)
- A button on a record that rechecks stock in our ERP or assigns a pick route — Ready, with limits (1)
- Extra fields on a purchase order and its lines, a goods receipt, a stock transfer, an expense or the till close — Ready, with limits (1)
Start a project shortlist with this need · Put it in your blueprint · Every need