Product brand information can be stored in different places depending on how a WooCommerce store is configured.

One store may use a dedicated brand taxonomy, another may use a WooCommerce product attribute such as pa_brand, while another may store the brand in a custom field.

Deviking Product Feeds Pro lets you select the appropriate source directly, configure fallback sources, or create a Dynamic Attribute when the exported brand needs conditional logic.

This allows you to create a consistent brand or manufacturer field without changing the original WooCommerce product data.

Common Ways Brand Data Is Stored

Depending on your store, brand information may be available as:

Product Brand taxonomy
WooCommerce Brand attribute
Custom product attribute
Custom taxonomy
Custom / meta field

For example, available sources may include:

product_brand
pa_brand
meta:_brand

The exact sources shown in the Source selector depend on the attributes, taxonomies and custom fields detected on your WooCommerce site.

Method 1: Use the Existing Brand Source Directly

If your products already contain the correct brand information, you normally do not need a Dynamic Attribute.

Open:

Deviking Feeds → Feeds

Edit the required feed and go to Mapping.

Configure the brand field using the appropriate source.

For example:

Output Field:
brand

Source:
Product Brand

or:

Output Field:
manufacturer

Source:
Brand

The output field name can be whatever the receiving system requires.

Example XML Output

A product whose brand is stored as:

Acme

could generate:

<product>
    <sku>ABC-100</sku>
    <brand>Acme</brand>
</product>

or:

<product>
    <sku>ABC-100</sku>
    <manufacturer>Acme</manufacturer>
</product>

depending on the configured output field.

Example CSV Output

The same source can be used in CSV:

sku,title,brand
ABC-100,"Product A",Acme
ABC-101,"Product B",Example Brand
ABC-102,"Product C",Demo Manufacturer

Use a Fallback Brand Source

Some WooCommerce stores contain brand information in more than one location.

For example:

Primary source:
Product Brand taxonomy

Fallback:
Brand attribute

Configure the Mapping row as:

Output Field:
brand

Source:
Product Brand

Fallback Source:
Brand

The resolution works as follows:

Product Brand contains a value
→ use Product Brand

Product Brand is empty
→ use Brand fallback

This is useful when older products use one brand system and newer products use another.

Example: Product Brand with Attribute Fallback

Suppose:

Product A
Product Brand taxonomy: Acme
Brand attribute: empty

Result:

Acme

Another product:

Product B
Product Brand taxonomy: empty
Brand attribute: Example Brand

Result:

Example Brand

The same Mapping row handles both products.

Advanced Source Tokens

Brand information can also be addressed through advanced source tokens when needed.

For example, a WooCommerce global Brand attribute can use:

attr:pa_brand

A custom product brand taxonomy can use:

tax:product_brand

A custom meta field can use:

meta:_brand

The exact key depends on how brand data is stored on the current WooCommerce site.

In most cases, selecting the source from the grouped Source dropdown is easier than entering the token manually.

When to Use a Dynamic Attribute

Use a Dynamic Attribute when the required brand value cannot be taken directly from one existing field.

Examples include:

Products in one category should return one brand

Products with a particular attribute should return another brand

Some products should use a fixed store brand

Unmatched products should use another source as a fallback

Go to:

Deviking Feeds → Dynamic Attributes

and click:

Add Dynamic Attribute

Enter a descriptive name such as:

Feed Brand

or:

Resolved Brand

Then create the required IF / ELSE rules.

Example: Assign a Brand from Product Category

Suppose your catalog structure indicates the product brand.

For example:

Acme Products
Example Products
Demo Products

Create:

Dynamic Attribute:
Feed Brand

Then add:

Rule 1

IF
Child Category = Acme Products

RESULT
Static value:
Acme

Rule 2

IF
Child Category = Example Products

RESULT
Static value:
Example Brand

Rule 3

IF
Child Category = Demo Products

RESULT
Static value:
Demo

The result becomes:

Acme Products
→ Acme

Example Products
→ Example Brand

Demo Products
→ Demo

The WooCommerce categories remain unchanged.

Configure the Default Brand

The ELSE / Default Result determines what happens when none of the Dynamic Attribute rules match.

You can choose:

Return empty value

Static value

or:

Source field

For example:

ELSE
→ Source field: Brand

allows the Dynamic Attribute to use its conditional rules first and then return the existing Brand attribute when none of them match.

Example: Conditional Rules with Existing Brand Fallback

You could configure:

Rule 1

IF
Child Category = Private Label

RESULT
Static value:
My Store

and:

ELSE

Source field:
Product Brand

The result is:

Private Label products
→ My Store

Other products
→ Existing Product Brand value

This is useful when only part of the catalog needs an overridden feed brand.

Use a Fixed Brand for Selected Products

A Dynamic Attribute can return a static brand name.

For example:

IF
Child Category = Own Brand

RESULT
Static value:
Deviking

The generated feed can then contain:

<brand>Deviking</brand>

without adding or modifying that value in the WooCommerce product itself.

Use Product Attributes as Conditions

Dynamic Attributes can also evaluate WooCommerce product attributes.

For example:

IF
Brand = Acme

RESULT
Static value:
ACME Corporation

This can be useful when the stored WooCommerce value and the required feed value use different terminology.

For simple one-to-one renaming, however, Value Map is usually easier.

Method 2: Normalize Existing Brand Names with Value Map

Suppose WooCommerce stores:

ACME LTD
Example Company Ltd.
Demo Industries Europe

while the destination expects:

Acme
Example
Demo Industries

Configure:

Output Field:
brand

Source:
Product Brand

Transform:
Value Map

Then enter:

