Klaviyo Product Prices: Review the Final Email

A product email can look finished while showing yesterday’s price. Start in Migma with the message, design, and approved offer, then review the populated Klaviyo block before releasing the campaign. The important question is where that number came from and when it will be resolved.

This guide is published by Migma for ecommerce teams preparing creative in Migma and sending through Klaviyo. It explains a review workflow, rather than comparing complete sending platforms. Product behavior was checked against official documentation on October 27, 2026. No design tool can establish that a catalog price is commercially correct without the store owner’s source of truth.

Capture the mismatch before changing the design

Pick one affected product and record the email’s displayed price, currency, product name, destination URL, and preview profile. Compare those with the intended storefront and the offer approved for this campaign. Note whether the email is a scheduled campaign or a flow that may run long after its template was created.

Do not begin by replacing every price with a manually typed number. That can hide the cause and create another version to maintain. First decide whether the discrepancy belongs to the creative, the catalog data, or the block’s configuration.

For example, imagine a fictional store reducing a sweater from £60 to £45. A draft approved last week still shows £60. The designer needs to know whether that amount is fixed copy, a manually chosen product detail, or a field resolved from a feed. Each requires a different correction. These sample prices illustrate the investigation; they are not a reported customer result.

Understand which product details can change

Klaviyo’s product block documentation distinguishes static blocks, where you select products, from dynamic blocks, where a feed determines the products shown.

The distinction matters for a later send. According to the current guide, details in manually selected products do not update dynamically at send time when Localize for recipient is off. Klaviyo recommends a feed containing the selected items with a dynamic block when those catalog details need to stay current. Localized catalogs introduce another supported path: eligible static blocks can localize product information at send time.

That does not mean every old price is a static-block problem. An outdated catalog, wrong field, or manually written headline may produce a similar symptom. Identify the source before selecting a fix.

Also distinguish an editor placeholder from a populated preview. Klaviyo says dynamic blocks show placeholder items during editing. Review real products using an email preview and a selected profile. A reassuring screenshot of placeholder content is insufficient evidence for the campaign.

Build a small price review sheet

Use Migma to prepare a clear product section and keep the approved wording together. Migma’s editable email workflow lets a team review text, links, buttons, and layout before exporting. Keep verified product facts in the brief so a design revision does not accidentally change the offer.

Create one row per test case with these fields:

• Expected product and destination storefront.
• Approved current price and currency.
• Whether an original price should appear.
• Catalog or other source used by the final block.
• Preview profile and market.
• Observed result, reviewer, and review time.

Include a full-price item, a sale item, and an item whose details recently changed. If the campaign serves multiple markets, add a relevant profile for each market. The sheet is a compact acceptance record, not a claim that a handful of previews covers every recipient.

Ask the commerce owner to approve the expected values. Designers should not infer tax treatment, currency conversion, or promotion eligibility from a visual mockup.

Review original prices and localized fallbacks

A crossed-out price is another factual claim. Klaviyo’s guide describes Original price for sale products in the block’s Styles settings. For supported dynamic catalogs, Klaviyo fills that value from the catalog when available. Static blocks also allow editing the original-price field.

Check both amounts and the surrounding wording. A correct current price beside an incorrect original price still creates a misleading offer. If you write a percentage saving into a headline or button, review that separate claim too. Do not assume it follows the product block’s logic.

For localized catalogs with Shopify Markets, the documentation describes a Localize for recipient option in eligible static blocks. When enabled, pricing, currency, and product information can follow the recipient’s language and region. Missing locale or localized product data invokes documented fallback behavior, potentially ending with the base catalog.

Test a profile with complete locale data and one without it. Record which fallback appears. Replacing a currency symbol manually does not prove the underlying numeric price is correct for that market.

Check the final email in its sending platform

Run Migma Email Preflight on the reviewed creative. It checks inbox previews, links, writing, and common sending risks. Fix relevant findings and rerun after changes. Preflight cannot approve your merchandise prices or promise inbox placement.

After handoff, review the populated email in Klaviyo. Confirm that any dynamic product logic remains in the intended sending-platform block. Do not assume exporting a Migma design creates or preserves every catalog lookup automatically. Klaviyo’s standard product blocks do not accept custom HTML; the help guide points to hybrid templates for combining a standard block with a custom HTML email.

Open each product link and compare the destination product, market, and visible offer. Review the sale item’s image and name as well as the numbers. A correct price beside the wrong variant or destination can still mislead the reader.

Keep sending tests and campaign activation with the authorized campaign owner. Document what was previewed and what remains uncertain before approving release.

Keep the correction from becoming another hidden version

When the issue is fixed, update the accepted brief in Migma and record the final platform configuration. Keep the review timestamp close to launch if prices are changing quickly. A later campaign copied from this template needs another data review, even if its layout is unchanged.

The useful outcome is a traceable agreement: this creative communicates this approved offer, the final product block uses this source, and these profiles produced the expected result. Start your next draft in Migma with those facts attached, then verify the populated email where it will actually be sent.

Frequently Asked Questions