Retail consists of many small repetitions of the same process: the same checkout system, the same inventory count, the same staff scheduling, but repeated in every branch. An acquisition in this sector does not merge one organization, but a multitude of locations, each with its own local practice that looks identical on paper and works slightly differently in practice. The relationship between head office and shop floor is skewed here: integration decisions are made centrally, but the consequences land decentrally, in branches that have little room to think along themselves because daily turnover has to keep going.
On top of that, the sector is sensitive to the time of year. An integration that starts just before a peak period touches on something other than sales figures: staff rosters, inventory levels and checkout systems are then not the moment to change. The question of when to start is therefore just as important in retail as the question of what to do.
Where in other sectors integration is mostly a matter of back-office systems, in retail part of the identity lies in the format itself: assortment, pricing, store layout, customer experience. Merging two formats can add value, but can also remove exactly the reason why customers chose one store over the other. That makes the question of whether something should be merged at all sharper here than elsewhere: a shared distribution center is an obvious step, a shared format is not automatically one.
The synergy baseline helps make that distinction early. Not every synergy that looks logical on paper — joint purchasing, shared IT, one inventory system — is equally valuable or equally risky to implement. By splitting the baseline by type of synergy, an ordered overview emerges of what is achievable in the short term and what first requires further investigation, without an outcome already being promised.
Inventory management and checkout systems are often the first point of contact between two organizations in retail, and at the same time the point of contact with the most operational risk. A system switch that goes wrong affects the shop floor directly: wrong prices, missing items, a checkout that does not connect to the inventory administration. This is precisely where the integration office proves its worth as a tool: a list of dependencies that makes clear which system switch is waiting on which other switch, before a branch is confronted with it.
The Day 1 plan and the Day 100 plan give that sequence a form that does not depend on improvisation on the day itself. Day 1 is about what a store and its staff notice on the first day after the deal — does the checkout keep working, who is the point of contact, does anything change on the shop floor. Day 100 is about the steps that follow after that, in an order that takes the shopping season into account rather than a calendar date that happens to fall a hundred days after closing.
A merger in retail affects two very different groups of employees: office staff whose roles may overlap, and store staff whose work largely continues unchanged, but who do face new procedures, new systems or a new management structure. Both groups require a different approach, and it is a recurring question whether centralizing office functions outweighs the loss of local knowledge about the own market and customer.
The decision list of what to integrate and what not forces that choice to be made explicit per component, rather than as a general starting point in advance. Some back-office functions lend themselves to merging, other local expertise does not. Benefit tracking then makes visible whether a chosen synergy, once implemented, also delivers what was expected of it beforehand — without an outcome being guaranteed in advance.
The bottlenecks in retail differ from sector to sector, but the underlying question — what should be merged and what not — is the same everywhere. In the hospitality sector similar questions arise about format and experience, while the real estate sector deals more with long-running contracts than with shop floor processes. The ICT sector also has its own dynamic, where systems and platforms are more central than branches. Anyone preparing an integration in retail would do well to know these differences before an approach from elsewhere is simply adopted.
An integration plan sets out which synergies are worth considering and which dependencies determine the order, but it still says nothing about how much of the underlying work — retyping inventory data, merging staff rosters, revising supplier contracts — can be accelerated with AI. For that follow-up, the work scan from FTE TO AI offers a concrete calculation method: per task it is determined which part of the work can be taken over by AI, so that an integration plan not only gets structure, but also insight into the capacity needed to carry it out.
The generators and the integration office are under construction. Anyone who wants to use these as soon as they become available can sign up for the waiting list.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.