---
title: "EDI and EDIFACT | Skills We Assign For | Azendo"
description: "EDI and EDIFACT in supply chains — partner variation, onboarding, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/edi-and-edifact/"
---

[Skills](https://azendo.co/skills/) APIs and integration 

# EDI and EDIFACT.

EDI is the structured exchange of business documents between organisations, with EDIFACT the dominant international standard. Orders, despatch advices and invoices move as standardised messages rather than as documents.

## Where EDI and EDIFACT fits on a long engagement.

EDI persists because it works and because the network effect is enormous. Large retailers and manufacturers require it, so suppliers implement it, and a format designed decades ago remains the entry condition for trading with major partners.

The standard is less standard than its name suggests. Each trading partner has an implementation guideline specifying which segments they use, which qualifiers they expect and which optional fields are mandatory for them. Supporting a new partner is an integration project rather than a configuration change.

## What an assigned team does with EDI and EDIFACT.

Partner onboarding is the recurring work. Each new relationship brings a specification to interpret, mappings to build and a testing cycle with the partner's own team, and it takes longer than anyone estimates.

Building a mapping layer that makes onboarding repeatable rather than bespoke each time is where the engineering value is, scoped under [software development outsourcing](https://azendo.co/services/software-development/).

## What we use EDI and EDIFACT for.

* Trading with partners who require EDI The entry condition for large retail and manufacturing relationships.
* Partner variation handled by mapping A layer that makes onboarding repeatable rather than bespoke per relationship.
* Acknowledgements handled properly Functional acknowledgements processed, so a rejected message is not assumed delivered.

## How EDI and EDIFACT capacity is assigned.

EDI capacity is assigned inside integration work, with partner onboarding treated as recurring scope rather than a one-time build.

## Industries that ask for it

* [Logistics and transportation](https://azendo.co/industries/logistics-and-transportation/)

## Related in apis and integration

* [REST — skill we assign for](https://azendo.co/skills/rest/)
* [GraphQL — skill we assign for](https://azendo.co/skills/graphql/)
* [gRPC — skill we assign for](https://azendo.co/skills/grpc/)
* [webhooks — skill we assign for](https://azendo.co/skills/webhooks/)
* [Kafka — skill we assign for](https://azendo.co/skills/kafka/)
* [API design — skill we assign for](https://azendo.co/skills/api-design/)
* [message queues — skill we assign for](https://azendo.co/skills/message-queues/)
* [FastAPI — skill we assign for](https://azendo.co/skills/fastapi/)

## Tell us what your roadmap needs EDI and EDIFACT for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)