Pimcore Shopware 6 Connector

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 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.

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.

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.

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.

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.

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.