eZ Commerce is build to communicate with ERP systems. It uses the data and logic already provided by the ERP system.
This ensures that the
If you are using a prepared connector (Connector) you will find further information about the configuration here: Web-Connector Configuration
In case a REST based ERP system is used see: Curl Configuration
In case your ERP supports Web-Services directly: Configuration for Webservice based ERPs
eZ Commerce is using a standard "language" (UBL) to model the business data. The ERP systems normally are using vendor specific structures and attribute names. A xslt based mapping feature allows to adapt the mapping between these formats. See Adapt the mappings for ERP functions for more details.
The Admin user interface provides a monitoring service which allows to check all messages exchanged between ERP and eZ Commerce.
After selecting a date range and a measuring point (recommended ones: "Request data before and after mapping" and "Response data before and after mapping" ) you will get more details about the request send to the ERP system and the mapping which has applied.
You can copy the input xml and copy the content to PHP-storm. This allows to test and adapt the mapping using the stated xslt file without testing it using the shop.
Besides the standard processes eZ Commerce offers an API to call ERP functions in your application. Check ERP communication for more details.
eZ Commerce offers prepared interfaces to
For the listed ERP systems connectors are available.
Since eZ Commerce offers an open interface using standards (REST, Webservices and a standard XML Format UBL) it is possible to adapt other ERP systems as well.
Requirements towards an ERP system: The ERP system has to be open (means offers e.g. a REST or Web-Service interface) and offers the functions as listed in "Supported processes with ERP integration" .
This chapter will describe which data is exchanged between eZ Commerce Advanced and the ERP system. It depends on the project specific configuration which data will be exchanged since in complex systems other systems might provide data as well (such as a PIM system).
|Data/Process||What is exchanged||When|
Data about the customer such as
|The data for a customer will be fetched from the ERP when the user logs in and has a customer number|
|Product data||Products and product groups||During the import. The import will be initiated e.g. every night or even more often. This data is usually provided using an export (XML,CSV,Json)|
List price and volume prices
List prices will be exchanged during the product import
Individual prices will be fetched from the ERP when a customer is logged in and has a customer number. In that case the shop requests prices in realtime from the ERP. It can be defined by project in which cases prices are requested from the ERP (.e.g product detail page, basket and checkout)
|Orders||Address data, Delivery address, products and customer number|
When the customer has ordered the order will be send immediately to the ERP system. If a electronic payment is involved the order will be placed when the payment provider has acknowledged the payment transaction.
|Documents||Invoices, orders, delivery notes, credit memos||The addon order history requests such documents in real time from the ERP. This ensures that the customer will see all documents even if an order has been placed by phone or fax.|
The documentation provides more information about this topic: