Mapping Your Feed to Catalog Fields

The Mapping tab tells Renable which of your feed's columns fills each catalog field, such as ID, Title and Price. Drag a column onto a field, add a fallback, and check coverage in the Fill column.

Updated November 6, 2026

The Mapping tab tells Renable which of your feed's columns fills each catalog field: ID, Title, Price and the rest. Once a field is mapped, every import fills it from the column you chose. To get there, open a catalog from your project's Catalogs list and choose Mapping.

Map a column to a field#

  1. Find the field in the Catalog fields table. Fields are grouped under Identity, Content, Images, Pricing, Availability and Attributes.
  2. Drag the matching column from the Feed columns rail onto that field's row.
  3. Check that the field's live sample shows the value you expect.
  4. Publish the catalog when you're done.

If the previewed value for a field like Price or Stock count can't be read as a number, a warning appears under the field.

To unmap a field, use Remove mapping in the menu at the end of its row. A field you only emptied still counts as mapped.

Required fields#

Required fields are marked with an asterisk: ID, Title, Description, Link, Image link, Price and Availability. The chips at the top of the table keep score, for example 12 mapped and 2 required missing.

A required field that is mapped but comes back empty for some products shows a warning tone and a note such as 14 empty on its row. A product with no ID, Title, Link or Price isn't imported at all, and the import warns you. One missing Description, Image link or Availability is imported, so fix it before a destination rejects the product. To see what each destination asks for, read Required vs. Recommended Feed Fields.

Fallbacks: a second source when the first is empty#

To give a field a fallback, a second source used only when the first comes back empty, open the ⋮ menu on its value and choose Add fallback. Order the stack from most preferred to least: the first value that isn't empty is the one that ships, and a live sample beside each entry shows which source wins for a real product.

A fallback can be a second column, a fixed value, or a value from a stock or supplier feed. For that last one, see Joining Another Feed with a Lookup.

When a rule already set the field#

Rules run first and the mapping fills in afterwards. So a rule that writes Title, or one that arrives from a Ruleset your catalog applies, wins for the products it matches, and your mapping covers every other product. The field's row then shows who supplies the value, with a badge such as provided by Nordics cleanup, overrides Nordics cleanup or adds to Nordics cleanup.

You can change that per field, from the menu on its row:

  • Always set: your mapping wins, replacing whatever a rule produced.
  • Only if not already set: your mapping fills the field only when nothing earlier produced a value.
  • Add to the list: your mapping's value is added to what's already there. Offered only for the fields that hold several values: Additional image link, Product highlights and product attributes.
  • Use the default for this field: single-value fields fill only when nothing else set them, and multi-value fields add to the list. Leave it here unless you have a reason not to.

If a rule produces an empty value, your mapping still fills the field. To write a field from a rule in the first place, see Fixing Your Feed Data with Rules.

Cleaning values as you map#

Every value supports + Add step: trim whitespace, replace text, change case, strip HTML, format a number, format a date, or map one set of values onto another, run in sequence. They are the same steps rules use, covered in Steps: changing a value before it is used.

If your feed repeats a column for a product and you map it to a field that holds one value, the first value is used. A First, Last, Nth or Join step lets you choose.

The Fill column: check your coverage#

The Fill column shows the percentage of products in your last import that got a value for each field. A 60% fill means four in ten products have no value.

After you change a field's mapping, its Fill is dimmed and marked with an asterisk, because it still describes the old mapping. Publish to refresh it: publishing starts an import.

Choosing the product the samples show#

The live samples show one product at a time, after your draft rules and mapping have run on it. Choose the product with the picker above the table: pick one of the sample rows, or type a product ID, a name or any other value to search your whole feed. The value editor has the same picker.

The product stays selected while you edit, on the Rules tab too. The picker goes back to the first sample product if that product leaves your feed, or if you change where the catalog reads its product feed from. A very large product can read Too large to preview, so pick another one.

The Feed columns rail#

The rail on the left lists every column in your feed, including ones the sample rows don't show. The Rules tab has the same list, where you drag columns into rules. The header says when your feed was last read, and its refresh button fetches the feed again, updating the sample and the column list together.

Each column shows:

  • A mapped or unmapped dot: whether the column already fills a catalog field.
  • A type badge: Text, Number, Date or Boolean.
  • A list icon when some rows hold several values. Hover it to see how many.
  • A sample value in ghost text. If none of the sample rows has a value, you get an example from elsewhere in your feed, in italics.
  • How full the column is, when you hover the row: how many rows carry a value, with the percentage.
  • A warning icon when a value couldn't be read as its declared type.

Reading a large feed takes a moment, and the header shows the progress. If the read stops early, the header says why and the rail shows what was found so far. Treat that list as incomplete: a column may still exist.

Below your feed's columns, Rule outputs lists the columns a rule writes, each with a link to its rule.

When none of the sample rows has a value in a column, hover or focus its row and use Trace a product that has a value in this column. Renable finds such a product and opens the trace on it.

A rule or field that reads a column your feed doesn't have right now shows not in the current feed. The value stays empty until the column comes back.

Column types and why they matter#

