How Can We Help?
Almost every unexpected warranty answer is missing configuration rather than a
fault. Read the Reason on the line first — it names the missing piece.
| What you see | Why | What to do |
|---|---|---|
| “Not mapped to a warranty group” on most lines | The parts’ families have no Family → Group rows. | Map each family you service onto a group. This is the one step that makes the whole feature work — a family with no row can never be covered. |
| One part is wrong while the rest of its family is right | That part needs to differ from its family. | Add it to Part exceptions against the correct group. |
| “No warranty on order” | No warranty was chosen on the order. | Select the warranty the customer bought on the order header. |
| “No start date” | The order has no delivery dates on its confirmed items, so there is nothing to start the clock from. |
Check that the confirmed items carry delivery dates. The warranty start is set automatically once they do. See When the warranty clock starts. |
| “This warranty group has no number of warranty days set” | The part resolved to a group, but that group’s Days is blank or zero. | Set the group’s Days on the Warranty Groups pane. Note this reads as “cannot determine” rather than “expired” on purpose — a group with no days is unfinished setup, not an out-of-warranty part. |
| Days allowed is not the number you just configured | You are probably looking at a line assessed earlier. Each ticket line stores the answer it was given, so it does not change under you. |
Re-add the line to reassess it. Remember that editing a group’s Days also changes the answer for orders already sold under that warranty — to change cover from now on, declare a new warranty type with a later effective date. |
| A whole-unit line is always amber | Expected — a configured unit has no part family to map. |
Select the specific assembly or part being serviced. |
| A part is never covered, whatever you configure | It is on the series’ service exclusion list. |
Reason will say excluded. If that is wrong, the exclusion list needs correcting. |