Said Aivazov
CEO, founder
Owns product, growth, manufacturer relationships and customer success. Has been working with e-commerce and B2B catalogs since 2018.
About the project
A Wiki-API platform built by manufacturers themselves
OneCatalog is a unified Wiki-API platform that gathers information about products of any category from any manufacturer. Manufacturers themselves publish and maintain the data about their products, while distributors and retailers consume an always up-to-date catalog through a single API.
Story
From a narrow problem to a universal platform
OneCatalog started inside a digital agency that built online stores for manufacturers and distributors across many different industries. On every new project — regardless of product category — we hit the same wall: product data lived in PDF catalogs, XLS spreadsheets and locked B2B portals.
Content managers filled product cards by hand. Scrapers broke at every supplier redesign. The specs of the same brand were inconsistent across stores. Launching a catalog took 3–6 months, with another 6 months of upkeep.
We realized something simple: the only reliable source of product data is the manufacturer itself. So we built a platform where manufacturers enter and maintain their products themselves, while distributors and retailers consume that data through a single API.
Today OneCatalog is a public Wiki-API platform: manufacturers own the data, distributors and retailers build their catalogs on top of the API.
Problems we solve
What hurts at the manufacturer → store boundary
01
Data scattered across PDFs
Manufacturers publish catalogs in PDF and XLS. To filter products by specs or SKU you first parse it all, then keep up with updates.
02
Every store uses different specs
The same product is described differently by each seller: units, formats, SKUs — everyone has their own. Comparing is impossible, filtering even less.
03
Bad-quality photos
Sellers have warehouse phone shots. Manufacturers have studio photos, but you can not access them without negotiation. The catalog ends up looking cheap.
04
Content teams are expensive
One manager per 200 SKUs/day is the typical norm. A 10,000-item catalog needs 5 people for half a year. Plus a proofreader. Plus a photographer.
05
Scrapers go nowhere
Scraping a supplier means fighting infrastructure, anti-bot systems and legal. Every redesign resets your work.
06
B2B portals = endless calls
Some brands have a closed B2B portal; access requires going through an account manager, signing an NDA, signing a contract. A month per brand.
What we do
One API where manufacturers enter their own products
Manufacturers get a dashboard and add their own products — with all specs, photos and updates. Distributors and retailers plug into the public API and receive a catalog that updates without any work on their side.
Structured data
Brands, collections, product types, specs — a relational model, not a JSON dump.
Unified specs
Units of measurement, ISO country codes, SKU formats — one set of rules for every product category.
Three photo sizes
min / middle / max — pick the right one for context; do not transfer extra bytes.
Manufacturer dashboard
The manufacturer enters products, updates specs and attaches photos. Data is immediately available through the API.
REST + OpenAPI
Standard spec, API-key auth, simple filtering. No GraphQL, no SOAP.
Catalog as a showcase
This site is itself an example of what you can build on top of the API. Use it as a reference.
In numbers
OneCatalog today
50+
manufacturers in the catalog
2,000+
products
99.5%
guaranteed API uptime
2
interface languages (RU/EN)
Who needs this
Our customers
Manufacturers
Set up your catalog once — and keep it current as new collections ship. Your data reaches every partner store immediately.
Distributors
Get up-to-date product data straight from manufacturers via a single API. No calls, no NDAs, no stale XLS files.
Retailers & online stores
Replace your content team with an API. Plug in the brands you need with a single integration and get updates automatically.
Team
Who is behind the project
A small team building a big tool. Every commit has a name attached.
Roman Tatarinov
CTO
Architect of the API and platform. Owns reliability, performance and data quality of the catalog.
Principles
How we work
01
No lying to users
No fake "trusted by 50,000 customers". The pricing page has no "trusted by" block with made-up logos.
02
No dependency creep
No UI framework. No icon library. No state manager. Only what is actually needed.
03
Built for load from day one
API via query-param bypasses CORS preflight. Photos in three sizes. Defensive response parsing.
04
UX beats features
One filter modal that works well is better than three half-working modes.
Try the API right now
1,000 requests per month free. No signup needed — a demo key is in the docs.