A product card has one job: help a shopper decide whether a product deserves a closer look. Good cards put the same facts in the same place across the grid: a representative image, a specific name, a visible price, a truthful sale state, and one clear route to the product page. Add a supporting line only when it changes the comparison. Then test the card with awkward real data (long names, missing images, sale and regular prices, narrow screens, keyboard focus), not with a perfect placeholder.

This guide covers product listings, not the product page itself. For how the product page should use those facts, see AI product page builders.

Start with the comparison shoppers are making

Before styling the card, name the decision it supports. A mug shopper compares capacity and material; a lamp shopper compares size and the direction of the light. That decision tells you whether the card needs one short supporting fact or whether image, title, and price are enough.

The catalog has to supply those facts consistently. Clean names, prices, and images come first; if those fields are uneven, start with the product and category preparation guide. Card design can’t repair a misleading title or an outdated price.

A practical product-card anatomy

┌──────────────────────────────┐
│                              │
│  1. PRODUCT IMAGE            │
│  consistent crop and ratio   │
│                              │
├──────────────────────────────┤
│  2. TRUTHFUL TITLE           │
│  Product type + distinction  │
│                              │
│  3. OPTIONAL DECISION FACT   │
│  e.g. 350 ml · stoneware     │
│                              │
│  4. PRICE / SALE STATE       │
│  current price; comparison   │
│  price only when valid       │
│                              │
│  5. ACTION PATH              │
│  Image/title → product       │
└──────────────────────────────┘
   6. Focus, hover, pressed,
      loading and error states

Use product images for recognition, not decoration

Choose the image that best shows what the shopper will evaluate next. Keep subject scale, background, and crop consistent enough that the differences in the grid belong to the products, not to the photography.

A shared aspect ratio stops the grid from jumping between tall and short cards. It doesn’t mean every object has to fill the frame the same way. Review the images as a set and fix crops that cut off a relevant part, make colors hard to judge, or suggest that accessories are included.

If an image is missing, the card should keep its shape and show a calm fallback rather than collapse. For shooting and cropping standards, see product images and brand assets.

Write a short, truthful title

A listing title should identify the product and show its most useful distinction. “Column table lamp — small” tells a shopper more than “The Column.”

  • Include the product type unless the category makes it obvious.
  • Add one factual differentiator when it prevents confusion: size, capacity, material, or another stable attribute.
  • Cut campaign language, repeated brand names, and adjectives that don’t help comparison.
  • Test the longest real title, not the average one. One long name shouldn’t break the row.
  • Limit the title to a set number of lines only after checking that similar products still look different.

If truncation hides the only word that tells two products apart, rewrite the title or allow another line. A neat grid isn’t worth making two products look identical.

Below the title, most compact grids need at most one short supporting line, and only when that fact changes the listing-level decision. Explanation, specifications, and persuasion belong on the product page. If a sentence applies equally to every product in the grid, put it above the grid instead. Check the result alongside your category-page design and the store’s colors, fonts, and spacing.

Make price and sale state unambiguous

Show the current selling price in the same position and format on every card. Don’t simplify a price in a way the card can’t support: the product page can explain complexity, but the card must not set a false expectation.

A sale is truthful only when both prices are valid right now. Emphasize the current price and keep the previous price readable but secondary. Never add a sale label, percentage, countdown, or urgency message because the design looks better with one.

Before you publish, look at three products side by side:

  1. one at its regular price;
  2. one with a sale price that is currently valid;
  3. the longest price format your store actually uses.

Check each value against the catalog.

Choose one predictable action

The safest baseline: the image and the title both lead to the product page. If the whole card is clickable, don’t nest other actions inside it, and make the focus outline show what will open.

A visible “View product” link helps when it isn’t obvious that the card is clickable; keep its label and destination the same everywhere. Add another control to the card only when it serves a real shopping task and you can test every state without making the card harder to read.

Design mobile and input states together

On a phone, the grid density you choose must keep the title and price readable, the image recognizable, and the link easy to tap. Nothing essential can depend on hover; a touchscreen has none.

Test one- and two-column layouts with real products, then work through the mobile e-commerce UX checklist for the rest of the path. Check orientation, enlarged text, slow-loading images, and long titles. Pick the density that keeps products comparable, not the one that fits the most on screen.

A keyboard user should be able to tab through the product links in a sensible order, see where focus is, open a link, and know where it leads. Make focus look different from the resting, hover, and pressed states. Write meaningful alt text when the image identifies the product, and skip alt text that only repeats the title next to it. Keep text and prices readable against their backgrounds.

Product-card state checklist

Test the card in a grid of representative products, not on its own.

StatePass whenMerchant check
DefaultImage, title, current price, and route onward are immediately clearFacts match the catalog
Long titleThe distinguishing words remain available and nearby cards stay readableUse the longest real names
Regular priceOne current price is visible in the expected formatCompare with cart and checkout
Truthful saleCurrent and previous prices have a clear relationshipConfirm the sale is active and valid
Missing/slow imageLayout remains stable and the product is still identifiableVerify the fallback with real records
HoverEmphasis does not reveal essential hidden informationTest with a pointer device
Keyboard focusFocus is visible, ordered logically, and identifies the actionNavigate without a mouse
Pressed/activationFeedback is clear and the expected product destination opensTest keyboard and touch activation
Narrow mobileImage, distinguishing title, price, and action remain usableTest representative phones
Text enlargementContent does not overlap, disappear, or become ambiguousRecheck the whole grid
Load/errorTemporary or failed content does not masquerade as a real price or productConfirm recovery and fallback behavior

Fix the card once, for the whole grid

Most of this checklist is about one thing: a card that works for the ideal product and breaks on the awkward one. The fix is to treat the card as one template applied to every product, then judge it on the worst cases.

That is how Setka, our product, builds product grids. It generates the card template as part of the store, in the same style as the rest of it, and applies it to every product in your grids. Your product images go into each card’s image slot, and the names and prices come from the same catalog that checkout charges from, so a card can’t show a price the cart won’t. When the longest title wraps badly, you open the page, describe the change, check the preview, and publish. The fix reaches every card, and there is no theme code to edit. To decide which products should sit together in the first place, see merchandising for a small catalog.

Start your store in Setka and open a grid with your most awkward products: the longest title, a regular price, a valid sale price, different image shapes, and one product without an image. Check it on a phone, with a keyboard, and against the catalog. Refine until the whole grid stays clear, then preview once more before you publish.