USE CASE

Warranty claims

Check warranty by serial number, log the claim, send a technician and close it on the record.

The problem

A customer calls with a faulty unit. Someone has to find the invoice, work out when it was sold, check whether it is still under warranty and decide who pays. Without serial numbers tied to sales, that takes a morning and ends in an argument.

How it runs in Sundial

1. Serial numbers are recorded when the product is delivered. Inventory links each serial to the delivery, the customer and the warranty period set on the item.

2. When the customer reports a fault, open a warranty claim in Support and enter the serial number. Sundial shows the item, the customer, the delivery date and whether the unit is under warranty or out of it.

3. Record the complaint and assign the claim to a person.

4. Schedule a maintenance visit if a technician has to go on site. The visit records what was found and what was done.

5. Close the claim with its resolution. If the unit is out of warranty, raise a quotation or sales invoice for the repair from the same records.

What the team sees

Support sees open claims by status and age. Service managers see visits scheduled and completed. Quality sees which items and batches generate the most claims, which feeds supplier and production conversations. Finance sees warranty work separately from billable service.

Sample for Kestrel Workspace: 18 open claims, 12 under warranty, 4 visits booked this week, one item model accounting for a third of all claims.

With AI (coming to Sundial)

Sundial is designed so an agent can spot a rising claim rate on one item or supplier batch and raise it for the quality team to review. This is on the roadmap; today the same pattern is visible in the claims report.

THE NEXT AGE OF ERP

Run the whole business
in one calm system.

Try the demoTalk to us