Three Things Missing From Your Collection Page Product Cards

A collection page is where most of the buying decision actually happens. The customer scrolls a grid, compares eight things at a glance, taps one. Everything after that is mostly confirmation.

Yet the card doing that work is usually the least-considered component on the whole store. An image, a title, a price. Done.

"The card doing that work is usually the least-considered component on the whole store."

The annoying part is that the missing information nearly always exists already. It is on the product page one tap away, or sitting in a metafield an app populated months ago. It just never got surfaced where the comparison is happening. Three gaps come up in almost every audit we run.

The star rating you are already collecting

Shopify has a standard rating metafield. product.metafields.reviews.rating.value holds the average and reviews.rating_count.value holds the number of reviews.

• Judge.me and Okendo write directly to that native metafield.
• Loox and Yotpo run proprietary systems and need their own badge snippet instead.

Either way the number exists. The question is whether it renders on the card. In most themes the card markup lives in card-product.liquid or product-grid-item.liquid, and adding the rating is a few lines. Newer themes such as Horizon have a native review stars block you can add in the editor once you have told it which review app you use.

Without it, the customer either taps in to check and loses the grid, or does not check at all. Either way the 240 reviews you paid for stop influencing the decision at the moment it gets made.

One caveat. Set a minimum display threshold, something like five reviews, so a product with a single four-star review does not advertise how thin its coverage is.

Unit pricing

Per kilo, per 100ml, per serve, per wash. If you sell anything in more than one size, this is the number the customer is trying to work out in their head, and they will either do the maths badly or not at all.

Shopify has this built in and free on Online Store 2.0 themes. You set a quantity and a reference measurement on the variant, and the unit price then displays on the product page, collection pages, cart, checkout and the default order emails. No app required.

There is a compliance angle as well. The ACCC's Unit Pricing Code is mandatory for many grocery retailers and it applies online, not just in-store, with rules about which products are covered and how the price must be shown. If you sell food, pet food, cleaning or personal care, check whether the Code covers you before you file this under nice-to-have.

Where it does not apply, the commercial argument still holds. Unit pricing is what stops the larger pack looking expensive and starts it looking like value.

Price context behind the badge

A SALE flash on a card showing one price is decoration. There is nothing to compare it to, no saving stated, no reason to move.

The badge only works when compare-at price is populated on the variant, so the card can show both numbers and the theme can work out the actual saving. What we see often enough to call it a pattern: a sale badge fired by a tag or a promo app, with compare_at_price empty behind it. The badge appears, the price does not change, and customers quietly learn that your badges mean nothing.

While you are in there, count how many badges a single card can display at once. New, Bestseller, Low Stock, Sale, free shipping ribbon.

"Five badges is not five signals. It is noise, and it costs you the one badge that mattered."

Run this in two steps:

1. Open a collection page on your phone. Look at the first six cards and write down, for each one, everything a customer could learn about that product without tapping. If the honest answer is the image, the name and the price, then three fields' worth of decision-making information is sitting one level down doing nothing.
2. Then go and check the data behind it. Export your products and count how many have the rating metafield populated, how many have compare_at_price set, and how many variants carry a unit measurement.

At beCommerce, we audit exactly this gap between the data you're already collecting and what actually renders on the card. If you want a hand surfacing it, let's talk.