MailChimp MplusKASSA Integration

Process

Inventory can be synced from MailChimp to MplusKASSA.

Settings p>

Different types of inventory calculations are supported. By default, the available stock - sales reservations is sent.

You can set the value to the target system if you want to have the stock managed or not.

Orders can be synchronized from MailChimp to MplusKASSA or vice versa.

Process

As soon as APIcenter retrieves the order data, it is processed, and missing data (for example, Employee number) are added, and the order is shipped.

First, APIcenter checks whether the order already exists; if it exists, the order will be skipped. If the order does not exist, APIcenter checks whether the customer exists and, depending on the outcome, the customer is created or updated. APIcenter checks whether all products exist, and then the order is confirmed.

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

The check whether a customer exists is based on the e-mail address.

Order types

MailChimp supports Invoices and Orders

MplusKASSA supports Orders

Settings

Within APIcenter you can set specific settings that are mandatory for MailChimp, such as employeeNumber. This number is mandatory. By default the value 999999 is used, but this can be customized.

By default we provide functionality to create specific mappings such as payment terms and methods from MplusKASSA to [source ]

Do you want to use a standard debtor? This is also available as standard in APIcenter.

For a complete overview you can consult the documentation.

Datamapper

By default, APIcenter provides a mapping that ensures that you can send an order to MailChimp. You can also adjust this yourself.

Standard fields that are mapped are, for example:

Customer name

Street billing address

Number

Zip code

City

Country

Street shipping address

Number

Zip Code

City

Country

SKU

Quantity

Price

Process

Products can be synchronized from MailChimp to MplusKASSA. Various types of products are supported within this synchronization. APIcenter collects the data from MplusKASSA, then it is run through APIcenter to have the correct settings, values and formats before being sent to MailChimp. Products are created or updated based on the SKU. Please note that SKUs sent to MailChimp must only contain numbers.

You can differentiate the behavior between creating and updating products within APIcenter. For example, when APIcenter creates a product and sends the long description of MailChimp, but if you then enrich the data in MplusKASSA, you don't want it to be overwritten with an update. To do this, you can set a checkbox to update the product information.

Product types

p>

Supported product types: Simple, variant/configurable products.

Attributes/Properties

In addition to the generic and custom fields from MailChimp, Item Attributes from MailChimp are also supported. These must be manually mapped in APIcenter.

Attributes are used to create configurable products, such as size/color/options. Properties are used as additional information fields, such as country of origin, type, delivery time, etc.

Categories

Categories can be created or updated from MailChimp to MplusKASSA.

Images

Images

strong>

Images are not supported

Datamapper p>

You can map additional fields available in the API. For a standard integration we have already mapped the basic fields that are needed, for example:

Fields

Name/Title

SKU

Long description

Short description

Price excl. tax or incl. tax

Quantity

EAN/GTIN

Currency