Upgrade to Pro — share decks privately, control downloads, hide ads and more …

From data platform to AI platform: how Winparts...

Avatar for Marketing OGZ Marketing OGZ PRO
September 18, 2026
0

From data platform to AI platform: how Winparts prevents returns with data & AI

Avatar for Marketing OGZ

Marketing OGZ PRO

September 18, 2026

More Decks by Marketing OGZ

Transcript

  1. Data & AI Consultant From Data Platform to AI Platform

    Data Engineer Our fitment guarantee, growing pains, and how we caught up Lead Data
  2. Our promises • Winparts helps you to get all the

    right parts for your car, fast and easy on your doorstep • Core promise: the fitment guarantee • Enter your license plate • Weʼll ensure that the part will fit your car • If not, weʼll help you get the right part.
  3. That's how we're going to win Europe 21 years ago

    we started selling car parts in Winneweer Now based in Groningen and Ede B2C Market leader in The Netherlands Expanding across Europe, country by country We increase exponentially in FTE, revenue, packages Winparts x MarkYourData x Data Expo 3
  4. Agenda Reducing returns with our data and analytics platform 1.

    The choices behind it, growing pains 2. The why 3. Our first use case: growing pains solved 4. Scaling up with AI: returns 5. Our takeaways Winparts x MarkYourData x Data Expo
  5. Growing pains Winparts is growing fast Fast growth brings its

    own kind of trouble License plate lookup system PostNL Returns system Google Analytics Warehouse system Backoffice CRM-system
  6. For instance with our customer Pete • He has old,

    rough wiper blades that make this annoying sound • He wants to replace them Winparts x MarkYourData x Data Expo
  7. Pete's problem • He already bought new wiperblades on Winparts.nl

    and he is very happy about the speed of delivery with all these rainy days Winparts x MarkYourData x Data Expo
  8. Pete’s problem • Pete is angry because the wiperblades donʼt

    fit and he goes on vacation tomorrow Winparts x MarkYourData x Data Expo
  9. Pete’s problem • He gets on the phone, and sends

    the whole order back Winparts x MarkYourData x Data Expo
  10. Winparts’ problem Bad for Pete, bad for Winparts We made

    one promise: the part fits, guaranteed. Problems like Pete's are preventable. They grew out of our own success, and fixing them is what this next part of the story is about.
  11. License plate lookup system PostNL Returns system Google Analytics Backoffice

    Logistics system What Pete's problem taught us We couldn't have stopped Pete's case in advance. But it, and stories like it, showed us exactly where to look. What it taught us: to catch problems like his, we needed to bring our data together from across the business, and turn it into insight we could actually act on. That's what we set out to build. CRM-system
  12. So we build a platform (a small one) The obvious

    move was to buy one big, all-in-one platform. We didn't. We don't handle streaming data, we're nowhere near that scale, a single vendor is a door that only opens one way — and our data has to stay in our own controlled environment. So we built something lightweight, out of open-source tools, sized for the Winparts we actually are.
  13. How it fits together Collect Two open-source tools do the

    heavy lifting. dlt collects the data from every source system; dbt models it into clean, trusted tables. Both run on Bigquery – our datawarehouse – in short scheduled batches on Cloud Run. Run only when needed not up around the clock. Power BI than turns the results into dashboards. The two tools that matter are open and portable, and deploying all infrastructure through Terraform so we're never tied to one cloud – and batches keep the bill small. dlt Model dbt Insight Power BI
  14. What "small" actually buys you No streaming cluster running around

    the clock. No seven-figure platform contract. No army of engineers to keep it alive. Just two open-source tool, one warehouse and a scheduler that wakes a couple of times a day. In total ingesting data from 7 different sources currently running 200 models for just 80 euros a month.
  15. Our first use case We started with the smallest useful

    question we could pick: which products get sent back the most? Nothing fancy — but now it's a ranked list, refreshed daily, across every system at once. If it doesn't fit, it comes back
  16. What we could suddenly see A product coming back 8

    times out of 10 stops being a hunch and becomes a number on a screen. That's the payoff: questions we used to argue about, we can now just look up.
  17. Scaling up with AI: returns We now know which products

    come back the most. What we still don't know is why. That question turned out to be harder to answer than it sounds.
  18. Asking the customer used to be enough When we were

    small At this scale With returns coming in by the thousands, reading every answer by hand stopped being realistic. The question didn't go away though: why does something come back so often, and what should we do about it?
  19. Turning free text into direction To answer that, we had

    to process text, not numbers. For every return, two things needed figuring out: which team should even see this, and what's actually behind it. Wrong product information on the website points to marketing. A data quality issue that causes a part not to fit points to assortment. A delivery that arrived too late points to logistics. The reason is usually in there, buried in a sentence a customer typed in a hurry.
  20. AI reads it, teams act on it What the AI

    does What teams get We never set out to do AI. But reading thousands of free-text return notes by hand stopped being realistic, so a small AI job reads every note, sorts it into a category, and summarizes the likely root cause. Instead of a pile of raw comments, our goal is that assortment, marketing, and logistics each get a clear signal back: here's what's actually going wrong, and roughly how often.
  21. An example This 300EUR bike carrier came back 9 times

    out of 10 in three months. In the return reason, repeatedly people indicate that a manual is missing After being informed by the feedback Product management tried to put it together without a manual: impossible
  22. It was never about the platform If you ask why

    Winparts needed a data platform and AI capabilities, the honest answer isn't '360 degree customer view' or 'digital transformation.' It's simpler than that: we needed to solve Pete's problem. Listening to what our customers were already telling us is what pointed us toward the infrastructure, not the other way around. The customer benefits directly from decisions that started with their own voice.
  23. The payoff compounds Customer care challenge Returns challenge Logistics challenge

    Dataplatform Marketing challenge And cheaper too The open tools we used for ingestion and modelling only need to run for a short window once a day. That's a fraction of the cost of committing to cloud-vendor-specific tools running around the clock. No lock-in, and a low bill.
  24. What's next More business challenges to solve More insights to

    deliver More datasources to enable Potential move to Azure Conversational analytics
  25. The next data-expo we would rather present with you then

    for you AI Engineer gezocht | Groningen https://werkenbij.winparts.nl/o/ai-engineer