Answers in one click.

It is a central management interface for product data directly inside the Shopware administration. Instead of opening products one by one and editing field after field, the plugin enables bulk-edits, CSV import/export, variant generation and targeted filter workflows — with snapshot & revert for every operation.

Functionally it is a full PIM that closes the gap between Shopware's standard product management and external PIM systems like Akeneo or Pimcore — without an interface, without cloud, without a second platform.

For shops with approx. 200+ products, complex variant structures, multilingual content or regular mass updates. Typical use cases:

• Seasonal price adjustments across hundreds of products
• Supplier imports via CSV with custom fields
• Range changes with cross-selling bulk management
• Multilingual shops with translator workflow
• Configurable products with extensive variant matrices
• Agencies managing multiple shops with the same data structure

For smaller shops with manageable volumes, the ROI is lower — the standard Shopware management still works fine.

Probably not. The benefit comes with volume. From about 200 products onwards — or for multilingual shops with custom fields — the time savings become noticeably significant.

However, if your 50 products each have 30 variants, it pays off too — the variant generator and bulk-edit features quickly justify themselves there.

No. The plugin runs entirely locally in your Shopware installation. No data leaves the shop, no external API calls, no external dependencies.

All data remains in your Shopware database. You keep full data sovereignty.

Shopware 6.7 in the current version is fully supported. Compatible builds for older Shopware versions (6.5, 6.6) are available on request.

For a Shopware major update, plugin compatibility is generally caught up promptly — larger jumps are communicated in advance.

Yes. All standard Shopware product types are supported — including products with tiered prices, customer-group-specific prices, custom fields, properties, cross-selling and variants.

Shopware's B2B suite (with quotes, order approval etc.) is supported at the product data level; specific B2B suite workflows are not included in the plugin.

Yes. Visibilities, category assignments and sales-channel-specific fields are supported — both for filtering and bulk-edits. For example, you can select products that are active in sales channel A but inactive in sales channel B, and then perform changes only for one selection.

Fully bilingual: German (de-DE) and English (en-GB). The language matches your Shopware administration language. Additional languages can be added on request.

Via the Shopware Community Store with one click — same process as for any other Shopware plugin (details in the getting-started docs):

• Subscribe to the plugin in your Shopware account
• In the Shopware administration: Extensions → My account → Sync licences
• Download and install the plugin
• Activate the plugin

After activation, a new menu item PIM appears in the administration. On first launch, the config matrix is initialised with default values.

No. The plugin operates directly on existing Shopware product data. There is no separate database, no sync processes — all changes are immediately visible in the Shopware administration and storefront.

Important: You are working on real products. So before the first bulk operations, we recommend a backup or a test on the staging environment — even though the plugin brings its own safety net via snapshot & revert.

No. The plugin is a pure admin tool and changes nothing in templates or storefront code. There are no Twig overrides, no CSS modifications to the storefront and no changes to frontend routes.

Pure installation takes a few minutes. For the initial config matrix (defaults for SKU pattern, variant logic, permissions) plan 30–60 minutes — afterwards everything runs automatically.

A step-by-step guide can be found in the online documentation.

Standard Shopware 6.7 requirements are sufficient:

• PHP 8.2 or higher
• MySQL 8.0+ or MariaDB 10.4+
• At least 512 MB memory per PHP process (recommended for larger bulk operations)
• max_execution_time ≥ 300 seconds recommended for very large imports

The plugin automatically batches all operations in chunks, so even with tight server limits it works — but higher limits are more comfortable for very large data volumes.

Yes, all sales channels are correctly recognised. Filters and bulk-edits can be executed either globally or per sales channel — including with domain sharing or multiple languages per channel.

The plugin works exclusively on standard Shopware entities and uses official DAL and API paths. Conflicts with other plugins are therefore very unlikely.

Known compatible: common theme plugins, payment and shipping plugins, SEO tools, marketplace integrations. If a conflict does occur, please submit a ticket via Shopware Store support.

The five main areas:

• Bulk-edit with snapshot & revert — edit hundreds of products at once, every change reversible
• CSV import/export — custom fields per language, categories via tree resolution, tiered prices, cross-selling
• Variant generator — automatic creation with patterns for SKU and name, optional main variant setting
• Filter & selection — complex filters incl. notContains with parent products, saveable as preset
• Config matrix — central defaults and permissions per user group

In addition there are many smaller helpers: audit log, edit-lock for multi-user, snapshot management, cache warming and more.

Yes. Product images can be reordered via drag-and-drop, cover images set, alt texts and titles edited. With "Cover first" enabled, the cover is automatically sorted to the front and locked against accidental moving.