Each feed column has a type, Text, Number, Date or Boolean, and the type describes each value in the column. Renable infers it from your sample and shows Inferred — click to declare on the badge. Click it to set the type yourself when the guess is wrong. A column with no value in the sample rows is treated as Text until you declare a type.

  • Number has a Decimal separator: Comma, Dot or Not set. It matters only for a single separator followed by exactly three digits, like 4.490, which can be read two ways. Every other number is read by its own shape. With Not set, such a value isn't read as a number, and the import warns you about the column. Hover the badge to see the separator you chose.
  • A warning dot on the badge means some sampled values can be read two ways and no decimal separator is set. Choose one, or clean the values with a Replace step. If the column's other values settle it, the choice opens on that answer, marked Suggested from this column's values. Nothing is saved until you press Apply.
  • Date has an optional parse pattern. Leave it blank to read dates in your catalog's Locale. Format date, Date difference and Shift date steps read the column with the same pattern. See Working with dates.
  • A list icon beside the type means some rows hold several values. The type still describes each value, and a condition looks at every value. See Steps: changing a value before it is used. To split a column whose cells hold a comma-separated list, add a Split step in a Set field rule, or Map each with Split inside it and then Flatten when the column can already hold several values.

A column's declared type decides how conditions compare it. Number columns offer is greater than and is between, Date columns is before, is after and is between, and Boolean columns is true and is false. You can declare a type on the Rules tab too: it's the same setting.

A column without a declared type is compared as text, whatever its badge infers, and publishing refuses a rule that compares one with a fixed number using is greater than, is between and the like. A value that already is a number or a date still compares as one: the numbers a Group products rule computes, and a Math or Shift date result a rule wrote into the column. When you first set up the feed, Renable declares the type it inferred for each column in your sample. A column that appears later, and every rule output, starts undeclared.

So if a rule writes a date into a column and you want to compare it with "60 days ago", set that column's type to Date under Rule outputs. To compare a number a rule computed with a fixed number, set its column to Number. If a rule writes a formatted price, set its column to Number and choose its Decimal separator.

Other column types lists types no column uses any more, such as the type of a rule output you renamed. Removing one asks first if a rule still reads that column, because its conditions then compare the column as text. If one column has two types set under different capitalisations, both are listed with a warning, so remove the one you don't want.

Spreadsheet and CSV feeds: several values in one cell#

In a CSV or TSV feed or a Google Sheet, several values share one cell, separated by commas, and Renable reads that cell as one value. So when Renable generates a mapping for such a feed, it splits the additional_image_link and lifestyle_image_link columns for you, both mapped to Additional image link, with Map each, a Split on , inside it, then Flatten. It does this on feed setup, on Regenerate from feed and on Map 3 unmapped fields, and never on an XML or JSON feed.

It leaves product_highlight and product_type alone, because a value there can contain a comma wrapped in quotes. If yours don't, add the same three steps to that mapping yourself. If they do, use a rule that cleans the quotes first.

If you change a feed's format after the mapping was generated, from XML to a sheet for example, the mapping keeps its old shape. Regenerate from feed rebuilds it for the new format.

Attribute pairs#

The Attributes group holds custom fields, including attribute pairs: extra key-and-value pairs Renable can pass through to your channels. Some feeds carry these as two matching columns that each hold several values, one with the attribute names and one with the values in the same order. Renable detects the common shape when it sets up your mapping, and the result appears as an Attribute pairs row showing which two columns fill it.

To set them yourself, use Add attribute pairs below the table and pick the two columns. A catalog has one attribute-pairs row, so once it exists you edit or delete it from the row itself.

A dropdown on the row offers the choices the field rows do:

  • Add to the list (the default): the pairs join attributes anything else produced.
  • Always set: the pairs replace attributes produced earlier.
  • Only if not already set: the pairs fill in only when nothing has produced attributes yet.

When your feed's columns change#

When your feed has a column for a catalog field nothing is mapped to, the button above the table reads, for example, Map 3 unmapped fields. It adds Renable's suggestion for those fields and never changes what you already mapped, so this is the one to use after a feed picks up new columns. If you don't like a result, use Remove mapping on its row. The button is greyed out when every field your feed has a column for is mapped.

Regenerate from feed rebuilds the mapping from your feed's current columns, suggesting field mappings and attribute pairs afresh. It keeps your rules but replaces every mapping you edited by hand, including attribute mappings. Use it when your feed's shape has really changed, not as a routine refresh.

If you see a message instead of the table#

A catalog on a pre-defined feed configuration can't be mapped until you switch it: open the Product feed source dialog, expand Advanced, and choose Renable engine under Processing. A catalog imported from Meta or Google can't use the Mapping or Rules tabs at all.

A catalog connected to a Meta or Google catalog has no such choice: mapping needs a feed address, a Google Sheet or an uploaded file as the source.

Or ask Aimée#

Tell Aimée what a field should draw from, for example "fill brand from the manufacturer column and fall back to the vendor column", and she can set the mapping and publish once you approve. She can also answer questions about your columns, such as "which of my columns is nearly always empty?"

Related articles#