PIM, ERP and Shopware admin: who maintains what?

PIM, ERP and Shopware admin access the same products in many shops. Without clear responsibilities the ERP overwrites maintained texts, prices are changed in two places and nobody knows which state applies. This page shows a proven split of roles for Shopware and how PIM for Shopware secures the boundaries with external system protection, CSV, feeds and approval.

Key facts

Each field has one leading system, all others only read.
The ERP leads commercial data, the PIM sales content, the Shopware admin the shop operation.
The external system protection resets maintained texts when an interface overwrites them.
CSV and feeds are the exchange, approval is the checkpoint before going live.

Three systems, three jobs

The ERP is a retailer's commercial memory: product numbers, suppliers, purchase prices, stock levels. Its strength is the reliability of these figures, not maintaining sales texts in several languages. The PIM is responsible for the content that sells a product: texts, translations, meta data, properties, categories, images with alt texts, custom fields and variants. The Shopware admin remains the place for everything concerning the shop itself: sales channels, rules, shipping and payment methods, orders, shopping experiences and settings.

Problems almost always arise at the transitions. An interface sends all fields with every sync, texts included. An import script writes values for every variant separately and thus undermines inheritance. And because everyone can change everything in the admin, prices end up sometimes in the ERP, sometimes in the shop.

PIM, ERP and Shopware admin: the split of roles at a glance

The following split has proven itself in many shops. What matters is less the specific assignment than the principle that every field has exactly one leading system.

Data area	Leading system	Route to Shopware
Product number, EAN, stock	ERP	Interface or CSV import
Purchase and selling prices	ERP or PIM, depending on the process	Interface or bulk edit
Product name, description, meta data, translations	PIM	directly in Shopware, protected by the external system protection
Properties, categories, custom fields, images	PIM	directly in Shopware
Variants and their options	PIM	Variant generator
Sales channels, rules, shipping, payment	Shopware admin	Shopware settings
Data for marketplaces and price comparison sites	PIM	Feed generator

How PIM for Shopware secures the boundaries

One data set instead of syncing

The PIM works directly with the product data in Shopware. There is no second product data set that has to be synchronised with the shop. The plugin uses its own tables only for settings, snapshots, logs and approvals. Users with the PIM role "View" are redirected from the Shopware product list to the PIM automatically, as long as "Redirect standard product list to PIM" is active. This way product maintenance happens in one place.

External system protection for texts

If an ERP writes to product texts via a Shopware integration, the external system protection detects it. For the chosen languages it keeps a reference state of name, description, meta title, meta description and keywords per product number and resets deviating fields to it. You choose which integrations count as external. Edits in the PIM, on the other hand, refresh the reference state immediately. A log with CSV export shows which products were reset, useful for clarifying things with the operator of the interface.

CSV and feeds for exchange

Where no interface exists, CSV is the exchange. The import matches products by product number, EAN, manufacturer number or ID, and profiles store mapping and settings. In the change log, "Undo last import" takes back the last import. In the other direction the feed generator delivers product data as CSV, XML or JSON under its own URL with a token, for example for an ERP, price comparison sites or Google Shopping.

Approval as a checkpoint

With the approval workflow a product only goes online once an authorised person has approved it. Submitting and rejecting deactivate the product, approving activates it. Who may approve is set in the config matrix in the Approval tab.

Permissions and traceability

Who may open the PIM, create or delete products is controlled by the four roles of the permission group "StawPim (products)" in Shopware. Super admins fine-tune with feature switches whether normal users may, for example, import CSV, start bulk edits or delete products. Snapshots before every bulk edit and the change history make it traceable what was changed and when.

Step by step: define responsibilities

Collect fields: list which product fields come from which system today.
Choose the leading system: define exactly one system per field that may write.
Limit the interface: configure the ERP interface so that it only transfers its own fields, as far as it allows.
Protect texts: enable the protection in the config matrix in the "External systems" tab, choose languages, fields and integrations and set the reference state while the texts are correct.
Assign permissions: assign the PIM roles, enter super admins and switch off features normal users do not need.
Set up approval and exchange: enable the approval workflow if needed and set up feeds or CSV profiles for the other systems.

Reference first, then protection: only set the reference state of the external system protection when the texts in the shop are correct. If a text has already been overwritten from outside, the external text otherwise becomes the reference.

Use cases

ERP delivers raw texts: the interface creates new products, the PIM takes over texts and SEO, and the external system protection prevents them from being written back.
An agency maintains content: external editors work in the PIM, only internal users may approve.
Several marketplaces: one feed per channel from the PIM instead of separate exports in the ERP.
Supplier catalogues: import data via CSV, check it and activate it only after approval.

Frequently asked questions

Should I maintain product texts in the ERP or in the PIM?

Sales texts, translations and meta data belong in the PIM. The ERP supplies commercial data such as product number, EAN and stock.

What happens if the ERP overwrites maintained texts?

With the external system protection active, the PIM resets name, description, meta title, meta description and keywords of the protected languages to the reference state.

Does the PIM need its own product data set?

No. The PIM works directly with the product data in Shopware. It uses its own tables only for settings, snapshots, logs and approvals.

How do other systems get data from the PIM?

Via the feed generator as CSV, XML or JSON under a URL with a token, or via the CSV export with profiles.

Can I prevent colleagues from importing CSV?

Yes. Super admins switch off the feature switch "CSV import" for normal users in the config matrix.

External system protection in PIM for Shopware - settings and reference state
Protect Shopware texts from ERP overwrites - the guide on protection
What is a PIM for Shopware? The basics - a PIM without an extra system
Shopware product approval workflow - check before going live
Shopware user permissions for product data - roles and feature switches
Feed generator in PIM for Shopware: guide - feeds for other systems

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