Shopware product data in Excel: limits and alternative

Maintaining Shopware product data in Excel is everyday practice in many shops: export the data, edit it in the spreadsheet, import it again. The approach is familiar and ideal for some tasks. With ongoing maintenance, variants and several languages, however, it hits its limits. This page shows when Excel fits, where it gets stuck and how maintenance directly in PIM for Shopware adds to it.

Key points

Excel is strong with formulas, find and replace and exchange with suppliers or translation agencies.
Limits: the file is outdated from the moment of export, format errors only show up on import, variants and languages become confusing.
In the PIM you maintain data directly in the Shopware admin: filters, bulk edit with snapshot, variant matrix, translation.
Excel stays as a bridge: the PIM import reads .xlsx and .xls with mapping, validation and undo.

Shopware product data in Excel: how the route works

The classic process has three steps. First you export product data from Shopware, usually via the import/export module with a profile. Then you edit the file in Excel or another spreadsheet. Finally you import it again. For one-off tasks this works well, and many teams have known their spreadsheets for years.

What speaks for Excel

Familiar tool: almost everyone on the team can use Excel, without access to the Shopware admin.
Formulas and mass operations: calculate mark-ups, concatenate columns, find and replace across thousands of rows.
Overview: many products and fields side by side, sortable and filterable.
Exchange: suppliers, translation agencies and agencies work with spreadsheets.

Where product data in Excel hits its limits

Outdated state: the file is a snapshot. If someone changes a product in the admin between export and import, the re-import overwrites that change.
Format traps: umlauts and accents appear wrong depending on encoding, decimal separators get mixed up, Excel removes leading zeros and likes to show long numbers such as EANs in scientific notation.
Errors come late: whether a row fits only becomes clear on import, in the worst case only in the shop.
Variants and inheritance: the spreadsheet does not show whether an empty cell means "inherits from main product" or "missing".
Languages: several languages mean more columns or more files, and a swapped column is noticed late.
Undo and traceability: without your own backup there is no easy way back, and who changed what is not in any spreadsheet.

Excel route and PIM compared

Task	Export, Excel, re-import	Directly in the PIM
Select products	Filter in the spreadsheet, then import the file back	Custom filters with AND/OR, saved as a preset
Change prices	Formula per column	Bulk edit: percent, amount or purchase price plus mark-up
Variants	One row per variant, inheritance invisible	Variant matrix, inheritance visible as placeholder
Translations	Fill language columns by hand	Gap filter, DeepL or AI in one run
Way back	Own backup needed	Snapshot before every bulk edit

The alternative: maintenance directly in PIM for Shopware

The PIM works in the Shopware admin on current data. You filter the product list across many fields, edit stock, price, EAN, manufacturer number, weight and active status directly in the row and change large volumes via bulk edit. Before every run, a snapshot saves the previous values. You maintain variants in the matrix, translations with DeepL or AI, and the change history shows who changed what.

Excel as a bridge: the PIM CSV and Excel import

Excel does not have to disappear. The PIM import reads CSV, TSV, XML, DATANORM and Excel as .xlsx and .xls, for Excel the first worksheet; for this, the browser loads a reader library from the internet once. Columns are detected from the header row, every mapping can be changed, and a sample value is shown next to each column. Numbers with comma or point are recognised. The validation counts new, updated and skipped rows in advance, strict mode resets everything on errors, and "Undo last import" brings back the previous state. The export writes UTF-8 with BOM, semicolon and decimal comma can be selected, languages are separate columns. Tier prices and warranty fields are not CSV columns.

Typical process: from the Excel list to maintenance in the PIM

Import the supplier list: load the Excel file in the CSV window, map columns and save as a profile.
Validate: check warnings and skipped rows, then import.
Filter gaps: save products without description or image as a preset.
Complete in the PIM: texts with AI, properties and prices via bulk edit.
Export if needed: output exactly the filtered products as CSV for a translation agency or sales.

Video · 1:41 min.Bulk editSee the feature in action, with on-screen explanations.Watch video →

Frequently asked questions

Can the PIM import Excel files directly?

Yes, .xlsx and .xls. The first worksheet is read. For this, the browser loads a reader library from the internet.

Does the PIM export an Excel file?

The export is a CSV file in UTF-8 with BOM that Excel opens with umlauts intact. You choose delimiter and decimal separator to match your Excel.

When is Excel still the better choice?

For data from suppliers, for translations by external agencies and for one-off restructuring with formulas. For ongoing maintenance in a team, working directly in the PIM is safer.

What if an import writes wrong values?

"Undo last import" in the "Change log" tab resets the most recently imported changes. In addition, each import creates a snapshot unless switched off.

Can tier prices be maintained via Excel?

No. Tier prices are not CSV columns. You maintain them in the detail view or set them for many products in bulk edit.

Try PIM for Shopware

All licence models and terms are listed on the pricing page. Want to know up front whether the PIM fits your shop and your processes? Get in touch via the contact form - we answer personally.

View pricing