How Product Cards and “Get More Info” Work in Appifire Chat

You will understand how product cards work in Appifire AI Chat on the storefront, what View Product and Get More Info do, and how to test them after a catalog sync. When you finish, you can tell whether a weak card experience is a data issue, a publish-status issue, or expected behavior.

For which product fields feed answers, see How Appifire Uses Shopify Product Information to Answer Questions.

Direct answer

When the assistant recommends products, Appifire can show a horizontal row of product cards under the bot message. Each card can show image, title, and price, with two buttons: View Product (opens the PDP) and Get More Info (asks a follow-up focused on that exact SKU). Cards appear for up to 6 published, active products whose exact catalog titles appear in the reply. There is no add-to-cart button on cards today.

Prerequisites

• Appifire installed and the storefront widget visible (Getting Started)
• At least one product sync completed (images need sync too for thumbnails)
• Products active and published to the online store
• Exact product titles you can type in a test question
• Optional: open chat on a PDP to see page-product context vs Get More Info focus

What shoppers see

Under a recommendation-style reply, cards can include:

Element	Behavior
Image	Featured image from sync when available; otherwise a placeholder
Title	Catalog product title
Price	Formatted in the shop’s currency when available
View Product	Opens the product page URL in a new tab
Get More Info	Sends a follow-up message about that product and focuses retrieval on it

The message text still keeps names and prices. When cards are present, Appifire cleans the reply so shoppers rely on cards for links: tags, product type/category lines, and product URLs in the text are removed or simplified.

How cards are chosen (current rules)

Cards are built from the assistant reply text, not from a random grab of RAG chunks alone.

1. Appifire looks for exact catalog titles (and related title/price patterns) in the reply.
2. Titles must match published, active products that have a storefront URL.
3. Draft, archived, or unpublished products do not get cards. Zero inventory is OK if the product stays published.
4. Matching is strict: a shared prefix without the full title does not pull sibling products.
5. Up to 6 cards, ordered by first mention in the reply.

So if chat never names the exact title, you may get a text answer without cards. If the title is wrong or the product is draft, you will not get a card for that SKU.

What “Get More Info” does

When a shopper taps Get More Info on a card:

1. The widget sends a user-visible message like: Tell me more about "Exact Product Title" (exact title in quotes).
2. The request also includes a focus product payload (productId, title, url, handle).
3. For that turn, focus product takes priority over normal PDP page context.
4. Appifire loads that product’s knowledge first and answers about that SKU.

Use this when a recommendation list is broad and the shopper wants depth on one item without leaving chat.

What “View Product” does

View Product opens the storefront PDP URL in a new browser tab. It does not add the item to cart and does not change the chat thread by itself.

PDP context vs card focus

Context	When it applies	Effect
Page product	Shopper is chatting on a product page	Requests can include the current PDP product to boost that SKU’s context
Focus product	Shopper taps Get More Info on a card	One-shot focus for that message; overrides page product for that turn

How to test on your store

1. Pick two published products with clear, distinct titles and images.
2. Open the storefront chat (home or collection is fine).
3. Ask for a comparison or recommendation that should name both exact titles.
4. Confirm cards appear (up to 6) with title and price.
5. Tap View Product and confirm the correct PDP opens.
6. Tap Get More Info on one card and confirm the follow-up is about that same title.
7. Repeat with a draft product title in your question: it should not appear as a card.
8. After bulk image or title edits, run Data Sync products if cards look stale (catalog change guide).

Quick pass/fail

Result	Meaning
Cards show correct PDPs	Happy path
Text answer, no cards	Reply may not include exact catalog titles, or sync/images incomplete
Wrong sibling card	Title match too loose on your side; use full distinct titles in Admin
Old image on card	Re-sync products so featured images refresh
Get More Info talks about another SKU	Capture timestamp + titles; treat as a defect and use the troubleshooting playbook

Limits and non-goals

• No add to cart from product cards today.
• No cards for draft/unpublished products.
• Cards need exact title presence in the reply; fuzzy “the blue one” alone is not enough.
• Metafield-only facts that never appear in synced product text still will not appear in Get More Info answers.
• Product cards are not a substitute for clear PDP copy (product page checklist).
• Screenshots of the card UI may be added to this guide later; behavior above matches current product docs.

Related Appifire guides

• How Appifire Uses Shopify Product Information to Answer Questions
• How to Improve Product and Order Answers in Appifire AI Chat
• Getting Started With Appifire AI Chat
• Appifire Installation and Setup Checklist
• How to Keep AI Product Answers Accurate When Catalog Details Change

Last verified

2026-09-05 against Appifire product-card docs (card criteria, View Product, Get More Info / focusProduct, reply cleanup, max 6 cards, published/active only). Re-check the live widget after app updates; button labels should match the storefront.

Next action

On a preview or live theme, ask for two published products by exact title. Confirm cards, View Product, and Get More Info for one SKU. If cards never appear, fix titles/publish status and re-sync before changing Appearance settings.