AFAS Yuki Integration

Orders can be synced from Afas to Yuki

Process

You can set the status on which orders are sent, like only the paid orders.

Once APIcenter retrieves the order data, it is processed, and missing data (for example, storeid) is added, and the sendOrder starts.

First, APIcenter checks if the order already exists; if it exists, we skip the order. If it does not exist, APIcenter checks if the customer exists and, depending on the outcome, creates or updates the customer. APIcenter checks if all products exist, and then the order is committed.

APIcenter differentiates in creating the customer based on the source data received. If APIcenter receives a company name from the source, then a company debtor is created with the underlying contact. If there is no company, then a person debtor is created.

The check if a customer is exists is based on the email adress.

Ordertypes

SalesOrders and Salesinvoices are supported towards Yuki

Settings

For a complete overview please check the documentation.

Standard we offer functionality to make specific mappings like payment terms and methods from the Yuki to the AFAS.

Do you want to make use of a default debtor? This is also per default available in APIcenter.

Datamapper

Per default APIcenter supplies a mapping that makes sure you can send an order towards AFAS. You can also make adjustments to this yourself.

Default fields that are mapped are for example:

• Customer Name
• Billing address street
• Number
• Postalcode
• City
• Country
• Shipping address street
• Number
• Postalcode
• City
• Country
• SKU
• Quantity
• Price