Detailed project case study

EDI-to-API Integration & Middleware Modernisation

A managed integration layer bringing legacy EDI and file-based flows together with modern APIs across internal systems and trading partners.

Portfolio headline

Modernised legacy EDI and file-based flows into a more flexible API and middleware model, improving visibility, exception handling and operational control.

Context

Retail operations depended on EDI messages, FTP drops, CSV files, marketplace APIs, carrier feeds and custom mappings. Failed or malformed messages could stall orders, distort inventory or leave teams without a visible explanation.

My mandate

Modernised legacy EDI and file-based flows into a more flexible API and middleware model, improving visibility, exception handling and operational control.

Scope

Multi-system / trading partners
Integration & APIs
simplehuman

Selected technologies

Key decisions

Designed a controlled middleware model for routing, transformation, validation, mapping and normalisation.

What the team delivered

Standardised JSON, XML, CSV, flat-file, SFTP and EDI patterns behind a consistent operating layer.
Introduced message traceability, monitoring, exception queues and repeatable partner-onboarding patterns.

Outcome

Improved message visibility and made failed transactions actionable.
Reduced manual intervention across partner data exchange.
Created a more scalable integration model for retailers, marketplaces and carriers.

Evidence

Public details are limited to the operational record and outcomes that can be discussed safely. Supporting evidence is available in interview where appropriate.

What this demonstrates

This work shows fluency across both legacy enterprise integration and modern API architecture—a combination that matters when critical retail operations cannot modernise in one clean step.