ACME LTD=>Acme;
Example Company Ltd.=>Example;
Demo Industries Europe=>Demo Industries

The result becomes:

The original WooCommerce values remain unchanged.

Dynamic Attribute or Value Map?

Use Value Map when the requirement is a direct conversion:

ACME LTD
→ Acme

Example Company Ltd.
→ Example

Use a Dynamic Attribute when the brand depends on conditions:

IF Child Category = Own Brand
→ My Store

IF another condition matches
→ Another Brand

ELSE
→ Existing Product Brand

A practical rule is:

Existing brand field
→ Map the source directly

Primary + secondary brand fields
→ Use Fallback Source

Simple brand-name conversion
→ Use Value Map

Conditional brand assignment
→ Use Dynamic Attribute

Combining Source, Fallback and Value Map

You can also combine several Mapping features.

For example:

Output Field:
brand

Source:
Product Brand

Fallback Source:
Brand

Transform:
Value Map

The processing order is:

Source
→ Fallback if Source is empty
→ Transform
→ Prefix / Suffix

This means the plugin first finds the appropriate brand value and then applies the Value Map to the resolved result.

Example Combined Configuration

Suppose your store contains:

Product A
Product Brand: ACME LTD
Brand attribute: empty

and:

Product B
Product Brand: empty
Brand attribute: Example Company Ltd.

with:

ACME LTD=>Acme;
Example Company Ltd.=>Example

The final output becomes:

Product A
→ Acme

Product B
→ Example

This can normalize brand data even when the original values come from different sources.

Custom Brand Taxonomies

Deviking Product Feeds can expose supported custom product taxonomies as feed sources.

For example:

tax:product_brand

can resolve the term names assigned to a product from the product_brand taxonomy.

When the taxonomy exists on the site, it can normally be selected through the Source selector.

This makes it possible to use brand data created by WooCommerce configurations or extensions that store brands as taxonomy terms.

WooCommerce Brand Attributes

If your store uses a global WooCommerce attribute for brand, it may appear as an attribute source such as:

pa_brand

The advanced source syntax is:

attr:pa_brand

You can use this source directly:

Output Field:
brand

Source:
Brand

or as a fallback to another brand source.

Custom Brand Meta Fields

Some stores save brand information as product metadata.

Detected product and variation meta fields are available in the Source system.

For example:

meta:_brand

or another site-specific meta key.

If that field contains the required brand value, it can be mapped directly or used as a fallback source.

Brand Values and Variations

Brand information is usually stored on the parent variable product rather than separately on every variation.

If your variation feed requires parent product information, Deviking Product Feeds supports parent-source resolution using:

parent:<source>

For example, when appropriate for your configuration, a parent product source can be used so variation records receive information stored on the variable parent.

Always use Preview to confirm the resolved value for your particular brand source and variation structure.

Use One Dynamic Brand Across Multiple Feeds

A saved Dynamic Attribute becomes a reusable source.

For example:

Resolved Brand

can be selected in:

Marketplace XML
Distributor CSV
Advertising Feed
Custom XML Feed

This allows you to maintain conditional brand logic in one place instead of recreating it separately for each feed.

Different Brand Output per Feed

Each feed has its own Mapping.

Therefore one feed can use:

Output Field:
brand

while another uses:

Output Field:
manufacturer

Both can point to the same source:

Resolved Brand

For example:

<brand>Acme</brand>

in one feed and:

<manufacturer>Acme</manufacturer>

in another.

The source and output field name are independent.

Example: Complete Brand Resolution Setup

Suppose a store contains:

• a product_brand taxonomy for most products;
• a pa_brand attribute on older products;
• a private-label category that should always output My Store.

Create a Dynamic Attribute:

Dynamic Attribute:
Resolved Brand

Add:

Rule 1

IF
Child Category = Private Label

RESULT
Static value:
My Store

Then configure:

ELSE

Source field:
Product Brand

If your catalog does not require the category override, the simpler Mapping solution may instead be:

Output Field:
brand

Source:
Product Brand

Fallback Source:
Brand

This is usually preferable when brand selection is only based on whether the primary field is empty.

Keep Conditional Logic as Simple as Possible

Not every brand setup requires a Dynamic Attribute.

If your store already has:

Product Brand = Acme

simply map that source.

If brand can exist in two fields:

Source:
Product Brand

Fallback:
Brand

If existing brand names only need renaming:

Transform:
Value Map

Use Dynamic Attributes only when the correct brand depends on actual IF / ELSE conditions.

This keeps feeds easier to maintain.

Preview the Brand Output

After configuring the brand source:

1. Save the Dynamic Attribute if you created one.
2. Open the required feed.
3. Configure the brand or manufacturer Mapping row.
4. Save the feed.
5. Run Preview.
6. Check products using the primary brand source.
7. Check products using the fallback source.
8. Check products matching any Dynamic Attribute rules.
9. Check variation records if they are exported.
10. Run Validate Feed.
11. Use Save & Generate when the result is correct.

Recommended Brand Configuration

When brand already exists in your WooCommerce data:

Output Field:
brand

Source:
Product Brand

Fallback Source:
Brand

When brand names need normalization:

Output Field:
brand

Source:
Product Brand

Fallback Source:
Brand

Transform:
Value Map

When the brand must be derived conditionally:

Dynamic Attribute:
Resolved Brand

Rule 1:
IF Child Category = Private Label
→ Static value: My Store

ELSE:
→ Source field: Product Brand

Then map:

Output Field:
brand

Source:
Resolved Brand

Using the appropriate combination of Source, Fallback Source, Value Map, and Dynamic Attributes allows Deviking Product Feeds Pro to build a consistent brand field from the WooCommerce data already available in the store.