During a proposed foods combination: handing over customer commitments and product data

01 Facts & context

Verified transaction context and source limits

Unilever publicly describes a proposed combination of its Foods business with McCormick. The planned model includes Americas Consumer, International Consumer, Food Service and Flavour divisions, with leadership and regional responsibilities. These are an agreement and future plans. They must not be described as a completed transaction or treated as the current service route for each customer.

The UK Competition and Markets Authority records the launch of its merger inquiry on 16 September 2026, with the case open when reviewed. Regulatory status and the company’s operating plans answer different questions: one establishes the review stage, while the other describes the intended organization. An inquiry does not predict approval or rejection, nor does it prove that customer handovers have occurred. The analysis below therefore distinguishes transaction context from GSP’s proposed customer-management arrangements.

The central question is how retailers, category teams and frontline staff can share the same effective commitment while organizational boundaries may change. A contact list explains whom to approach, but not when a price applies, which packaging unit can be ordered or who approved an exception. Reliable handover preserves that knowledge in maintained records, distinguishing matters dependent on completion from everyday service that must continue.

02 GSP analysis

Four planned divisions are not four ready-made customer routes

Unilever’s public material describes four planned commercial divisions: Americas Consumer, International Consumer, Food Service and Flavour. This is a starting point for understanding the proposed model, but it does not explain every local contract, data record or project transfer. A clear high-level structure and continuity of an individual transaction are different questions.

GSP proposes mapping each customer task against market, type of service and the effective date of the commitment. Retail listing and a food-service formulation request may need different specialist interfaces. Brand identity alone cannot determine the receiving owner. Show the planned route alongside the current authorized route, with the conditions for switching and the person able to confirm the switch. Preparation can begin before completion without describing the future arrangement as already operational.

The useful output is a continuity table rather than another organization chart: current contact, current approvals, receiving owner, pending conditions and exception handling. Rehearse a real historical transaction and ask whether the receiving team can find its full explanation. If the answer depends on an individual’s unwritten recollection, add the missing knowledge to the record before deciding that the organizational structure itself must change.

03 GSP analysis

GS1 makes the data handover concrete

GS1’s product-data guideline describes foundation attributes supporting listing, ordering, movement, storage and sale. Individual items, packs, cases and pallets have corresponding places in a trade-item hierarchy. This makes a customer-relationship handover more concrete: who maintains the record, ordering unit and packaging relationship, and how are changes communicated to customers using that data? It is not a description of Unilever’s or McCormick’s internal system.

In a hypothetical organizational transition, a familiar product name may remain while an ordering unit, packaging description or record owner changes. A handover limited to contacts and sales targets could leave the receiving team unable to explain a mismatched order. GSP proposes retaining the source, effective version and approver for important fields, then checking representative products from internal records through to customer-facing information.

Distinguish the same name from the same item identity, and a retail unit from a logistics package. When a discrepancy appears, identify affected orders and periods before deciding whether the correction belongs in documentation, data or commercial arrangements. Do not classify every difference as a system defect or silently change a customer commitment. The 2020 guideline provides a reference for data responsibilities; it does not establish the companies’ current architecture or claim to cover every current standard.

The handover should also identify who may edit each field, who may only view it and how teams still using an older version are notified. Receipt of a file and the ability to use its record correctly are different acceptance checks; a sent email is not sufficient proof of completion.

04 GSP analysis

Connect current performance with future commitments

Customer management in a transition can examine current trading and future delivery together. Revenue, margin and trade spending provide one perspective; joint plans, price conditions, availability and unresolved issues provide another. Different people may own these tasks. The transaction announcement does not establish that profit-and-loss authority has been delegated to a customer manager or that central planning has stopped.

GSP proposes a commitment register connecting the two perspectives. Each promotion, listing or supply arrangement records its customer, period, approval basis and receiving owner. That makes it possible to ask whether current sales depend on an unconfirmed future condition, and to distinguish an effective commitment from a proposal still under discussion. The transferable asset here means operating records and relationship knowledge, not an estimate of the transaction’s accounting value.

