AsPos Plytix Integration

Process

Stock can be synced from AsPos to Plytix.

Settings

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

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

Process

Products can be synced from AsPos to Plytix. Within this sync, different types of products are supported. APIcenter gathers the data from Plytix, then it is run through APIcenter to have the correct settings, values, and formats before it is sent to AsPos. Products are created or updated based on the SKU. Please be aware that SKU's send towards AsPos can only contain numbers.

You can differentiate within APIcenter the behavior between creating and updating products. For example, when APIcenter creates a product and sends in the long description from the AsPos, but if you enrich the data after this in Plytix, you don't want to have it overwritten with an update. For this, you can set a checkbox to update the product info.

Product types

Supported product types: Simple, variant/configurable products.

Attributes/Features

Besides the generic and custom added fields from AsPos, Item Attributes from AsPos are also supported. These need to be manually mapped in APIcenter.

Attributes are used for creating configurable products, like size/color/options. Features are used as extra information fields, think about the country of origin, type, delivery time, etc.

Categories

Categories can be created or updated from AsPos to Plytix.

Images

Images are not supported

Datamapper

You can map extra fields that are available in the API. For a default working 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

Orders can be synced from AsPos to Plytix or the other way around.

Process

Once APIcenter retrieves the order data, it is processed, and missing data (for example, Employee Number) 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 address.

Ordertypes

AsPos supports Invoices and Orders

Plytix supports Orders

Settings

Within APIcenter you can set specific settings that are mandatory for AsPos, like employeeNumber, This number is mandatory. By default, the value 999999 is used, but this can be adjusted.

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

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

For a complete overview please check the documentation.

Datamapper

Per default APIcenter supplies a mapping that makes sure you can send an order towards AsPos. 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