Sheets as the control plane
Non-developers already trust spreadsheets. Making Sheets the approval gate meant the pipeline fit the team instead of forcing a new admin UI.
Upwork · E-commerce · 2024
Supplier catalogs change faster than merchants can type. Blind auto-import destroys trust; full manual can’t keep up. I built the middle path: scrape, AI-format, humans approve in Sheets, PHP pushes to Woo, Telegram watches every hop.
My role Pipeline designer — scrape, AI normalize, Sheets control plane, Woo import plugins, Telegram logging.
Ecommerce clients on Upwork needed catalog sync without publishing garbage. Reviewers lived in Sheets. Failures had to surface in Telegram — not a log file nobody opens.
Browserless for capture, AI for normalization, Google Sheets as the approve/reject control plane, WooCommerce import plugins for the push, Telegram for ops visibility. Same philosophy as the Bondi/TCD migration tooling — structure first, publish second.
Catalog velocity with a human brake — approved rows only, failures loud enough to fix.
Non-developers already trust spreadsheets. Making Sheets the approval gate meant the pipeline fit the team instead of forcing a new admin UI.
If a scrape dies or an import fails, it has to land where people already watch. Silent pipelines are how bad data ships.
Browserless capture and AI cleanup before a human opens the sheet.
Only reviewed rows hit WooCommerce.
Success and failure land in the ops channel.