Optimizely Configured Commerce has been configured and integrated with many backend ERP's and PIM systems. Many of these vary in implementation and customization. The following describes common integrations and considerations.
Common integrations
Infor SX.e example
Epicor E9 example
Integration approaches
Traditional
SOAP web services or RESTful services
- Products
- Inventory
- Pricing
- Customers
- Dealers / Sales Reps
- History of Orders / Invoices
- Shipments
Configured Commerce Windows Integration Service (WIS)
Extract-Transform-Transport-Load Agent
Connection types
- SQL Server
- OleDb / Odbc
- Web Service
- CSV File (Flat File)
- Sap .NET Connector
Configured Commerce integration flow example
Infrastructure topology
Deployment topology
Enterprise scale
Expectations for the design and development of non-payment connectors
For most connectors, the implementation partner is responsible for the evaluation, design, development, implementation, and testing of the connector.
Although the Optimizely team has created several connectors to common ERP, PIM, tax, and other data providers, these connectors should serve as a starting point, only, upon which the implementation partner may need to extend further to fit the unique needs of each client.
See Rules of Engagement: Payment Gateways for Configured Commerce Cloud for more detail.
Expectations for the design and development of Payment Gateways
The one exception to this above process is payment gateways. Payment gateways that allow for the use of credit cards must be implemented in a specific way to ensure PCI compliance.
As such, the Optimizely team will own the design and development of the credit card portion of payment gateways to ensure PCI compliance. The implementation partner will still be responsible for the implementation and testing of the credit card portion of each payment gateway, as well as all non-PCI scope of payment gateways, including eCheck, ACH, SEPA, and, in many cases, frontend design.
The Optimizely Configured Commerce engineering team will evaluate, design, and develop connectors to support nearly any payment gateway that a client chooses but requires at least 120 days of notice before a new connector will be available for implementation and testing by the client or its implementation partner.
See Payment gateway development expectations for more detail.
<%= heading %>