Verdana Warranty management · assets, warranties and service orders

Warranties claimed on time, not discovered expired

Warranty value is rarely lost at the negotiating table — it is lost through missing information. Equipment fails, maintenance repairs it or sends it out, and nobody checks whether the failure was covered. The coverage existed, the term was current, and the repair was paid for anyway. The problem is not contractual; it is that coverage status was not available at the moment the repair decision was made.

Months and hours run at once. The service order checks coverage before spend is authorized, and the warranty expires on whichever condition is met first.

What changes with Verdana Warranty management

Coverage stops living in a folder and shows up at the moment a repair is decided.

  • No paying for covered repairs

    The service order shows current coverage and its scope before spend is authorized.

  • Expiration by time or usage

    Months and operating hours, or months and kilometers, tracked in parallel with advance notice on both.

  • Original terms stay readable

    Extensions, replacements and covered repairs are derived records; the warranty itself is never modified.

From asset to claim, step by step

Each step links to the page that explains it in more detail.

  1. The asset and its supplier

    Each asset is tied to the supplier that granted its warranty. Serialized assets are tracked individually with their own service history; lot-managed goods are tracked at lot level.

    What is warranty management →
  2. The warranty and its scope

    What is covered and excluded, the term and the start condition, tied to the asset and the supplier.

    Warranty management →
  3. The clock starts as agreed

    Goods receipt, commissioning or invoice date: the start event is set per warranty.

    Verdana Procurement →
  4. Two conditions in parallel

    Twenty-four months or five thousand operating hours, twelve months or a hundred thousand kilometers, whichever comes first, with advance notice on both.

    Compound expiration →
  5. Failure and service order

    The service order opens against the asset and shows whether current coverage applies, and to what extent, before spend is authorized.

    Verdana Procurement →
  6. The effect as a derived record

    A term extension, a replacement or a covered repair is recorded without modifying the original warranty.

    Evidence of compliance →
  7. History that supports the claim

    The service history per asset or lot is what lets a claim be evidenced instead of argued.

    Evidence of compliance →
  8. Decommissioning

    Warranties change state with the asset instead of generating alerts, and the history is retained.

    Verdana Procurement →

Warranty management in depth

How it works inside, and why it is designed this way.

A warranty with its own lifecycle

Verdana manages each warranty as an object with its own lifecycle, tied to the asset it covers and the supplier that granted it: scope of what is covered and excluded, term, start condition, and status over time. The clock starts on whatever event was agreed — goods receipt, commissioning, or invoice date. And expiration can be compound, which is how industrial warranties actually work: twenty-four months or five thousand operating hours, twelve months or a hundred thousand kilometers, whichever comes first. Both conditions are tracked in parallel on the same asset, the warranty expires on whichever is met first, and advance notice is given on both.

Traceability by the nature of the goods

Traceability follows the nature of the goods. Serialized assets are tracked individually, each with its own warranty and service history; lot-managed goods are tracked at lot level with coverage applied to the batch. That distinction determines whether a claim can be evidenced or becomes an argument about which specific unit failed. When a failure occurs, the service order opens against the asset and the platform indicates whether current coverage applies and to what extent, before spend is authorized.

Effects never rewrite the terms

The effect of that coverage — a term extension, a replacement, a covered repair — is written as a derived record and never modifies the original warranty. That is deliberate: when the scope of a coverage is disputed with a supplier three years later, the original terms must still read exactly as agreed, with the full history of effects recorded around them. Decommissioning closes the cycle: warranties change state with the asset instead of generating alerts about something that no longer exists, and the history is retained.

Frequently asked questions

What teams ask most about warranties and service orders.

Why are valid warranties lost?

Because coverage status is not available when the repair decision is made. Equipment fails, maintenance repairs it, and nobody checks whether the failure was covered. Verdana shows coverage when the service order opens, before spend is authorized.

When does a warranty start?

On whatever event was agreed: goods receipt, commissioning or invoice date. The start condition is set per warranty.

Can a warranty expire by time or by usage?

Yes. Both conditions — for example, twenty-four months or five thousand operating hours — are tracked in parallel on the same asset, the warranty expires on whichever is met first, and advance notice is given on both.

Can lot-managed goods be tracked?

Yes. Serialized assets are tracked individually and lot-managed goods at lot level, with coverage applied to the batch.

Related concepts