runelaenen/sw6-extended-admin-config

Configurable admin listings and product label for Shopware 6

v6.0.0 2026-04-10 13:35 UTC

Requires

• shopware/core: ~6.6.0

MIT

README

Configurable admin enhancements for Shopware 6. Control which product fields appear in the order form search label, and add custom columns to the Orders and Customers listing pages from the settings page in the admin.

Features

• Product label fields: choose which product fields appear in the order line item search dropdown, their order, and formatting:

  Acme Widget Pro | Acme Corp | 42 | €29.99
  

• Order list columns: add any order entity field as an extra column to the Orders listing, with control over placement and visibility.
• Customer list columns: add any customer entity field as an extra column to the Customers listing, with control over placement and visibility.

All three are configured from Settings > Plugins > Extended Admin Config.

Requirements

• Shopware 6.6.x
• PHP 8.2 or higher

Installation

Via Composer (recommended)

composer require runelaenen/sw6-extended-admin-config
bin/console plugin:install --activate LaenenExtendedAdminConfig
bin/console cache:clear
bin/build-administration.sh

Manually

1. Download or clone this repository into custom/plugins/LaenenExtendedAdminConfig.
2. Install and activate the plugin:

   bin/console plugin:install --activate LaenenExtendedAdminConfig
   bin/console cache:clear

3. Build the administration assets:

   bin/build-administration.sh

Configuration

Go to Settings > Plugins > Extended Admin Config. The page has three sections.

Product Label Fields

Configures the label shown for each product in the order line item search dropdown.

Field	Description
Field path	Dot-notation path into the product entity, e.g. manufacturer.translated.name
Format	Raw value (default) or Currency (applies Shopware's currency formatter — use for price fields)
↑ / ↓	Reorder fields
✕	Remove a field

Fields are joined with | in the label. Fields whose path resolves to an empty or null value are omitted automatically.

Common paths:

Path	Description
translated.name	Product name (translation-aware)
productNumber	Product number / SKU
manufacturer.translated.name	Manufacturer name
stock	Available stock quantity
price.0.gross	Gross price (first price tier) — use Currency format
ean	EAN / GTIN barcode
weight	Weight
customFields.your_field_key	Any custom field

Order List Columns

Adds extra columns to the Orders listing page.

Field	Description
Field path	Dot-notation path into the order entity, e.g. orderCustomer.email
Column label	Text shown in the column header
After column	Property name of an existing column to insert after, e.g. orderNumber. Leave empty to append at the end
Active	Uncheck to hide a column without deleting it
↑ / ↓	Change the order of appended columns
✕	Remove a column

Common paths:

Path	After column example	Description
orderCustomer.email	orderCustomer.firstName	Customer e-mail address
orderCustomer.company	orderCustomer.firstName	Customer company name
billingAddress.countryState.name	billingAddressId	Billing state/province
customFields.your_field_key		Any order custom field

Customer List Columns

Adds extra columns to the Customers listing page.

Field	Description
Field path	Dot-notation path into the customer entity, e.g. email
Column label	Text shown in the column header
After column	Property name of an existing column to insert after, e.g. defaultBillingAddress.city. Leave empty to append at the end
Active	Uncheck to hide a column without deleting it
↑ / ↓	Change the order of appended columns
✕	Remove a column

Common paths:

Path	After column example	Description
email	firstName	Customer e-mail address
defaultBillingAddress.countryState.name	defaultBillingAddress.city	Billing state/province
defaultBillingAddress.country.name	defaultBillingAddress.city	Billing country
customFields.your_field_key		Any customer custom field

How it works

Dot-notation paths

All field paths use dot-notation to traverse the entity graph. Array indices are supported where needed (e.g. price.0.gross accesses the first element of the price array).

Associations are loaded automatically

The plugin reads Shopware's entity schema at runtime to determine which segments of a configured path are associations. Only association segments are added to the API query — scalar and JSON fields are excluded. Multi-level paths are fully supported: billingAddress.countryState.name causes both billingAddress and countryState to be loaded.

On the order entity, paths starting with billingAddress load their nested associations through the addresses collection, which is how Shopware's order data model is structured.

Column positioning

The After column field accepts the property value of any existing column (including core Shopware columns). If the value doesn't match any column, the extra column is appended to the end instead. Multiple extra columns targeting the same existing column are inserted in the order they appear in the configuration.