6 min read

Isabelle Dufour

What she needs: A governance interface she can operate without engineering expertise, with audit trails certification bodies consume independently. What she will not do: Hire engineers, ask suppliers to do anything beyond a guided web flow, or approve technology she cannot explain. Why she buys: Replacing spreadsheet-and-email supply chain data collection with verifiable, auditable exchange.

Head of supply chain transparency at a mission-driven consumer goods brand, with a background in fair-trade certification rather than technology, no engineering team, and tier-2 suppliers in West Africa and Southeast Asia who are not infrastructure teams either. She needs a governance interface accessible without engineering expertise and audit trail data certification bodies can consume independently.

Role: Head of Supply Chain Transparency, mission-driven consumer goods brand (620 employees)

Background

Isabelle studied international development at Sciences Po Lyon before completing a master’s in sustainability management at the Rotterdam School of Management. She spent her early career at a fair trade certification body, where she developed a detailed understanding of what supply chain claims actually require to be credible, not just audited at a point in time, but continuously verifiable. She joined her current employer five years ago, attracted by the brand’s public commitment to radical transparency: the company publishes its full supply chain, its pricing structure, and its supplier relationships openly. Her job is to make sure that transparency is backed by data rather than narrative. She does not have a technical background, but she understands data flows, audit trails, and what certification bodies require when they assess a supply chain claim. She has never heard of the Eclipse Dataspace Components project. She has heard of GAIA-X because it appeared in a European Commission report she read last year, but she could not describe what it does.

Responsibilities

Isabelle is responsible for the integrity of the brand’s supply chain transparency programme, ensuring that the claims the company makes about its sourcing, its supplier conditions, and its environmental footprint are backed by verifiable, auditable data rather than self-reported assertions. She manages relationships with the certification bodies that audit the supply chain, coordinates with tier-1 and tier-2 suppliers to collect and validate the data those certifications require, and oversees the internal reporting that feeds the brand’s annual impact report. She has recently taken on the task of building a data exchange infrastructure that allows the brand’s suppliers to share verified supply chain data directly, in a way that is auditable by certification bodies without requiring manual document collection and reconciliation.

Challenges

Isabelle’s current supply chain data process is built on spreadsheets, email, and periodic on-site audits. It works, but it scales badly, as the supplier network grows and certification requirements become more granular, the manual collection process consumes an increasing share of her team’s capacity and introduces reconciliation errors that create audit findings. She also faces a credibility problem: the data she collects is self-reported by suppliers, and while auditors spot-check it, there is no continuous verification. A consumer or journalist who asks how she knows the data is accurate gets an answer that depends on trust rather than evidence. She has concluded that the only durable solution is infrastructure that allows suppliers to share verified data directly, under policies the brand controls, in a form that certification bodies can query independently. She does not know what that infrastructure looks like technically, and she does not have an engineering team to build it. She has a small innovation budget and a board that is supportive but will want to see a working pilot before committing to a full rollout.

Goals

Isabelle wants to replace her spreadsheet-and-email supply chain data process with a data exchange infrastructure that allows suppliers to share verified data under policies she defines, in a form that certification bodies can access and audit independently. She wants the infrastructure to be credible to external assessors, not a proprietary dashboard that requires trust in her organisation’s data management, but a system where the data provenance and access policies are auditable by design. She wants to be able to onboard suppliers with minimal technical friction, her tier-2 suppliers in West Africa and Southeast Asia are not infrastructure teams, and if onboarding requires anything more complex than a guided web flow, she will lose them. She also wants the solution to be explainable to her CEO and her board without a technical translation layer, if she cannot describe how it works in two sentences, it will not get past the approval conversation.

Technology use

Isabelle uses standard business tools, Google Workspace, Notion for documentation, Airtable for supplier data tracking, and is comfortable with web-based platforms that have clean, purposeful interfaces. She is not a developer and has no interest in becoming one. She evaluates technology by whether it solves a specific problem she has already identified, whether the onboarding process is clear enough that she can complete it without hiring a consultant, and whether the vendor can explain what they do in terms that connect to supply chain transparency rather than cloud infrastructure. She will not approve a technical solution she cannot explain. She will not engage with a sales process that leads with Kubernetes.

Needs from Kaphera Cloud

Isabelle needs a platform that she can describe as a governed data exchange layer, not a cloud service, not middleware, but an infrastructure that enforces the rules she sets about what data her suppliers share, with whom, under what conditions, and with what audit trail. She needs the governance interface to be accessible without engineering expertise: registering a dataspace profile, configuring supplier onboarding rules, and reviewing access logs should be tasks she can complete through a clear web console without touching a configuration file. She needs supplier onboarding to be as close to self-service as possible for the suppliers themselves, with a guided flow that does not presuppose infrastructure knowledge. She needs the platform to produce audit trail data in a format that certification bodies can consume independently, without requesting it from her team. She needs a pricing model that fits within an innovation budget, the shared or dedicated tier, not an enterprise contract, so that the pilot can be approved at team level rather than requiring board sign-off. And she needs to be able to tell her CEO that the infrastructure is operated by a European company, on European infrastructure, that cannot be acquired by a hyperscaler, because the brand’s sovereignty narrative extends to its own data infrastructure.

Quote

“Our suppliers trust us with their data because we have a reputation worth protecting. I need infrastructure that earns that trust by design, not by asking them to take our word for it.”

Graph View

Backlinks