Wholesale earns money on the difference between purchase and sales price on a flow of goods that moves through the company. That is a different logic than a factory that adds value to a product itself, or a service provider that sells hours. The ratio between revenue and margin is narrow: a large part of revenue goes into purchasing, and the profit lies in the difference that remains after logistics, storage and sales costs. A merger or acquisition in this sector therefore immediately touches the core of the business model, not just the boundary conditions. Whoever merges two wholesalers does not merge two production lines, but two purchasing conditions, two inventory positions and two sets of customer agreements. That makes the question of whether something should be integrated at all just as relevant here as in any other sector — perhaps even more relevant, because the margin leaves little room for mistakes.
The first place where integrations get stuck is the assumption that purchasing advantage is simply additive. Two companies that buy from the same supplier appear on paper to offer a scale advantage as soon as the volumes are combined. In practice, there are tiered agreements, exclusivity clauses and years-long relationships underlying that which do not automatically move along with an acquisition. A synergy baseline that takes this advantage along as an established fact is adding up something that has not yet been agreed. The question of whether and how purchasing is merged, and what that does to the relationship with existing suppliers, should be on the decision list early on, not as a finishing step.
The second place is the warehouse. Merging two inventory systems means not only linking two databases, but also two physical locations, two ways of order picking and often two definitions of what "in stock" precisely means. A Day 1 plan that assumes inventory data will match immediately gets stuck at the first count. A Day 100 plan that takes warehouse consolidation as an established goal should first establish what that consolidation costs in terms of lead time, temporary overcapacity and risk of delivery problems. Not every warehouse needs to be combined; some combinations yield more risk than benefit.
The third place is the customer itself. In wholesale, customer conditions often exist per relationship: price agreements, payment terms, delivery frequencies that have been built up over years of negotiating. When two customer files are merged, the temptation arises to standardize conditions. That can yield margin, but it can also drive away customers who see their current agreement as a vested right. Benefit tracking that treats this as a line in a profit and loss statement misses the point: it concerns individual relationships, each with its own breaking point. This dependency between commercial and operational systems is exactly where an integration office must provide oversight, so that decisions about standardization are not made without insight into what is at stake per customer.
Wholesalers often work with specific ERP and inventory systems that are closely tailored to their product range and their way of working. Merging two of those systems is rarely a matter of data conversion alone; it touches invoicing, accounts receivable management and the reports that management uses to monitor margin. Comparable bottlenecks around systems and administrative processes can be seen in what gets stuck in integrations in manufacturing and in the way transport companies struggle with merging planning systems. The dependencies therefore run not only within one's own company, but also between sectors that share logistics as a core activity.
The question that keeps returning with each of these components is not how quickly something can be integrated, but whether integrating adds value or mainly risk. Letting a separate administration continue to exist because the customer relationships are too fragile for it is a legitimate outcome. Letting two warehouses continue to run alongside each other because consolidation costs more than it yields, likewise. That distinction — what does and does not come together — is exactly what a decision list is meant for, not as a formality but as a record of a choice that would otherwise be made silently under time pressure. That same trade-off plays out in other sectors with thin margins and a lot of manual work, as can be read in the analysis of bottlenecks in integrations in retail.
A synergy baseline, a Day 1 plan and a Day 100 plan give structure to the decisions, but say nothing yet about who actually carries out the work once the decisions have been made. Once it is clear which tasks continue to exist — order processing, inventory control, invoicing, customer communication — the next question is which part of that must remain manual and which part can be supported with AI. The work scan of FTE TO AI calculates that per task, based on what the work actually entails, not on an assumption about the sector as a whole.
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.