Products are synced from the source application to Exact Online. Within this sync different types of products are supported. APIcenter gathers the data from the source application, then it is run through the APIcenter to have the correct settings, values and formats before it is send to Exact Online. Products are created or updated based on the SKU.
You can differentiate within APIcenter the behaviour between creating and updating products. For example when APIcenter creates a product and sends in the long description from the source application, but if you enrich the data after this in Exact Online, you don't want to have it overwritten with an update. For this you can set a checkbox to update the product info.
Due to the limitations in Exact Online there are several things that need to be taken into account when using the sendProduct flow.
Products need to have a start date in Exact to be able to actually sell the product on orders. For that purpose the start date can be mapped in the datamapping. When this is not present in the data the now moment will be used instead to set as start date.
Also when updating a product a check is done to see if the products end date has not already been passed as this will make updating the product impossible and an exception will be thrown as a result of that. When there is no end date set or it has not yet expired the product will be updated however the end date will be left alone and not be updated.
Supported product types: Simple, virtual, variant/configurable products.
- Attributes & Features settings
This is where you create a mapping table for attributes & features. specify the attribute/features for both the source and target application.
- Update products
Do you only want to add new products or also make adjustments on products? You can set this up here.
Exact Online does not support attributes and features like other applications do. However this can be done by using the
ItemExtraFields in Exact Online. A mapping table can be used to specify which attribute or feature should use which item classification or extra field.
When the product or variant is processed the
ItemExtraFields are retrieved and a check is done to see if the value from the attribute or feature is already present. If this is the case the attribute of feature will be further processed and added to the data but when this is not the case the attribute or feature will be skipped as it is currently not possible to create
ItemExtraFields in Exact Online.
Exact Online does not support variants by nature but this can still be achieved by having a custom property that holds the reference to the parent product. For this purpose the setting 'Parent product reference' is enabled which can be used to specify the field name that should hold the reference.
When this setting is left blank, any variant included in the data retrieved will not be processed and a message in the flow report will be displayed instead.
In combination with the handling of the attributes and features there is no problem with working with variants in Exact Online.
Only one category is currently supported. This will be the category on the highest level which is the first category in the data received that does not have a parent category set.
All categories are retrieved before processing the product and variant and the value from the category name will be used to find the category in the
ItemGroups from Exact. If the category cannot be found an exception will be thrown as it is currently not possible to create
ItemGroups in Exact Online.
Currently not yet supported
Per default APIcenter supplies a mapping that makes sure you can send product data towards Exact Online. You can also make adjustments to this yourself.
Default fields that are mapped are for example:
- Long Description
- Short Description
- Price excl. tax or incl. tax
More information about data mapping can be found here.