PIM for Shopware 6: the Shopware PIM plugin right in the admin.

Strong on longer, nuanced texts

Own API key, own model choice, own tone default - completely independent.

Models: Sonnet 5 · Sonnet 4.6 · Opus 4.8 · Fable 5 · Haiku 4.5

Fast, cost-effective generation

Proven for large volumes. Own key/model/tone configuration here too. Connection test directly in the admin.

Models: GPT-5.6 Sol · GPT-5.6 Terra · GPT-5.6 Luna · GPT-5.5 · GPT-5.4 mini · GPT-5.4 nano

Strong European models

Good value, own key/model/tone default, connection test in the admin.

Models: Mistral Large 3 · Medium 3.5 · Small 4

Very fast flash models

Large context windows, own key/model/tone default, connection test in the admin.

Models: Gemini 3.1 Pro · 3.5 Flash · 3.1 Flash-Lite

All configurable in parallel

When several providers are active, pick the right one per call in the generator modal - Claude for the demanding main description, a flash model for fast meta data, for example.

Individual texts per channel & language

Each channel-language combination gets unique texts. Or generate once and write the same text to all selected combinations - you decide per run.

Five style templates

Professional, casual-modern, premium/luxury, technical-factual or emotional-promotional. Set a default per provider, override per generation.

You control what the AI sees

Which product data flows into the prompt? Name, manufacturer, properties, category, price - selectable via chip. Plus own keywords for SEO focus.

AI in bulk too

In bulk edit, ChatGPT and Claude generate texts for many products at once and DeepL translates - each with its own switch in the config matrix. The number of parallel requests is adjustable for ChatGPT and Claude. Mistral and Gemini are not available there.

Review first, then apply

In the detail view, generated texts appear in a preview first and are only saved with "Apply texts". In bulk edit the AI writes directly into the selected fields; a snapshot saves the previous state beforehand.

Master prompt for every provider

Set salutation, brand spelling, mandatory information or forbidden phrasings once - the instruction travels with every request, in the detail view as well as in bulk edit and regardless of the provider.

Targets per field in words and characters

Product name 120 characters, SEO title 60, meta description 155, description 250 words - the lengths search engines display in full. The values also drive the token budget, so the response no longer breaks off mid-JSON.

Copy from the default language

A channel with its own language but no own texts? Name, description, meta fields and keywords can be copied over from the default language - only then does the AI have something to rewrite in that language. By default only empty fields are filled.

The product name as well

Besides description, meta title, meta description and keywords, the AI now also writes the product name - for ChatGPT as well as Claude. Not preselected, so existing names are not overwritten by accident.

Saved in batches instead of product by product

Generated texts are collected and saved in blocks: for 2000 products the number of save operations drops from over 2000 to around 40. On request limits the run waits and retries automatically.

What's bulk-editable

• Status, top seller, closeout, free shipping, EAN, release date
• Manufacturer, essential characteristics, warranty, categories, tags, properties
• Visibility per sales channel, cross-selling, tier row from 1
• Sales price: fixed price, raise or lower by % or €, purchase price + % or purchase price + €
• Pseudo price (list price), link, unlink or prescribe tier prices
• Stock, tax class, order quantities and purchase steps
• Weight, dimensions, delivery time, restock time, packaging unit
• Base price (content quantity + base unit), product unit
• Meta title, meta description and SEO URL as a template, main category per channel, canonical variant
• Custom fields (also per language)
• AI & texts, generate variants, clear fields, delete

From parent to all variants

In bulk edit, "Transfer to variants" copies the price tiers and cross-selling of the main product to all variants, joined by "Visibility to variants" and "Properties to variants". In the detail view you pick price, pseudo price, purchase price, stock, delivery time, weight & dimensions, EAN and further fields individually.

Before-state + one-click revert

By default every bulk edit creates a snapshot of the state before. It is managed and restored in the config matrix, tab Snapshots.

• Kept for 90 days by default, at most 50 snapshots, both adjustable
• Diff per product and field: snapshot against the current state in the shop
• Not restorable: generated or deleted variants and deleted products

Progress in real time

Even with 500+ products, no black-box feeling: live counter, phase indicator (snapshot / apply), ETA calculation and cancel button mid-operation.

Source: selection or preset

The bulk operation is based on a manual selection or a saved preset. The article count with products and variants is shown right in the dialog.

• From current selection: selected rows
• From preset: all filter-matching products, up to 500 by default, adjustable to unlimited
• Variants according to "Include variants by default"

Complete overview of all active filters

