Skip to content
FlowBity logo
FlowBityMVPs, operational apps and e-commerce automation
ServicesHow It WorksResultsPortfolioBlogContactBook a Free Call
ServicesHow It WorksResultsPortfolioBlogContactBook a Free Call
Back to portfolio

Case study

ECU Flow

Automated ECU listing on Allegro & Ovoko

Downloading offers & images from Allegro

Hundreds of ECU parts listed a day, with about 80% less time spent preparing each listing.

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

A pipeline pulls offers and images from Allegro or takes parts the seller adds by hand, 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

  • ▹Hundreds of ECUs processed per day
  • ▹About 80% less time to prepare a listing
  • ▹6 variant images per listing plus part-number validation
PythonAllegro APIOvoko APITkinter GUIasync pipelineOCR

Have a similar project?

Book a free call
FlowBity logoFlowBity
ServicesHow It WorksResultsPortfolioBlogContact
LinkedInEmail

© 2026 FlowBity. All rights reserved.

Privacy PolicyTerms of Service