An electrical accessories business sells specification. A gland is bought because it is the right size and thread for the cable and carries the approval the site requires — IS, IEC, ATEX, IECEx or UL, each with its own laboratory, scope and expiry. The part is interchangeable; the certificate is not. Which makes it striking how often the register of those certificates is a spreadsheet maintained by one person.
The failure mode is predictable and expensive. An order is accepted for a part whose certification lapsed two months ago, or whose scope does not cover the customer’s application, and nobody notices until third-party inspection at site — the furthest point from the factory and the most costly place to find out. The consignment is rejected, the renewal is started in a hurry, and the commercial team explains a delay it did not cause.
Treating approvals as master data changes where the problem surfaces. Certificate, laboratory, scope and expiry sit against the part, renewals are raised as planned work before they lapse, and order entry checks the approval an enquiry requires against the approval the part actually holds. An unsupported combination is then refused at enquiry, which is a sales conversation rather than a site incident.
The second benefit is quieter. When the certificate that released a lot travels with the despatch documents, a warranty claim two years later can be answered with the batch, the supplier and the test record attached. That evidence is what separates a technical discussion from a commercial concession.
High-SKU channel businesses tend to invest in pricing and stock visibility first, which is reasonable. But the orders lost to a lapsed certificate never appear in either report, because the order was never lost — it was rejected somewhere else entirely.
