Good morning, Ana.

Hi All, Hereby the weekly update. Update 06-04-2026 (Week 15) 🟢 On Track Q1 fresh waste 3.4% against a 4.1% baseline. Detail in a separate note. Timeline On plan. [Image removed by sender] Topics worked on last week 1. Q1 results compiled Topics planned for this week 1. Present Q1 results 1. Bakery build continues If there is anything else you'd like to see in these update emails, please don't hesitate to let us know. Kind regards, Best regards,

Extracts. Slower is acceptable, the other thing is not. Ivan, no offence intended. It is not about Meridian, it is that I cannot explain to my data protection officer why a third party had read access to everything.

Realistic but not free. Roughly two weeks of setup and it needs somewhere to run. The cheaper option is extracts. Slower for Meridian and no risk on the fresh side. Med vänliga hälsningar,

Honest answer: read access is read access. There is no category level restriction in the current configuration. So either they see the fresh configuration, or we create a separate environment, or they work from extracts we prepare. Tomas, is a separate environment realistic?

There were two versions because I asked for there to be two versions. My mobile is now with a consultancy I have no contract with. Please ask them to delete it and tell me when they have.

I forwarded the file I had. I did not know there were two versions.

Then I will ask him.

It sits under logistics IT. The owner is Nils Ackermann. Priya has asked him twice, in 2024 and again in 2025. Mit freundlichen Grüßen

Robert, Indicative numbers attached. Summary here so you have it in the mail. Chain wide for the three fresh categories, 340 stores: additional annual licence of approximately 420 thousand, plus implementation of approximately 260 thousand one off. On your second point, and this is the honest version. The twelve month expectation was missed for one reason above all others. The value case depended on fresh, and fresh depended on a data field that we identified as a dependency in April 2024 and never obtained. Everything else largely went to plan. We built a workaround in September 2025 which works acceptably on fast moving articles and poorly on slow moving ones, and your category manager has been compensating for the difference by hand ever since. For the next number to be different, that field has to be available. It is not a RELEX deliverable and I cannot commit to it on your behalf, which is why I am putting it in writing rather than in a slide. If it is not resolved, chain wide will reduce waste by less than the pilot suggests, because the slow moving articles are a larger share of the tail across 340 stores than across 25.

I put the extract totals next to the till numbers for January to March.

They do not reconcile. The extract is lower.

I am not going to give you a number in this meeting because I have had it for

two days and I do not trust it yet. It is not a rounding difference.

I took three point four to the board in April.

Then I would like to know whether I was wrong, and I would like to know it

before the next one, not after.

Understood. I do not have a cause yet.

Hi Ana, It is March. Was this ever finished? I have not had the list Marco promised, and the document history point was still open when we last spoke in November.

Marco, Item 3.

Marco, Following this afternoon, the four actions as I recorded them. 1. Written confirmation of hosting region and whether it is named in the current agreement. 2. The fifth sub-processor: identity, what they process, where processing occurs, and the transfer mechanism if any of it is outside the EU. Plus why we were not notified. 3. The erasure request made in November: confirmation that it is fully closed, with a list of every location the data was held. 4. A stated retention period for meeting recordings and transcripts, and a position on the existing two years of material. I would like all four within four weeks.