Automotive · Data integration

220+ dealers. 10,500+ vehicles. Live on Google every day.

One ingestion platform turned every dealer's stock feed, whatever its format, into accurate Google Vehicle Ads, refreshed twice a day.

Before

Every dealer sent stock differently: a web link, a file uploaded to our SFTP, or files we had to collect from theirs. Each used its own column names, and key details like registration dates were often missing. Onboarding a new dealer was slow and messy, and keeping Google Merchant Center accurate got harder as the dealer list grew.

What we built

One ingestion platform that accepts every format (CSV, XML, JSON, APIs, webhooks, SFTP) and turns it into a single inventory model. It matches each dealer correctly, fills in missing details through an API, applies business rules automatically (minimum stock, custom labels, finance pricing) and publishes to Google Vehicle Ads through the Merchant API. Every dealer refreshes twice a day.

What we found

The hard part wasn't volume. It was variety: the same field had many different names, and important details were often missing. Fixing that once, in one model, made every new dealer easier.

After

  • 10,500+ vehicles from 220+ dealers live on Google every day.
  • Dealers' ads match their real stock, refreshed automatically twice a day.
  • New dealers plug into the same model instead of needing a custom build.

Stack

  • Azure Data Factory
  • Azure Functions
  • .NET
  • Google Merchant API
  • Auto Trader API
Five kinds of dealer feed flow into one inventory model, which publishes to Google Vehicle Ads.Dealer feeds arrive by web link or SFTP as CSV files, XML files, JSON files, APIs or webhooks. All five flow into one inventory model, which publishes to Google Vehicle Ads.Dealer feeds, by web link or SFTPCSV filesXML filesJSON filesAPIsWebhooksOne inventory modelGoogle Vehicle Ads
Every feed format lands in one model before anything reaches Google.

More case studies

Ready to see where your data stands?