Skip to content
How it works

See every step from source file to approved catalog.

Follow one synthetic lighting product through a continuous, evidence-led workflow—from supplier spreadsheet to reviewed channel output.

Synthetic example. The readiness score is illustrative.
Catalog workspace Illustrative example
Source files
supplier-master.xlsx2,480 rows
LL24-spec-sheet.pdf8 pages
product-images146 files
catalog-export.csvLegacy record
4 sourcesMatched to 1 product
CAILAR
01Extract attributes
02Match product
03Normalize units
04Score confidence
05Route exception
Reviewed record

Aster LumaLine 24

LED wall fixture · AST-LL24-30-BK

92ready
Channel readiness · illustrative
Wattage24 W Verified
Input voltage120–277 V Review
Output2,200 lm Verified
Color temp.3000 K Verified
Source evidence attached3 files · 7 approved fields · 1 exception
Ready for review
One product, end to end

A workflow built around exceptions—not repetitive checking.

The example stays constant so you can see what enters, what changes, why it changes, and what gets approved.

01

A supplier spreadsheet arrives

The spreadsheet includes 148 lighting products, mixed field names, inconsistent units, and incomplete variant relationships.

supplier-master.xlsx148 rows
02

Technical details are extracted

Cailar links the product to an authorized PDF and extracts output, dimensions, color temperature, temperature range, and voltage.

LL24-spec-sheet.pdf7 attributes
03

The sources disagree

The spreadsheet says 120 V. The specification PDF says 120–277 V. Both values and their evidence remain visible.

Input voltageConflict
04

The exception is routed

A catalog manager sees the conflicting values, confidence, source context, and the downstream records affected.

Review queue1 decision
05

The approved source is chosen

The manager approves the current technical PDF, records the decision, and keeps the change history.

Approved value120–277 V
06

The product record is completed

Units, taxonomy, product family, attributes, evidence, and approved channel content are brought together.

Readiness92 / 100*
07

Channel output is prepared

The reviewed record is formatted for the agreed catalog destination without replacing the existing PIM or ERP.

DeliveryCSV + JSON

* Illustrative score calculated from the synthetic sample’s defined field requirements.

Human review

Your team decides what becomes trusted data.

Cailar concentrates judgment where it matters: ambiguous matches, conflicting values, missing evidence, and rule failures.

  • View both source values
  • Open the original source context
  • See affected products and channels
  • Approve, reject, or defer
  • Retain the decision history
Exception queue1 open
Aster LumaLine 24AST-LL24-30-BK
Supplier spreadsheet120 VView row 82
DeferApprove 120–277 V
A practical first step

Bring one difficult product category.

We will help define the sources, expected output, review rules, and representative sample for an initial catalog audit.

Discuss your catalog