Suppose a retailer asks for a deeper discount. The team could compare a price concession, display support or content support without presuming that a non-price option always protects the brand better. Cost, stock, customer need and execution conditions matter. The important handover is the reason for the choice and what the next team must know. A discount number without its scope or expiry is an incomplete record. A sound review keeps short-term performance visible while preventing it from concealing commitments that someone else will later have to fulfill.

05 GSP analysis

Manage the full launch cycle without inventing a fixed window

A launch connects preparation, listing, replenishment and feedback, and these stages can require different amounts of time. GSP proposes choosing an observation period according to the product, the customer’s buying calendar and the replenishment cycle. It should reveal whether initial supply was delivered, subsequent replenishment worked and feedback informed adjustments. Define the starting point, completion conditions and intermediate checks before choosing a calendar duration. This avoids treating initial orders as proof of lasting demand or imposing one launch timetable on every category.

Before launch, check product information, ordering terms, channel pages and execution resources. After launch, establish whether the product actually reaches the intended stores, is available to buy, changes inventory as expected and generates feedback linked to the correct item. This separates nominal listing from real availability, while avoiding the assumption that weak demand must be an execution failure. Every failed check needs a known person who can supply information or change the plan.

If a hypothetical condiment underperforms after listing, first inspect distribution and availability, then display, price and demand. Sampling or merchandising trials can be options, but their resources and approvals must be explicit. Cross-cycle management preserves a continuous explanation rather than producing more weekly reports. At the end, hand over the facts, remaining questions and actions still required. That record helps the next owner understand what was tested and what remains uncertain, instead of interpreting an isolated sales result without context.

06 GSP analysis

Category analysis needs definitions and a customer purpose

Shopper and store data can support a category discussion, but this article does not treat a requirement to use particular commercial databases as a verified job fact. Whether information comes from company sales, a retailer or licensed research, record the sample, period, category definition and permitted sharing. Measures of share, frequency and price bands from different sources should not be compared without checking their basis.

GSP separates a category recommendation into observation, explanation and proposal. The observation describes what happened; the explanation offers possible reasons; the proposal changes assortment, display or promotion. A retailer needs to see how the suggestion serves its customers and operating objectives, not merely a supplier’s desire for more share. If evidence does not distinguish among causes, keep the alternatives visible.

Suppose sales in a premium band are limited. Possible explanations include low demand, unsuitable products, weak placement or poor availability. Identify the missing evidence before proposing a limited test. The handover should include definitions and unconfirmed assumptions, allowing the receiving team to reproduce the reasoning. An attractive chart without those conditions becomes difficult to use after responsibilities change. The quality of the analysis lies in an interpretable decision, not in the name of a data supplier or the volume of information included in the presentation.

07 GSP analysis

Inventory handover includes status and commercial conditions

Food inventory involves remaining shelf life, batches, channel conditions and changing demand. A proposed transaction does not prove that a company has excess inventory or that a customer manager holds sole disposal authority. GSP includes inventory because a handover needs more than quantities: whether goods can still be supplied, which orders they suit and what arrangements have already been confirmed.

Discounting, transferring stock, reducing replenishment or another option each has conditions. Moving goods to another channel is not automatically better for the brand. The team needs to consider product suitability, agreements, logistics and actual demand, with approval by the relevant authority. Place facts and alternatives together rather than inferring a single action from a total stock value.

For a hypothetical slow-moving batch, record the quantity, remaining life, customer commitments and implications of different options. The receiving team needs to know why an immediate discount was not selected, and which change would trigger a new decision. That avoids repeating negotiations or applying an obsolete plan. Analyze inventory alongside forecasting, supply and channel execution without presuming one owner caused the result. A useful handover enables a new person to reconstruct the decision and take the next authorized step. It is more demanding than passing on a spreadsheet, but more specific than describing all stock management as protection of brand equity.

08 GSP analysis

Hand over inputs and approvals as well as contacts

Planned divisions provide a high-level direction of responsibility, not a complete answer about every local customer. An operational handover must explain what product information a category team supplies, what commercial conditions sales confirms, how supply teams determine that an order is executable and how service handles exceptions. Similar function names can carry different rights in different organizations.

