Attributes, Options & Custom Fields
Summary
Attributes describe a parent product, Options define parent/variant relationships, and Custom Fields carry any extra data; all three import via mapping templates or manual entry and are managed in bulk from the Attribute and Options managers.
Attributes describe a parent, Options define parent/variant relationships, and Custom Fields carry any extra data. All three import via the Get Inventory Primary mapping template or can be added manually, and are managed in bulk from the Attribute and Options managers. Use these fields to build detailed, channel-ready listings and to keep naming consistent across Source Inventory, Product Catalog, and Channel Listings.
- Attributes — parent-level characteristics shared by all variants, e.g. Material = Cotton.
- Options — define variant differences under a parent (Size, Color); required for multi-variant parents.
- Custom Fields — any extra data point, used in Flxpoint or mapped to a channel field.
- Merge & rename — consolidate duplicate attribute names and values and rename them across all levels.
- Permissions — set attributes public or private to control what publishes to channels.
| Field | Name header | Value header |
|---|---|---|
| Attributes | Attribute Name 1 | Attribute Value 1 |
| Options | Option Name 1 | Option Value 1 |
| Custom Fields | Custom Field Name 1 | Custom Field Value 1 |
| Field | Where it lives |
|---|---|
| Attribute | Parent record (shared by all variants). |
| Option | Option Name on the parent; Option Value on each variant. |
| Custom Field | Parent or variant, depending on whether it is universal or variant-specific. |
Publish fails with "Missing option name value ..."
A listing variant is missing an option value the channel requires. Make sure every variant under the parent has a value for each option, then rebuild the listing so options inherit from the master and mapping template.
A product shows a low quality rating
Usually missing or inconsistent option values, or a custom field not mapped to the channel. Check that all required fields are present and the option structure is identical across variants.
Renamed or merged attributes appear to revert on reimport
They do not. Flxpoint tracks the Original Source Name and re-associates the old name to your renamed or merged attribute automatically on the next import.
Can I un-merge attributes?
No, un-merging is not supported.
When importing inventory with old attribute names, will they map to my renamed attributes?
Yes. Flxpoint matches the original source name and associates it to the new attribute.
When are options required?
Whenever a parent has more than one variant. Each variant needs a value for every option.
Can I delete attributes in bulk?
No. Delete them individually at each Product or Listing Parent.