Shopware

Documentation Index

Fetch the complete documentation index at: https://docs.frontic.com/llms.txt

Use this file to discover all available pages before exploring further.

​

What you get

The Shopware connector follows the standard integration model — see how integrations work for the shape of Connection, Channels, and Data Feeds. This page covers the Shopware-specific pieces: the plugin install, the onboarding hand-off, the channel and feed details, and the data shape after normalization.

​

Install and setup

The plugin is the same either way — pick how you’d like to load it into Shopware, then run the onboarding to provision your Frontic project.

​

Install the plugin

​

Run the onboarding

With the plugin active, you can start the onboarding wizard on the plugin’s configuration page to provision your Frontic project end-to-end: it sets up the integration’s connection settings, creates one Channel per Shopware sales channel (with the matching currencies and translations), creates Data Feeds for Products, Categories, and CMS Pages, and seeds matching Data Storages and Data Syncs. On the project side it also creates one scope per sales channel, one region per channel/currency pair, and one locale per channel language. Before any of that runs, the wizard tests the Shopware connection from Frontic — if the keys are wrong or the host can’t be reached, it stops on a Connection-Test failed screen instead of provisioning a broken setup. See Troubleshooting the onboarding for the failure modes.

​

Troubleshooting the onboarding

When the connection check fails, the wizard shows a Connection-Test failed screen with the message Shopware returned and a failure type. Match it against the table below to find the fix — once the test passes, the wizard continues to provisioning automatically.

​

Without the plugin

If you can’t install the plugin in your Shopware environment — for example a managed setup where you can’t load custom extensions — you can connect manually using a Shopware Integration account.

Create an Integration account in Shopware

Open Integrations

In Shopware admin, go to Settings → System → Integrations and click Add integration.

Name the integration

Enter frontic-sync (or anything you’ll recognize later).

Assign read permissions

Assign a role with read access on: Product, Category, Sales channel, Currency, Language, Media, Manufacturers, Properties, Shopping Experiences, Landing Pages, Delivery times, Essential Characteristics, Scale Units, Tags, Tax. Plus read on the *_translation detailed privileges for product, media, manufacturer, property group, property group option, unit, delivery time, cross-selling, and feature set.

Copy the access keys

Save the integration, then copy the Access Key ID (SWIAMG…) and Secret Access Key (dXhZQ2…) — you’ll paste them into Frontic next.

In Frontic admin, Integrations → Add → Shopware asks for the host URL plus those two keys. With manual setup, you also build out the project (scopes/regions/locales) yourself in Project Settings — see Multi-Channel & Multi-Region — and create channels and feeds manually as covered below.

​

Connection settings

The settings panel shows a Connection Status indicator. When the connection is broken, it surfaces the reason returned by the Shopware API (with sensitive details redacted) — so you can tell whether credentials are missing, the host is unreachable, or the keys were rejected. Update credentials here and re-test after rotating keys in Shopware.

​

Channels

A Shopware channel in Frontic maps a Shopware sales channel to the currencies and translations Frontic should pull from it. The plugin onboarding seeds one Frontic channel per sales channel; you can add more from Channels → Add. The Refresh button on the channel detail re-fetches sales channels, languages, and currencies from your Shopware instance — use it after you’ve added one of those on the Shopware side. For how channels become project scopes and locales at sync time, see Data Sync mapping in the overview.

​

Data Feeds

The Shopware connector exposes three feed types: The standard Settings → Updates → Schema setup wizard applies — see Data Feeds in the overview. For Shopware specifically:

• Updates step — Shopware supports the Trigger update method (the plugin pushes webhooks). Scheduled polling and the Ingest API are not used; the plugin’s webhook stream is the source of real-time updates.
• Manual refresh — every Shopware feed exposes a Refresh action that re-runs the feed against the source. Use it when something changed on the Shopware side that didn’t reach Frontic, or to recover from a webhook gap. Configuration changes — Value Composer, storage schema, sync mappings — don’t need a refresh; they revalidate automatically.

​

What the data looks like

​

Associations pulled along

The connector fetches more than just the entity’s own fields — it pre-loads the associations a typical storefront needs, so your Data Sync doesn’t have to chase them. Need an association that isn’t on this list? Get in touch.

​

Variants

A product with options is denormalized: the parent record carries the shared fields, each variant is a separate record linked back via parentId. Either side can drive a Detail Block — product-level for grids, variant-level for cart and detail views. See Product Models for the full picture.

​

Currency-resolved prices

For products, the connector pre-filters the prices array to the currencies declared on the channel and stamps every price element with currencyCode and currencyPrecision. Map those into the Price composite and you’re done — no per-region price-picking logic in your Value Composer needed.

​

Translations

All translatable fields are resolved at the connector level for every locale on the channel. Use the base field in your Data Sync (name, description) — not translated.name. Frontic’s Request Context picks the right localized value at response time. For categories, breadcrumb arrays are also de-indexed so the translated breadcrumb path is a clean list rather than a 0:..., 1:... map.

​

Auto-delete reconciliation

When a feed runs (refresh, full backfill), the connector diffs Shopware’s current state against what Frontic has on the feed and emits deletes for products, categories, or CMS pages that have disappeared on the Shopware side. Your storage doesn’t accumulate orphan records when items are removed in Shopware.

​

Category relations

From the categoriesRo association, the connector also extracts a flat list of category IDs and stamps them onto the feed record under the reserved $rel namespace as $rel.categoryIds. Category-link blocks (or any sync that just needs the IDs without the full association payload) can map this directly in the Value Composer — no need to walk categoriesRo to pluck IDs out yourself.

​

Good to know

• No scheduled polling. Shopware sync relies entirely on plugin webhooks. If the plugin is disabled or your instance can’t reach Frontic, changes won’t be pushed — fix connectivity, then hit Refresh on each feed to backfill.
• Webhook delivery retry is on the plugin side. The Frontic plugin queues outbound webhooks in Shopware and retries delivery — events older than Shopware’s retention can’t be replayed and need a manual feed Refresh to reach Frontic.
• Batch size. Records are fetched in batches to keep Shopware’s API response size small enough for catalogs with large associations.

​

Related