The big question in this episode is “How can we create 10 million personalized webshops? Tailormade for every one of our customers so it suites their needs best?” In short, the answering is Measuring 2. 0. This enables us to measure more accurately how customers are behaving in our webshop.
Measuring 2.0 - Streaming measurementsBonjour ! Félicitations messieurs, il y a seulement deux semaines, que le bol. com application multilingue est disponible dans les app-stores. That's how we started this episode.
Moving to multilingual, first step Wallonia'OK Google. . .
'OK Google.....' - the future of voice is hereTurning to business analytics this episode, we discover it’s a broad field. Business Intelligence hasn't been discussed that much yet in our podcast. So, we are excited to learn more.
Opening our Data Treasure Chest with TableauHow interaction resulted in a guest appearance “We like interactions and feedback”, that’s what we say in our outro. The guest of our show reacted to one of our podcasts earlier this year. We reached out to him and invited him to the podcast.
Outside perspective on the edges of autonomyIn this episode we dive into the world were e-commerce becomes physical. We talk about the bol. com Fulfilment Center (BFC).
Performance boost the pick algorithm in the warehouseWith only a few weeks to go to our peak season, we wanted to ensure that the chat app on our webshop was performing up to par. An important part of our customers' questions is answered via this chat app. You can feel the importance of it to be able to handle a load of questions during our peak season.
Performance testing the chat appAs long as retail exists, people tried to predict the future. An accurate forecast makes it much easier to buy the correct amount of products from suppliers, know what you need to keep on stock and even know what...
No more crystal ball for forecasting, data science it isIn this episode we talk about GO. Go is not a language that is used the most at bol. com.
From zero to PRO: Using GO @ bol.comKotlin was first used by our teams a couple of years ago. It had an interesting start that shows how we adopt technology in general. In different feature teams a group of software engineers explored their own use cases for Kotlin.
Our Kotlin adoption journey