Variants

UnoPim configurable products map to WooCommerce variable products. Variant axes (the "size", "colour", "material" attributes that vary between variants) become WooCommerce variation attributes. Each variant becomes a WooCommerce variation under the parent variable product.

Concepts

Pull (UnoPim → WooCommerce variants)

For an incoming configurable product:

1. The parent is created or updated as a WooCommerce variable product, and each variant axis attribute is marked "used for variations".
2. For each variant in UnoPim:
   • The connector resolves the axis combination (e.g. color=red, size=M).
   • It finds or creates the matching variation under the parent.
   • It applies the variant axis values, plus any non-axis attributes from your mapping.
   • It applies price, stock, SKU.
3. Per-variant images are pulled separately, queued in the background so they don't block the parent product import.

Push (WooCommerce → UnoPim variants)

When you save a variable product:

1. The parent is sent as a UnoPim configurable product, with the list of variant axes.
2. Each variation is sent as a separate UnoPim product, with its own SKU and variation values.
3. Per-variant images are sent to UnoPim's media area.

Variant images

Some UnoPim setups attach a different image per variant — for example a red T-shirt and a blue T-shirt with their own photos. The connector pulls each variant's image separately and sets it as the featured image on the matching variation.

Variant images are queued in the background, so they don't block the rest of the import.

How variant axes are resolved

A UnoPim configurable product knows which attributes are its axes. WooCommerce stores the same fact via the parent product's "used for variations" attributes.

The connector reads UnoPim's variant axes, finds the matching WooCommerce attribute taxonomies, and marks them as "used for variations" on the parent. If a UnoPim axis has no matching WooCommerce taxonomy (rare), the importer creates one automatically.

Family schema

The product's UnoPim family decides which attributes are valid as variant axes. If a product accidentally lists an attribute that the family doesn't allow as an axis, the connector logs an error ("axis outside family schema") and skips that variant.

Channel availability per variant

Each variant can be active on some channels and inactive on others. The pull side translates this into:

• Per-variation visibility
• Per-variation publish status (published, private, draft)

Edge cases

A UnoPim product converts simple → configurable

The existing simple WooCommerce product is re-typed to variable. Its existing fields are preserved. The same happens in reverse on push.

A variant is deleted in UnoPim

Behaviour depends on your On-delete setting:

• Trash — the variation is moved to the trash
• Delete — removed permanently
• Skip — the variation stays even though UnoPim removed it

Variant SKUs collide with the parent SKU

UnoPim and WooCommerce both require unique SKUs across products and variations. A SKU collision logs an error and the offending variant is skipped.

Troubleshooting

The connector also exposes hooks for developers who need to extend it.

Next: Multisite