There is no need to create data mapping for packaging and ETIM data. If products are set up with this information, it will be automatically synchronized with NOBB.
Packaging:
Along with the feed® NOBB module, basic data for registering NOBB packaging types is provided. To export packaging information from feed® to NOBB, you must create packages of these types.
Refer to the NOBB documentation for their packaging requirements and rules. Although you can have multiple consumer units (F-Pak) for your product in feed®, only one consumer unit is allowed per product in NOBB.
Note: It is crucial to create packaging in the "correct order" according to NOBB's rules concerning levels. When exporting a product from feed® for the first time, ensure that all packaging has been created or that they are created in the correct sequence (F-Pak before D-Pak, etc.).
Note: If you currently have packaging information in "regular" packaging fields in feed® or registered as attributes, your packaging data must be migrated to NOBB packaging types to be exported from feed® to NOBB.
| Info |
|---|
Can m2 be defined as F-PAK in NOBB?
|
ETIM:
Similar to packaging, there is no need to create data mapping for ETIM data, but a valid ETIM class must be specified according to the associated NOBB module for the product.
In feed®, ETIM data is stored directly on the product, whereas in NOBB, it is associated with the NOBB module of a product. Even though it is recommended to use the ETIM class defined on the module, it is possible to use other classes.
| Info |
|---|
ETIM information is currently not mandatory in NOBB. Even if the NOBB module associated with a product has an ETIM class, it is not required to have ETIM information on the product in NOBB. |