PIMcore Product Selector module: C37_Product Selector

Within the general setting the editor can predefine the product selector application view.

• Show filters: usually the filters are shown in order to provide the user the option to filter. In the use case that the user should just see a pre-filtered result page wiht less products, the filters can also be hidden.
• Show compare: the editor can define, if the compare fuction should be provided. There are product groups where it make sense to compare technical data of products in order find the right product.
• Show initial results: either the user does not get any result before a selection in the filter was done or the user gets initially all results and can reduce the products by filtering. 

The content of the product detail pages is definied directly in PIMcore. But within this module tab the editor can define some more general settings. This is important if several product selectors are used on just one content page. In this use case the different application results need to be differentiated.

• Name Prefix for PDP URL: the here defined name of the product / product group will be added within the URL of each product detail page of the resprective product selector.
  Example: product selector for brand1 products are placed on this content page - next to other product selector applications on the same page - and the prefix is "brand1", it will be added to the PDP URL as in the following:
  "https://heraeus-business.com/en/products/...../brand1-ps-detail"
• Meta robots: this information we know from other link definitions. The editor can define if search engines should index and follow the product detail page link.
• Canonical product selector: if there are several product selector applications on one content page, the editor should define for search engines, what are the product detail pages to index.
• Remove from global search: further editors can define, if the product detail pages should appear in the global website search.

On each product detail page there is a "request a quote" button that opens a separate contact form for the user. This contact form already includes 2 read-only fields with the selected product information to be handed over to the receipient.

NOTE: the contact form needs to be set up separately. In the following we assume that the contact form is already existing in magnolia.

• Product field name + Productselecotor field name: these field names are mapped to the respective fields within the Contact form. To keep it simple you can use for exampele "input0" and "input1" as in the screen below.
  Within the contact form these field names need to be the same in order to map it correctly!
• Where to show the "request a quote button"?
  Either it can be shown just on the overview page or just on the product detail page or even both. The editor can define this here.
• Select the contact form page out of the magnolia pages app to link the "request a quote button" accordingly.

Within the label settings the editor can define own labels for all fields within the product detail page.

For sure, there are labels pre-defined in the backend, but within the module you can overwrite it individually.