Use case
Keep a product catalog in sync with supplier and store sites
Pull the products a supplier or store publishes as records with SKU, title, price and stock, compare them with your own catalog and import what changed. The supplier does not need to give you a feed.
The problem
Retailers, marketplaces and distributors depend on supplier data. When a supplier offers no feed or API, the catalog is updated by hand from their website, or from a spreadsheet that is already out of date by the time it arrives.
The result is listings with stale prices, products shown as available that are not, and new items that appear on the supplier's site weeks before they reach your shop.
How CleanedWeb solves it
A website becomes an API. CleanedWeb turns the supplier's product pages into records with the same fields on every call, so syncing becomes a comparison between two lists.
-
Discover the fields
CleanedWeb reads the product pages and proposes the fields it finds, such as SKU, title, brand, price, stock status and image URL. You keep the ones your catalog uses.
-
Build the API
It builds and validates an API with inputs such as a category and a limit on how many products one call returns.
-
Get a versioned contract
The schema is saved with a version. Your import maps the contract to your catalog's fields once, and pins the version it mapped.
-
Run it on your schedule
Call the API from your own scheduler, then diff the records against your catalog by SKU: new products, price changes and items that went out of stock.
-
Repairs when the site changes
When the supplier redesigns its site, CleanedWeb rebuilds the API for it. A rebuild that would remove or retype a field is not swapped in silently, so your import keeps working against a contract you reviewed.
What a record looks like
An illustrative record from a fictional supplier site. Real fields come from the site you choose and are listed on the API's contract.
{
"sku": "CHR-1180",
"title": "Folding chair, oak",
"brand": "Example Furniture",
"price": { "amount": 38.5, "currency": "EUR" },
"stock_status": "in_stock",
"category": "Chairs",
"image_url": "https://supplier.example.com/images/chr-1180.jpg",
"url": "https://supplier.example.com/products/chr-1180"
}
Use the SKU as the join key between the supplier's records and your catalog. Check each run's summary before you apply a change, because a partial run is not a complete product list.
Docs for this use case
- Schedule API runs Collect on a recurring schedule from your own scheduler.
- Store and deduplicate Keep each response and apply records without duplicates.
- Versions and changes Pin the contract your import was written against.
- Source changes What happens when a supplier changes its site.
- Pagination and output Set how many products one run collects.
Free tools that help
- Website data checker See what product data a supplier site already publishes, such as JSON-LD or a sitemap.
- Shopify store to CSV Export a Shopify supplier's public products and variants once, as CSV.
- Sitemap checker See how many product URLs a supplier's sitemap lists.
- JSON to CSV converter Turn a response into a CSV your catalog tool can import.
- JSON Schema generator Write the schema for the product records you import.
Questions
Can it write to my store or catalog system?
No. CleanedWeb returns records; your code or an import tool applies them to your catalog. The JSON to CSV converter is one way to prepare a file for a tool that imports spreadsheets.
What if the supplier already offers a feed or API?
Use it. A feed the supplier maintains is the better source. CleanedWeb is for the suppliers and stores that publish products only on their website.
Can I sync several suppliers?
Yes. Each supplier site becomes its own API with its own contract. You map each contract to your catalog's fields once.
Am I allowed to copy a supplier's product data?
That depends on the supplier's terms and on the law where you operate. Get the supplier's agreement where you can, and check both before you build. CleanedWeb reads public pages only.
Ready-made APIs in the catalog
These published APIs already return records for this kind of work. Open one to see its fields and a sample record.
-
Blocket Vehicle Listings API
Car listings from Blocket.se search results, with title, price, year, mileage, location, image and listing link.
-
Clas Ohlson Product Details API
One Clas Ohlson product page, read by its URL, with title, brand, SKU, price, currency, rating, review count, availability and link.
-
Craigslist Cars & Trucks (SF Bay Area) API
Car and truck listings from Craigslist SF Bay Area with title, price, location and listing link, searchable by keyword, make and model, body type, fuel…
-
DBA Marketplace Listings API
Second-hand listings from DBA.dk in Denmark, with title, description, date and category, plus price and brand from each ad's page.
-
ehorses Seller Details API
One seller profile on ehorses, read by its URL, with the seller's name and link, plus a phone number when the page shows one.
-
Kith Product Details API
One product page from kith.com, read by its URL, with title, price, currency, description and brand.
More use cases
-
Price monitoring
Track competitor and marketplace prices from an API that returns price, currency and availability as records.
-
Job data
Collect postings from job boards and career pages as records with title, employer, location and date.
-
AI data pipelines
Give RAG pipelines, agents and LLM apps records with a versioned schema instead of scraped page text.
Turn a site into an API
CleanedWeb turns a website into a maintained REST API that returns structured records, with a versioned schema and repairs when the site changes.