EDI carries the orders, invoices, and shipping data that keep global supply chains moving. Whether you’re a retailer ordering goods from suppliers, a healthcare manufacturer supplying medical products around the world, or a large manufacturer sending tires to automotive companies, it’s often EDI that powers these processes. At the same time, APIs create new ways for companies and their partners to connect in real time. The good news is that IT teams can support these new patterns without replacing the B2B/EDI systems they already rely on.
Continental Tires is one of the world’s largest tire manufacturers, producing tires for cars, trucks, buses, off-road vehicles, and two-wheelers. Behind these operations is a complex B2B ecosystem connecting Continental with its business partners. For years, Axway TradeSync Integration Manager (TSIM) has supported this B2B/EDI environment, exchanging critical business documents such as purchase orders, shipping notices, and delivery confirmations. But as new connectivity needs emerged, Continental needed a way to add APIs without disrupting the B2B/EDI environment it already relied on.
With Axway Amplify Platform, Continental’s IT team extended its established B2B environment to support modern API connectivity, rather than building the required capabilities from scratch in its traditional EDI environment.
The core
Electronic Data Interchange, or EDI, has powered the core of the supply chain for decades now, and it is not going away. EDI remains deeply embedded in enterprise systems, and its standards and protocols keep growing.
Axway TSIM is a high-performance EDI solution commonly used in manufacturing and automotive supply chains. It handles key EDI standards, complex mapping, high-volume processing, and secure protocols including OFTP2, HTTP(S), and AS2.
TSIM does what it was built to do and does it reliably. The question was how to extend B2B operations to new patterns that partners were asking for.
Connectivity pattern
While Continental continues to rely heavily on EDI for its core B2B operations, its IT team began receiving more partner requests to connect through APIs. These connections work differently from EDI. While EDI exchanges standardized business documents, often in large batches over dedicated protocols, APIs support a two-way, real-time conversation, where a partner can send a request and expect an answer shortly after. This model relies on JSON and XML formats, real-time synchronous exchanges at high frequency, and support for modern security protocols like OAuth 2.0 and API keys that verify the request.
This is a common challenge when organizations extend traditional B2B/EDI environments to support API-led integration. Custom development can address individual requirements, but as API use grows, maintaining one-off integrations can add complexity. New data formats, real-time communication, and modern security requirements also introduce needs that traditional EDI environments were not originally designed to address. Changes on the partner side can mean additional development work, making partner onboarding and ongoing management more complex.
See also: Why manufacturers treat EDI as part of the production line
Axway sees this across organizations. Enterprises connect their systems with custom-coded automation and integration bridges that solve an immediate problem. But these custom solutions complicate longer-term scalability: partner connectivity suffers, but so do visibility, security, and control.
Adding APIs to the B2B ecosystem without rip-and-replace
Continental’s IT team worked with Axway to identify the correct approach to the problem. They chose Amplify Platform to support API-based integration alongside their established EDI environment. Now, Continental runs an environment where each pattern runs where it fits best.
There was no reason for Continental to replace TSIM. It remains a mission-critical part of operations, processing a large volume of business transactions as it was designed to do. Amplify now takes care of the API traffic with modern JSON and XML formats, real-time synchronous communication, lightweight mapping, modern security protocols, and smaller, high-frequency payloads.
The first flow that Continental put into production shows how the two patterns work together.
- A partner calls Continental’s API and authenticates with OAuth 2.0.
- Amplify receives a JSON message and maps it to XML.
- Amplify calls Continental’s SAP to receive the master data and attaches it to the message.
- Amplify then posts the order to Continental’s web system and receives the response.
- If an error occurs, Amplify automatically emails a copy of the file through its Microsoft Outlook connector.
- Amplify maps the response back to JSON and returns it to the partner.
- The incoming message and the response are automatically archived in TSIM via SFTP.
The modern API pattern and the established EDI environment operate as one integration landscape.
Standardizing API-led integration
Amplify Platform’s pre-built connectors and standard components now support these API-led integration flows. When requirements change, Continental can update the flow rather than relying on one-off development. Amplify Platform has made establishing new flows easier too. With the support of Axway’s professional services, the team can now build new integration flows on Amplify Platform itself.
The multi-pattern integration model balances workloads. Amplify absorbs the lightweight and high-frequency traffic, and TSIM can focus on heavy EDI transactions. This balance helps manage a large volume of simple information requests that need little translation but can weigh heavily on an EDI system. Continental’s team expects faster partner onboarding, improved productivity, lower complexity, and better scalability for growing transaction volumes.
The transition to Amplify Platform unlocked additional benefits. Partner APIs are now secured with modern OAuth 2.0. Incoming requests, responses, and translated messages are archived, enabling centralized traceability.
Modernizing at the customer’s pace
The project was not a rip-and-replace operation. Amplify Platform added the API capabilities Continental needed while TSIM remained an integral part of its EDI operations.
Continental chose Amplify Platform to build the integration that it runs today: EDI on TSIM, APIs on Amplify Platform. This approach preserved the partner connections that Continental had built over the years and made adding new connections easier.
Axway’s professional services team brought knowledge of B2B standards and protocols, and expertise in advising on ecosystems that serve the automotive industry.
The next frontier: AI
Managed APIs are the foundation for AI, which depends on controlled access to real-time data and an orchestration layer that connects systems with consistent governance. Amplify Platform opens this path for TSIM customers. Organizations that choose to explore AI can connect B2B/EDI capabilities with AI platforms for potential use cases such as monitoring and partner onboarding.
If you’re starting to think about where AI could fit into your own B2B integration strategy, take a look at our white paper: How to make the next move in B2B integration.
Make the next move in B2B integration