Splitting Variants into Separate Products

Turn one feed row that carries several sizes or colors into one product per variant, with the Split into variants rule action. Each variant becomes its own catalog item for ads.

Updated November 6, 2026

A feed row that packs several sizes or colors into one entry can only advertise as one product, with one price and one availability. Split it, and each variant becomes its own catalog item with its own price, availability, image and identifier. A shared Item group ID tells destinations the variants belong to one family: see item_group_id and Product Variants.

How to split a feed into variants#

  1. Open the catalog from your project's Catalogs list and go to the Rules tab.
  2. Choose + Add rule, then set the action to Split into variants.
  3. In column to split on, name the column that holds the variants.
  4. On the Mapping tab, map ID to a column inside each variant (see the next section).
  5. Publish the catalog. Publishing starts an import, and the variants appear when it finishes.

If the variants are in one cell#

A repeated feed element like variant splits on its own. If one cell lists the sizes or colors separated by commas, you first turn it into several values: add a Set field action, before the split in the same rule or in a rule above it, that writes a column with a Split step on it (the delimiter, with Trim whitespace and Remove empty items on). Then split on that column. Without this, the split reads the whole cell as one item and you get one product back.

If the column already holds several values (the Mapping tab's rail shows a list icon beside it) and each of them is a list, use Map each with Split inside it, then Flatten. A plain Split on such a column splits only its first value. See Steps: changing a value before it is used.

Give each variant its own stable ID#

Every variant needs its own ID, or they collapse into one catalog item, and Renable won't let you publish until they have one. There's no separate ID setting: on the Mapping tab, map ID to a column inside each variant, such as its own SKU or a value built from it. See Mapping Your Feed to Catalog Fields.

Everything after the split runs once per variant#

Rules above the split run once on the original row. Rules below it, and the mapping, run once per variant. The same goes for actions before and after the split inside its own rule, so an action before the split can build the column it reads.

A rule below the split can read the parent row's shared fields, such as the title or brand, and each variant's own values, such as its size, SKU or price. So it can build a title from the shared product name plus each variant's size.

To check a split, use Trace on the Rules tab toolbar. After a split it lets you step through each variant and see how every field resolved. See Fixing Your Feed Data with Rules.

You can split a feed only once#

A catalog's feed can carry one split, and a second split is rejected. So you can't stack a split on sizes and another on colors. To get one product per size-and-color combination, split on a single column or list where each entry already is one combination, such as a variants element that lists each size and color pair.

A single feed row can produce up to 1,000 variants. If a row lists more, Renable keeps the first 1,000 and warns you.

A row with nothing to split, such as a product with a single variant or an empty variant column, passes through as one product, so a catalog can mix variant products and simple products. A row with an empty variant column has no value inside a variant to read, so give the ID mapping a fallback to a column on the row itself, or that product isn't imported.

Or ask Aimée#

Tell Aimée what you want, for example "split my feed into one product per size, using the variant SKU as the ID", and she can set up the rule and the ID mapping, then publish once you approve.

FAQ#

Can a rule do other things besides splitting?

Yes. The same rule can set fields before or after the split, carry conditions, and have an "Otherwise…" branch for the products that don't match. The split itself can sit in the "Otherwise…" branch, so "if it's a simple product keep it as-is, otherwise split it" is one rule. A Group products action always runs before the split: see Grouping Products.

Does each variant count toward my plan's feed item limit?

Yes. Every variant a split produces counts as one feed item. See Plans and limits.

What if one variant is missing a field the others have?

That field stays empty for that variant.

Related articles#