Contents
02 · Documents

Which documents are transferred with EDI?

EDI is not tied to a single document type. Depending on the business partners' processes, orders, order responses, dispatch advices, delivery notes, invoices, stock or product data can be exchanged electronically.

OrderOrder responseASNDelivery noteInvoiceStock data
Document selection depends on the process. Which messages are used is determined by the sector, the commercial relationship and the parties' system structure.
03 · Operation

What is the contribution of using EDI to businesses?

The main contribution of EDI is that it reduces the need to manually enter the same commercial data repeatedly into different systems. A properly designed flow can help reduce inconsistencies in data entry, speed up document processing and make transaction statuses easier to track.

The result is not the same for every company. The benefit depends on transaction volume, existing processes, data quality, integration scope and the participation of business partners.

04 · Comparison

What is the difference between EDI and API?

EDI and API are not direct alternatives to each other. They can meet different needs within the same architecture.

CriteriaEDIAPI
Primary purposeExchange of business documents based on standardsAccess to application data and functions
Flow structureDocument and partner orientedService and transaction oriented
Decision to useBased on business partner ecosystem and document standardBased on real-time needs and application architecture
The correct approach should be assessed according to data frequency, existing standards, the technical capacity of the parties, and real-time needs.
05 · Area of use

Which companies use EDI?

EDI can be used in sectors that regularly exchange high volumes of business documents, such as retail, automotive, manufacturing, logistics and distribution. It is particularly meaningful for suppliers working with a large buyer, organisations managing many business partners, and companies that want to establish standard data flow between ERP systems.

The usage model does not have to be the same for every company. Full system integration, Web EDI or hybrid approaches are evaluated according to transaction volume, technical capacity and business partner requirements.

06 · Preparation

What questions should be asked when starting an EDI project?

  1. Which business partners and document types will be included in the scope?
  2. What are the source and target systems?
  3. What is the message standard and communication method to be used?
  4. Who will be responsible for data mapping, testing, error management and monitoring?
  5. How will new business partners be added to the system?
  6. What operational criteria will be used to evaluate success?