Issue

The previous KDD066 established the principle of simplifying and standardizing EDI platforms by defining that each business process must have:

• One Primary EDI system

• One (optional) Secondary EDI system, allowed only by exception

However, at the time of KDD066 approval The Primary and Secondary EDIs listed in the table were indicative and are based on the conceptual Design understanding. As part of Detailed Design (SyWay), there is now a need to revisit each process from the KDD066 table and evaluate the options and Finalise the Primary and Secondary EDI. Along with that there is a need to establish a governance process in case any new EDI is required.

Recommendation

Summarise the recommendation being made for the reader, leaving the pro/con evaluation and exact decision-making process to the subsequent sections.

Background & Context

KDD066 established a strategic direction to simplify and standardise EDI platforms by:

• Defining a Primary EDI per process

• Allowing Secondary EDI only by exception

• Reducing fragmentation and long-term operational complexity

  KDD066 - EDI platforms in the f…

Since then, SyWay Detailed Design has delivered:

• A clear To-Be integration architecture centred on SAP Integration Suite, APIs, events, and controlled legacy EDI coexistence for 3PLs

  3PL SyWay TO BE Final

• A clarified supplier collaboration strategy, including Ariba Network, Supplier Portal, and phased onboarding models

  Ariba Network

• Confirmed bank connectivity decisions (e.g. continued SWIFT Bureau usage)

  SyWay - Workshop_ MBC recommend…

As a result, the indicative EDI assignments in KDD066 no longer reflect the executable To-Be design and must now be formally confirmed or adjusted.

Assumptions

Clearly describe the underlying assumptions which informed or limited the choices available, or impacted the decision: cost, schedule, regulatory requirements, business drivers, country footprint, technology, etc. Include links as necessary. This section is important because a future change in circumstances might invalidate some key assumptions, which then prompts a decision to be revisited. 

Constraints

Capture any constraints or limitations inherent to the recommended option. This could be aspects which, if changed or removed in future, could cause the decision to be revisited or invalidated. For example, a constraint might be that a new product has significant gaps in important functionality, which caused an older alternative to be recommended. If those gaps are closed in future, this might cause the decision to be invalidated.

Impacts

Describe the impact of the decision on other aspects such as other processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.

Financial Impact

Explain the financial impact of adopting the recommended option. This must explain both the implementation and operational aspects, i.e. both the effort & cost of implementing and operating longer-term. 

Business Rules

The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order". 

Options considered and Evaluation

Sales

Commerce Portal – Primary EDI

Description

• Customer- and distributor-facing digital channel supporting end-to-end Lead-to-Cash interactions.

• Enables product discovery, pricing, cart & checkout, order tracking, document access, and support through a single portal.

• Integrated in real time with SAP and CRM, designed as the strategic digital front door for customers.

Why Primary

• Aligns with SyWay and ERP Rebuild To-Be architecture and digital ambitions.

• Provides a single, standard onboarding channel for new customers and distributors.

• Supports real-time, transactional processing rather than document exchange only.

• Reduces manual handling and dependency on legacy EDI platforms.

• Enables future capabilities (self-service, AI support, analytics, digital revenue growth).

• Ensures consistent customer experience across GBUs (“One Syensqo”).

Elemica – Secondary EDI

Description

• VAN-based B2B integration platform used for structured exchange of orders, shipping, inventory, and settlement documents.

• Currently supports a set of key and strategic customers with established, high-volume integrations.

• Provides stable, proven connectivity for customers with long-standing Elemica dependencies.

Why Secondary (and not Primary)

• Several key and strategic customers are already deeply integrated with Elemica and have explicitly indicated no appetite to migrate to a new EDI or portal channel.

• Forcing migration would introduce commercial risk and potential disruption to critical revenue streams.

• Elemica ensures business continuity for these customers without impacting ongoing operations.

• However, Elemica is not aligned with the long-term SyWay / ERP Rebuild strategy, which favors SAP-native, API-driven, and portal-based interactions.

• Retaining Elemica as Primary would:

  • Prolong dependence on a VAN-based model

  • Increase long-term cost and complexity

  • Slow down adoption of standardized digital channels

• Positioning Elemica as Secondary allows:

  • Protection of strategic customer relationships

  • Controlled, exception-based usage

  • Prevention of further expansion of the Elemica footprint

Recommendation:

• Commerce Portal is the Primary EDI, as it is scalable, reusable, and applicable to all customers.

• Elemica remains Secondary, as each onboarding requires a dedicated project and some strategic customers are unwilling to migrate.

Procurement

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log