Integration & applications

B2B and EDI

Trading-partner interfaces, validation, acknowledgements and reconciliation.

Capability in business terms

Why this capability matters

A message sent is not a transaction completed. Visibility must run from submission through acknowledgement to business reconciliation.

What we typically scope

Trading-partner interfaces, mapping, validation, acknowledgements, reconciliation, onboarding.

How we approach the work

Design for the exception, because the exception is the business.

Work we take on

Example engagement — illustrative. Typical scopes of work, not named client case studies.

Onboarding partners takes months

Why it happens
Each new trading partner is a bespoke project and the sales team has stopped promising dates.
How we work it
Standardise a canonical internal format with partner-specific maps at the edge, build a reusable onboarding kit with test harness and sample data, define a certification checklist, template the partner communications.
What you end up with
A repeatable onboarding process with a stated typical duration, and partner variation isolated at the edge.

Orders that vanish between systems

Why it happens
Partners claim orders were sent that the business has no record of, and there is no way to adjudicate.
How we work it
Implement functional acknowledgements at every hop, assign a correlation ID from receipt through to the business document, build a searchable message tracker for operations, alert on missing acknowledgements.
What you end up with
A tracker that answers "where is this order" in one query, and disputes resolved with evidence.

Chargebacks from a major retailer

Why it happens
Compliance chargebacks are rising and the cause is inside the message flow somewhere.
How we work it
Analyse chargebacks by code and root cause, trace each to the responsible step, fix validation and timing at that step, add pre-send compliance checks against the partner's specification.
What you end up with
Chargeback causes ranked by cost, with a fix or a mitigation for each and pre-send validation in place.

A VAN contract up for renewal

Why it happens
VAN costs have grown with volume and alternatives have not been assessed in years.
How we work it
Model cost by partner and volume, assess direct AS2 and API alternatives per partner, weigh migration effort against saving, sequence any moves by partner relationship risk.
What you end up with
A cost model by partner with migration options ranked by saving against effort and relationship risk.

Modernising to APIs without abandoning EDI

Why it happens
Newer partners want APIs; established partners will remain on EDI indefinitely.
How we work it
Establish a canonical business document model, treat EDI and API as protocol adapters over it, share validation and reconciliation logic, publish both an API specification and EDI implementation guidelines.
What you end up with
One business logic path with two protocol adapters, and a published specification for each.

Related business solutions

In your sector

Ways to engage

How we approach the work

Understand the estate

Map dependencies, constraints, decision owners and the current operating model.

Make the decision explicit

Record options, risks, costs and acceptance criteria before implementation.

Make the handover usable

Document changes, operating instructions and the remaining risks.

Delivery is subject to specialist fit and availability.

Start with clarity.

What would make your business easier to run?

Tell us the operational challenge. We will discuss whether a short conversation, a scoped assessment or a delivery engagement is the right next step.