Inside the IT and Engineering Engine of Colruyt Group

Chapter 1

The Order-Picker's Headset and the Company Nobody Sees

An order-picker walks into a food distribution centre before most of Belgium has had breakfast. A headset connects to a small wireless computer clipped to a belt. A voice tells them where to go. They confirm with a spoken check digit, and their hands stay free to lift and stack. Nobody watching a Colruyt shelf that afternoon will ever see this moment, but every product on it passed through someone wearing that headset.

This is the part of Colruyt Group most customers never think about: the internal machinery of IT, engineering and real estate that keeps 800-odd stores stocked, cooled, built and staffed. It is not a shopping platform. There is no cart, no checkout, no price list here. What this part of the site actually offers is something rarer – a company describing, in its own words, how its support divisions are organised, what they have built, and how someone gets hired into them.

The voice-picking system itself is thirteen years old and was recently rebuilt from the ground up, because the old hardware stopped being manufactured and a new EU law required tobacco products to be tracked with a bluetooth finger scanner mid-pick. Rather than patch around the gap, the team rewrote every command in a new programming language and standardised the dialogue across every distribution centre feeding Colruyt, OKay, Retail Partners Colruyt Group and Colruyt Prix Qualité. One dialogue means a picker can move between distribution centres and already know the system.

That single decision – one dialogue instead of several – is a pattern worth watching for through the rest of this book. Colruyt Group's support divisions keep choosing standardisation over customisation, even when it costs more up front, because it is what lets a company this size run reliably without doubling its support staff every time it adds a brand.

What you can actually do here

Colruyt Group publishes dozens of first-hand accounts of its own internal projects. Here is what a reader can actually pull out of them, and where each one leads.

Understanding how the group operates

Seeing where new technology gets tested first

Finding a way in as an employee or student

Chapter 2

Two Cities Running One IT Department

Colruyt Group's IT department is not one office. It is Halle and Hyderabad, working as one team split across a clock. Engineering work concentrates in Belgium; support and operational work concentrates in India. Maintenance that has to happen outside working hours – patching a server, testing an update – lands in the middle of the Indian team's normal working day, because Belgium is asleep by then.

That split exists because keeping the business running is unglamorous, constant work. Hardware ages out. Software stops being supported. A supplier announces it will discontinue a platform, and years of dependent applications suddenly need somewhere new to live. One such platform replacement, triggered by a vendor's support announcement, took over a decade to fully unwind – not because anyone moved slowly, but because untangling one dependency reveals three more underneath it.

To manage that, the department builds roadmaps: documents that map every application to the software package and hardware it depends on, so a team can see the knock-on effect of a change before making it. This matters more now than it used to, because Colruyt Group increasingly runs on external software packages like SAP rather than code written entirely in-house – which means IT has to synchronise its own maintenance calendar with a supplier's release calendar, not just its own.

📰 Recommended for You

How Magic Hour’s Credit Balance Covers Video, Image and Voice

Read More →

How Picsart Turns One Photo Into a Production Line

Read More →

None of this reaches a customer directly. What it buys is the thing a shopper never notices: a checkout that works, a price label that updates correctly, a mobile app that does not go dark during a supplier's own update window. The department estimates that a large share of its work at any time is dedicated purely to this kind of continuity rather than to building anything new – the unglamorous majority of the job.

Chapter 3

Thirty Technicians Keeping Five Hundred Sites Cold

About thirty refrigeration technicians maintain roughly two thousand two hundred individual cooling units spread across stores, warehouses and production sites. They typically install at least one new system a week on top of routine maintenance, and since 2014 they have been converting older installations away from synthetic refrigerant gases entirely – a project with a firm 2030 completion target.

The reason the group keeps this work in-house rather than outsourcing it is stated plainly: a third-party contractor means a queue, and a queue means leaked refrigerant sitting unrepaired for longer. In-house technicians can respond immediately, and the group's own leak rate sits well below what is typical for larger retailers in the region.

The system behind that low rate is worth pausing on, because it is a genuinely unusual piece of engineering for a grocery chain to have built itself. Two simple sensors sit inside each cooling unit's buffer tank. A machine-learning model, trained separately for every single installation using outside temperature, store opening hours and scheduled defrost cycles, predicts what the refrigerant level in that tank should look like. When the real reading drifts too far from the prediction, an alarm fires – and a technician is dispatched only when it does, rather than on a fixed schedule.

That sensitivity has increased roughly tenfold over the past decade. A system that once only caught a leak once it had lost a fifth of its refrigerant now catches a loss of around one percent. The trade-off the team had to solve for was trust: an alarm too sensitive trains technicians to ignore it, and one too coarse lets damage build up before anyone notices. Getting that balance right, on thousands of separately-trained models, is not a small technical achievement, and it happened almost entirely out of public view.

The same design office responsible for keeping buildings running also decides what a new one looks like before it is built. Prototypes for new store formats are tested life-size on a dedicated site before a design is finalised, and older buildings are studied for which materials can be reused before anything is demolished.

Chapter 4

One App Replacing Three

Before 2022, a Colruyt Group shopper who wanted the full digital experience needed three separate apps – Xtra, MyColruyt and Collect&Go – and more than half of the group's combined app users had at least two of them installed at once. That duplication is what the Xtra rebuild set out to remove.