When you choose a preset as the source, its filters appear as readable chips: for example status, stock, with/without variants, manufacturer, categories, dynamic product group, sales channel, tag, tax, delivery time, price and weight. IDs are resolved to clear names. "No filters active" is marked red as a warning.

First the overview, then the run

With "Confirmation before applying" (default) the dialog lists all planned changes before the start. Delete and clear fields always ask for confirmation. With "Automatically revert on cancel" the snapshot takes back changes already written.

Required-field errors as clickable modal

Save with empty required fields: instead of a wall of warning banners, a modal opens listing all errors. Clicking an error jumps directly to the relevant section - it expands, the field is briefly highlighted with an indigo outline.

Add property translations on the spot

Options without a translation are marked and counted - the pencil icon lets you enter the translated name immediately, several languages at once, without leaving the Shopware property catalogue. The check runs against the languages of the assigned sales channels.

Also assign to the master product

A checkbox additionally writes the selected properties to the parent product of the affected variants, and removes them there in removal mode. That way master product and variants never drift apart.

Clear custom fields selectively

Besides master data, SEO and link fields, custom fields can be cleared as well - per language and with a snapshot, so it stays reversible. Deliberately selected individually rather than with a select-all switch.

Maintain the GARAN label

Warranty period in months and retailer confirmation as their own section in the master data, inheritable per variant and settable in bulk edit. Shopware has the fields from 6.7.14; in older installations the section is visible but locked.

One search for properties and options

Instead of two separate search fields: a single search at the top filters properties and options simultaneously. Type "red" and all groups with the option "red" remain visible while matches on the right are highlighted.

SKU + name as separate accordions

Instead of raw inputs side by side: two dedicated accordions. Collapsed they show the current pattern as a chip; expanded the input appears with clickable variable chips.

• Variables: {parentNumber}, {firstVariantNumber}, {parentName}, {options}, {option1}-{option3}, {group1}, {group2}, {counter}
• Live preview of the first 5 combinations
• Config matrix as default, override per operation

Prices, stock and status in one table

Instead of opening variants one by one: all of them in a matrix. From two property groups on, the rows show the options of one property (e.g. colour), the columns those of the other (e.g. size). In each cell you edit the selected value directly.

• Cell value selectable: price, stock or active
• Default view and default value in the config matrix
• Up to 500 variants (default, adjustable)

Variant deletion with order check

You delete variants of many articles in bulk edit, tab "Generate variants". The plugin checks whether orders refer to the variants.

• "Only without orders" (recommended): variants with orders are skipped
• "Delete ALL variants": including variants with orders
• Preview with the number of deleted and protected variants

Transfer properties and images to variants

As soon as a variant has an own value it inherits nothing in that field - which is why fewer properties or no image at all sometimes appear in the storefront. Two buttons add the missing properties, or create own image assignments including the cover image.

Spot deviations immediately

Properties that only sit on variants are highlighted in orange, affected groups get a dot and the counter bar states the number. Groups without "display on product detail page" are marked "not in storefront".

Choose inheritance when duplicating

When duplicating a variant product, a dialog asks which fields the variants should inherit: images, name, price, weight, EAN. The new master product receives its own correct SEO URL instead of pointing at the original through its main variant.

Parents + variants in one listing

Display in the format Products: 153 (Variants: 543) - separated, above and below the pagination.

• Expand variants inline directly in the table
• Badge with variant count per product
• Lazy-loading: variants load only when expanded

Edit directly in the row

Stock, price, EAN, manufacturer number and weight edit directly in the listing row - also for variants. Click the value, change, done.

• Active switch per product
• Saved when leaving the field, with a message on success or error
• Inherited values of a variant highlighted

Master data in a modal - no detail switch

A click on a variant in the listing opens a compact modal with master data, prices, availability and SEO. Ideal for maintaining variants one after another.

• Prices (gross/net), purchase price, pseudo price, omnibus price
• Stock, closeout, free shipping, delivery time
• Fields selectable in the config matrix (tab Variants)

Filters with AND / OR

Combine arbitrary filter conditions. Also across variant fields - search automatically traverses parent and child fields.

• Text and number 8 operators each (e.g. contains, starts with, greater/less, is empty), yes/no 2
• AND or OR per filter set
• Variant-aware: also matches parents with matching variants

Save and load filter presets

Define frequent filter combinations once, restore with a click - perfect for recurring maintenance.

• Stored in the shop database, available to all users
• Optionally shown as a quick filter right above the list
• Source for bulk edit, feeds and category assignment

Native list virtualisation

For large lists (1000+) the browser only renders visible rows - via content-visibility: auto. Smoother scrolling without UI change.

