PRISM SmartConnect

Connector Directory

Browse the applications and platforms ECOM discusses for SmartConnect integrations, from ERP and commerce to messaging, queues and enterprise applications. Search by name, or filter by category.

Talk to an EDI/API Expert Request a Demo

Connector availability and scope are confirmed with ECOM for each application, version and use case. The names below are integration targets ECOM discusses with customers, not a promise of a prebuilt connector, and some connections need custom development or additional testing.

Core business systems

ERP and accounting (12)

Systems of record for orders, inventory, pricing and finance.

Commerce and marketplaces (6)

Selling channels that create orders and need inventory and shipment updates.

Warehouse and shipping (4)

Fulfillment, parcel and transportation applications.

Customer and enterprise apps (9)

Application families discussed during scoping. No single product is implied.

Messaging and collaboration

Team chat and collaboration (7)

Route order exceptions, fulfillment alerts, service updates and approval requests to the responsible team.

Mobile and customer messaging (8)

Order updates, appointment reminders, delivery notifications and service conversations through supported business channels.

Email and shared mailboxes (9)

Route inbound requests, send operational notifications and connect mailbox activity with business workflows.

Communications platforms (5)

Multi-channel messaging, provider callbacks and delivery-status updates through a communications provider.

Mobile and browser notifications (3)

Alerts for mobile workers, warehouse users, field teams and customer applications.

Queues, events and streaming

Enterprise messaging (4)

Exchange application messages and hand work between business systems.

Cloud queues and notifications (5)

Buffer work, route messages or distribute notifications to downstream applications.

Event routing (3)

Route order, inventory, shipment and service events to the appropriate workflow.

Event streaming (6)

Continuous operational feeds and multiple consumers of business events.

Lightweight and device messaging (5)

Events from field devices, equipment, connected assets and distributed applications.

Connection patterns (5)

The integration method that fits the broker, application and deployment environment.

Extended enterprise applications

CRM and sales (5)

Accounts, contacts, opportunities, customer updates and sales handoffs.

Customer service (6)

Tickets, order context, shipment updates and service escalation.

Procurement and suppliers (5)

Purchase orders, catalogs, acknowledgments, invoices and supplier updates.

Payments, billing and tax (7)

Payment status, refunds, subscriptions, tax requests and reconciliation inputs.

Product and digital content (5)

Product attributes, descriptions, publishing events and digital asset references.

HR and workforce (6)

Approved employee data, onboarding events and workforce workflow handoffs.

Documents and signatures (7)

Document movement, signature status and approval-related events.

Work and project management (6)

Tasks, issue escalation, ownership and milestone updates.

Marketing and engagement (5)

Approved audience updates, customer events and campaign workflow handoffs.

Data and operations roadmap

Data and analytics (6)

Operational data feeds, reporting inputs and transaction analysis.

Databases and business data (5)

Approved record exchange, reference-data lookups and scheduled synchronization.

Cloud storage and files (5)

File handoffs, import and export workflows and document delivery.

Identity and access (3)

Identity-related workflow events and approved provisioning handoffs.

IT operations and response (5)

Incidents, integration exceptions, escalation and resolution events.

Warehouse and transportation (12)

Fulfillment requests, inventory events, shipment milestones and delivery updates.

Additional commerce and shipping (12)

Orders, product updates, shipment requests, labels and tracking where supported.

Not listed? Universal connectivity reaches applications that have no branded connector. How universal connectivity works

Product names and logos are trademarks of their respective owners, shown only to identify the applications ECOM can discuss integrating. They do not indicate endorsement of, or affiliation with, ECOM.

Frequently asked questions

Does a name in the directory mean a prebuilt connector exists?

No. The directory lists integration targets. ECOM confirms the exact product, version, API access, supported operations and connector readiness during scoping, and some connections need custom development or additional testing. A connector is described as available only after ECOM has verified it for the product and version.

Why are the logos shown?

Product names and logos identify the applications ECOM can discuss integrating. They are trademarks of their owners, shown for identification only, and do not mean the owners endorse or are affiliated with ECOM.

Can ECOM connect an application that is not in the directory?

Often, yes. REST, SOAP, GraphQL and webhook connectivity, with a custom connector SDK for customer-specific applications, is designed for applications beyond the directory. ECOM assesses interface access and any custom work first.

How is connector readiness confirmed?

During scoping, ECOM checks the product and version, API access, the operations you need and any required testing or development, then confirms what is ready and what needs work before committing to a connection.

Talk to an EDI/API Expert

Send us your application list. ECOM confirms the exact product, version, API access, supported operations and connector readiness, and tells you what is ready and what needs work.