Catalog Ingest Pipeline — Case Study | brdz.net
Case study

Partner catalogs in, editor time back

Content operations

Confidential 2–3 weeks Python Playwright Node.js CMS seed

Challenge

Editors were copying product cards from partner sites by hand: titles, pictures, categories. A new batch meant a lost day. Pictures arrived huge, names collided, and nobody wanted to do it twice.

Solution

A two-step pipeline: a server in a friendly network collects the full list and original covers; locally we review, keep a sane set, convert images, and seed the CMS. Failures show up in a short report instead of a blank page.

Results

A catalog refresh that ate a day of copy-paste is now collect → review → publish. Editors argue about which 80 items to keep, not about filename typos. The boring half of the job no longer blocks the public site.

Collect on a server, curate locally Images prepared for the site Report when a source is empty