← All resourcesPlaybook

How to Show Live Prices and Discounts on Meta Catalog Ads

FeedForce Team · 5 min read
How to Show Live Prices and Discounts on Meta Catalog Ads

Catalog ads can stay connected to current inventory while still showing an outdated price inside the creative. The feed may tell Meta that an item now costs $79, but a static image exported last week can continue to display $99. That mismatch creates friction at the exact moment a shopper is deciding whether to click.

Live price and discount overlays solve this creative problem by turning feed values into visual elements. Instead of editing thousands of product images whenever a promotion changes, you define how prices should look and let automation apply the design to eligible SKU assets. The result is a catalog that can present current commercial information while keeping a consistent brand system.

Why static catalog creative goes stale

A static product image captures one moment. Prices, promotions, and availability keep moving after that image is exported. Seasonal campaigns may change weekly, markdowns can happen by category, and a single product can return to its regular price before the rest of a promotion ends.

The problem becomes larger at catalog scale. Manually updating 20 hero products may be realistic. Rebuilding images for 2,000 products, checking every price, and uploading them before the next feed refresh is not. Even a careful team can end up with inconsistent typography, missing sale treatments, or products that advertise a discount that no longer exists.

There is also a customer experience issue. If the creative says $49 and the landing page says $59, shoppers may distrust the offer or leave. If the creative shows no promotion while the product page has a meaningful discount, the ad may fail to communicate an important reason to visit. The goal is not to place more text on every image. It is to keep the message accurate and useful.

How dynamic price overlays use feed data

A dynamic overlay starts with structured product data. The regular amount usually comes from price, while a promotional amount comes from sale_price. An automation layer maps those fields into a branded layout and generates the appropriate visual for each product.

The logic should be explicit. If sale_price is present, valid, and lower than price, the creative can show a sale treatment. If it is missing or equal to the regular amount, the product should use the standard price layout. This avoids empty labels and false discount signals.

A useful workflow includes these steps:

  • Confirm that price and sale_price use consistent currency and formatting.
  • Define one standard-price state and one valid-sale state.
  • Set rules for products with missing or malformed values.
  • Apply brand colors, logo, type hierarchy, and spacing consistently.
  • Preview edge cases such as long prices and narrow product images.
  • Refresh assets when relevant feed values change.

FeedForce supports this design-system approach. A brand can establish its colors, logo, and layout once, then apply them across eligible products instead of treating every SKU as a separate design task.

Showing regular prices, sale prices, and savings

The simplest overlay shows one current price. It is compact, easy to scan, and useful when price is a strong purchase signal. During a promotion, however, showing both the previous and current values can make the offer easier to understand.

A common sale treatment displays price with a strikethrough and gives sale_price greater visual weight. Another option is a discount banner, such as a percentage or amount saved. Whichever format you choose, calculate it from clean feed values and use consistent rounding rules. A shopper should not see conflicting discount claims between the image, ad copy, and product page.

Visual restraint matters. The product should remain the focus, and the price must remain legible on different image backgrounds. A solid color container can improve contrast. A small badge can work for short discounts, while a longer message may need a dedicated band. Keep safe spacing around product details and avoid covering faces, key features, or variant information.

Rules that prevent misleading overlays

Automation is only as reliable as its conditions. Before enabling overlays across a whole catalog, decide how the system should handle unusual products and incomplete data.

Useful protections include suppressing the sale design when sale_price is not lower than price, excluding products with invalid values, and removing an expired discount as soon as the feed changes. You may also use availability to avoid preparing promotional creative for products that cannot be purchased.

Product-level exclusion rules add another layer of control. A team might exclude gift cards, bundles with variable pricing, low-quality images, or categories where a visible price is not appropriate. The point is to encode exceptions once, review them, and keep the catalog from publishing preventable errors.

What to test in Meta catalog campaigns

Price overlays are a creative variable, not an automatic improvement. Their value depends on the audience, product category, price position, and promotion. Test them against a clean control and keep other differences limited enough to interpret the outcome.

Start with a few practical comparisons: current price versus no price, current price plus strikethrough versus current price alone, a percentage badge versus an amount-saved badge, and bottom placement versus a corner badge. You can also compare stronger brand color with a quieter neutral treatment.

Evaluate more than click-through rate. Review conversion rate, revenue, ROAS, and product-level behavior. A treatment may help discounted items but add little for full-price products. Segmenting results by category, price range, or custom_label_0 can expose those differences. Allow enough time and volume for a fair comparison, and do not declare a winner from a handful of purchases.

A practical rollout process

Begin with feed quality. Check sample products, confirm currency conventions, and identify cases where sale_price is incomplete. Then create a small set of visual states rather than many one-off designs. Preview those states on products with light, dark, busy, and unusually cropped photography.

Launch on a controlled product group, monitor landing-page consistency, and inspect individual SKU outputs. Once the rules behave as intended, expand coverage and document who owns feed corrections, creative approval, and campaign evaluation. Agencies may also benefit from a client approval step before a new price treatment reaches the full catalog.

Live overlays work best when data rules, design rules, and review responsibilities are clear. If you want to explore the workflow without committing to a manual rebuild, FeedForce is one option for applying branded price and discount treatments at catalog scale, with a 14-day fully unlimited free trial.

Frequently asked questions

What is a price overlay in a Meta catalog ad?

It is a visual layer that places feed data, such as the current price or sale price, directly on each product image used in a catalog ad.

How does a dynamic price overlay stay current?

The creative system reads the latest values from fields such as `price` and `sale_price` whenever it generates or refreshes product assets.

Should every product show a discount banner?

No. A rule should show discount treatment only when a valid `sale_price` exists and is lower than the regular `price`.

What should brands test first?

Start with price visibility, discount format, badge placement, and a control version without an overlay, then compare results by product group.

Turn your feed into on-brand catalog ads.

Get Started
Contact me