Asperion Feeddex Integration

Process

Inventory is synchronized from Asperion to Feeddex.

The inventory from Feeddex is synchronized in the Order flow (i.e. when a customer has an order placed).

Settings

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

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

Customers are synced from Asperion to Feeddex.

Process

The customer flow is different from the customers created via the order flow. In this flow, customers are always updated in case of a change. And in the order flow, customers are only updated or created when an order is placed.

We check by default whether the customer exists based on email address.

Settings

You can set the required fields for Asperion on the Settings tab, for example the business booking group.

p>

Data mapping

By default, the fields from the flow are already linked. You can also make adjustments here yourself.

Standard fields that are assigned are, for example:

• Customer name
• Billing address
• Street
• Number
• Zip code
• City
• Country
• Shipping address
• Street
• Number
• Postcode
• City
• Country

Asperion

To the Asperion For the application to function correctly with APIcenter, the following conditions must be met.

• An account on app.apicenter.io. You can register for aaccount.
• An Asperion inBalance or inTrade package.

Process

Products are synchronized from Asperion to Feeddex. Various types of products are supported within this synchronization. APIcenter collects the data from Asperion, then it is passed through the APIcenter to have the correct settings, values and formats before being sent to Feeddex. Products are created or updated based on the SKU.

You can distinguish between creating and updating products within APIcenter. For example, when APIcenter creates a product and sends the long description from the Asperion, but if you then enrich the data in Feeddex, you do not want it to be overwritten with an update. For this you can use a checkbox to set whether you want to update the product information.

Product types

Supported product types: "simple" products.

Variants are not supported by Feeddex.

Can you transfer variant products in Asperion to a [ target]?

Attributes/characteristics

In addition to the generic and custom fields from Asperion Item Attributes from Asperion are also supported. You can assign these manually in APIcenter.

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

Articles in Asperion have five fields that can potentially be used for characteristics or attributes.

Categories

Categories are not supported in Asperion.

Images

Images are not supported in Asperion.

Datamapper

You can map additional fields available in the API. We have already linked the basic fields that are required for standard integrations; for example

Fields

• Name / Title
• SKU
• Long description
• Short description
• Price excl. VAT or incl. tax
• Quantity
• EAN/GTIN
li>
• Currency

Orders can be synced from Asperion to Feeddex or from Feeddex to [source ]

Process

You can set the status when orders are shipped from Feeddex, such as only the paid orders.

Once APIcenter has retrieved the order data, it is processed, missing data is added (for example mandatory data) and the shipping process to Asperion starts. First, APIcenter checks whether the order already exists; if it does exist, we skip the order. If it does not exist, APIcenter checks whether the customer exists and depending on the outcome, creates or updates the customer. APIcenter checks whether all products exist and then the order is placed.

APIcenter distinguishes itself by creating the customer based on the received source data. If 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 on the existence of the customer is carried out by e-mail address as standard.

Order types

You can decide which type of order you want to send to Asperion.

Our Asperion integrations support Sales Orders and Invoices

Settings

Within APIcenter you can set specific settings that are mandatory for Asperion. For a complete overview, please consult the documentation.

By default we provide functionality to create specific mappings such as payment terms and methods from the Feeddex to Asperion.

Do you want to use create collective accounts receivable? This is also available as standard in APIcenter.

Datamapper

By default, APIcenter provides a mapping that ensures that you can send an order to Asperion. You can also make adjustments here yourself.

Standard fields that are assigned are, for example:

• Customer name
• Street billing address
• Number
• Postcode
• City
• Country
• Shipping address street
• Number
• Postcode
• City
• Country
• SKU number
• Quantity
• Price