This module uses configurable rules to determine whether an order should be exported. The conditions for the export can be linked to the payment method, for example, depending on the status of the order. If such an order is recognized, a corresponding export pipeline is being initialized. This process can be set individually for each website (client). The export pipeline is divided into up to four steps:
Depending on the target system, these steps can be deactivated or merged.
In the Transformation step, the Magento order is converted into a target format. Any file format can be easily defined with a template in the Magento backend. Specific formats can be extended programmatically through appropriate interfaces. For example, by means of the SAP plugin for Pacemaker, which we developed.
In the Transport step, the previously transformed order is transferred to the target system. In the standard system, the purchase order can be stored within the local file system. Using appropriate extensions, (s)FTP, REST, SOAP, etc. can be added as additional handlers. Depending on the type of transfer, the processing of the response from the target system can be processed directly within this step or with the next step.
The Response step processes asynchronous responses from the target system. In the standard system, a predefined file is imported that expects the request ID (of the target system). As with the steps described above, there are also numerous extension points to adapt the response processing to the respective target system.
The Notification step enables you to send a notification as soon as the order has reached a corresponding status. This means, for example, that the order confirmation can only be sent once the order has also been accepted by the target system.