Verified document registry

Downloads & Evidence Center

Find files by type, applicable product/series, version and update date. A catalogue supports selection; it does not automatically prove every specification or certificate for every SKU.

Direct answer

Use the document that matches the quoted model and decision

The registry below contains six production-hosted PDF files verified as accessible on 2026-08-05. Confirm exact-model applicability, revision and destination-market requirements before using any file for project approval.

FileTypeApplies toVersionRegistry updateStatus
Besen Panel Light Catalogue 2025CataloguePanel light series
Related product page
20252026-07-31file verified 200/PDF
Besenled Magnetic Track Light CatalogueCatalogueM15 and M20 magnetic track system records
Related product page
Source catalogue2026-07-31file verified 200/PDF
11-MINI Magnetic Track Product CatalogCatalogue11-MINI magnetic track system
Related product page
2024-062026-07-31file verified 200/PDF
UN5 Besenled CatalogueCatalogueUN5 magnetic track system
Related product page
2025-022026-07-31file verified 200/PDF
MT26 Belt Track CatalogueCatalogueMT26 belt track system
Related product page
Source catalogue2026-07-31file verified 200/PDF
MT26 Accessories GuideManual / accessories guideMT26 compatible accessories
Related product page
Source guide2026-07-31file verified 200/PDF

Evidence types still needed

  • Exact-model datasheets
  • Certificates and model coverage lists
  • Test reports
  • IES/LDT photometric files
  • Drawings and BIM/Revit files
  • Installation, wiring and dimming-compatibility documents

Document release rule

A file should record title, type, applicable model/series, version, language, update date, evidence status and reverse links. Missing or outdated files are not represented as current proof.

Downloads FAQ

Does a catalogue prove all specifications on a product page?

No. A catalogue is a selection source. Final specification should use the approved exact-model revision and supporting test evidence where required.

Are these files product certifications?

No. The current verified registry contains catalogues and one accessories guide. Certificate records need issuer, number, validity and model/market coverage.

What if a required file is missing?

Request it through RFQ and keep the requirement marked for confirmation. Do not substitute an unrelated family file.

Request an exact-model evidence package

Provide the model, variant, destination market and required file types so applicability can be reviewed.

Request project documents

02

/shop/

Product Catalogue

03

/solutions/end-to-end-lighting-project-support/

Project Support

04

/contact-and-support/

Request Documents

  • Private internal documents
  • Expired or unrelated certificates
  • Files without version or applicable product scope
  • Downloads need version, language, update date and applicable product.
  • Never expose restricted files.
  • Link files back to product and solution pages.

Continue with products, evidence or RFQ

Questions to confirm before publishing

FAQ schema should only be generated after these answers are visible on the page and fact-checked.

What should be verified before publishing Downloads?

Verify product links, evidence, author or reviewer, fact-check date, schema visibility, and sitemap or noindex behavior on staging.

Can this page use schema immediately?

Only generate schema from visible, verified facts. Do not generate FAQ, Product, Article or Service schema from hidden or unverified fields.

What should remain as needs_confirmation?

Any missing certificate number, project outcome, exact specification, MOQ, lead time, warranty scope, or client proof should stay marked for confirmation.

RFQ ready

Send the project inputs for a specific review

Share drawings, quantities, voltage, controls, application, destination market, required certificates, customization needs and timeline.

Request Project Review