Description
Pimcore Shopware 6 Connector is a Pimcore bundle that links Pimcore data with a Shopware 6 store. It moves catalog data both ways over the Shopware Admin API.
This Pimcore Shopware integration adds import and export screens inside Pimcore Studio. Admins pick a saved credential, choose an entity, and start the run from one screen.
Each synchronization run creates a job that reads records, builds payloads, and writes data to Shopware in batches while updating read and write counts.
Catalog data is created as real records in Shopware, with categories preserving parent order, variants retaining option values, and images uploaded as Shopware media files.
Admins set the field mapping in the user interface, not in code. They pair each Shopware field with a Pimcore field once, and both directions then use that same map.
Additionally, if you want to translate a Pimcore catalog before you send it to a store, then check Pimcore DeepL Translation Connector.
Highlighted Features of Pimcore Shopware 6 Connector
Two-Way Catalog Sync
Send categories, products, and attributes to Shopware 6, and pull customer and order records back into Pimcore.
Shopware Admin API Transport
The connector reads data through the Shopware search endpoint and writes it through the Sync API in batches to handle large data runs efficiently.
Dynamic Field Mapping
Map each Shopware field to a Pimcore field from the screen. One saved map drives both import and export.
Variant Product Support
Export a parent product with its property groups, then each child variant with its own number and images.
Background Job Engine
Jobs run through the Symfony Messenger queue, so a long catalog run never blocks the Pimcore screen.
Duplicate-Free Re-Runs
Each record carries a fixed Shopware id built from its Pimcore id, so a repeat run updates the same row.
Image and Media Sync
Pimcore assets upload as Shopware media, and Shopware images download into the Pimcore asset tree.
Fine-Grained Permissions
Separate rights cover credentials, mapping, export, import, and job control for each admin role.
Why Do We Need Pimcore Shopware 6 Connector?
Pimcore stores clean product records, while Shopware 6 handles sales, requiring teams to manually transfer catalog data between systems.
Manual transfers require CSV exports, column checks, and fresh uploads for price changes, while variants and images create additional complexity. This connector simplifies PIM to Shopware sync by creating jobs that map fields, select entities, and transfer records automatically.
Each product export uses the Pimcore object ID as its Shopware ID, allowing repeated exports to update existing products.
The same process removes Shopware media missing from Pimcore and skips products without exported images during each synchronization run.
Also, if you want to send the same Pimcore catalog to an ERP system, you can check our extension Pimcore Odoo Connector.
Use Cases
Shopware 6 catalog sync suits teams that keep one clean product record and sell it in more than one place. If a second storefront runs on Shopify, pair this bundle with Pimcore Connector for Shopify.
-
Move a Catalog to Shopware
A brand that already keeps its catalog in Pimcore can push categories, attributes, and products into a new Shopware 6 store.
-
One PIM, Many Storefronts
Each Shopware store gets its own credential record. A team runs the same export against any store it has enabled.
-
Keep Variant Data Correct
Fashion and furniture sellers hold colour and size values in Pimcore, and the export rebuilds the same option set in Shopware.
-
Pull Shopware Data Into Pimcore
A store that grew inside Shopware can import its live categories, products, and attributes to start product information management in Pimcore.
Shopware Credentials in Pimcore
The Credentials screen lists every Shopware store the connector can reach. Each row is one saved store, and a team keeps as many rows as it has environments.
- Add a store from the Credentials screen, then keep one row per Shopware environment.
- Read the Name, Version, Test, Status, and Actions columns for every saved store.
- Run Test connection on a row to check the host and the keys before a job starts.
- Turn a store off with the enabled switch; a disabled row drops out of the job picker.
- Mark one row as active, and edit or delete any other row.
Add a Shopware Integration Credential
Add credential opens a two-part form. Connection holds the store details, and API integration holds the key pair that Shopware issues.
The form names the exact route to follow inside Shopware, so nobody has to hunt for it.
- Enter a Name and the store URL, such as https://shop.example.com.
- Pick the Shopware Version, which reads 6.5.x or above.
- Follow the on-screen route: Shopware admin > Settings > System > Integrations.
- Paste the Access Key ID, which starts with SWIA, and the Secret Access Key.
- Save the row, then run Test connection against it from the Credentials list.
Shopware to Pimcore Field Mapping
Field Mapping pairs each Shopware field with a Pimcore field in one table. A third column gives variants their own target, so a child can differ from its parent.
- Work in the Attribute Mapping tab, with Other Mappings beside it.
- Read three columns: Fields in Shopware, Fields in Pimcore, and Variant Fields in Pimcore.
- Keep productNumber paired with sku at the head, where the variant column reads n/a.
- Pair gross with price, and give each variant its own listPrice.
- Map stock, description, metaTitle, packUnit, and shippingFree in the same table.
Cover, Gallery and Variant Image Mapping
The Other Mappings tab drives media sync by keeping the image roles apart. Cover, parent gallery, and variant gallery each read from their own Pimcore attribute, so one never overwrites another.
- Set Attributes to be used as Cover Image on its own picker.
- Set Attributes to be used as Images for the parent gallery.
- Set Attributes to be used as Images (For variants) for the child galleries.
- Pick ProductImage (productImage · image) for any of the three roles.
- Choose the Properties Values (For Export) set, with SELECT ALL and DESELECT ALL.
Export Products with Currency and Locale
Product Export writes Pimcore products to Shopware. Three selectors sit above the run button, so a team can narrow a run instead of pushing the whole catalog every time.
- Pick the target store from the credential list at the top of the screen.
- Set Currency to limit the extra currency rows a run writes.
- Set Locale to choose the language written beside the base language.
- Set SKUs to export a named list instead of the whole catalog.
- Leave a selector on its default to export every mapped value.
- Press Export products to queue the run in the background.
Job Runs and Result Counts
Each Export and Import screen carries its own run list. A row records who started the run, which store it wrote to, how it ended, and how many records it touched.
- Read Start Date/Time and User for every run on that screen.
- Read the Credential column to see which store a run wrote to.
- Read the Status column, which shows Completed, Stopped, or Failed.
- Read the Result column, which counts records read, created, and updated.
- Open a row to follow a running job while it is still working.
Shopware Options Import
Options Import fetches the reference lists a Shopware product needs before it is exported again. Re-running refreshes each list in place, so nothing is duplicated.
- Press Import from Shopware to pull the lists, then Refresh to reload the table.
- Read Option type, Available, and Values for each list.
- Load Tax, and read its rates, such as Standard rate and Reduced rate.
- Load Manufacturer, Delivery Time, Scale Unit, and Sales Channel in the same run.
- See a count against each list, and a not-imported note for one never fetched.
Support
For any query or issue please create a support ticket here http://webkul.uvdesk.com/
You may also check our other top-quality Shopware Modules.