Enterprise integration
Any Partner. Any System. Anywhere.
Connect trading partners, enterprise applications and business systems through secure, any-to-any integration. From traditional EDI to modern APIs, and from batch processing to real-time connectivity, ECOM brings your business together through the PRISM platform and its integration specialists.
What is any-to-any integration?
Any-to-any integration is an approach that connects any combination of partners, applications and data sources, whatever communication method, security requirement, data format or standard each one uses. Instead of building a separate point-to-point connection for every pair of systems, an integration platform translates, validates and routes data between them, so adding a partner or system means configuring one more connection rather than rebuilding the others.
Integration flexibility
Any communication. Any security. Any format or standard. Any ERP.
These are the dimensions ECOM designs for in every integration. Each partner and system connects in the way it supports, and all of them reach your business through one platform.
-
Any partner
Every kind of trading partner
Customers, suppliers, carriers, manufacturers, banks and other partners, whatever their technical capability.
- Customers
- Suppliers
- Carriers
- Manufacturers
- Financial institutions
-
Any system
Your applications and data
ERP, WMS, TMS, CRM, databases, legacy applications, cloud applications and APIs.
- ERP
- WMS
- TMS
- CRM
- Databases
- Legacy
- Cloud apps
-
Anywhere
Wherever systems run
Cloud, on-premises and hybrid environments, across sites and regions.
- Cloud
- On-premises
- Hybrid
- Multi-site
-
Any communication
The connection each partner needs
Secure file transfer, EDI communications, APIs, VANs, files and databases.
- AS2
- SFTP
- FTPS
- FTP
- HTTPS
- REST
- SOAP
- VAN
-
Any security
Controls that fit the requirement
Security settings chosen per partner and architecture, under your policies and agreements.
- Encrypted transport
- Partner-specific settings
- Access control
- Audit trails
-
Any format or standard
Translation between formats
EDI standards, industry specifications and application formats translated in both directions.
- ANSI X12
- EDIFACT
- TRADACOMS
- RosettaNet
- XML
- JSON
- Flat files
-
Any ERP
38+ ERP connectors, and custom integration
Prebuilt connectors where they exist, custom integration for the rest.
- SAP
- SAP Business One
- Oracle
- Microsoft
- NetSuite
- Infor
- Epicor
- QAD
- Sage
-
Batch or real-time
Scheduled volumes and on-demand transactions
Scheduled batch processing and API-driven, event-triggered integration on the same platform.
What "any" means: ECOM designs for the mix of partners, systems and requirements you have. Some connections need custom mapping, adapters, security configuration or partner onboarding, and the scope is confirmed during discovery.
Outcomes
What you can expect
One platform instead of many connections
Partners and systems connect to one integration layer instead of to each other, so a change in one does not ripple through the rest.
Partners connect the way they can
Each partner uses the communication method, security settings and format it supports, without forcing one method on everyone.
Systems change without starting over
Replacing an ERP or adding a warehouse system means changing one connection, not every partner integration.
Batch and real time together
Scheduled volumes and on-demand transactions run on the same platform, with the same monitoring.
Approach
How ECOM delivers it
-
Communication flexibility
AS2, SFTP, FTPS, FTP, HTTP and HTTPS, REST and SOAP services, VAN connectivity, files and databases, chosen per partner and system.
-
Security per partner
Security settings chosen for each partner and architecture, under your policies and agreements, from encrypted transport to access control.
-
Format and standard translation
Translation between ANSI X12, EDIFACT, TRADACOMS, RosettaNet, XML, JSON, flat files and application formats, in both directions.
-
ERP and application connectivity
38+ ERP connectors, plus custom integration with ERP, WMS, TMS, CRM, databases, legacy and cloud applications.
-
Batch and real-time processing
Scheduled batch processing for volume and API-driven, event-triggered integration for transactions that cannot wait.
-
Anywhere it runs
Integration across cloud, on-premises and hybrid environments, and across sites and regions.
-
Partner onboarding
Specifications, connectivity, testing and go-live support for each trading partner, whatever method it uses.
-
Monitoring and visibility
Business and technical teams follow transactions and exceptions across integration workflows with PRISM-SCV.
Inputs, outputs and integration
Communication methods ECOM supports
Partners and systems connect through different transports, interfaces and networks. ECOM selects the method each one requires and documents it for security teams.
| AS2 | Transport for EDI over HTTP or HTTPS, with signing, encryption and signed receipts (MDNs) |
|---|---|
| SFTP | File transfer over SSH |
| FTPS | File transfer over FTP secured with TLS |
| FTP | Unencrypted file transfer, used only where a partner requires it; encrypted alternatives are recommended |
| HTTP and HTTPS | Web transport for documents and services; HTTPS encrypts traffic in transit |
| REST APIs | Application interfaces over HTTPS using JSON or XML |
| SOAP web services | XML-based service interfaces used by many enterprise and legacy applications |
| VAN | Managed value-added network services for partners that require or prefer them |
| File-based integration | Flat files, CSV, XML and other files exchanged with applications and partners |
| Database integration | Data exchanged with application databases or staging tables where a system has no API |
Security
Secure integration built around your business requirements
Security configurations and controls are selected according to the integration architecture, applicable requirements and customer agreements. These are the areas ECOM addresses in every design.
Security and compliance at ECOM-
Encryption in transit
Encrypted protocols such as AS2, SFTP, FTPS and HTTPS protect data as it moves between partners and systems.
-
Authentication and certificates
Certificates, keys and credentials are set up for each partner connection, with their expiry and renewal planned rather than discovered.
-
Partner-specific settings
Each partner's required protocol, encryption and authentication settings are configured and documented for that partner.
-
Access control and audit trails
Each design defines who can access integration tools and data, and how activity is recorded, according to your policies.
Realistic scope
What "any" requires in practice
Any-to-any describes how ECOM designs integration, not a promise that every technology is preconfigured. Some connections need work before they go live.
-
Custom mapping
Partner and application formats that ECOM has not mapped before need maps designed and tested for them.
-
Adapters and interfaces
Systems without a prebuilt connector need an adapter, API or database interface built for them.
-
Security configuration
Certificates, keys, firewall rules and access settings are configured and tested with each partner.
-
Partner onboarding
Each partner goes through specifications, connectivity, testing and go-live, on the partner's timeline as well as yours.
Scenarios
Common scenarios
Consolidating integration tools
Replace separate translators, file servers and scripts with one platform for partners and applications.
Connecting a new ERP or cloud application
Add the new system to existing partner and application flows without rebuilding them.
Mixed partner capabilities
Support partners that use EDI, APIs, file transfer or documents in the same business process.
Compare
Transport protocols, application interfaces and managed networks
These terms are often mixed up. They describe different layers of a connection, and many integrations use more than one.
| Criteria | Transport protocols | Application interfaces | Managed network services |
|---|---|---|---|
| Examples | AS2, SFTP, FTPS, FTP, HTTPS | REST APIs, SOAP web services, database interfaces | Value-added networks (VANs) |
| What it does | Moves files and messages between two endpoints | Exposes an application's functions and data to other systems | A third-party network that relays documents between many trading partners |
| Typical use | EDI and file exchange with partners | Real-time integration with ERP, cloud and partner applications | Partners that require a VAN or have no direct connection |
| Security | Encryption, certificates and keys, depending on the protocol | Authentication and authorization on each call | Provided and governed by the network operator under its agreements |
Frequently asked questions
Does any-to-any mean every technology is already preconfigured?
No. It means ECOM designs for any combination of partners, systems and requirements. Some connections need custom mapping, adapters, security configuration or partner onboarding, and the scope is confirmed during discovery.
Which communication protocols does ECOM support?
ECOM supports AS2, SFTP, FTPS, FTP, HTTP and HTTPS, REST APIs, SOAP web services, VAN connectivity, file-based integration and database integration. The method for each partner depends on its requirements.
Do you support both batch and real-time integration?
Yes. ECOM supports scheduled batch processing and API-driven, event-triggered real-time integration. Actual processing times depend on architecture, networks, partner systems and service agreements.
Which ERP systems can you connect?
ECOM offers 38+ ERP connectors, including SAP, SAP Business One, Oracle, Microsoft Dynamics, NetSuite, Infor, Epicor, QAD and Sage, plus custom integration for other ERPs.
Can integration run on premises as well as in the cloud?
Yes. ECOM integrates systems across cloud, on-premises and hybrid environments. Where the integration platform itself runs is agreed for each customer.
How is security handled?
Security settings are selected for each partner and architecture, according to your requirements and agreements. ECOM documents the protocols, encryption and authentication used for each connection.
Tell us what you need to connect
Share the partners, systems, protocols and security requirements involved. An ECOM integration specialist will explain how they would connect.