> For the complete documentation index, see [llms.txt](https://docs.platter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platter.com/smart-theme/smart-theme/products/product-cards.md). # Product Cards Navigate to `Theme Settings > Product Cards` or `Theme Settings > Article Cards` to adjust the level of information shown on your cards, such as toggling review star visibility. The changes made here will cascade throughout all card instances. ### Product Badges Product badges allow you to display 'Sale', percentage off, dollar amount off, or custom messaging. Product badges are managed within `Theme Settings > Product Card > Label` Click below for more detail on custom badges, including custom colors. {% content-ref url="/pages/EO0npaCiJ1Hqew6F2QIl" %} [Custom Product Badges](/smart-theme/smart-theme/products/product-cards/custom-product-badges.md) {% endcontent-ref %} ### Mockup {% embed url="" %} --- # 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.platter.com/smart-theme/smart-theme/products/product-cards.md?ask=&goal= ``` `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.