AFAS: Send products to AFAS

The attribute set APIcenter uses for products when the data contains none. Attribute sets are a webshop concept (for example in Magento). The standard data mapping to AFAS does not use this value, so for AFAS you normally leave it empty.

The feature set APIcenter uses for products in the target system when the data contains none. The standard data mapping to AFAS does not use this value, so for AFAS you normally leave it empty.

When on, APIcenter always uses the default attribute set for products, even if the product data contains one. When off (default), the default is only used when no attribute set is present. Attribute sets are used by webshops such as Magento; the standard data mapping to AFAS does not use them.

When on, APIcenter always uses the default feature set for products, even if the product data contains one. When off (default), the default is only used when no feature set is present. The standard data mapping to AFAS does not use feature sets.

Turn this on to use a default attribute set when products contain none. You enter the attribute set in Default attribute set. The standard data mapping to AFAS does not use attribute sets, so for AFAS you can normally leave this off. Off by default.

Turn this on to use a default feature set when products contain none. You enter the feature set in Default feature set. The standard data mapping to AFAS does not use feature sets, so for AFAS you can normally leave this off. Off by default.

Use a mapping table to link attribute fields to the attributes in the other application. Attributes are the properties that make a variant unique, such as size or color; in AFAS you keep them in free fields (vrije velden) on the article. In the table you link each field to the attribute name in the other application. Do not put features, the properties that all variants share, in this table: use Use feature mapping for those. Off by default.

Meant to translate the attribute set of a product into the attribute set of the receiving application, for webshops that group attributes in sets. The AFAS product flow does not use attribute sets, so this setting has no effect when you send products to AFAS. Leave it at the default (off).

Use a mapping table to link feature fields to the feature names in the other application. Features (kenmerken) are properties that all variants of a model share, such as the material or the country of manufacture; in AFAS you keep them in free fields (vrije velden) on the article. In the table you link each field to the feature name in the other application. Off by default.

Meant to translate the feature set of a product into the feature set of the receiving application, for webshops that group features in sets. The AFAS product flow does not use feature sets, so this setting has no effect when you send products to AFAS. Leave it at the default (off).

Decides what happens with an attribute set that has no row in the attribute set mapping table: Use default (default) uses a default attribute set if one is set, Use value keeps the original value and Ignore value leaves it out. The AFAS product flow does not use attribute sets, so this setting has no effect when you send products to AFAS.

Decides what happens with a feature set that has no row in the feature set mapping table: Use default (default) uses a default feature set if one is set, Use value keeps the original value and Ignore value leaves it out. The AFAS product flow does not use feature sets, so this setting has no effect when you send products to AFAS.

Turn this on to use a default category when a product or variant has no category. When sending products to AFAS, the default is used as the article group (artikelgroep) of new articles. You enter the name in Set the value for the default article group, and with the force setting you can apply it to all products. Off by default.

Meant to always give a variant the category of its parent product, even when the variant has a category of its own. The AFAS flows do not use this setting at the moment, so changing it has no effect. Leave it at the default (off).

When on, APIcenter always uses the default category, even if the product already has one. When retrieving products from AFAS, every product then gets the default category instead of its own article group (artikelgroep). When sending products to AFAS, every product is created in the default article group. When off (default), the default is only used when a product has no category.

Meant to give a variant the category of its parent product when the variant has no category of its own. The AFAS flows do not use this setting at the moment, so changing it has no effect. Leave it at the default (off).

The name of the category APIcenter uses as default. When sending products to AFAS this is the article group (artikelgroep) a product is created in; every new article needs an article group, so use the name of an existing article group in AFAS. When retrieving products from AFAS it is the category given to products without one. Default: Import API Center.

Used by file-based connections, such as CSV files on an SFTP server, where the column headers of a file are translated with a mapping table. AFAS connects through its API and not through files, so this setting has no effect for AFAS. Leave it at the default (Use default).

Sets a default enrichment level for new product content, a concept used by sales channels that rate how complete product content is. APIcenter does not use this setting when sending products to AFAS, so you can leave it off. Off by default.

Meant for webshops that use a URL key, the product part of the web address: APIcenter then creates that key on the product. AFAS articles have no URL key, so this setting has no effect when you send products to AFAS. Leave it at the default (on).

Meant to only update products that already exist in the receiving application and never create new ones. The AFAS product flow does not use this setting: it updates an article that already exists in AFAS and creates an article that does not exist yet. Leave it at the default (off).

Meant to only update variants that already exist in the receiving application and never create new ones. The AFAS product flow does not use this setting: it updates an article that already exists in AFAS and creates an article that does not exist yet. Leave it at the default (off).

Meant to control whether variants that already exist in the receiving application are updated at all. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated, and an article that does not exist yet is created. Leave it at the default (off).

Meant to control whether products that already exist in the receiving application are updated at all. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated, and an article that does not exist yet is created. Leave it at the default (off).

Meant to control whether APIcenter updates the brand of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the categories of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the description of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the features of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the images of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the stock management and allow backorders flags of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (off).

Meant to control whether APIcenter updates the long description of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the metafields of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the price of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the short description of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the SKU of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the supplier of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the title of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the product type of an existing product when the product is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the attributes of an existing variant when it is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the categories of an existing variant when it is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the description of an existing variant when it is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the images of an existing variant when it is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the long description of an existing variant when it is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the metafields of an existing variant when it is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the price of an existing variant when it is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the short description of an existing variant when it is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Meant to control whether APIcenter updates the title of an existing variant when it is sent again. The AFAS product flow does not use this setting: an article that already exists in AFAS is always updated with all fields from the data mapping. Leave it at the default (on).

Turn this on to use a default warehouse (magazijn). For orders sent to AFAS, APIcenter then puts this warehouse on the order and on order lines without a warehouse. If this is on but no warehouse code is filled in, the order is not sent. Off by default.

When on, APIcenter always uses the default tax class (VAT code), even if the data contains another one. When off (default), the default is only used when the data contains no tax class. For products sent to AFAS, this means every new product gets the default tax class.

Use a mapping table to translate VAT classes or rates from the other application into VAT codes (btw-codes) in AFAS, for example the 21% rate of a webshop into the matching AFAS code. On orders, refunds and purchase orders the code is set per order line; for financial mutations it is also used as the VAT code of the booking. Values that are not in the table are handled by What to do when the mapping can not be made?. Off by default.

Turn this on to use a default tax class (VAT code) when the data contains none. You enter the value in Set the value for the default taxclass when products are created. This default is also used for the extra order lines for costs when they have no tax class of their own. Off by default.

The tax class (VAT code) APIcenter uses when the data contains none. Enter the value without a % sign. With a mapping table you can translate the tax values of the source into the VAT codes of AFAS. For products, the tax class is only set when the product is created in AFAS; you change it later in AFAS itself.

Decides what happens when the VAT mapping table has no row for a value from the incoming data.

• Use default: APIcenter uses the default tax id, if that default is switched on; otherwise the field stays empty.
• Use value: the original value is sent to AFAS unchanged.
• Ignore value (the AFAS default): the field stays empty.

For products, AFAS always expects a VAT value, so choose Use default there and set a default tax id.