> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/rules-and-customizations/product-card-customizations.md).

# Product Card Customizations

Product cards are the tiles a customer sees when choosing a plan or add-on in a journey or storefront — the icon or image, title, description, price, billing period, and the select action that adds the plan to their order. In PeakCommerce these cards are **components**, so you customize *how they look and behave* without editing HTML templates.

## Why customize them

A product card is the moment of choice in a buying flow. Tailoring it lets you match your brand, surface the right details (feature highlights, pricing framing, the billing cycle), and steer the action — whether selecting the card links onward to the next step or adds the plan straight to the cart.

## Key fields

You configure a Product Card component through its content fields, including:

* **Name** and **Description** — the plan's title and supporting copy.
* **Price** and **Period** — the displayed amount and billing cycle (for example `$29` and `/mo`).
* **Image** — an icon or product image.
* **Button text** and **Button action** — the label, plus whether the action is **Link / Navigate** or **Add to Cart**, with an optional **Button link URL**.

## How to use

Build or adjust a product-card component in the [Component Library](/product/using-peakcommerce/templates.md) (**Content → Component Library**), then place it on your checkout or storefront pages. Because the card is a reusable component, edits propagate everywhere it's used.

**Gotcha:** the price and period shown on a card are configured as content — confirm they reflect the live plan so the displayed amount and the order total stay consistent.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/rules-and-customizations/product-card-customizations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.