Grouping properties in the Shopware listing: presenting technical data clearly

Technical data often gets lost in product boxes. If you group properties by topic, they become easier to read and barriers to purchase fall. This article shows how to form meaningful groups, what changes for the listing and the product detail page, how a Shopware extension implements the grouping, and what requirements and limits it has.

Properties output in no particular order confuse visitors and increase the bounce rate. At the end you will find a checklist for the setup and a rule of thumb for the number of groups.

How do you prevent technical data from confusing customers?

Structure technical data according to your customers’ tasks and decision criteria instead of showing it as a loose list.

Customers look for information in order to make a decision: does the product fit into the available space, does it work with the existing peripherals, does it meet a performance requirement? Arrange the attributes according to these questions. Dimensions go into one group, connections and compatibility into another, performance data into a third. This reduces cognitive load, because visitors only need to skim the relevant fields.

Here is how to proceed:

1. Attribute audit: list all existing attributes and note the typical customer questions about them.
2. Taxonomy: define groups (e.g. dimensions, performance, connections, certificates).
3. Mapping: assign each attribute to exactly one group and set rules for naming and units.
4. Presentation: choose a compact inline format for the listing and collapsible sections or tabs on the product detail page (PDP).

Typical mistakes are inconsistent units (cm and mm mixed without explanation), inconsistent attribute names (several fields with the same content but different labels), empty or irrelevant groups and too many groups in the listing. Add to that technical terms without explanation, missing contextual help (tooltips, short explanations) and too little consideration for the limited space on a smartphone.

Prioritise by purchase relevance (which group answers the most important customer question?), by context (listing or PDP) and by device (mobile or desktop). Define for each category which groups always appear, which are optional and which appear only on the detail page.

What changes when you bundle properties by topic?

Bundled properties are quicker to grasp, maintenance becomes easier, and the presentation can vary by channel and context without attributes being maintained twice.

In your workflow, you no longer edit attributes individually per product but manage groups centrally and assign them to categories. This clearly defines who is responsible for attribute maintenance, and fewer errors occur when new products are created. Templates can reference groups, so that the listing and PDP use the same information blocks.

Technically, a flat attribute list becomes a hierarchical model (groups with attributes beneath them). This allows for an order, conditional visibility (e.g. only show if a value exists or a certain product type applies) and different presentations per channel: compact in the listing, detailed on the PDP. Check whether attributes are also used as filters. Switching to groups must not change the filter logic unnoticed.

For maintenance and governance, you need rules for names and units and a person responsible for the attribute taxonomy. Bulk imports and data feeds should automatically assign new products to the right groups. Without these rules, the maintenance effort stays high and unstructured lists creep back in.

How does the plugin implement the grouping in practice?

The plugin comes with an interface in the Administration. There you create property groups, assign them to categories and define the presentation for the listing, product boxes and PDP.

In the Administration you create groups with a label and order, assign attributes to them and assign the groups to categories. The presentation can be configured for different areas (listing, product box, detail page, cross-selling), and position and display type are selectable. During setup, remember to translate the group labels and to use a consistent translation strategy.

Check how the plugin is integrated into your shop’s templates. There are often template slots or hooks for this. Decide what happens when attributes are missing (hide the group or show a placeholder). Also keep an eye on performance: many groups in a listing can affect loading time and caching. For catalogue pages, lazy loading or server-side aggregation can help if needed.

Usability and accessibility call for a clear visual hierarchy (a heading per group, compact list items), ARIA attributes for screen readers and groups that can be reached by keyboard. On smartphones, a concise default view whose details can be expanded is recommended.

You can find the plugin’s feature description with the design options mentioned in the Shopware Store.

What requirements and limits do you need to consider?

Check compatibility with your Shopware version, the integration needs with PIM, ERP and feeds, and whether the solution is sufficient for products driven heavily by variants.

The extension is compatible with Shopware versions 6.5.0.0 to 6.7.13.0. During an active subscription, updates and support from us as the manufacturer are included, and the subscription starts with a free trial month. This information comes from the plugin description in the Shopware Store.

According to the description, there is no automatic mapping logic for complex variant or matrix products. If variants have very different attributes, you maintain the mapping manually or handle it via an additional PIM. Also pay attention to the effects on existing filters, the quality of the imported attribute data and consistent units.

Before rollout, clarify how product data gets into the shop (feed, PIM, manual entry) and who is responsible for the data. For large catalogues, a PIM integration is worthwhile so that group assignments are maintained centrally. Test the changes in a staging environment, check the administrators’ permissions and document the change process so that no errors creep in.

Which practical rules help with setup and prioritisation?

Set clear priorities, limit the number of visible groups per context and test step by step with typical products and devices.

Setup checklist:

• Audit: identify the most common purchase and support questions for each category.
• Define groups: form groups based on customer tasks (e.g. dimensions, connections, performance, certificates).
• Assign: assign attributes to groups and groups to categories.
• Prioritise: set the order according to purchase relevance and available space.
• Configure the presentation: compact formats in the listing, detailed blocks on the PDP, hide empty groups.
• Test: check on different devices, with variants and together with the filters.

As a rule of thumb from experience, use no more than three property groups per product box in the listing so that the box stays compact. On the PDP, up to five groups make sense. Common mistakes are too many groups in the listing, empty values that aren’t handled, inconsistent units and a lack of coordination with the product filters. It is also problematic if groups exist only in the template and not in the data model, as the output then becomes inconsistent.

Prioritise by (1) direct purchase relevance, (2) frequency of support requests and (3) legal requirements that must be displayed. Show sparingly on smartphones and in more detail on desktop.

For ongoing operation, set up a review for new groups and attributes, document naming and unit rules, and check the output for formatting and display errors after rollout. For questions about compatibility or features, the plugin page in the Shopware Store is the authoritative source.

Frequently asked questions

Can I create property groups only globally or also per category?

You create the property groups in the Administration and assign them to different categories. That way only the matching groups appear on a category page (source: Shopware Store).

Can the presentation in the listing and on the product page be controlled?

Yes. According to the store description, you can enable the presentation in product boxes, on detail pages or in both, and set the position and display type.

Are updates and support included in the price?

During the subscription, all released updates are included and we provide support as the manufacturer. The subscription starts with a free trial month (information from the Shopware Store).

Is the plugin suitable for complex variant matrices?

The description does not mention any automation of its own for variant attributes that differ greatly. For very complex variant configurations, you should check suitability before buying.

Conclusion

With the extension, you group properties by topic, assign the matching groups to categories and control presentation and order. The listing becomes clearer, and customers find the technical data they need to make a decision. View the plugin in the Shopware Store