MailBlue MplusKASSA Integration

Orders can be synced towards MailBlue as E-Commerce orders.

From MailBlue we can retrieve deals and send them as orders towards MplusKASSA.

Process

You can set the status on which orders are sent from MplusKASSA, like only the paid orders, completed orders or all orders. 

Once APIcenter retrieves the order data it is processed, we add missing data and start the send process towards MailBlue. 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 and create an order.

APIcenter differentiates in creating the customer based on the source data received. If APIcenter receives a company name from the source, then an account is created with the underlying contact. If there is no company then a contact is created. Per default for mailBlue we only create contacts

The check on customer existence is done by default based on the email address.

Order types

The MailBlue integration supports E-Commerce orders and deals

Settings

Within APIcenter you can set specific settings that are mandatory for MailBlue. For example, if you leave the Connection ID empty, it will create a new ID that is used for this specific integration. If you want to make use of an existing Connection ID you can add that value there.

For a complete overview, please check the documentation.

By default, we offer functionality to create specific mappings like payment terms and methods from MplusKASSA to MailBlue.

Datamapper

By default, APIcenter supplies a mapping that ensures you can send an order towards MailBlue. You can also make adjustments to this yourself.

Default fields that are mapped are for example:

• Customer Name
• Billing address street
• Number
• Postal code
• Citdy
• Country
• Shipping address street
• Number
• Postal code
• City
• Country
• SKU
• Quantity
• Price
• ProductURL
• ImageURL