The plugin uses native Shopware media management — no duplicate data storage. Images uploaded in normal Shopware administration are immediately available in the PIM and vice versa.

Yes. You can add a new cross-selling group to hundreds of products at once — either with a dynamic product group (stream) or with a fixed product list. Existing cross-selling entries remain unchanged.

Example: "Add a cross-selling group 'Matching accessories' with the stream care products to all products in the Shoes category, sorted by price, limited to 12 items."

Yes. Every change is logged with user, timestamp and affected fields. The log is filterable by user, period, product and change type. Export as CSV is possible.

For bulk operations, the entire process is stored as a single log entity, so the log remains clear even with frequent bulk updates.

A central settings interface where you define standards for all bulk operations:

• SKU pattern (e.g. {parent}-{option})
• Name pattern for variants (e.g. {parentName} {options})
• Automatic property assignment
• Main variant pre-selection (first variant / lowest SKU)
• Listing behaviour (cover first, default view)
• Cross-selling defaults (sorting, limit)
• Permissions per user group
• Approval workflow on/off

These defaults then automatically apply to all bulk operations — but can be overridden per operation if needed.

Yes, all custom field sets from Shopware are automatically recognised and can be used in filters, bulk-edit and CSV export — including all custom field types: text, number, boolean, single-/multi-select, date, entity-select, media.

Yes. Individual or multiple products can be duplicated — optionally with or without variants, with or without images, with or without custom fields. The copied products automatically get new SKUs according to the pattern.

You select any number of products in the listing view and then change together (details: bulk-edit docs):

• Prices — absolute, percentage or as markup/discount, with or without VAT
• Pseudo prices (RRP)
• Tiered prices (complete or additive)
• Stock — set, add, subtract
• Categories — add, remove, replace
• Main category
• Tags
• Properties
• Custom fields of all types
• Cross-selling groups
• Visibility per sales channel
• Active status
• EAN, manufacturer, manufacturer number
• Variant generation across multiple parent products

Before every operation, a snapshot of the affected fields is automatically created (more in the bulk-edit docs). Via the snapshot management you can completely revert every change with one click — even days later.

Example: You raise prices of 500 products by 5%. After an hour you realise the calculation was wrong. In snapshot management you select the corresponding entry and click "Revert" — all 500 prices are back to their original values.

Snapshots are stored permanently until you manually delete them. You can view, export or selectively apply them per operation.

Optionally an automatic cleanup after X days can be enabled in the config matrix — default is "keep indefinitely".

Yes, this is configurable. Per operation you decide whether:

• Only the selected parents are changed
• Parents + all variants are changed
• Only the variants of the selected parents are changed

For certain fields (e.g. tiered prices) there are special options like "copy to variants" or "aggregate from variant values".

Yes. Before every operation a summary is shown: how many products (and variants) are affected, which fields are changed and what the new values look like. Only after confirmation is the change executed.

Yes. During the progress bar you can click "Cancel" at any time. Already changed products remain changed (but can be reverted via the snapshot), unstarted chunks are skipped.

The CSV format covers practically all relevant product data (full column list in the CSV documentation):

• Master data: SKU, name, description, meta data
• Prices: gross, net, pseudo price (RRP), list price
• Tiered prices incl. customer groups
• Stock, delivery time, EAN, manufacturer, manufacturer number
• Categories (incl. main category) with tree resolution
• Properties
• Custom fields of all types, per language
• Cross-selling (streams or product lists)
• Visibilities per sales channel
• Tags, SEO URLs, active status

Yes, both for import and export (see translation workflow in the CSV docs). The CSV structure supports custom fields per language with the format cf_<name>__<langCode>, so external translators can work without admin access.

Example: cf_care_instructions__de-DE, cf_care_instructions__en-GB, cf_care_instructions__fr-FR — all three columns in the same CSV.

Practically unlimited. The import runs chunked — rows are processed in batches of 50–100, so CSVs with 50,000 rows can be imported without hitting memory or timeout limits.

Recommendation: For very large imports (> 10,000 rows) test on a staging environment and raise PHP memory to at least 1 GB.

Standard CSV with the following configuration options:

• Delimiter: comma, semicolon, tab (auto-detected)
• Encoding: UTF-8 (with or without BOM), Windows-1252
• Line ending: LF, CRLF
• Quote character: " or ' (auto)
• Excel-export-compatible (semicolon + UTF-8 BOM)

Yes, in two stages:

• Pre-check: Before import, the file is checked for missing required fields, invalid values, duplicate SKUs, unknown custom fields.
• Row-level: During import, errors per row are logged — the import still continues for all valid rows. At the end there is a detailed report.

