Shops (Multi-Shop)
Overview of the multi-shop management of the Shopware 6 Connector. Each Shopware 6 shop is kept as its own record with its own connection, defaults, sync toggles and process overrides. This lets you run several Shopware 6 instances in parallel from a single BC environment.
Shop = sub-account in the hub
The Shop Code maps 1:1 to the sub-account code in the merchantCENTRAL Hub. Order, quantity and price sync run per shop. The first shop is named MAIN by default.
Opening the page
- Via Search: Shopware 6 Shops
- Via the Setup Card → Manage Shops
- Via the Dashboard → navigation → Shops
List
| Field | Description |
|---|---|
| Shop Code | Unique code (e.g. MAIN, B2B, OUTLET) – maps to the hub sub-account. |
| Name / Description | Display name and description; appear in messages and lists. |
| API URL | Base URL of the shop. |
| Enabled | Only active shops are synchronised. |
Shop Card – fields
Connection
| Field | Description |
|---|---|
| API URL | Base URL of this shop. |
| Access Key ID | OAuth2 access key (via drill-down, in the credential store). |
| Secret Access Key | Secret key of the integration (via drill-down, in the credential store). |
Sync toggles
Controllable per shop: Order Import, Item Sync, Price Sync, Inventory Sync, Customer Sync, Image Sync. This way one shop can import orders only, while another also receives items and images.
| Field | Description |
|---|---|
| Max Orders Per Run | Maximum orders per job queue run (default 15). |
| Order Date Filter | Earliest order date to import. |
Defaults (override the setup default)
| Field | Description |
|---|---|
| Default Tax ID / Rate | Default tax for this shop. |
| Default Currency ID | Default currency for this shop. |
| Price List Code | BC price list for this shop. |
| Sales Channel ID | Sales channel (visibility, SEO). |
| Description Template | Description template (empty = setup default). |
| Variant Container Suffix | SKU suffix of variant containers (empty = setup default). |
| Custom Field/Text 1–2 (Name/Label) | Own custom field mapping; empty = setup default. |
Process overrides (Default / Yes / No)
Default takes the setup value.
| Override | Effect |
|---|---|
| Suppress Status on Ship | No status update to this shop on shipping. |
| Auto Payment on Ship | Mark the order as paid on shipping. |
| Auto Credit Memo on Return | Automatically create a credit memo in BC on return. |
| Upload Documents to Shop | Invoice/credit memo as PDF to the shop order. |
| Sync Product Documents | Upload product documents on item push. |
| Default Feature Set ID | Essential characteristics for uploaded items. |
Shop card – action “Clean Up Empty Media”
If a document upload fails after the media entry was created, an entry without a file stays behind in the shop – hardly findable in the admin, with neither name nor preview. The Clean Up Empty Media action on the shop card cleans up:
- Finds all media entries of the shop that never received a file and are older than 60 minutes (the age limit protects uploads running right now).
- If such a medium is still linked to a product (as a download or product image), the confirmation names the affected product numbers. These links are broken anyway – the download delivers nothing, the image stays blank – and are removed along with the media.
- Deletes the entries after confirmation; the result message reports the count.
Media with files are never touched. Individual delete failures do not abort the run and are recorded in the activity log (context EmptyMediaDelete).
Notes
Migration from single-shop setup
When upgrading from a single-shop configuration, the existing settings are automatically migrated into a MAIN shop record.
Credential store
All API credentials are stored per shop in the central credential store – never in clear text.
- Each shop is registered in the merchantCENTRAL Hub as its own sub-account.
- The job queue processes all enabled shops.
- For strongly divergent catalogs across shops, a shared catalog currently applies (per-shop catalog scoping is in progress).