Shopify Product Card Builder

The Product Card Builder controls the product card layouts used by Nimstrata Search Results, Product Grid collection pages, Dynamic Autocomplete, and Recommendations AI App Blocks.

It does not replace Shopify's native product cards outside the Nimstrata storefront experience.


Build in Production or a Profile

The page header's Editing Production or Editing profile name pill controls which product card is being changed. Template selection, builder changes, starting without a template, and clearing the layout remain in the current page draft until the merchant uses Save. Discard restores the saved layout for that Production or named profile.

Named profiles can be assigned to selected Search Results, Product Grid, Dynamic Autocomplete, and Recommendations AI theme surfaces before their product card is promoted to Production. See Storefront Settings Profiles for the complete create, compare, publishing, and promotion workflow.


Choose a Storefront Surface

The builder has four tabs:

  • Search is the standard card for Search Results and Product Grid collection pages. It is also the fallback for Dynamic Autocomplete and Recommendations.

  • Dynamic Autocomplete can use its own card. Until it is customized, every product row—including search previews, recommendations, and bestsellers—uses the Search card. A customized card supports every configured component, including options, basket actions, and Custom components; the Search fallback omits those interactive components.

  • Recommendations can use its own card for the standalone Recommendations AI App Block.

  • Chat is disabled and marked Coming soon. Chat cards are not changed by this page yet.

Choose Customize on Dynamic Autocomplete or Recommendations to start with a copy of the current Search card. Choose Use Search card, clear the specialized card, or save it without components to restore the Search fallback. Search and both optional cards are part of the same Production or named-profile draft and save together. The Product Card Links setting remains shared by Search, Dynamic Autocomplete, and Recommendations.


Start With a Template or Start From Scratch

When the builder opens, merchants can:

  • Start with a Nimstrata template
  • Start without a template and build a custom layout

Templates are the fastest way to launch. Merchants can then refine the layout to match storefront branding, product data, and conversion goals.


Component Types

The builder can assemble standard product-card components without theme code:

Component Use when
Image or Image Gallery The card needs primary imagery, hover imagery, or a small image carousel
Product Title The card should show the imported product or variant title
Brand Vendor or brand data should be visible on the card
Price The card should show price, sale price, and compare-at price behavior
Rating Review count and average rating are imported
Option Shoppers should see variant options such as color or size
SKU SKU is useful for high-intent shoppers or B2B catalogs
Product Type Shopify product type is useful merchandising context
Inventory Availability or stock messaging belongs directly on the card
Wishlist The theme or a custom component supports wishlist behavior
Add to Basket Shoppers should add the selected variant from the card
Tag: Is Reduced Sale or reduction badges are driven by imported pricing data
Metafield A product metafield should display on the card
Custom A bespoke Web Component should render inside the card

Horizontal blocks can contain up to two child components. Use this for compact rows such as brand plus badge or price plus inventory.

The Image Gallery component lets shoppers flip through product images directly in the results grid on mobile.

The Rating component can display the exact filled-star value or round it to the nearest quarter, half, or whole star. Star rounding does not change the numeric rating shown to shoppers.



Product Metafields and Custom Components

If the storefront design needs more than the default card elements, merchants can:

  • Add product metafields to the card layout
  • Use Custom Components only when the built-in card components are not enough
  • Declare code-driven Shopify Storefront API requirements on a custom component when extra product data is needed

The Product Card Builder supports product metafields. Variant metafields are not available through builder fields and require code-driven Storefront GraphQL requirements inside a custom component.

Custom components are a good fit for advanced badges, quick views, wishlists, extra product metadata, or layouts that need custom JavaScript behavior. Adding a JavaScript file alone is not enough; merchants must also add a Custom component to the Product Card Builder layout. Custom component Product metafields are configured in the builder; custom GraphQL requirements live in the component code, not in Product Card Builder fields.


Use Layout Settings to choose whether product cards link to the selected variant or the main product page without a variant in the URL.


Good Practices

  • Keep image, title, and price above the fold on the card

  • Use consistent card heights to avoid uneven grids

  • Test customized layouts on search, collection, Dynamic Autocomplete, and standalone recommendation placements

  • Guard custom components for missing optional fields because search and recommendations may provide different product shapes

  • Fix data quality issues in imports first, then refine card design