Yes. Column mappings, default values and validation rules can be saved as import profiles and re-applied with one click. This is especially useful for regular supplier imports with always the same CSV structure.

Yes, via URL reference. The CSV contains columns with image URLs; the import downloads the images, stores them in Shopware media management and links them to the product. Alt texts and order are also manageable via CSV.

You select properties and their options, the plugin generates all combinations from them and creates the variants (step-by-step: variants docs) — including:

• Correct linking to the parent product
• Taking over prices, stock, custom fields (configurable)
• Automatic SKUs by pattern (e.g. {parent}-{option1}-{option2})
• Automatic variant names by pattern (e.g. {parentName} {options})
• Optional automatic selection of a main variant for the storefront detail page

Existing variants are recognised and can either be skipped or supplemented.

After variant generation, the plugin can automatically set one of the new variants as the visible main variant (mainVariantId) on the storefront detail page. Two strategies are available:

• First generated variant — the variant that came first in click order
• Lowest SKU — all new variants are sorted alphabetically by SKU, the smallest becomes the main variant

Optionally the parent product itself can be hidden from the listing (displayParent: false), so that only variants appear in the shop.

Yes, via bulk-edit. You select multiple parents in the list, open the variant generator in the "Variants" tab and configure properties and options there. When applied, the corresponding variants are created for each parent — with the respective parent-specific data as basis.

Yes, optionally. In the config matrix you can set that, when creating a variant, the selected options are also automatically assigned as properties — so they appear in the storefront filter without you having to manage them twice.

The generator shows a live preview of all combinations — with SKUs and names according to the configured patterns. You immediately see which combinations already exist and which would be newly created.

Yes. The generator has a "delete mode" that removes variants by specific criteria (e.g. "variants without stock", "variants older than X") in one operation. Also with preview and snapshot here.

Yes, with complex filters (all filter types in the listing docs):

• Text: contains, does not contain, starts with, ends with, is empty, is not empty
• Numbers: equals, not equals, greater, smaller, between
• Boolean: yes / no
• Category membership (incl. sub-categories)
• Manufacturer, tags, properties
• With / without variants, with / without cover image, with / without description
• Custom field values (all types)
• Visibility per sales channel
• Created at / changed at (periods)

Filters can be combined via AND/OR.

