Custom attributes are attributes you can use in the different models of the platform.
Model | System | Purpose |
Asset | Return Dock | The data for these custom attributes can be entered by an operator when handling returned products. |
Product | Return Bird | The data for these custom attributes can be entered by the customer or an agent when adding a product to the return. |
Return | Return Bird | The data for these custom attributes can be entered by the customer or an agent when creating a return. |
Product master | Return Bird | The data for these custom attributes can be entered by an administrator when adding an administrative product to a product in the product master. |
You can control system attributes at 3 levels:
General: define the setup of the attribute (type, active, required)
Translations: define the language-specific values of the attribute (label, placeholder)
Appearance: define where the attribute appears to be filled in and where the attribute is visible
General
In general settings, you can define the custom attribute in all its details. The label, placeholder, and tooltip can be set up in all languages that have been activated for your account.
Translations
In translations, the label and placeholder can be translated for all languages that have been activated at the account level.
Appearance
In the appearance settings, you can define when the custom attribute is active, where it appears to enter a value, and where it appears to show the value:
Custom attributes at the asset level can be specified by return policy, product group, and product.
Custom attributes at the product level can be specified by the return policy and product group.
Custom attributes at the return level can be specified by the return policy.
Dependencies for appearance:
Level | Return policy | Product Group | Product |
Asset level | Yes | Yes - AND relation with the Product | Yes - AND relation with the Product Group |
Product level | Yes | Yes |
|
Return level | Yes |
|
|
Appearance for a custom attribute is controlled with the following logic:
Level | Logic |
Return Policy | If no return policies are set to "allowed", the custom attribute will be shown for all return policies. If one or more, but not all return policies are set to "allowed", the custom attribute will only be shown for the return policies that have been set to "allowed". |
Product Group | If no product groups are set to "allowed", the custom attribute will be shown for all product groups. If one or more, but not all product groups are set to "allowed", the custom attribute will only be shown for the product groups that have been set to "allowed". |
Product | If no products are set to "allowed", the custom attribute will be shown for all products. If one or more, but not all products are set to "allowed", the custom attribute will only be shown for the products that have been set to "allowed". Products need to be set one by one. |
For the asset level, there is an AND relation between the Product Group and the Product.
When you specify a Product, the associated Product group can but does not have to be selected. The allocation will be done at the Product level.
When you specify a Product (from a certain product Group), you should not specify another Product Group. In that case, the allocation will fail.