For representative customers, map who receives a request, proposes a response, confirms product and data, approves terms and communicates the final answer. Keep the current route and the proposed route together, marking the conditions under which the latter takes effect. Before a transaction is completed, an anticipated structure should not replace existing formal responsibility. A future contact should not be treated as holding authority that has not been granted.

Imagine a request for a different pack size. It can be recorded and examined for technical feasibility before a commitment is made. Delivery timing and price still require the relevant confirmation. The handover should preserve discussion status, next action and due date. Good coordination does not mean one person decides everything. It means nobody has to guess where a request belongs or what information it needs. This distinction also helps reveal whether delay comes from missing evidence, unavailable authority or a genuine dependency in the work.

09 Suggested actions

Confirm continuous service, then rehearse the new handover

First inventory arrangements that must continue: effective orders, service terms, product information and confirmed promotions. Name the current owner and identify what needs receiving confirmation. Second, check that data and terms match the actual item, especially packaging levels, order units, price periods and channel information. A relationship meeting alone should not declare completion while these records remain inconsistent.

Third, rehearse the handover with representative customers and products. A receiving person should be able to explain one order, one promotion and one exception, and find their approval basis. The exercise can use historical business without changing actual terms. When it exposes a problem, distinguish a data correction, an authority question and a workflow change rather than attributing everything to training.

Fourth, update the arrangement as transaction progress and formal authorization change, retaining versions before and after the effective point. Stability and growth are not necessarily a fixed choice between two priorities. A well-defined new project can continue, but should not hide an unresolved service gap. Each stage needs a verifiable output and an owner. These are GSP’s proposed steps, not a description of procedures already adopted by Unilever or McCormick. The practical standard is that an authorized successor can understand and continue the work, with open questions visible rather than quietly transferred.

10 Suggested actions

Measures should explain continuity

Observe operating results and the handover process together. Operating measures can include availability, order fulfillment, application of price conditions and inventory movement. Process observations can include ownership of open issues, data errors, repeated confirmation and resolution time. Every measure needs a denominator, period and recording method; otherwise teams may report apparently identical numbers that cannot be compared.

A small test should address a specific hypothesis. If master data may be causing order errors, inspect the mapping between the item, packaging level and customer order. A quarterly revenue change is not the appropriate direct test of that correction. If customers cannot understand a new contact route, have them complete a real inquiry and check whether it reaches an authorized responder. These problems require different evidence and potentially different remedies.

Poor outcomes do not automatically establish weak customer-manager performance. Demand, supply, price and transaction progress may all contribute. Preserve that context in the review. Do not add a new assessment definition retrospectively at period end; agree in advance what will be observed, when it will be reviewed and who explains it. Evidence of a transferable capability is a successor understanding and continuing real business. More documents or meetings alone cannot demonstrate that outcome, even if they make the transition appear busy and well organized.

11 Suggested actions

Change the role or change the handover according to the failure

Explicit handovers are particularly useful when boundaries are still being discussed, customers need continuous service and product information and terms span several teams. Changes in transaction progress or authorization should update the responsibility route. Where an existing team already maintains accurate continuity, transition does not itself justify adding a coordination layer. The role should serve actual tasks rather than a fixed organizational model.

Use concrete signals. Repeated forwarding of customer questions may indicate an unclear entry point or authority. Repeated misidentification of an item suggests checking the data mapping. Persistent delay needs separation of supply, approval and demand causes. An unconfirmed customer plan needs a receiving owner rather than simply more reporting. Each signal points to a different object of correction.

This article does not forecast the transaction or equate customer relationships automatically with a measurable brand asset. Its narrower judgment is that operating knowledge supports continuity only when it is accurately recorded, understood and carried forward. Preserve the distinction among present commitments, future conditions and unresolved issues. That is more actionable than assigning a grand asset-custodian title. Whether responsibilities should change follows the gaps revealed by rehearsal and live follow-up. A successful handover is demonstrated by the next authorized person’s ability to act correctly, not by the date of a meeting or the completion of a presentation.