Case Study · Retail

Fifteen years working on the retail systems that serve 628 stores in 30 countries.

For a leading European food wholesaler with revenue over €10 billion, operating across 30 countries, rinf.tech has worked on the systems behind article listing, suppliers, and contracts for fifteen years. It still develops and maintains them today, now including checkout.

IndustryRetail · food wholesale
Engagement typeLong-term product engineering & maintenance
ScopeArticle listing (NAL), supplier management, contracts; MPOS checkout
Since15+ years, ongoing
Executive summary

A food wholesaler with revenue over €10 billion, operating in 30 countries, runs its business on a set of core systems: article listing, supplier management, and contracts. These moved off legacy technology onto a modern stack.

rinf.tech has worked on these systems for more than a decade. It helped consolidate the article-listing system, develop supplier management, and build multi-country contract management, and has kept each one running in production.

The engagement later extended to the client's checkout software (MPOS), the point-of-sale system a store cannot trade without.

628

Stores, across 30 countries
The store network these systems serve.

15+ yrs

On the client's core systems
rinf.tech has worked on the client's core systems and kept them running since.

4

Critical systems
Article listing, supplier management, contracts, and now checkout.

Chapter 1 · The challenge

The systems that run the business

Three systems decide whether the stores can trade. Article listing sets which products a store can order and sell. Supplier management runs ordering and promotional pricing. Contracts govern terms across 30 countries. When those systems are slow or inconsistent, the effect reaches stores across the network.

The article-listing system had grown into 10 to 15 separate form screens, hard to maintain and hard to work with across different article types. These systems ran on legacy technology, and had to be modernized without taking the business offline.

Chapter 2 · What rinf.tech worked on

The catalogue, the supplier platform, and contracts

What each system does, and the engineering problem in each, at a 30-country scale

# 01 — New Article Listing (NAL)

The system that defines which articles a store can stock, and in which variants and bundles: between 100,000 and 500,000 articles per country, drawn from 10,000 to 50,000 suppliers. It replaced 10 to 15 legacy form screens with one application, and pulls supplier data from external data pools where suppliers post it, with hundreds to thousands of updates flowing through each day. The hard part is consistency: a change in supplier data has to reach the catalogue without leaving a store with a wrong or missing listing. With the technical and business validations in one place, an article can be listed in 5 to 15 minutes, depending on its complexity, and the chance of a wrong listing drops.

# 02 — Supplier management

The platform that runs the supplier side of the business. It integrates ordering and evaluates promotional pricing: the process by which the client reviews the promotional offers suppliers send and decides which are commercially worth approving. It integrates with the client's internal ERP and its other systems. The demanding part is doing this consistently across a large supplier base, so buyers can act on it.

# 03 — Contract management

A web application for generating and managing supplier contracts across the client's countries. Every supplier has contracts, and no article reaches the shelf without being part of at least one; a promotional price puts it in another. Each market carries its own commercial and legal terms, so the system produces and tracks contracts that are correct for each country, not one template stretched across all of them.

Running in production

The work is not only building these systems but keeping them running. It also covers their production operations: monitoring service availability, tracking SLAs and reporting on them, investigating and escalating incidents, on-call and out-of-hours support, and managing deployments and releases across separated environments.

Chapter 3 · Results

Still on the core systems, 15 years on

The systems were modernized and kept running.

rinf.tech helped move the article-listing, supplier, and contract systems onto a modern stack, and has kept them running for more than a decade. A system a business runs on needs years of upkeep after the launch.

The engagement extended to checkout.

It later took in the client's point-of-sale checkout software (MPOS), the system a store cannot trade without.

Fifteen years of continuity.

The client has kept rinf.tech on its core systems through modernization, development, and the operations that keep them running.

What it shows

Fifteen years is the result

For systems a business runs on, the test is not the launch date. It is whether they still run years later, and whether the same partner is still trusted with them. The client has kept rinf.tech on its core systems for fifteen years, and extended it onto checkout.

Industry
Retail · food wholesale
Client
Leading European food wholesaler, revenue over €10 billion, 628 stores across 30 countries
Engagement type
Long-term product engineering & maintenance
Scope
Article listing (NAL), supplier management, contracts; MPOS checkout
Operations
Monitoring, SLA tracking, incident management, on-call, releases
Since
15+ years, ongoing