Navigating Digital Payments

Anouk delivers a handful of genuinely useful practitioner observations - inter-brand collaboration to fix shared factory equipment, live editing of DPP data to trigger product recalls, child-safety constraints on button shapes - but Edwin's contributions are largely meandering and abstract. Too much time is spent re-explaining the basic concept and summarising prior points.

“we could call another brand which we see on a digital product passport, which is working with this facility as well. Like, hey, let's collaborate. Let's put in some money together. Let's buy a new washing machine for this facility so we all have safe products in the end”

“when there's a test regarding chemicals and it of course passes or maybe fails, you can put it in the digital product passport, because when you scan it and it has a fail and you haven't seen the pop up on the website, like, please bring back this garment because it. It is toxic. Sometimes happens, you can edit in the digital product passport”

The idea that DPPs could catalyse collaboration between competing brands sharing the same factories is a genuinely non-obvious angle. Everything else - regulation creates opportunity, supply chains are complex, younger consumers are less brand loyal - is recycled conventional wisdom delivered without a contrarian edge.

“back in the days was like, okay, we will not share our supplier list. It's a supplier which we are only using, which is completely not true. If I look at Dutch fashion brands. We are most of the times producing in a facility all together”

“brand is maybe not the right word. They might choose a product, but maybe they choose it because of someone”

Anouk is a credible on-the-ground practitioner who has actually mapped supplier networks and navigated resistance from factories - her experience shows. Edwin holds a senior title at Huawei but his answers are largely theoretical cloud-promotion talking points with minimal DPP-specific operational depth.

“When we started mapping out all our suppliers, it was very hard because it said like, okay, I don't want to show you. I don't want to show you the back door where maybe, uh, migrant workers are, are walking out”

“we have our own cloud, it's globally available. It's a very specific Cloud, if you compare it to other cloud operators and cloud providers, because it's born out of a necessity and it's born out of an industry”

A few concrete data points appear - 100+ stores in 30+ countries, 50-60% production capacity with a shared factory, batch-level passport granularity - but there are no regulatory deadlines cited, no implementation costs, no uplift metrics, and Edwin's technology sections are almost entirely number-free abstraction.

“in combination have over 100 stores in over 30 countries”

“Maybe we have 50 or 60% of the production capacity. So we are important for our suppliers”

The host structures the conversation sensibly and occasionally asks a clarifying question worth asking (batch vs. item-level scope). However, he rarely follows up with pressure, consistently validates and restates rather than probes, and lets Edwin's lengthy, vague answers pass entirely unchallenged.

“Is it for a product range, let's say so one design of T shirt, for example, or is it literally for each specific T shirt, each specific item”

“So you've mentioned that in terms of challenges, there's the, the make or buy decision and then there's maybe this challenge around. Well, why do we have to do this?”