Connect Edifact and Intershop

Connecting Edifact and Intershop for a company would involve enabling the automated exchange of structured business documents, such as orders or invoices, between the two systems. This could reduce manual data entry, help ensure data consistency, and support more efficient transaction processing between business partners or internal departments.

You can build this integration on the System2System platform. We design the connection between Edifact and Intershop around the way you work — not as an off-the-shelf connector, but to fit your systems.

Contact us

Why connect Edifact and Intershop?

A company running both Edifact and Intershop could benefit from enabling these systems to exchange data, as this could streamline processes and reduce manual effort. Without a connection, staff may need to enter the same information in both systems, which increases the risk of errors and consumes additional time. Over time, records in Edifact and Intershop could diverge, resulting in inconsistencies that make it harder to reconcile orders, inventory, or customer data. This situation could also lead to decisions being made based on outdated or incomplete information, as updates in one system would not automatically appear in the other. If these systems were connected, the kinds of data exchanged could include order details, product information, pricing, inventory levels, and customer records, provided that both systems support such data types. The connection could help ensure that transactions processed in one system are reflected in the other, supporting more accurate reporting and operational efficiency. However, the specific data that can be exchanged depends on what each system exposes through its API and is determined for each situation individually.

How System2System builds an integration

Connectors

We connect to each system through the interface it offers — an API, a database, a file exchange or a webhook — and handle authentication, rate limits and retries.

Mapping

Fields rarely line up one to one. We map and transform the data so both systems receive it in the shape they expect.

Workflow

We define what triggers an exchange, in which direction data flows and which system takes precedence when the two disagree.

Monitoring

Every exchange is logged. Failures are flagged and can be replayed, so nothing disappears without anyone noticing.

What can actually be exchanged?

That depends on what Edifact and Intershop make available through their APIs, on the licences and modules in use, and on the version each system runs. Which records are synchronised, in which direction and how often, is something we determine together before any work starts.

We are happy to look at your specific situation and tell you what is feasible — including when the answer is that it is not.