SpecLatch for lighting

Lumens, CCT, and CRI — one luminaire record behind every cut sheet and submittal

Specification-grade lighting lives and dies by its documents: cut sheets, submittals, photometry, and the ordering matrix behind them. SpecLatch models the family once — outputs, optics, finishes, options — and generates the documents and public data your reps and specifiers pull from.

The fields you actually spec

SpecLatch has no fixed schema — you model your own catalog. These are the kinds of fields lighting teams typically define, each unit-aware and tiered from day one:

Photometrics

  • Luminous flux
  • Efficacy (lm/W)
  • CCT
  • CRI
  • Beam angle
  • IES files

Electrical

  • Input power
  • Voltage range
  • Dimming (0–10 V / DALI)
  • Power factor
  • THD

Physical

  • Dimensions
  • Weight
  • Finishes
  • Mounting options
  • IP / IK rating

Compliance

  • UL / cUL
  • DLC listing
  • Energy codes
  • Warranty terms

Series & models

One series, every model's data

Shared construction lives on the series record; each model records only what differs. No more forty near-identical rows where one forgotten cell becomes a customer-visible error.

Rollups go the other way: the series knows its own range, computed from the models beneath it.

What SpecLatch does with lighting data

The family is the unit

One family, every ordering code

Outputs × CCTs × optics × finishes — modeled as a series with model records underneath, not as forty rows pasted in a spreadsheet. Shared data lives once; each SKU records only what differs.

Documents, designed once

Cut sheets and submittals that fill themselves

Design the cut sheet once — photometric summary, dimensions, ordering matrix, your brand. Every model in the family gets its document from live data, regenerated when anything changes.

Portal & API

Reps and specifiers read the published truth

A public product page and a read-only API serve the published, public-tier data — while dealer pricing stays tiered away on the same record. Import the existing matrix from CSV to start.

Three questions that tell you if SpecLatch fits

If two of the three sound familiar, it does:

01

Projects are won on the submittal package — cut sheets and photometry the specifier can approve.

02

A driver change means redoing the cut sheet, the spec grid on the website, and every agent's file — one edit, many artifacts.

03

Your catalog is families with ordering codes underneath: same fixture, many outputs, CCTs, and finishes.

See it on your own catalog

Start a free trial and import one of your own product families — the fastest way to evaluate SpecLatch is on your own data.

Start your free trial

30 days of Growth-plan features · no credit card required · your data exports any time