How the price_inherited Field Simplifies Variant Pricing Import in Shopware 6

Managing prices across parent and variant products is one of the recurring challenges in Shopware 6 catalogs, especially when dealing with numerous variations and frequent pricing updates. In many stores, variants unintentionally accumulate outdated, inconsistent, or manually modified prices that no longer align with the parent product’s intended pricing structure.

To solve this, the Improved Import & Export Tool for Shopware 6 introduces a new field: price_inherited. This feature helps merchants enforce clean, consistent pricing by ensuring that variant products automatically inherit pricing from their parent.

This article explains how price_inherited works, why it matters, and how to use it effectively.

What Is the price_inherited Field and Why It Matters

In Shopware 6, parent products serve as the primary source for product definitions, while variants can override specific attributes, including pricing. Over time, this leads to a common issue:

• Variants may hold outdated or incorrect prices
• Merchants have to manually edit each variant to reset pricing
• Price synchronization between parent and variants becomes difficult

The price_inherited field offers a clean solution:

• Reset variant-level prices
• Automatically inherit all prices from the parent product
• Consistently manage pricing rules across large product catalogues

This is especially important when:

• Migrating catalogs
• Replacing outdated price structures
• Running large discount campaigns
• Correcting catalog inconsistencies
• Standardizing pricing across regions or store views

Where the price_inherited Field Appears

The field is available during product import mapping: price_inherited

You simply add it as a column to your CSV file as part of your import job.

How to Use price_inherited in Your Import File

Accepted Values

The column supports the following values:

• 1 (recommended)
• true
• empty / not set → default (variant prices remain unchanged)

What It Does

When price_inherited=1 is set on a variant:

• Any custom prices on the variant are wiped
• The variant adopts all prices from the parent product
• Gross, net, and advanced price definitions follow the parent as well

This ensures full parent–variant pricing synchronization.

Example CSV Input for price_inherited

productNumber,name,price_inherited
PARENT-001,Parent Product,
VARIANT-001-RED,Red Variant,1
VARIANT-001-BLUE,Blue Variant,1

It results in the following outcome:

• PARENT-001 keeps its own price
• VARIANT-001-RED inherits the parent price
• VARIANT-001-BLUE inherits the parent price
• All previous prices on the variants are cleared

What price_inherited Does Not Do

⚠️ The field has no effect when applied to parent products. It only affects variants.

This prevents accidental overwriting of parent prices and ensures predictable behavior.

Why This Feature Is Important for Large Catalogs

1. Eliminates Price Drift Across Variants

Variants often get manually edited over time. With price_inherited, you can reset them systematically.

2. Makes Pricing Updates Significantly Faster

Instead of editing hundreds of variants:

• Update the parent price once
• Import CSV with price_inherited=1
• All variants instantly sync

3. Ensures Data Consistency in Multi-Store Environments

Especially helpful for:

• Multichannel setups
• Multi-region pricing
• Products with dozens of variant combinations

4. Simplifies Migration Workflows

When migrating from another platform, old variant-level prices often cause inconsistencies. This field lets you reset and standardize everything in one pass.

Best Practices for Using price_inherited

• Use it during catalog cleanup. A perfect tool for fixing inconsistent variant pricing accumulated over years.
• Use it after bulk updates. When applying new base prices to a parent, run an import that reverts variants to the parent pricing logic.
• Combine with advanced pricing. Ensure variant inheritance does not conflict with custom price tiers — or intentionally override them for uniform pricing.
• Use version-controlled CSVs. Always keep your pricing imports archived for traceability.

Common Mistakes and How to Avoid Them

• Setting price_inherited=1 on parent products
  Has no effect.
  Avoid unnecessary CSV entries for parent rows.
• Expecting inheritance without clearing old data
  Variants must have price_inherited defined during import for old prices to be removed.
• Forgetting to include productNumber
  Without a unique product identifier, Shopware cannot match the variant properly.
• Assuming this affects advanced price rules
  Advanced prices are inherited only if they are not defined at the variant level or if replaced.

Troubleshooting

Variant still shows the old price

• Confirm the variant row contains price_inherited=1
• Make sure no variant-level advanced pricing rules override it
• Check that the import job ran successfully without warnings

Variant price disappears completely

• Ensure the parent product has valid pricing defined
• Check VAT/tax configuration, as Shopware calculates missing values automatically

Wrong variant inherits pricing

• Confirm that the productNumber matches the correct variant SKU

Conclusion: A Simple Tool With Big Impact

The price_inherited field is a small but extremely powerful addition to Shopware’s import/export capabilities. It allows merchants to:

• Maintain consistent variant pricing
• Eliminate data discrepancies
• Save time on catalog maintenance
• Reset outdated variant price overrides
• Improve migration workflows

With just a single CSV column, you can standardize pricing across even the largest and most complex product catalogs — reliably and efficiently.

👉 Update your app today and experience seamless Shopware 6 product price updates.

🔧 Get the Improved Import & Export Tool for Shopware 6
💬 Contact our team for expert support and personalized import strategies