SKU & MPN Display on Product pages

Modified on Mon, 23 Nov 2020 at 04:06 PM

For each product you choose to show in your AIM Storefront website, you have the ability to choose among 7 product page layouts in order to find the one that works with your data. We are often asked about which packages support the display of SKU and MPN and we hope that this page can answer a majority of those questions. Below we’ll list each standard display package and its display settings that can be changed to further customize it to your needs.


Below is a list of AIM Storefront Standard product display pages and which settings will affect each page. You can find each setting in /aesys by navigating to “Configuration > Settings” and searching for each setting name.


The ShowManufacturerPartNumberOnProductPage setting is 'global', meaning it will turn the MPN display on or off for all products, regardless of which layout is in use. The Manufacturer Part Number value associated with your products in AIMStorefront matches the Model value in AIM.


Note: AIM converts all SKUs to add an “ae00-“ to the beginning of each SKU number. This is by design and you will not be able to configure the display package to show that number differently.


The options for each of the settings, ProductSkuDisplay & VariantSkuDisplay, allow you to select from these options:

  • None: Hides the SKU (don't show anything!)
  • FullSKU: Displays the full product SKU ( Product SKU + ProductVariant SKUSuffix )
  • SKU: Only shows the product SKU ( Product SKU )
  • SKUSuffix: Only shows the variant SKUSuffix ( ProductVariant SKUSuffix )


Available Display Package Options:


No Product Variants: 


These 2 product XML display packages are not designed to work with product that have only one variant. They are the simplest of the product display packages and will not work if your product has more than a single variant. The setup on them is equally simple.


Simple Product - product.SimpleProduct.xml.config

  • ProductSkuDisplay - toggles whether SKU shows on the page. You can use this setting to define which parts of the SKU and variant sku suffix show on the page. 
  • VariantSkuDisplay – not used.


Simple Product With Large Image - product.SimpleProductLargeImage.xml.config

  • ProductSkuDisplay - toggles whether SKU shows on the page. You can use this setting to define which parts of the SKU and variant SKU suffix show on the page. 
  • VariantSkuDisplay – not used.


Product Variants in a dropdown: 


These 2 product XML display packages are not designed to work with products that have more than one variant. They will only show one variant at a time, so the product SKU display is the only setting that will matter on these pages. I typically recommend setting up your SKU to show the SKU and the suffix, knowing that the suffix will change when a variant is chosen in the dropdown.

 

Variants In Dropdown - product.VariantsInDropDown.xml.config

  • ProductSkuDisplay – not used.
  • VariantSkuDisplay - toggles whether SKU shows on the page. You can use this setting to define which parts of the SKU show on the page.


Variants In DropDown With Tabbed Layout - product.TabbedUI.xml.config

  • ProductSkuDisplay – not used.  
  • VariantSkuDisplay - toggles whether SKU shows on the page. You can use this setting to define which parts of the SKU and variant SKU suffix show on the page. 


Multiple Variants displayed at once:


Each of the next 3 product XML display packages show multiple variants on the same page at the same time, so they can take advantage of both SKU display settings. You’ll want to experiment with each of the configuration options for your SKU display, such as setting the main product to only display the SKU, but using the variant SKU display option to set either the full SKU or the SKU suffix.


Keep in mind on these pages, that MPN will show at the top of the page, and on each variant and you will toggle both on or off globally with the ShowManufacturerPartNumberOnProductPage setting.

 

Variants In Grid - product.VariantsInGrid.xml.config

  • ProductSkuDisplay – will display the product SKU near the top of the page, under the product name.  You can use this setting to define which parts of the SKU show for each variant.
  • VariantSkuDisplay - toggles whether SKU shows on the variants that appear in the grid further down the page. You can use this setting to define which parts of the SKU show for each variant.


Variants in List - product.VariantsInList.xml.config

  • ProductSkuDisplay – will display the product SKU near the top of the page, under the product name.  You can use this setting to define which parts of the SKU show for each variant.
  • VariantSkuDisplay - toggles whether SKU shows on the variants that appear in the list further down the page. You can use this setting to define which parts of the SKU show for each variant.


Variants In Right Column - product.VariantsInRightBar.xml.config

  • ProductSkuDisplay – will display the product SKU near the top of the page, under the product name.  You can use this setting to define which parts of the SKU show for each variant.
  • VariantSkuDisplay - toggles whether SKU shows on the variants that appear further down the page. You can use this setting to define which parts of the SKU show for each variant.


Troubleshooting: 


If you're not seeing these updates on your store, you might be using a modified layout. 

Modified layouts (XmlPackages) are not automatically updated when we update your website with new releases. You can either merge the new code from the root /XmlPackages folder into your Skins XmlPackages folders (advanced users), or remove your modified layout from the Skins XmlPackage folder.


You can remove your modified layout by logging in to your website's FTP account and navigating to your Skins/Skin_1/XmlPackages folder ("Skin_1" may vary depending on your store's configuration). Look for files like:  entity.*.xml.config, and product.*.xml.config, download them to your computer to make a quick backup, then delete them in your FTP client.


If you're not sure how to go about this, please submit a ticket, our team is standing by ready to help!

 

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article