Yes, correctly — which is a known weakness in the Shopware standard. The notContains filter in the PIM plugin also returns parent products whose variants meet the filter (or don't meet it).

Example: "All products whose SKU does not contain -EUR" — works correctly even when variants have different suffixes.

Yes, common filter combinations can be saved as presets and recalled with one click. Presets can be created private (only for you) or shared (for all users).

In the filter modal, filters are defined per field; multiple filters are linked with AND by default. Via the AND/OR switch in each filter row, more complex logic can be built, e.g. "Category Shoes AND (Price < 100 OR Tag Sale)".

Via the view toggle: "Parents only", "Variants only" or "All". With "Limit to filter" active, the selection also applies to bulk operations — e.g. a price change then only applies to the filtered items, not all products in the selection.

Yes. In the config matrix, permissions can be set granularly per user group:

• View / create / delete products
• Change active status
• Execute bulk-edits
• Manage / restore snapshots
• Use CSV import / export
• View / edit translations
• View audit log
• View / change config matrix
• Control approval workflow

Yes, optional. Changes can go through an approval workflow before going live — definable per user group. Typical scenario: translators may change texts, but an editor must approve before the texts go live in the shop.

Yes. The plugin has an edit-lock per product — when someone is editing a product, other users see a notice and can view the product read-only. The lock is automatically released when the editor leaves the product or after a timeout.

For bulk operations, locked products are automatically skipped and listed in the report.

Yes. Specific users can be entered as "PIM super-admins" in the config matrix — they have full access to all PIM features regardless of their Shopware permissions. Useful for the main responsible people or the agency team.

In the storefront: not at all. The plugin is purely active in the administration and delivers no frontend assets, no Twig extensions, no subscribers for storefront events.

In the admin itself, bulk operations are implemented in batch chunks (50–100 products at once), so even large shops don't run into timeouts.

Tested in practice up to 10,000 products in one operation. The batch logic chunks automatically, a progress bar shows the status, and server limits are automatically compensated.

For even larger volumes (50,000+) the CSV route is recommended — the import then runs in the background and doesn't block the admin.

All data remains in your Shopware installation. There are:

• No external connections
• No telemetry
• No data transmission to third parties
• No cloud dependencies
• No tracking cookies or pixels

Only for licence validation does the plugin occasionally communicate with the Shopware account server — that's Shopware standard for all paid plugins.

The plugin follows Shopware major releases with compatible updates. If a version jump is once blocked, this is communicated in the store beforehand. Patch and minor updates of Shopware are generally unproblematic and the plugin continues running directly.

The plugin creates its own tables for snapshots, audit log and configuration (all with prefix staw_pim_). Shopware product tables are accessed read-only, and write accesses go exclusively through official DAL and API paths — no direct SQL manipulation.

On uninstall, the plugin-owned tables are removed. Your product data remains unchanged in Shopware. Snapshots and audit log are lost — so export them before uninstall if needed.

Note: On pure deactivation (instead of uninstall), all plugin data is preserved and immediately available again on reactivation.

Yes. The plugin processes exclusively product data — no personal data of customers. The audit log stores usernames of plugin users (employees); these are part of internal Shopware user management and are subject to normal employee data protection.

€179.99 per month — subscription model, cancellable monthly.

The price refers to one Shopware licence / domain. For multiple shops, contact us for volume conditions.

• Full access to all features
• Regular updates with new features
• Bugfixes and security updates
• Compatibility for new Shopware versions
• Technical support via the Shopware Community Store
• Access to online documentation

Yes. The Shopware Community Store offers the usual 30-day trial. You can test all features in full before the subscription starts. No costs during the trial.

Per Shopware licence / domain — as with all Shopware plugins. If you run multiple shops with separate Shopware licences, you need a separate subscription for each.

Yes. There is no minimum term beyond the current month. Cancellation is done directly in the Shopware account.

The plugin stays installed, but features are deactivated after licence expiry. Your product data in Shopware naturally remains — it sits in the standard Shopware database anyway, not in the plugin.

Snapshots and audit log also remain in the DB. On later reactivation of the subscription, all data is immediately available again.

On request from Stone & Water — depending on the number of licences. Especially for agencies with multiple customer shops there are individual conditions. Contact: stoneandwater.online/contact

The detailed documentation is available at /dokumentation.html — with step-by-step guides, screenshots and concrete examples for all features.

The docs are regularly updated together with the plugin.

Via the Shopware Community Store (standard support channel) and directly with Stone & Water at stoneandwater.online/contact.

For detailed bug reports it's helpful if you include screenshots or a brief description of the steps that lead to the problem.

Tickets are typically answered within 24 hours on business days. Critical bugs (e.g. data loss, complete functional outages) are handled with priority.

Yes. Tooltips and notes are built in at many places, explaining directly in context what each option does. Hover over the small info icons gives additional explanations.

Feature requests can be submitted directly to Stone & Water. Useful extensions that benefit other shops are usually incorporated in one of the next versions.

For very specific requirements, custom development can also be offered — as additional service or as customer-specific extension.

Stone & Water is a Shopware agency — custom developments around the PIM (own custom field handlers, import mappings for special suppliers, ERP integrations, own pattern engines) are possible as additional service.

Enquiry via stoneandwater.online/contact — we discuss the scope and make an offer.

Yes, on request. We offer online training for teams — typically 1–2 hours for an introduction to the most important workflows, more for in-depth topics like CSV structures or complex variant setups. Enquiry via the contact form.

Via the CSV import function, product data can be imported from any system that can export CSV — Akeneo, Pimcore, OXID, Magento and others. The mapping logic is flexible and also supports non-Shopware-standard fields via the custom field concept.

Akeneo and Pimcore are standalone PIM systems with their own interface and data storage, connected to Shopware via an interface.

This plugin lives directly inside Shopware — no second platform, no synchronisation, no interface maintenance.

For pure Shopware shops: faster, cheaper and without interface complexity.

For multi-channel scenarios (shop + marketplaces + print catalogue + ERP), where a central PIM serves different channels: standalone PIMs still make sense.

No — it extends them. Standard product management in Shopware continues to work in parallel. The plugin is the more efficient alternative for bulk operations and multilingual workflows; single product editing still works in the standard interface.

If your ERP provides data via CSV or API, you can use the CSV import workflow — also automated via Shopware console or scheduled tasks.

Direct ERP integrations (DATEV, SAP, Microsoft Dynamics, Sage, JTL and others) are possible as custom development via Stone & Water — enquiry via the contact form.

Technically yes — as long as the other plugins also work via the official Shopware APIs. In practice, a combination is usually not necessary: our plugin covers the classic PIM functional scope. For special cases (e.g. an additional plugin for print catalogue generation), please briefly test beforehand.