Why does my Klaviyo order email omit products or repeat the same item in every row?

Locate the real collection before changing the design

Klaviyo's dynamic table requires a consistently structured nested list. Row collection identifies that list; Row alias supplies a shorthand used throughout the repeated content. The documentation recommends existing default flow-library blocks for standard ecommerce integrations rather than rebuilding their dynamic tables.

Start with the order represented by the selected preview event. Compare its distinct line entries with the intended email rows. Do not infer the collection from a product name visible in the editor: that name might be one indexed entry, a separate field, or an unrelated catalog selection.

Also distinguish line entries from total units. Two units of the same mug need not mean two distinct product lines. Establish what the source actually contains before deciding that the email has lost an item or needs another manually duplicated row.

In the selected Table block, open Styles and choose Dynamic, set Row collection and Row alias, then return to Content to edit each cell. As a fictional field example only, a first-image reference event.products.0.imageURL can belong to a collection event.products and become item.imageURL when the alias is item. Copy your actual event structure; this example is not an account-independent tag.

The collection, alias and Dynamic controls are documented in How to use a table block in an email.

Illustrative exercise A: preserve a standard order block

A fictional store uses a standard integration and wants to restyle an existing placed-order flow. Its sample order contains a kettle and a filter pack. Begin with the appropriate default flow-library block and compare its collection and content references before changing colors or spacing.

If only the kettle appears, inspect whether the current block still points to the list or has been changed to a single entry. Compare the selected event with the intended order, too. Adding a fixed second product card could hide this example's omission while failing for the next customer's one-item or larger order.

Keep the purchase summary tied to its event. A best-selling-products feed may display attractive alternatives, but it cannot establish that the buyer ordered those products. Recommendations belong in a separately identified merchandising area.

Illustrative exercise B: repair a custom row's references

Another fictional store has custom event data. Its table produces three rows, but each shows the first item's photograph while the names change. Inspect each image and text reference rather than assuming the loop itself is broken.

Use the chosen alias across the row's image, name, price and variant information, preserving the actual child-field structure. The official examples use item as the alias; your source determines the remaining path. An image still pinned to entry zero would not express the intended row-relative selection.

Compare each completed row with its source entry, including the link destination where present. Three rows are not sufficient evidence if the second photograph belongs to the first product or a price is paired with the wrong variant.

Preview different order shapes with matching data

In Preview & test, select the relevant triggering event. Compare a one-line order with a multi-line order and inspect every displayed item relationship. These are proposed cases, not a claim that a preview has already passed.

When a discrepancy remains, return to the source list, alias or individual cell that explains it. Avoid replacing dynamic rows with a fixed number of cards merely to make one sample look complete.

No email was sent, platform account operated, event created or live template tested for these illustrative exercises. No Itemlume integration is claimed.

Once the order entries are correct, consult the mobile table layout guide for narrow-screen presentation; that is a separate task from proving what was purchased.

Illustrative exercise: standard flow block versus custom row-reference repair

These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.

Download review worksheet (CSV)