• Row count: 10 / 25 / 50 / 100
• Variants load only when expanded
• Quick-scroll-to-top button

Find missing translations precisely

The "translation missing" filter is resolved server-side against exactly the selected language - with the variants name missing, description missing or both. The filter chip names the language checked, for example "Translation: name missing (Alpendampf DE)".

Inheritance is taken into account

If a text only exists on the parent language it still applies in the storefront. Filter and completeness therefore check the whole language chain, and completeness follows the language of the selected sales channel instead of the system language.

Leaner queries for variants

When expanding, only the fields the list actually shows are loaded, and completeness arrives ready-made from the server - following the same rule as the filter. Description and meta texts of every variant no longer travel to the admin.

Built-in export profiles

Predefined column sets for typical use cases - usable immediately, adjustable, saveable as new profile.

• Master data, prices & stock, SEO, images
• Translations, variants, full export
• Own profiles in the shop database, for all users

Each field as its own column

Custom fields get their own column in the export (cf_myField), language-specific cf_myField__en_GB. On import they are recognised directly - no more JSON blob.

Unit as readable name instead of UUID

Column "Product unit (name)" exports "Litre" or "Kilogramm" instead of UUID. On import the name is automatically resolved to the correct Shopware unit ID - Excel-friendly.

By SKU or EAN

For fields normally requiring a UUID (parentId, mainVariantId): UUID, SKU or EAN possible, for variants additionally the column parentProductNumber. Lookups are cached.

Batch sync with progress

Everything via the Shopware sync API in batches, with batch size and parallel image uploads adjustable in the config matrix. With progress per phase and estimated remaining time.

• Match by SKU / ID / EAN / manufacturer number
• Create new products OR update existing
• Custom field JSON is merged, not overwritten

Import and export via feature switches

Super admins can always import, regular users as long as the feature switch "CSV import" is on (default). Export has its own switch "CSV export"; there are no separate Shopware permissions for either.

Google Shopping, portals, ERP

Typical consumers are Google Shopping, idealo or Billiger.de, an ERP system or an analytics pipeline. The URL is tokenised - without the token nobody sees anything.

From a template or your own profile

Built-in templates for master data, prices & stock, SEO, images, translations, variants and full export create profile, feed and token in one click. Alternatively an existing export profile is activated as a feed directly.

Filter templates instead of checkboxes

Instead of simple checkboxes the feed uses a saved filter template - the same one you use in the listing and in bulk edit. The feed filters like the product overview; under "Applied in the feed" the editor shows which criteria take effect.

What does not apply in a feed

Only the approval status and "RRP invalid" cannot be mapped server-side. If a template contains these criteria, the feed returns more products than the filtered list.

One profile, many consumers

Any number of feeds can be created for the same profile - for example a "master data" profile as the basis for several feeds with different filter templates per portal.

CSV, XML and JSON

The feed URL follows the pattern /staw-pim/export/{token}; the format is set in the feed. For shop URLs that redirect there is the domain-independent route /api/staw-pim/export/{token}. Character set, BOM and decimal separator are adjustable.

Streaming instead of a memory mountain

Output runs as DBAL streaming in batches of 2000 with keyset pagination instead of LIMIT/OFFSET, plus gzip over HTTP and a file mode for very large catalogues.

Live hit count and token change

The product count is calculated live in the editor. One click creates a new token and invalidates the old URL - useful when a link has leaked or partner access should end.

Per sales channel and language

The tree is built per channel from the navigation root, loaded directly through the category repository - no separate endpoint, no separate page. For regular users it is controlled by the feature switch "Manage categories".

Have descriptions and meta fields written

An "AI texts" button generates description, meta title, meta description and keywords - across all four providers, with tone selection and a free field for further instructions. Switches for "include subcategories" and "overwrite existing texts".

Individually or across the whole tree

"Translate" sits as its own action next to the AI texts and transfers the fields from source to target language, via DeepL or an AI provider. With "select all", AI texts and translations run as a bulk action across every marked category.

Copy from default language

When a channel gets its own language, no own texts exist there at first. The bulk action copies name, description and meta fields from the default language - with a progress bar, and existing own texts stay untouched.

Dynamic group or preset

Which products sit in the category is controlled by two clearly separated options: a Shopware product stream, or a StawPim preset with a live hit count. In preset mode the resolved products are assigned permanently; zero hits deliberately do not empty the category.

Slug per channel and language

The SEO URL can be set per channel and language. The old URL stays as a 301, the new one becomes canonical; an empty field reverts to the Shopware default.

Category image with alt text

