Case study
ECU Flow
Automated ECU listing on Allegro & Ovoko
Downloading offers & images from marketplaces
From hours of manual listing to thousands of ECU parts a day, 80-90% faster preparation.
Context
A used auto-parts seller listing ECU (engine control unit) parts by hand across Allegro and Ovoko.
The problem
Manual listing ate hours every day, part numbers got mixed up, and photos were inconsistent. It did not scale.
What we built
An end-to-end pipeline scrapes offers and images from the marketplaces, classifies each ECU and validates its part number with OCR, then publishes complete listings to Allegro and Ovoko. Photo-quality sorting and pricing stay with a human operator, who reviews the queue before publishing. Python, Allegro API, Ovoko API, async pipeline, OCR.
Results
- ▹Thousands of ECUs processed per day
- ▹80-90% faster listing preparation
- ▹6 variant images per listing plus part-number validation
PythonAllegro APIOvoko APITkinter GUIasync pipelineOCR