Demarc › Answers › Why does a cabling warranty submission get delayed or rejected?
In their own words
“Poorly managed or badly organized data can delay approval or even result in the rejection of the warranty.”CommScope warranty webinar description · source
“End Users may refuse to sign warranty documents when this information is incorrect or incomplete, which results in delays in processing.”Hubbell Mission Critical registration steps · source
“Many cabling vendors will reject any results carried out with a 2-cord reference, which could prevent you from acquiring a warranty.”Fluke Networks blog, top 10 cable testing mistakes · source
What it is
A manufacturer system warranty (Panduit, CommScope, Belden, Leviton, Hubbell and others) is issued only after the manufacturer's warranty desk reviews the installer's package: the certification results for every link, the bill of materials, the cable schedule or drawings, the installer's program ID and the end-user details. Each program publishes its own list, and a package that is missing one item, carries a failing link, or was tested the wrong way comes back or waits.
The common reasons are written in the manufacturers' own documents: results that are not 100% passing, a tester outside its calibration year, a fiber reference method the program does not accept, a copper test configuration (permanent link or channel) the program did not ask for, and missing project or end-user information.
How Demarc does it
Demarc builds the package from the test export you already have and checks it against the program you pick, item by item, before you download it. Every item it checks comes from the manufacturer's published document, and each rule in the code carries the manufacturer's sentence and the document URL. Anything missing is listed by name on the kit page, so you fix it before the desk sees it.
You still submit the package yourself, through the manufacturer's portal or desk. Demarc prepares it; it does not send it for you.
| Program | What the Demarc kit checks before you download it |
|---|---|
| Panduit |
|
| CommScope |
|
| Belden |
|
| Leviton |
|
| Hubbell |
|
The bar Demarc is held to
Every program Demarc supports lists each missing item the manufacturer's own document names. When the desk answers, you record accepted or sent back on the project, with the desk's reason; Demarc turns a returned package into a checklist of what to fix, and the project dashboard shows your first-time acceptance per program. With no answered submissions it says "no data yet", never 0%. We do not publish an acceptance rate across customers: none has been measured yet.
What the usual tools leave to you
Tester reporting software checks each result against the test limit and cable IDs planned for the job. Whether the package meets a particular manufacturer's program is left to the installer: the tester vendor's own guidance is to make sure tests follow the specification required for the certification job.
Questions
- What gets a warranty package sent back?
- Incomplete or incorrect information, failing or marginal links, a tester outside its 1 year calibration, a 2-cord fiber reference where the program names the one-jumper method, and a copper test configuration the program did not ask for. Each of these is in a manufacturer's published document.
- Does Demarc submit the package to the manufacturer?
- No. Demarc prepares and checks the package; you submit it through the manufacturer's portal or desk.
- Which warranty programs does Demarc check against?
- Panduit, CommScope, Belden, Leviton and Hubbell. Each program's requirements, quoted, are on the warranty programs pages.
Related answers
Do I send the original raw tester file or a PDF for a cabling warranty? · Will the manufacturer reject results from a tester out of calibration or a 2-cord fiber reference? · How many days do I have to submit test results for a manufacturer cabling warranty? · All answers · Warranty programs · Free export checker