Catalog Normalization: Units, Prices, and Providers in One Model
Omnicost normalizes messy supplier data into canonical construction catalog items that can be searched, priced, and benchmarked.
Supplier catalogs are messy by default. The same material can appear with different names, packaging, units, currencies, tax assumptions, and regional availability. A human can often tell two items are equivalent, but software needs a normalized model.
Omnicost separates raw supplier observations from canonical catalog items. A raw observation preserves what the source published: name, URL, price, currency, unit, timestamp, and provider. A canonical item represents the construction concept teams actually want to estimate against.
This distinction matters. If a supplier changes a product name, the raw observation can change without breaking every budget. If several suppliers publish equivalent items, Omnicost can aggregate them under one canonical item and compute a more useful market benchmark.
Units are one of the hardest parts. Construction teams price per m2, m3, kg, hour, day, unit, roll, bag, pallet, and more. The system has to preserve the source unit while helping estimators compare like with like. When conversions are unsafe, Omnicost marks the uncertainty instead of hiding it.
Provider metadata is also part of the model. A price from a trusted supplier with recent updates should carry more weight than an old scraped page. Trust, freshness, and region all influence how useful a price is.
The result is a catalog that behaves like infrastructure. Budgets, search, APIs, agents, and dashboards all consume the same normalized price layer.