Cover from the media library or by upload, with preview and language-specific alt text - so category pages also count in image search.

Multi-select in the tree with history

Categories can be multi-selected by checkbox and set active or inactive together, and shown or hidden in the navigation. A named snapshot is created before every action; a "history" button lists them with an audit log and restores them.

Score per language

The percentage per category counts only the own texts of the selected language - matching the form next to it. That shows immediately where nothing has been maintained in a channel language.

CSV and JSON backup

The complete tree of the selected channel can be exported as CSV including custom field columns and read back in - the parent category through the parentPath column. A JSON backup additionally secures all languages, custom fields and IDs.

Critical stock levels at a glance

Stock status and low stock appear right on the PIM start page, without building a filter first.

Top issues by severity

The biggest gaps in the catalogue come first, such as products without a description. You fix what is most visible in the shop first.

From issue to filtered list

One click on an issue opens the product list with exactly the affected items, including a jump into editing.

Add missing texts with AI

A missing description is created directly with AI text generation and saved to the product.

Completeness across the whole catalogue

Items without an image, without a description or with incomplete meta data become visible before customers notice.

Every fixed gap counts immediately

Once an issue is fixed, the number on the dashboard drops right away. Maintenance rounds become measurable and the team sees what is done.

Submit, approve, reject

A product is submitted for approval and then approved or rejected. Submitting and rejecting deactivate the product, approving activates it. The typical case: after a mass import nothing goes live before someone has looked at it.

A signal to the team

There is also the status "in progress", which editors set themselves - a hint that someone is currently working on the product. That keeps two people from doing the same round of work twice.

Badge, filter and indicator

The detail view shows a status badge with a button to set it, the product list a coloured status indicator and its own filter. That makes it easy to filter for everything still waiting for approval.

Approval statistics

The settings show statistics on the approval state, with "in progress" counted in. How much is still open is visible at a glance.

Approvals in batches

Multiple approvals run through a dedicated batch endpoint with one request per 200 products - so even a batch of several thousand articles stays quick.

Who may approve is configurable

Approving and rejecting are allowed for the users entered under "Approval authorized users" in the config matrix, tab Approval, and for all PIM super admins. Maintaining and approving can therefore be split between different people.

Every decision in the audit log

Submitting, approving and rejecting land in the audit log with user name and timestamp - so you can look up who approved what and when.

You decide what is visible

Per field you decide whether it is visible in the detail and variant views and whether it is required; the quickview fields are chosen in the tab Variants. Fields Shopware requires anyway are marked as required and cannot be switched off.

Set the section order freely

Master data, prices, media, SEO, properties, cross-selling: you set the order in the product detail view in the tab Products with "Move up" and "Move down", and separately for the variant view in the tab Variants.

Switch gross and net individually

All four price types can be shown or hidden independently for gross and net, separately for main products and variants: selling price, purchase price, list price/RRP and the 30-day best price under Omnibus. Pure gross, pure net or mixed.

Two generators or the Shopware standard

Either the canonical custom field system with token patterns, whose URLs survive every reindex, or the Shopware standard mode, in which the native SEO URL is editable right in the PIM - controllable separately for product detail, variant modal and quickview.

Release functions selectively

In the tab PIM super admin you switch 14 functions on and off for regular users, among them creating and duplicating products, bulk edits, deleting, CSV import and export, feed generator, generating variants, managing categories and transferring to variants. Super admins always see everything.

Custom columns from any field

Besides the standard columns you create your own - the source is a master data field or any custom field, optionally sortable through the DAL path. Date and yes/no values are formatted automatically.

Ctrl+K across all tabs

Ctrl+K (Mac: ⌘+K) jumps into the quick search across every tab of the config page, with a match counter per tab. Enter and Shift+Enter or the previous and next buttons move from hit to hit.

One shared view for the team

Column selection, page size, filter presets, tone and all other settings apply shop-wide to all users. Differences between users are handled by the super admin list and the feature switches.

Errors that jump to the spot

If something is missing on save, a modal opens with all errors instead of a wall of banners. One click jumps to the affected section, expands it and highlights the field briefly.

Change history per product

Creating, saving in the detail view, variant and media changes and every approval step land in the tab "Changes" with action, user name and timestamp. Kept for 90 days by default, at most 100 entries per product.

Roles, super admins and feature switches

Four Shopware roles (view, edit, create, delete) control access. For all users without super admin status you switch off 14 functions individually, such as bulk edits, CSV import and export, deleting, snapshots and change history.

One-click restore

In the config matrix, tab Snapshots, you compare a snapshot with the current state and restore it with one click - all products of the run return to the state before the operation.