In a 1:1 mapping with fallback data fields, you assign a primary PlentyONE data field to the sales channel data field and additionally define one or more alternative data fields. These fallback data fields ensure that the system continues searching if the primary data field for a variant is missing or empty.

How the fallback principle works

The system checks the assigned PlentyONE data fields in the order in which they were assigned in the catalogue:

1. First data field (Primary): The value is transferred if the data field is filled.
2. Fallback data field 1: Is checked if the first data field meets the defined fallback condition (e.g. null or empty). If a value is found, it is transferred.
3. Fallback data field 2: Is checked if fallback data field 1 also meets the condition, and so on.

Important: For each variant, only one value is transferred in the end.

The two fallback conditions

Step-by-step guide to creation

1. Click on the Mapping tab next to the sales channel data field on + Add data field.
2. Select the primary PlentyONE data field and add it.
3. To add a fallback data field, click the plus next to the desired fallback data field again in the list of PlentyONE data fields.
   • The fallback data field is added by default with the condition null.

Option 1: Fallback condition null (keep default)

• Click Confirm.
• Result: The fallback data field is exported if the data field above is not linked to the variant.

Option 2: Fallback condition empty (make changes)

1. Click the gear icon to the left of the fallback data field.
   • The Data column settings window appears.
2. Select the option empty for the setting Fallback condition.
3. Click Save.
4. Click Confirm.

• Result: The fallback data field is exported if the data field above is linked but empty.

Example: If you assign the variant ID as a fallback data field with the condition null to the sales channel data field SKU, the variant ID will be exported if no SKU data field is linked to the variant.