It took roughly four years and close to a thousand people working across the project at different points, including external partners brought in because the internal team did not yet have the specific platform experience the rebuild required. The first version reached the public in September 2022, carrying about four-fifths of the features spread across the old apps. MyColruyt was retired at the end of 2023. Collect&Go's standalone app followed in April 2024, at which point Xtra became the only personal shopping assistant across the group's food brands.

The app now ships a new version roughly every two weeks – a release rhythm the team only reached after the consolidation project taught it how to work across internal and external teams without waiting on each other. What the article does not explain is what happened to a customer's saved history during the eighteen-month window when all three apps still technically existed side by side; that migration detail simply is not documented here.

A separate but related project, Collect&Go Drivers, applies the same logic of consolidation to a different problem: rather than running its own delivery fleet everywhere, the group built an app that lets private individuals pick up groceries from a collection point and deliver them locally for a fee, capped so it stays a side activity rather than a job. It launched informally during the pandemic and was later given its own dedicated app and automation.

Chapter 5

When the Software Learns to Watch the Store Instead of a Person

A shelf gets rearranged. In the past, a manager might tell the next shift verbally and hope the message survived to the shift after that. Now it goes out as a chat message on a smartphone every store employee carries, alongside about thirty other functions covering communication, stock counts, price-label updates and step-by-step training videos for tasks like cleaning a coffee machine.

One of those thirty functions is easy to walk past in a bullet list but does real work on the floor: an employee scans a product's barcode with the app, and the corresponding electronic price label physically lights up on the shelf. It is credited with saving roughly an hour and a half a day during restocking – a number that only appears because it sits buried in a feature list rather than on its own page.

The wider pattern is computer vision quietly replacing tasks that used to require a trained eye. A camera at checkout scans groceries directly rather than requiring a cashier to scan each barcode by hand, running around a fifth faster and more comfortably for the person working it. Self-driving forklifts move pallets inside distribution centres using the same underlying vision and sensor technology. And at the crate-return centre in Halle – one of the larger installations of its kind in Europe – a vision system sorts incoming pallets by material and crate type before any washing happens at all: plastic against wood, rigid crates against folding ones, each routed down a different line automatically.

None of this technology sells itself as artificial intelligence to a shopper. It shows up as a slightly faster checkout, a shelf that gets restocked a little sooner, a grocery box that arrives at exactly the temperature it should. The intelligence is deliberately invisible, which is also why it took reading a set of internal interviews, rather than a marketing page, to find any of it.

Chapter 6

From Store Floor to Software Team

Two people who now write software for Colruyt Group started out stocking shelves and working the refrigerated aisle. One spent twelve years at a checkout before applying for the group's own software engineering traineeship, taught himself the basics through online courses first, then formalised it once he learned the internal programme existed. The other did an evening-class programming diploma while still working in-store and turned an internship into a full-time coding role before finishing the course.

The traineeship itself runs once or twice a year and starts with roughly three months of external theory covering Java, Spring Boot and Angular, delivered at a pace trainees describe as demanding but manageable alongside evening study. It ends with a final project presented to the wider IT organisation, after which trainees are assigned to a live team with a personal coach and usually inherit a real piece of legacy code to modernise – in one case, rewriting the software layer behind the store's own cash registers.

A separate, higher-level path exists for university graduates: a two-year IT management traineeship built around whichever area of IT management interests the trainee, paired with a dedicated supervisor who helps find projects that serve both the trainee's development and the business at the same time. Two of its first participants moved into an audit role assessing the IT risk of newly acquired companies and a financial planning role inside IT services respectively – neither path fixed in advance.

A third, narrower programme addresses a specific gap rather than a general one: the Young Potential Boostcamp pairs experienced women in the IT department with early-career women considering the field, focused less on technical training and more on the soft-skill confidence needed to hold a room in a sector where women remain a clear minority. One mentor pairing included a full cycle of job-shadowing, where the mentee watched a typical working day unfold from the inside before deciding whether the path suited her.

Chapter 7

What This Part of the Site Won't Tell You

This is a careers-and-operations window into Colruyt Group, not a shop front. It will not tell a reader what a product costs, where the nearest store is, or what a loyalty card earns – those questions belong to the group's separate brand sites, and looking for them here is the one thing this part of the site genuinely cannot answer.

It is also, by its nature, told from the inside. Every account here comes from an employee describing a project that generally succeeded – the traineeship graduate who is now thriving, the leak-detection system that hit its target, the app consolidation that landed on schedule. A reader weighing whether to apply for a role, or whether to trust the group's sustainability timeline, should treat this as one well-documented perspective rather than an independent audit.

Some of the group's own targets are still ahead of it rather than behind it: zero-emission goods transport by 2035, and full conversion away from synthetic refrigerants by 2030, are both described as work in progress with real cost and infrastructure barriers still being tested rather than solved. That honesty is worth noting, because it is rarer in corporate material than the success stories are.

What this collection of accounts is genuinely good for is exactly what it set out to be: understanding how a large, multi-brand retailer organises its engineering, its technology and its own workforce development – in enough operational detail that a reader could walk into an interview for any of these teams already knowing more than most other applicants will.

Questions readers actually ask