All solutions

SpecLatch for operations & IT

The gap between ERP transactions and customer-facing data, filled

Your ERP is excellent at part numbers, prices, and orders, and silent on everything a customer needs to select the product. SpecLatch is the system of record for that layer, with real access control and no lock-in.

Your ERP keeps the transactions. SpecLatch keeps the specs, and each reader gets the fields its key allows.

Store · scope · serve

Your ERP

Keeps what it is good at, for the same SKU:

  • Part number
  • Customer prices
  • Stock on hand
  • Open orders

It has no place for a unit, a curve or a spec sheet. It reads those from SpecLatch by SKU.

HB-240 LED High Bay

Published

The record in SpecLatch · SKU HB-240

  • Luminous flux33,600 lm
  • Input power240 W
  • Efficacy140 lm/W
  • List price (USD)389.00Internal · not sent
  • Lead time (weeks)2Internal · not sent
  • Unit cost (USD)171.20Confidential · not sent

A tier is set on each field:PublicInternalConfidential

Who is reading

What it receives

GET/api/v1/records?sku=HB-240
{ "records": [{
"modelNumber": "HB-240", "status": "PUBLISHED",
"specs": [
  { "field": "luminous_flux", "value": 33600, "unit": "lm" },
  { "field": "input_power", "value": 240, "unit": "W" },
  { "field": "efficacy", "value": 140, "unit": "lm/W" }
]
}] }
GET/api/v1/records?sku=HB-240
{ "records": [{
"modelNumber": "HB-240", "status": "PUBLISHED",
"specs": [
  { "field": "luminous_flux", "value": 33600, "unit": "lm" },
  { "field": "input_power", "value": 240, "unit": "W" },
  { "field": "efficacy", "value": 140, "unit": "lm/W" },
  { "field": "list_price", "value": 389 },
  { "field": "lead_time_weeks", "value": 2 }
]
}] }
What is the efficacy of the HB-240?

search_records1 record

140 lm/W: 33,600 lm from 240 W.
And what does it cost us?
I can't see a cost. This key reads public fields only.

A key's tier is set when an admin creates it and cannot be raised by a request. A field above it is absent from the response, so a reader cannot learn that it exists. Every key is read-only.

Sound familiar?

Not the ERP's job

Specifications bolted into item masters as freeform text: unsearchable, unvalidated, blind to units.

Access control by folder

Confidential costs live in a spreadsheet whose protection is “the right people know which folder it's in.”

Every tool holds a copy

The website CMS, the document templates, and the sales lists each keep their own version of the data, and nobody owns the master.

In one sentence

SpecLatch fills the technical-product-data gap between ERP transactions and the information customers actually need.

What changes

One enforcement layer

Three visibility tiers per field, applied to the grid, PDFs, portal, and API by one enforcement layer rather than page by page.

The tier model →

A read API with scoped keys

Integrations read the catalog with keys that are rate-limited, scoped to your organization, and capped at a tier. The same keys let an AI assistant answer from the catalog. Included from the Growth plan.

API & AI assistants →

A clean exit, always

One click exports the entire organization to XLSX; documents are standard PDFs. No proprietary formats in the exit path.

Import, grid & export →

Rather see it by industry?

The same system written in your trade's vocabulary: valves, pumps, motion, lighting.

Browse by industry →

Or by capability?

Formulas, curves, confidentiality, documents, the portal, the API and AI assistants. Each has its own page.

Browse the features →

Learn it in the guide

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