Skip to main content
GabbyEsposito
Community Manager
Community Manager
September 30, 2026
F.A.Q.

Why are products blank, outdated, or wrong in my Klaviyo email?

  • September 30, 2026
  • 0 replies
  • 21 views

How to troubleshoot product blocks, feeds, dynamic tables, event data, and abandoned-cart products

If products are blank, outdated, or wrong in a Klaviyo email, first identify how those products are being added. A static product block, dynamic product feed, dynamic table, and event-driven abandoned-cart block use different data, and therefore break for different reasons.

If the content is blank only in preview, check the event you are previewing with before changing the template itself.

First: what kind of product content are you using?

Goal

Likely mechanism

Manually pick specific products

Static product block

Show personalized recommendations

Dynamic product block and product feed

Show items from a checkout or order event

Dynamic table block

Pull a specific event or catalog property

Dynamic variables or catalog data

Choosing the wrong mechanism is one of the most common reasons a message does not behave as expected.

Why are my products blank in preview?

For event-driven content, preview with the event that contains the product data. For example, an abandoned-cart message should be previewed with the relevant Started Checkout event.

If you preview a dynamic table with a profile or event that does not contain the expected product list, there may be no rows to display. Confirm the event first, then check the variable, row collection, and row alias.

Why aren’t my abandoned-cart products appearing?

A dynamic table needs a list of items from the triggering event.

For example, if the preview panel shows a product variable such as:

{{ event.extra.line_items.0.product.title }}

Use the repeating collection before the item number as the Row collection, such as:

event.extra.line_items

Then set the Row alias and use the alias in the table, such as:

{{ item.product.title }}

The exact event path depends on your integration and trigger event. Use the preview panel as the source of truth for the variables available in your message.

The wrong products are showing. What should I check?

Check:

  • Whether the block is static or dynamic
  • Which product feed is selected
  • Feed criteria and filters
  • Catalog availability and inventory
  • Product IDs and event data
  • Whether the message is using a fallback recommendation
  • Whether the preview uses the correct profile or event

If you manually selected products for a future flow or scheduled campaign, the product details will not update dynamically at send time. Use a dynamic product feed when the content needs to update.

Why is everyone seeing the same recommendations?

Personalized recommendations may not be available for every recipient. When they are unavailable, Klaviyo can use the configured fallback recommender, such as best-selling or most-viewed products.

That fallback behavior can make multiple recipients see the same product. Check the product-feed configuration and the data available for the recipient before treating it as a rendering defect.

Why are old or out-of-stock products appearing?

Check the product’s catalog status, inventory, feed criteria, and integration sync. If you use Shopify and the catalog information is stale, use the appropriate catalog resync option for the affected item or page.

Why are images or prices wrong?

Confirm that the product data in the catalog or triggering event contains the expected image, title, price, and product identifier. Then check whether the message is using catalog data, event data, or a fallback recommendation.

Preview using a profile or event that contains the product data you want to test. If the source data is wrong, changing the email block will not fix it.

It works in preview but not in the delivered email. What should I do?

Send a test using the same message type and data source, then check the delivered message. For a flow message, confirm that the live recipient receives the expected triggering event and that the product is still eligible at send time.

Capture the profile, event, product ID, feed name, and delivered-message timestamp before asking for help.

Related Help Center guidance