Once APIcenter retrieves the order data it is processed, add missing data (for example SalesVatcode) and start the send process towards the target application. First APIcenter checks if the order already exists, if it exists we skip the order. If it does not exists APIcenter checks if the customer exists and depending on the outcome create or update the customer. APIcenter checks if all products exist and then the order is committed.
APIcenter differentiates in creating the customer based upon the source data received. If APIcenter receives from the source a company name then a company debtor is created with the underlying contact. If there is no company then a person debtor is created.
The check on customer exists is done per default by email address.
Jortt doesn’t have any products so an order is always send as a
- Amount to process
The amount of orders we try and sync at once. Always check if the target system can handle the amount of data.
- Specify the Date from which you want to retrieve Orders
Determines the date from which orders are retrieved based on the modify date.
- Self or email setting
When sending in a mutation we can send it with 2 statuses.
sent. By default, the
draft status is selected.
To select the
send status you need to turn on the
Make Use Of A Default Customer Communication Method Id setting and fill in the
Default customer communication method id setting with either
send_method and if it is filled in with either
Per default APIcenter supplies a mapping that makes sure you can send orders towards the target application. You can also make adjustments to this yourself.
Default fields that are mapped are for example:
- Customer Name
- Billing address street
- Shipping address street
More information about data mapping can be found here.