When WooCommerce variations are exported as individual feed records, some information may exist on the variation itself while other information is stored only on the parent variable product.

Deviking Product Feeds Pro lets you combine both levels of data through the Mapping system.

This is useful for fields such as descriptions, brands, images, categories and other information that is often stored on the variable parent rather than repeated on every variation.

How Parent Sources Work

For variation records, a parent product value can be requested using the:

parent:<source>

source format. For example:

parent:description

returns the description of the parent variable product rather than the variation’s own description.

Other examples include:

parent:short_description
parent:image
parent:price
parent:sku

The exact source depends on the field you want to retrieve.

Three Ways to Combine Parent and Variation Data

By combining Source and Fallback Source, you can decide which value has priority.

1. Use the Variation Value First

Use this configuration when you want the variation’s own value whenever it exists, but want to fall back to the parent when the variation value is empty.

For example:

Source:
Description

Fallback Source:
parent:description

The result is:

Variation has description
→ Variation description is exported

Variation description is empty
→ Parent description is exported

This is a common configuration for variation feeds.

Example

Parent product:

Premium Running Shoes
Description:
Lightweight running shoes with breathable mesh.

Variation:

Black / Size 42
Description:
(empty)

Generated feed:

<description>Lightweight running shoes with breathable mesh.</description>

The variation remains the exported product record, but its missing description is supplied by the parent.

2. Prefer the Parent Product Value

Sometimes you want the parent value to have priority but still allow the variation value to be used when the parent value is empty.

Configure:

Source:
parent:description

Fallback Source:
Description

The result is:

Parent has description
→ Parent description is exported

Parent description is empty
→ Variation description is exported

This is useful when the parent product contains the primary catalog information for all of its variations.

3. Always Use the Parent Product Value

If a variation must always use the parent value, select the parent source without a variation fallback.

For example:

Source:
parent:description

Fallback Source:
None

Every exported variation will then use the parent product’s description.

A typical result may look like:

<product>
    <sku>SHOE-BLK-42</sku>
    <description>Lightweight running shoes with breathable mesh.</description>
</product>

<product>
    <sku>SHOE-BLK-43</sku>
    <description>Lightweight running shoes with breathable mesh.</description>
</product>

Both variation records use the same description from their parent product.

Combine Parent and Variation Data in the Same Record

You are not required to use either entirely parent data or entirely variation data.

Each mapping row can be configured independently.

For example:

This allows a variation feed to contain:

<product>
    <title>Premium T-Shirt</title>
    <description>Premium cotton T-shirt.</description>
    <sku>TSHIRT-BLK-L</sku>
    <price>29.90</price>
    <quantity>7</quantity>
    <color>Black</color>
    <size>Large</size>
</product>

The title and description can come from the parent while SKU, price, quantity, color and size belong to the variation.

Product Titles

Deviking Product Feeds already provides variation-aware behavior for product names.

The standard:

Name / Title

source returns the parent product title when the current exported record is a variation.

If you need the full WooCommerce variation name instead, including its selected attributes, use:

Variation Name / Title

For example:

Name / Title
→ Premium T-Shirt

while:

Variation Name / Title
→ Premium T-Shirt - Black, Large

This allows you to choose whether your destination receives a shared parent title or a variation-specific title.

Images

Variation images are also handled intelligently.

The Featured Image URL source uses the variation’s own featured image when available and falls back to the parent product image when the variation does not have one.

For example:

Variation has image
→ Variation image

Variation has no image
→ Parent product image

This means you usually do not need to create an additional fallback rule for the main image.

Categories

WooCommerce variations do not normally maintain their own independent product category structure.

Deviking Product Feeds automatically uses the parent product categories for variation records when built-in category sources are used.

This allows a variation such as:

Premium T-Shirt - Black / Large

to inherit the category of:

Clothing > T-Shirts

without duplicating category information on the variation.

Brand and Product Attributes

Brand information may be stored in several ways depending on the WooCommerce store:

Product Attribute
Custom Taxonomy
Custom Field / Meta

If the brand is stored only on the parent product, use the corresponding parent source.

For example:

Source:
parent:attr:pa_brand

or the appropriate parent-compatible source for the way your store stores brand information.

You can also use a fallback strategy when some variations contain their own value.

Example: Brand from Variation, Then Parent

If variations sometimes contain their own Brand value:

Source:
Brand Attribute

Fallback:
Parent Brand

The variation value is used first.

If it is empty, the parent value is exported.

Example: Parent Description with Variation Price

A common marketplace configuration is:

Title       → Parent title
Description → Parent description
SKU         → Variation SKU
Price       → Variation Current Price
Quantity    → Variation Stock Quantity
Image       → Variation image with parent fallback
Color       → Variation Color
Size        → Variation Size

For example:

<product>
    <title>Premium Hoodie</title>
    <description>Premium cotton hoodie with soft inner lining.</description>
    <sku>HOOD-BLK-M</sku>
    <price>49.90</price>
    <quantity>8</quantity>
    <image>https://example.com/hoodie-black.jpg</image>
    <color>Black</color>
    <size>Medium</size>
</product>

This keeps shared information consistent while preserving the individual commercial data of each variation.

Parent Fallback for Multiple Fields

You can use parent fallbacks independently on as many mapping rows as required.

For example:

Description
Source: Description
Fallback: parent:description

Short Description
Source: Short Description
Fallback: parent:short_description

Brand
Source: Brand
Fallback: Parent Brand

Image
Source: Featured Image

You do not need to apply one global inheritance rule to the entire product.

Each field can have its own behavior.

When Should You Use Parent Data?

Parent values are particularly useful for information that is shared by all variations, such as:

• product descriptions;
• short descriptions;
• brand;
• categories;
• general product information;
• common images;
• manufacturer information;
• custom metadata stored only on the parent.

Variation values are usually preferable for information that can differ between purchasable options, such as:

• SKU;
• price;
• stock quantity;
• stock status;
• color;
• size;
• weight;
• variation-specific images.

Preview the Result

After configuring parent and variation sources, use Preview before generating the complete feed.

Check several variable products and confirm that:

• variation-specific values are used where expected;
• parent values are inherited correctly;
• fallback sources activate only when required;
• SKU, price and stock still belong to the correct variation;
• descriptions, brands and images are coming from the intended product level.

Once the result is correct, click:

Save & Generate

to rebuild the complete feed.

Quick Reference

For a field such as Description:

VARIATION FIRST
Source: Description
Fallback: parent:description

PARENT FIRST
Source: parent:description
Fallback: Description

PARENT ONLY
Source: parent:description
Fallback: None

This gives you precise control over parent/variation inheritance without changing the original WooCommerce product data.