Delivery models
ECOM offers five ways to run B2B integration. They differ in who hosts the platform, who builds and maintains integrations, and who watches production. Use this guide to find your starting point.
Typical responsibilities. Your exact scope is defined in your service agreement.
| Model | Platform hosting | Maps and partner setup | Daily monitoring | Issue resolution |
|---|---|---|---|---|
| PaaS Our managed integration platform; your team, our specialists or both build and run integrations. | ECOM | You | Shared | You |
| SaaS Hosted applications such as PRISM-SCV, PRISM-WebEDI and PRISM-SmartConvert. | ECOM | Shared | Shared | You |
| Private Cloud A dedicated environment for strict control requirements. | ECOM | You | Shared | Shared |
| EDI Team as a Service Our specialists extend your team on your platform or ours. | Shared | ECOM | ECOM | Shared |
| Fully Managed EDI We operate the defined EDI services end to end. | ECOM | ECOM | ECOM | ECOM |
Our managed integration platform; your team, our specialists or both build and run integrations.
Hosted applications such as PRISM-SCV, PRISM-WebEDI and PRISM-SmartConvert.
A dedicated environment for strict control requirements.
Our specialists extend your team on your platform or ours.
We operate the defined EDI services end to end.
Four questions that point most organizations to the right starting model.
Yes: iPaaS or Private Cloud keep your team in control of integrations.
No: Consider EDI Team as a Service or Fully Managed EDI.
Yes: Private Cloud gives you dedicated infrastructure and change control.
No: iPaaS or SaaS keep costs and effort lower.
Yes: EDI Team as a Service lets you set priorities while ECOM does the work.
No: Fully Managed EDI hands defined outcomes to ECOM.
Yes: SaaS applications such as WebEDI are usually the quickest start.
No: An integrated model connects partners directly to your ERP.
Yes. Many organizations combine models, for example iPaaS for core integrations with EDI Team as a Service for extra capacity, or SaaS WebEDI for small partners alongside managed EDI for large ones.
Yes. Because every model runs on PRISM or supports your existing platform, moving between models is usually a change in responsibilities rather than a re-implementation.
No. Features and responsibilities differ by model and are defined in each service agreement. ECOM recommends a model after reviewing your requirements.
It depends on your volumes, partner count, internal skills and the cost of staffing EDI roles. ECOM can help you compare the total cost of each option for your situation.
Tell us about your partners, systems and team. We will recommend a delivery model and explain the trade-offs.
