Featured Products in SuiteCommerce can help merchandising teams highlight priority items, seasonal collections, new arrivals, or products that need additional visibility. The result depends on more than installing a bundle. Item eligibility, configuration records, storefront placement, deployment settings, cache behavior, and catalog permissions all influence what shoppers actually see.
To configure Featured Products in SuiteCommerce, install and verify the appropriate bundle or extension, define which items qualify, connect the configuration to the storefront presentation, deploy the changes through the correct SuiteCommerce environment, and test the resulting catalog output across desktop and mobile views. The exact field names and setup screens depend on the SuiteCommerce version, bundle release, account configuration, and customizations, so we recommend following the version-specific documentation while validating the live storefront behavior independently.
This guide focuses on the practical configuration decisions that determine whether a featured product area remains accurate and useful after launch. It does not treat the bundle as a standalone visual component. The important question is whether the storefront consistently displays the right products, in the right context, with current price, availability, images, and customer visibility rules.
What Featured Products in SuiteCommerce actually controls
A Featured Products configuration typically controls a curated product presentation on one or more areas of a SuiteCommerce storefront. Depending on the implementation, it may determine the products shown, their sequence, the title of the content block, the number of visible items, and the page or component where the block appears.
The bundle or extension does not replace the item record, pricing configuration, inventory logic, or customer-specific catalog rules in NetSuite. Instead, it presents product information that SuiteCommerce retrieves through the commerce application and its underlying services.
That distinction matters. A merchandising user might select a product as featured, but the storefront still needs to resolve several related values:
Whether the item is active and available for web presentation.
Whether the item belongs to the relevant website or domain.
Whether the current customer or customer group can view the item.
Which price level, currency, and customer-specific pricing rule applies.
Whether inventory or out-of-stock settings allow the product to appear.
Which image, URL, option structure, and product detail page the shopper receives.
Featured Products therefore works best as part of a controlled catalog process. It should not be treated as a simple list of product names added to a page.
For broader NetSuite ecommerce architecture, product synchronization, and storefront integration decisions, our NetSuite ecommerce services provide a useful starting point. This article narrows the focus to featured product configuration inside SuiteCommerce.
What should you check before configuring the bundle?
Before changing the storefront, confirm what the bundle is expected to do in your account. A bundle name alone does not prove that the installed version supports the presentation, item selection, or page placement your team expects.
Start by reviewing the following information in NetSuite:
Bundle or extension identity. Confirm the publisher, version, release notes, dependencies, and compatibility with the SuiteCommerce implementation. NetSuite interfaces and bundle installation screens change over time, so the visible labels in your account might differ from documentation written for another release.
Storefront architecture. Identify whether the website uses a standard theme, a customized theme, extensions, custom modules, or a combination of these. A custom template can override the output of a standard component, while a custom module can introduce its own item-selection logic.
Deployment model. Establish whether changes move through local development, a development domain, a staging environment, and production. Configuration stored in NetSuite and code deployed through the SuiteCommerce application do not always move through the same process.
Catalog governance. Decide who selects featured products, who approves the selection, and who removes products when they become inactive, unavailable, or commercially irrelevant. Without ownership, featured content becomes stale even when the technical configuration works correctly.
Customer visibility rules. Confirm whether the storefront serves anonymous shoppers, logged-in customers, customer-specific catalogs, or multiple websites. A product visible to one audience might not be valid for another.
A practical pre-configuration review should also include the item types that will appear. Standard items, matrix items, kits, assemblies, and service-related records can behave differently in search, product detail pages, inventory availability, and option selection. Test the item types that your catalog actually uses instead of assuming that one successful product proves universal compatibility.
How do you configure Featured Products in SuiteCommerce?
The configuration process has four connected layers: account setup, product eligibility, storefront presentation, and deployment validation. Keeping these layers separate makes troubleshooting much faster.
1. Confirm the installed bundle and dependencies
Locate the relevant Featured Products bundle or extension in the NetSuite account and review its installation status. Record the installed version and compare it with the SuiteCommerce release used by the storefront.
Do not assume that a completed bundle installation automatically activates the feature. A bundle can install records, scripts, templates, or configuration objects without changing the visible storefront until the corresponding extension or theme settings are enabled.
Check for:
Required SuiteCommerce or SuiteCommerce Advanced compatibility.
Dependent bundles, scripts, custom records, or extensions.
Required permissions for administrators and merchandising users.
Configuration records created during installation.
Any instructions for adding assets, modules, or theme settings.
Known limitations around domains, websites, item types, or customer groups.
If the bundle requires a script deployment, confirm that the deployment is active in the correct account context. If it requires a custom record, verify that the record is available to the roles responsible for maintaining featured products.
2. Define item eligibility in NetSuite
Select products that are genuinely ready for storefront promotion. Featured status should not be the only condition that determines whether a product appears.
At minimum, verify the item’s web availability, website assignment, display settings, price, inventory behavior, product URL, and image data. For matrix items, confirm whether the parent item or a specific child item should be presented. A parent product with incomplete option data can create a poor experience even when the featured block itself renders correctly.
Customer-specific catalogs require additional care. If pricing and availability vary by customer or customer group, test the featured product while logged in as representative account types. The same configuration record can produce different storefront results depending on access rules.
Inventory settings also deserve explicit attention. Decide whether an unavailable item should:
Remain visible with an out-of-stock message.
Remain visible only when backorders are accepted.
Be removed from the featured area.
Be replaced by another curated product.
This behavior belongs to the overall commerce configuration, not simply to the visual component. If the bundle does not provide replacement logic, the merchandising process needs a regular review of featured items.
3. Create or update the featured product configuration
Open the configuration area provided by the bundle or extension and create the relevant featured product entry. Depending on the release, the configuration may use a custom record, a list, a merchandising field, a page-level setting, or an extension configuration value.
Use clear internal naming. A record called “Homepage Products” is easier to maintain than a generic label such as “Featured 1.” If the account supports multiple websites, domains, languages, or customer experiences, include enough detail to distinguish each context.
Configure the presentation rules supported by your implementation, such as:
The product selection and display order.
The heading or introductory text.
The number of products displayed.
The target page or content area.
Desktop and mobile behavior.
Whether shoppers can navigate to a category, search result, or product detail page.
The start and end dates for time-sensitive merchandising.
Avoid selecting more products than the component is designed to display. Some implementations retrieve all configured items and hide the extras in the browser, which creates unnecessary data and rendering work. Other implementations limit results at the service or application layer. Confirm how your version behaves rather than relying on assumptions.
A useful operational practice is to keep a small reserve of approved products. That gives merchandising teams alternatives when an item becomes unavailable, discontinued, restricted, or unsuitable for a campaign.
4. Connect the configuration to the storefront
The configuration record and the visible storefront block are separate concerns. The storefront must know where to request and render the configured products.
Depending on the SuiteCommerce implementation, this connection can involve a theme setting, extension configuration, template region, CMS content area, custom module, or page-type setup. Review the implementation’s source code and configuration files before editing a template. A seemingly small template change can affect product tiles, responsive behavior, accessibility, and other content areas.
Confirm the following:
The correct extension or module is included in the build.
The component is assigned to the intended page type or content region.
The template uses the expected product data model.
Existing customizations do not suppress the component.
The component has a fallback when no eligible products are returned.
Links resolve to the correct product detail route.
Images use the expected image role and responsive behavior.
The heading structure remains accessible to screen readers.
Product images are a related but separate implementation concern. If the featured area shows missing images, incorrect crops, or inconsistent image roles, use our guide on setting up the Find SuiteCommerce Image bundle for the broader image bundle installation and troubleshooting process. The featured product configuration should not be used to compensate for incomplete item image data.
5. Build and deploy through the correct environment
After connecting the component, build the SuiteCommerce application in the intended development environment. Review build output, JavaScript errors, dependency warnings, and template compilation messages before moving toward production.
A reliable deployment sequence separates configuration validation from code validation. First confirm that the featured product records contain the expected items. Then verify that the storefront build includes the component and that the relevant page type renders it. Finally, test the deployed result through the actual domain and customer access paths.
Pay attention to cache behavior. SuiteCommerce storefronts can use application, browser, CDN, or service-level caching. A configuration change may be correct in NetSuite while the storefront continues to show an earlier response. Clear or invalidate the appropriate cache according to the implementation’s deployment procedure, then test in a private browser session.
Do not make several unrelated merchandising and template changes in one deployment. Isolating the featured product change makes it easier to determine whether a problem comes from the bundle, catalog data, theme code, or cached output.
Where should featured products appear?
Featured products should appear where they support a clear shopper decision, not everywhere a content block is technically available. The homepage is a common location, but category pages, search landing pages, campaign pages, and customer-specific content areas can also be appropriate.
The page context should determine the selection. Products featured on a general homepage need broad relevance. Products shown on a category page should reinforce that category rather than send shoppers to unrelated items. On a campaign landing page, the featured collection should support the campaign’s message and destination.
Placement also affects performance. A component near the top of the page receives more immediate attention, but it may also add product data and image requests to the initial page experience. A component lower on the page can support discovery without competing with the primary navigation or purchase decision.
Use the browser’s developer tools to inspect the actual request pattern. Check whether the component requests product data on initial page load, after client-side rendering, or only when the component enters the viewport. This detail affects perceived performance and helps identify whether a slow featured area is caused by the bundle, image delivery, API response time, or frontend rendering.
How do you test a Featured Products configuration?
Testing should validate both the visible design and the commerce rules behind it. A single desktop homepage check is not enough.
Test the feature against a defined matrix that includes:
An active item with complete pricing and image data.
An inactive or discontinued item.
An out-of-stock item.
A matrix item with required options.
An item restricted to a customer group.
A product with a long name or unusual image dimensions.
A configuration with fewer items than the display limit.
A configuration with more items than the display limit.
An empty or invalid configuration.
An item assigned to another website or domain.
For each scenario, confirm the product title, image, price, availability message, options, product URL, and add-to-cart behavior. Test anonymous and authenticated sessions when the storefront supports both. Also check customer-specific pricing if the account uses pricing levels, contracts, or custom catalogs.
Responsive testing should cover common mobile and desktop breakpoints. Inspect keyboard navigation, focus order, link labels, heading hierarchy, image alternative text, and the behavior of any carousel controls. A featured product component that looks correct but cannot be navigated accessibly is not complete.
Use browser network tools and NetSuite logs where available to distinguish data errors from presentation errors. A blank component can result from an empty response, an authorization rule, a failed script, a route mismatch, a JavaScript exception, or stale cache. Each cause requires a different fix.
Why are featured products not showing in SuiteCommerce?
The most common reason is that the selected item fails a catalog or visibility condition rather than the visual component failing outright. Check item activity, website assignment, web display settings, customer permissions, inventory rules, and effective pricing before changing templates.
Other common causes include:
The component is not included in the deployed build. The configuration exists in NetSuite, but the extension, module, or theme setting is missing from the deployed source.
The page region is incorrect. The block is assigned to a page type or content area that the current URL does not use.
The configuration contains an unsupported item type. A bundle may expect a standard item reference while the record points to a matrix parent, kit, assembly, or another unsupported structure.
The storefront is displaying cached content. The account contains the new selection, but the browser, CDN, application, or service response has not refreshed.
A custom template overrides the output. A customized product tile or page layout can omit the fields required by the featured product component.
The item is visible to one audience but not another. Customer-specific catalog rules, website restrictions, or pricing permissions can change the response for logged-in users.
Troubleshoot in that order. Start with data and visibility, then inspect configuration, deployment, rendering, and cache. This prevents unnecessary code changes when the root cause is simply an ineligible item.
How should teams maintain featured product selections?
Featured products need a maintenance process because catalog conditions change after the original configuration. Products sell out, prices change, images are replaced, campaigns end, and customer visibility rules evolve.
Assign ownership for selection, approval, and removal. Establish a review cadence that matches how quickly the catalog changes. The review should compare featured selections with current product status, inventory, pricing, content quality, and commercial priorities.
Use descriptive records and documented naming conventions. If the bundle supports scheduling, use start and end dates rather than relying on a person to remember a manual change. If it does not support scheduling, maintain a simple change calendar and include cache invalidation and deployment checks in the process.
Measure more than clicks. Review product detail visits, add-to-cart activity, conversion behavior, search refinement, and zero-result or unavailable-item events where those analytics are available. A product can receive attention without helping shoppers complete a purchase. Merchandising decisions should use both engagement and catalog quality signals.
When should you use a different SuiteCommerce approach?
A Featured Products bundle is appropriate when the merchandising requirement is a relatively focused curated product presentation. It is not the best answer for every type of recommendation or personalization.
Use a different approach when the requirement depends on real-time behavioral recommendations, complex customer segmentation, algorithmic ranking, large-scale campaign management, or product relationships that the standard bundle does not represent. A custom SuiteCommerce extension, CMS-driven content model, search configuration, or external recommendation service might be more suitable, depending on the account architecture.
The decision should consider data ownership, performance, governance, accessibility, deployment complexity, and long-term maintenance. Building a custom component only makes sense when the business rule cannot be represented reliably through the existing configuration.
Conclusion
Featured Products in SuiteCommerce works reliably when product selection, catalog eligibility, storefront placement, deployment, and maintenance are treated as one process. Installing a bundle is only the starting point. The configuration must respect website assignments, customer visibility, pricing, inventory, product type, responsive presentation, and cache behavior.
Start with a small, well-defined set of eligible products. Validate the data and visibility rules before changing storefront code, then deploy through the correct environment and test realistic customer scenarios. If the configuration requires deeper SuiteCommerce development, NetSuite catalog governance, or integration work, contact Versich to discuss the right implementation approach.
