Sector · Supply chain

The goods cross borders. The rules change.

A supply chain moves data between organisations governed by different law. Every copy that leaves the original perimeter is a decision, and it is rarely treated as one.

What we see

  • Forecasts come from an ERP, confirmations from a supplier portal, incidents from a shared mailbox. Reconciliation happens by hand more often than anyone writes down.
  • A tier-three supplier has neither a portal nor an interface to call. It sends a file, and part of the chain depends on that file.
  • Data shared with a partner leaves the contractual perimeter the moment it is copied into a collaboration tool. Nobody decides on that copy; it simply happens.
What is at stake

Visibility is missing. The data exists.

01

Visibility beyond tier one

Systems see direct suppliers and infer the rest. Making tier two visible requires an exchange format accepted by parties whose IT resources differ widely.

02

Sharing with third parties

Forecasts, prices and volumes are shared with partners under other legal regimes. Where the sharing tool is hosted determines who can reach that data by legal process.

03

Reversibility

An exchange platform with no provision for getting data back creates an operational and contractual dependency. Exit conditions are read at signature, not at termination.

What we do

Framed exchanges. Exits planned.

01

Azure landing zone with an exchange zone

The environment is written as Infrastructure-as-Code, with a separate exchange zone for inbound partner flows. What arrives from outside does not touch business systems directly.

02

AI agents on supplier documents

Eight weeks to put an agent into service on acknowledgements, dispatch advices and dispute correspondence. Contractual documents stay out of scope until their handling has been cleared legally.

03

Microsoft 365 Copilot with partner separation

The programme starts by separating internal spaces from those shared with third parties. Without that, a supplier document becomes readable across the whole organisation.

04

WIN TO LUX

Migration from Windows Server to Linux and from Active Directory to FreeIPA, with the option of relocating to a European operator such as OVHcloud, Scaleway, Infomaniak or Delos. The move runs in waves, each reversible until the next one is committed.

Applicable frameworks

The data travels. The law follows.

GDPR

Supplier contacts, drivers and consignees remain identifiable people. Transferring that data outside the European Union requires a legal basis and an analysis of the receiving country’s regime.

Data Act (EU)

The regulation governs access to data generated by connected products and sets conditions for switching data processing service providers. It makes reversibility contractual rather than theoretical.

CLOUD Act

A company subject to US law can be compelled to produce data it holds, regardless of where the server physically sits. An exchange platform hosted in Frankfurt by a US company remains within that reach.

Start by seeing

No proposal. A first conversation.

Describe the flow that worries you most and we will say plainly whether it is within our remit.

See your external surface