Login / Sign up
Supplier catalogs

How to turn repeated supplier attribute columns into normal fields

2026-06-30
Task

A supplier sends one XLSX or CSV file where attributes are stored as column pairs: Property1, Value1, Property2, Value2. You need normal columns such as Color, Material, and Power for filtering, editing, or export.

Short answer

Use a table profile and Field Builder. For a single file, the consolidated catalog is not needed: the builder converts the repeated pairs into normal columns before the table editor opens.

How to do it in Eofferix

  1. Create a table profile for the supplier XLSX or CSV and wait for Build table before editor. If the table is already open, click Field Builder.

    Animation of building attributes from repeated columns
    The animation shows entering the builder, setting the column mask, confirming, and seeing the result table.

  2. Open the detected repeated column group. In this example, the future column title comes from Property{i} and the cell value comes from Value{i}.

    Opening Field Builder in Eofferix
    The builder appears before the table editor when repeated column pairs are detected.

  3. In mask mode, set the property title column as Property{i} and the value column as Value{i}. The {i} index connects the first pair with the first value, the second pair with the second value, and so on.

    Repeated column mask in Field Builder
    Use a mask when the table stores attributes in numbered repeated columns instead of an array.

  4. Check the preview of generated columns. If an attribute is not needed, hide it in the preview.

    Confirming generated columns in Field Builder
    After confirmation, the original technical pairs do not have to be added to the final table.

  5. Click Add and continue, then work with a normal table: filter rows, clean values, and export CSV, XLSX, JSON, or another required result.

    Table after attributes were built into separate columns
    The final table contains direct product fields and readable attribute columns.

Before / after

Before

source data
skunameProperty1Value1Property2Value2Property3Value3
LMP-2201Onyx desk lampColorwhiteMaterialsteelPower12 W

After

result
skunameColorMaterialPower
LMP-2201Onyx desk lampwhitesteel12 W

How to check the result

  1. The table should contain attribute columns, not technical pairs such as Property1 and Value1.
  2. Check several rows: each value should appear in the column named by the matching pair.
  3. If there is one source file and you only need a transformed output, do not move the scenario into the consolidated catalog.

Process data faster with Eofferix

Create a free account to automate catalogs and price lists around your own rules.

Sign up